Re: Can I alter the extent size of Sysprocedures?

NEXTSIZE can be changed, I've done it with no problems. The usual SQL works fine. The more interesting question is "are catalog tables subject to the same extent limits as garden variety user tables"?? If so, then jack up NEXTSIZE to make darn sure you never hit that limit (200ish or so...). Next time you do a dbexport/import, remember to ALTER the NEXTSIZE first thing in the schema file. Ive done that too and it works great. I wonder if you can "ALTER FRAGMENT ON TABLE SYSPROCEDURES INIT IN rootdbs?". I don't have a system handy I'm willing to try this on. As for number of extents and performance, Art is right on as usual in that caching makes it a non issue. Greg Art S. Kagel wrote: > > HARINATH VENKATA wrote: > > > > Hi > > > > The sysprocedure table has large number of extents. Can I alter the next > > extent size for sysprocedure table? > > You probably can but it is unneccessary and anyway you could not reorg > or defragment the table successfully. > > I say it is unneccessary because sysprocedures and sysprocbody data, > like all important catalog data, is cached in memory in a hashed cache > table separate from the normal data buffer pool. The default table is > large enough for about 50 active stored procedures and can be adjusted > by sites requiring the caching of larger numbers of procedures using > the PC_HASHSIZE and PC_POOLSIZE config parameters which are > undocumented. You can get specifics of permitted values (one of these > probably must be prime) from tech support. > > Art S. Kagel -- Greg Moye The above are my opinions only.