windows-1252?Q52=45=3A=20=77=69=6E=64=6F=77=73=2D=
Posted in 2007
Topics: Storage & Space Management, Migration, Import/Export & Data Conversion
#2 - rebuilding sysmaster - won't help at all.
Tables without special columns (AFAIK only sysindices is the only one that has
one special column) can have around 210 extents, so you may not be up against
the wall yet. A stopgap would be to increase the NEXT size for those catalog
tables to minimize the number of new extents.
In 9.2x your only recourse if it's getting close is to perform a dbexport -ss,
edit the schema file to add near the top of the file: ALTER TABLE NEXT SIZE
... for all system catalog tables that are currently in trouble so that
something like 1/4 of the current pages fit into a single extent, then
dbimport. In IDS 11.10 (Cheetah) you can set the default extent size of system
catalog tables that will be used when creating databases.
Art S. Kagel
----- Original Message -----
From: Ernest Knox <ids@iiug.org>
To: ids@iiug.org
At: 11/09 16:21:28
Question:
We have a system catalog tables (syscolumns, sysviews, and systabauth to name
a few...), that are currently (> 140) extents. Should we be concerned and
reduce their extents? If so, should we:
1. drop and re-create the application database(s) and export/import data
or
2. drop and re-create the sysmaster database using buildsmi on the sysmaster.
This is for version 9.2x and higher.
Thanks,
**************************************
Ernie Knox
Sears Holding Co.
IT Database Administrator Specialist
IT Service Management, Strategy & Architecture
3333 Beverly Rd., B4-266A
Hoffman Estates, IL. 60179
Office: (847) 286-5735
Fax: (847) 645-3874
Pager: (800) 759-8352 Pin#: 7271042
Email: eknox@sears.com
" It's always a great day to watch Football ! "
**************************************
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Hi Knox
I'd like to add more...If you do a dbexport / dbimpor is the best time to
redimension all extents (first and next) for each table.
The good idea is:
Create a dbspace with 1 chunk (or more) only to put a database.
That means you do not put any table in the same dbspace, someting like:
create database <db_name> in dbspacedb.
Alter the whoole file <db>.sql especifying another dbspace for each user table
before dbimport.
Run dbimport , and check extents.
As the indexes are created following tables in dbimport the catalog tables:
systables, sysindexes will be growing together. After, at the end of dbimport,
will be created the contraints and finaly stored procedures...
That means these tables will have only one extents for that.
Best regards. R Ferronato
> To: ids@iiug.org> From: kagel@bloomberg.net> Subject:
windows-1252?Q52=45=3A=20=77=69=6E=64=6F=77=73.... [10350]> Date: Mon, 12 Nov
2007 09:02:41 -0500> > #2 - rebuilding sysmaster - won't help at all. > >
Tables without special columns (AFAIK only sysindices is the only one that has
> one special column) can have around 210 extents, so you may not be up
against > the wall yet. A stopgap would be to increase the NEXT size for those
catalog > tables to minimize the number of new extents. > > In 9.2x your only
recourse if it's getting close is to perform a dbexport -ss, > edit the schema
file to add near the top of the file: ALTER TABLE NEXT SIZE > .... for all
system catalog tables that are currently in trouble so that > something like
1/4 of the current pages fit into a single extent, then > dbimport. In IDS
11.10 (Cheetah) you can set the default extent size of system > catalog tables
that will be used when creating databases. > > Art S. Kagel > > ----- Original
Message ----- > From: Ernest Knox <ids@iiug.org> > To: ids@iiug.org > At:
11/09 16:21:28 > > Question: > > We have a system catalog tables (syscolumns,
sysviews, and systabauth to name > a few...), that are currently (> 140)
extents. Should we be concerned and > reduce their extents? If so, should we:
> > 1. drop and re-create the application database(s) and export/import data >
> or > > 2. drop and re-create the sysmaster database using buildsmi on the
sysmaster. > > This is for version 9.2x and higher. > > Thanks, > >
************************************** > Ernie Knox > Sears Holding Co. > IT
Database Administrator Specialist > IT Service Management, Strategy &
Architecture > 3333 Beverly Rd., B4-266A > Hoffman Estates, IL. 60179 >
Office: (847) 286-5735 > Fax: (847) 645-3874 > Pager: (800) 759-8352 Pin#:
7271042 > Email: eknox@sears.com > > " It's always a great day to watch
Football ! " > **************************************
_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces.
It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=
en-us