Hello,
My system info:
$ db2licm -l
Product name: "DB2 Enterprise Server Edition"
License type: "License not registered"
Expiry date: "License not registered"
Product identifier: "db2ese"
Version information: "9.5"

$ db2level
DB21085I Instance "db2inst" uses "64" bits and DB2 code release "SQL09050"
with level identifier "03010107".
Informational tokens are "DB2 v9.5.0.0", "s071001", "AIX6495", and Fix Pack
"0".
Product is installed at "/opt/IBM/db2/V9.5".


We recently upgraded from DB2 v8 (I believe). Now it appears that there is a memory leak in the db2sysc process. Here is a chart of the memory usage of the machine over the past 2 weeks:


The red line is ram and the black line is paging space.
As of when that chart was copied the db2sysc process was using around 31.5 gb and continuing to slowing climb.


In moving to the new version of DB2 I basically followed a recipe for configuring the database. I'm afraid I have some configuration problem that is resulting in this issue. Nothing has changed in the underlying code. That's not to say there isn't some bug in there that was just masked in the older DB2 version. Are there any configs that could result in this type of behavior? I'm very green in playing db admin to db2 (obviously ).
Thanks for reading

Give me a break. FP0 more than 18 months old. At a minimum you should have FP3a, but FP4 is now available from the FTP site (may not be available from the IBM fixpack webpage yet).

Here is the FTP site:
ftp://ftp.software.ibm.com/ps/produc...k/FP4_U825478/

There are some memory leak APARs, IZ35230 is HIPER (high impact). It's first fixed in v9.5 fp3: IBM - IZ35230: THERE IS A PERVASIVE UNIX-SPECIFIC PRIVATE MEMORY LEAK IN THE SECURITY COMPONENT.

So, please follow Marcus's advice and upgrade.