DB2MEMMAXFREE = 8192000 Without the DB2MEMDISCLAIM, DB2 will not make a proper effort to release private memory when it is finished with it. The number of connections into DB2 would also have some bearing on memory consumed by the DB2 instance. An easy rule of thumb is 1MB per connection. You should run the "db2set" command to verify if the AIX environment variables are set and if not, use "db2set DB2MEMDISCLAIM=YES" and "db2set DB2MEMMAXFREE=8192000" commands to properly set them. And, I'd also like to see 20GB of paging space allocated for the operating system. If this is a data warehouse database with a small number of concurrently executing connections, he could also try using INTRA_PARALLEL=ON which would cause DB2 to do shared memory sorts and exploit CPU parallelism. But, turning this on should be done with great care and in conservative increments to the DFT_DEGREE of parallelism.
Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .VO7aaqqaAFk.0@/search390>discussion forums.
Dig Deeper on IBM DB2 management
Related Q&A from Craig S. Mullins
To export data from a DB2 table to a flat file, you need to run an export specifying the proper file format. The export utility exports data from a ... Continue Reading
Craig Mullins recommends two specific resources for learning how to create and support Binary Large Objects (BLOB) in DB2. Continue Reading
Craig Mullins explains various definitions of a data mart and sheds some light on the complexity of its relation to a data warehouse. Continue Reading