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

stale statistics or whats the difference?

P: n/a
Hello Folks,

i've got two structural identical tables (including tablespace and indexes)
with identical data, on which the access path of an SQL is differs. But I
don't see a reason for the different behaviour.

Both tables are allocated in the same database and storage space and use the
same buffer pool. The DB2 subsystem is Version7.1 on z/OS. On both tables
I've run REORG with standard statistics.
I've checked for stale statistics with the following selects on the system
tables and found difference and no stale entries.

The only difference between the tables I know are:
- prefix of the table and index names
- creation date.

Does anybody have an idea what I could have missed?

Thanks in advance,

Ulrike

----

SELECT * FROM SYSIBM.SYSTABLES
WHERE NAME = 'S55RARCB'
AND CREATOR = 'D$TS55T7'
;
SELECT * FROM SYSIBM.SYSTABLESPACE
WHERE NAME = 'S55AARCB'
AND CREATOR = 'D$TS55T7'
;
SELECT * FROM SYSIBM.SYSCOLUMNS
WHERE TBNAME = 'S55RARCB'
AND TBCREATOR = 'D$TS55T7'
ORDER BY TBNAME, COLNO
;
SELECT * FROM SYSIBM.SYSCOLDIST
WHERE TBNAME = 'S55RARCB'
AND TBOWNER ='D$TS55T7'
-- AND TYPE = 'C'
;
-- NUR PARTITIONIERTE:
SELECT * FROM SYSIBM.SYSCOLSTATS
WHERE TBNAME = 'S55RARCB'
;
-- NUR PARTITIONIERTE:
SELECT * FROM SYSIBM.SYSCOLDISTSTATS
WHERE TBNAME = 'S55RARCB'
;
-- NUR PARTITIONIERTE:
SELECT * FROM SYSIBM.SYSINDEXSTATS
WHERE NAME LIKE 'S55IARCB%'
;
SELECT * FROM SYSIBM.SYSINDEXES
WHERE TBNAME = 'S55RARCB'
AND TBCREATOR = 'D$TS55T7'
;
SELECT * FROM SYSIBM.SYSINDEXPART
WHERE IXNAME LIKE 'S55IARCB%'
AND IXCREATOR = 'D$TS55T7'
;
Oct 5 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"Ulrike Klusik" <kl****@mathematik.uni-marburg.dewrote in message
news:eg**********@news.sdm.de...
Hello Folks,

i've got two structural identical tables (including tablespace and
indexes) with identical data, on which the access path of an SQL is
differs. But I don't see a reason for the different behaviour.

Both tables are allocated in the same database and storage space and use
the same buffer pool. The DB2 subsystem is Version7.1 on z/OS. On both
tables I've run REORG with standard statistics.
I've checked for stale statistics with the following selects on the system
tables and found difference and no stale entries.

The only difference between the tables I know are:
- prefix of the table and index names
- creation date.

Does anybody have an idea what I could have missed?

Thanks in advance,

Ulrike
If you program uses embedded static SQL such as would likely occur in a
COBOL or PL/I program, you need to rebind the plan or package (whichever
applies).
Oct 6 '06 #2

P: n/a
Hello Mark,

I've been using EXPLAIN SQL.

In the meantime my problem vanished in such a way, that I have now on both
tables the bad access path :-(
But I found no update the table stats!

Best wishes,
Ulrike

"Mark A" <no****@nowhere.comschrieb im Newsbeitrag
news:v8******************************@comcast.com. ..
"Ulrike Klusik" <kl****@mathematik.uni-marburg.dewrote in message
news:eg**********@news.sdm.de...
>Hello Folks,

i've got two structural identical tables (including tablespace and
indexes) with identical data, on which the access path of an SQL is
differs. But I don't see a reason for the different behaviour.

Both tables are allocated in the same database and storage space and use
the same buffer pool. The DB2 subsystem is Version7.1 on z/OS. On both
tables I've run REORG with standard statistics.
I've checked for stale statistics with the following selects on the
system tables and found difference and no stale entries.

The only difference between the tables I know are:
- prefix of the table and index names
- creation date.

Does anybody have an idea what I could have missed?

Thanks in advance,

Ulrike

If you program uses embedded static SQL such as would likely occur in a
COBOL or PL/I program, you need to rebind the plan or package (whichever
applies).


Oct 13 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.