Re: systabauth fragmentation
Posted in 1993
Topics: Storage & Space Management, Connectivity: ESQL/C, 4GL & Embedded SQL, Migration, Import/Export & Data Conversion, Jobs, Consulting & Announcements
In article <16BFECD0D.CJSENFT@lexmark.com> CJSENFT@lexmark.com writes:
>In one of my databases the systabauth table is fragmented into 10
>segments. What's the best way to fix a system table when this happens.
>I usually unload the table, recreate it and reload. But, I'm afraid
>to try anything like this with a system table.
>
>Thanks,
>Cathy
>
I'm assuming your running under Informix-OnLine...
I've had this happen with 'syscolumns' before. When Informix
creates a database, all the system tables are created with
the default extent sizes (usually 8).
The best thing to do is alter the next extent size of the
'systabauth' table. Use either 'isql' or write a quick 4GL
program that executes the following SQL statement (su informix first):
alter table systabauth next size (100)
(I think the syntax is correct). The '100' is the extent
size Informix will use the next time it grabs an extent.
Feel free to change that number (the larger, the less number
of extents will be created). You might as well do 'syscolumns'
too.
Hope that helps!
- Dave
*--------------------------------------------------------------------------*
| (Doctor) David R. Gilbert (doc@balr.com) | "A shorter .sig file |
| Consultant - BALR Corporation - (708) 575-8200 | promotes health and |
| UUCP: ...uunet!balr.com!doc | happiness to all." |
| Snail: 600 Enterprise Dr, Oak Brook IL 60521 | - doc |
*==========================================================================*