Skip to main content

Private memory grows significantly while using PD_GET_DIAG_HIST table function.


Technote (FAQ)


Question

Why is a significant private memory growth upto 4 GB is observered when PD_GET_DIAG_HIST table function is used to monitor the diagnostic data

Answer

This is a current designed behavior of DB2 V10.1. The function uses upto 20% of instance memory which causes the private memory to grow significantly. You can filter things more specifically or use unions to fetch larger a quantities of data over multiple queries.

Alternatively you can use the following two work-arounds to restrict private memory growth.
1) Running multiply "select statement" with 1 day parameter.
So if you need record for 6 days, then you need to use 6 select statements.
2) Using the db2diag tool to filter the message in the db2diag.log.
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.trb.doc/doc/c0020701.html


Related information

PD_GET_DIAG_HIST table function

Rate this page:

(0 users)Average rating

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page:


(0 users)Average rating

Add comments

Document information

DB2 for Linux, UNIX and Windows


Software version:
10.1


Operating system(s):
AIX, Linux, Windows


Software edition:
Advanced Enterprise Server, Enterprise Server


Reference #:
1613707


Modified date:
2012-10-26

Translate my page

Content navigation