469,286 Members | 2,522 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,286 developers. It's quick & easy.

Growing SYSCATSPACE

hi,
the problem i am having is that the SYSCATSPACE of one of the
ODS's growing overnight. I am sure no new objects are being created.
What can be the cause of this? I am on db2udb for aix 8.2 fp 12. Please
let me kow if I need to be more specific

Aug 28 '06 #1
3 3238

Asphalt Blazer schrieb:
hi,
the problem i am having is that the SYSCATSPACE of one of the
ODS's growing overnight. I am sure no new objects are being created.
What can be the cause of this? I am on db2udb for aix 8.2 fp 12. Please
let me kow if I need to be more specific
One reason could be that a RUNSTATS WITH DISTRIBUTION was run for the
first time against all (or most) tables. This blows up system table
SYSCOLDIST (and others ...)

HTH
Joachim

Aug 28 '06 #2
I found some objects that were created unauthorized, i managed to drop
those objects but syscatspace has not gone down yet. Its at the same
level.
its not the problem with runstats, I have ascertained that.

Joachim Klassen wrote:
Asphalt Blazer schrieb:
hi,
the problem i am having is that the SYSCATSPACE of one of the
ODS's growing overnight. I am sure no new objects are being created.
What can be the cause of this? I am on db2udb for aix 8.2 fp 12. Please
let me kow if I need to be more specific

One reason could be that a RUNSTATS WITH DISTRIBUTION was run for the
first time against all (or most) tables. This blows up system table
SYSCOLDIST (and others ...)

HTH
Joachim
Aug 29 '06 #3

am******@gmail.com schrieb:
I found some objects that were created unauthorized, i managed to drop
those objects but syscatspace has not gone down yet. Its at the same
level.
its not the problem with runstats, I have ascertained that.

Joachim Klassen wrote:
Asphalt Blazer schrieb:
hi,
the problem i am having is that the SYSCATSPACE of one of the
ODS's growing overnight. I am sure no new objects are being created.
What can be the cause of this? I am on db2udb for aix 8.2 fp 12. Please
let me kow if I need to be more specific
One reason could be that a RUNSTATS WITH DISTRIBUTION was run for the
first time against all (or most) tables. This blows up system table
SYSCOLDIST (and others ...)

HTH
Joachim
AFAIK System tables behave like "normal" tables, means once they are
blown up they stay at that size until a reorg is done. Run runstats and
reorgchk on your system catalog to see which tables are overallocated
and reorg them.

HTH
Joachim

Aug 29 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

8 posts views Thread by Ryan R. Rosario | last post: by
3 posts views Thread by Esger Abbink | last post: by
41 posts views Thread by Nitin Bhardwaj | last post: by
4 posts views Thread by yashgt | last post: by
6 posts views Thread by Burkhard Schultheis | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.