Increasing virtual memory on AIX for large environments

Monitoring, Version 6.2

Increasing virtual memory on AIX for large environments

The Tivoli Enterprise Portal Server process (KfwServices) is linked with the default memory model, which allows for data and stack of only 256 MB. In large environments, this can cause the portal server to crash at startup. In smaller environments, this may not cause a problem at startup, but may at some later point as more virtual storage is required. The problem can be predicted if the topas command shows KfwServices with PgSp value of 180-250 MB. If a smaller environment is close to that value, it may occur when large queries are being handled. If the topas output shows that KfwServices is nearing these values, the memory model should be changed in smaller environments as well as large ones.

Changing the memory model requires that KfwServices load header be modified. Also, changes must be made to DB2 configuration changes. Complete the following steps to make these changes. These steps use the default directory. Use the directory locations appropriate to your system.

Important::

You must run the ldedit command below each time new Tivoli Enterprise Portal Server maintenance has been applied.

To make the required memory model and DB2 configuration changes:

Stop the Tivoli Enterprise Portal Server:

cd /opt/IBM/ITM/bin ./itmcmd agent stop cq

Issue the following commands:

cd /opt/IBM/ITM/aix533/cq/bin
cp KfwServices KfwServices.orig
 /usr/ccs/bin/ldedit -bmaxdata:0x80000000 KfwServices

To verify that the maxdata value has been set issue the following command:
```
dump -ov KfwServices
```
This will display the maxdata value in KfwServices. Maxdata should show as:
```
maxSTACK maxDATA SNbss magic modtype 0x00000000 0x80000000 0x0003 0x010b 1L
```
Issue the following command:
```
cd /opt/IBM/ITM/config
```
Using your preferred editor add the following line to cq.ini:
```
EXTSHM=ON
```
Using the db2 installation user ID (the default is db2inst1), make the DB2 configuration changes as follows:
1. Stop the DB2 server if not already stopped:
```
cd /db2inst1/sqllib/adm db2stop
```
2. Issue the following configuration changes:
```
export EXTSHM=ON 
db2set DB2ENVLIST=EXTSHM 
db2set -all
```
3. Using your preferred editor add the following lines to /db2inst1/sqllib/db2profile:
```
EXTSHM=ON 
export EXTSHM
```
4. Restart DB2:
```
cd /db2inst1/sqllib/adm db2start
```

Restart the TEPS:

cd /opt/IBM/ITM/bin ./itmcmd agent start cq

For more information about using the large and very large address-space models to accommodate programs requiring data areas that are larger than those provided by the default address-space model, see http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.genprogc/doc/genprogc/lrg_prg_support.htm. For more information about using the EXTSHM environment variable to increate the number of share memory segments to which a single process can be attached, see http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic.

Feedback

[ Top of Page | Previous Page | Next Page | Contents | Index ]