By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,590 Members | 2,191 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,590 IT Pros & Developers. It's quick & easy.

SYSIBM.SQLSTATISTICS

P: n/a
We have a number of client installations where dynamic sql snapshots
show that:

CALL SYSIBM.SQLSTATISTICS(?,?,?,?,?,?)

is the top consumer of CPU, usually by a wide margin. We regularly do
runstats/rebind on SYSIBM.*, like this:

DB2 -x "SELECT 'RUNSTATS ON TABLE SYSIBM.'||TABNAME||' WITH
DISTRIBUTION AND DETAILED INDEXES ALL SHRLEVEL CHANGE' FROM
SYSCAT.TABLES WHERE TABSCHEMA = 'SYSIBM' AND TYPE='T'" .
\RUNSTATS.SQL

DB2 -o -v -f .\RUNSTATS.SQL -z .\RUNSTATS.LOG

DB2 -x "SELECT 'REBIND NULLID.'||PKGNAME FROM SYSCAT.PACKAGES WHERE
PKGSCHEMA = 'NULLID'" .\REBIND.SQL

DB2 -o -v -f .\REBIND.SQL -z .\REBIND.LOG

Does the fact that this is so expensive -- 490 executions consumed 39
seconds of user CPU time -- indicate that something else is wrong?

Oct 27 '07 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.