Oninit cdi / Archive
Talk to an expert →

Table size and extent mgmt.

Posted in 2011

Topics: Storage & Space Management

ANTONIO VARRICCHIO — — source: IIUG Forums & Mailing Lists

I have a table that is as follows; -------------------------------------------------------------------------------- Table Information -------------------------------------------------------------------------------- table name: rsddstataggrdef dbspace: psapstab rows: 12612601 fragmentation: none columns: 9 row size: 166 bytes locking mode: row first extent: 36 KB views: 0 next extent: 393216 KB indexes: 1 size: 4373308 KB extents: 196 (33 still available) fill level: 87 % s) Reorganize Indexes t) Reorganize Table u) New 'N. Extent'/'Lock Mode' What can be done to properly manage the next extent for this table. And how can I properly manage the remaining 33 extents. I am running SAP with Informix Dynamic Server Version 9.40.FC5XS. Thanks.

↪ replying to ANTONIO VARRICCHIO
Celso Cabral Coimbra — — source: IIUG Forums & Mailing Lists

Antonio, If I were you, I would reorganize the table fitting all records in the first extent of the table and a little bit bigger, like 4500000Kb for example, the next extent with some thing like 10% of first extent (like 500000kb). If you have many extents in a table or index cause performance issue. After that reorganize the index. Lock mode row avoid concurrency issues. Is a good practice. Regards, Celso Cabral Coimbra Administrador de Banco de Dados ClearTech Ltda "Trust at the heart of Communications" Tel. (11) 3576-4509 -----Mensagem original----- De: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] Em nome de ANTONIO VARRICCHIO Enviada em: quarta-feira, 9 de fevereiro de 2011 03:41 Para: ids@iiug.org Assunto: Table size and extent mgmt. [22726] I have a table that is as follows; -------------------------------------------------------------------------------- Table Information -------------------------------------------------------------------------------- table name: rsddstataggrdef dbspace: psapstab rows: 12612601 fragmentation: none columns: 9 row size: 166 bytes locking mode: row first extent: 36 KB views: 0 next extent: 393216 KB indexes: 1 size: 4373308 KB extents: 196 (33 still available) fill level: 87 % s) Reorganize Indexes t) Reorganize Table u) New 'N. Extent'/'Lock Mode' What can be done to properly manage the next extent for this table. And how can I properly manage the remaining 33 extents. I am running SAP with Informix Dynamic Server Version 9.40.FC5XS. Thanks. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

↪ replying to ANTONIO VARRICCHIO
Art Kagel — — source: IIUG Forums & Mailing Lists

As things stsnd, the remaining 33 extent have room for at least 160,000,000 rows unless you hit the 16,777,216 page limit for a single partition first. So, no worries. Art On Feb 8, 2011 11:41 PM, "ANTONIO VARRICCHIO" <antonio.varricchio@domtar.com> wrote: > I have a table that is as follows; > > > -------------------------------------------------------------------------------- > > Table Information > > -------------------------------------------------------------------------------- > > table name: rsddstataggrdef > > dbspace: psapstab rows: 12612601 > > fragmentation: none columns: 9 > > row size: 166 bytes > > locking mode: row > > first extent: 36 KB views: 0 > > next extent: 393216 KB indexes: 1 > > size: 4373308 KB > > extents: 196 (33 still available) fill level: 87 % > > s) Reorganize Indexes > t) Reorganize Table > u) New 'N. Extent'/'Lock Mode' > > What can be done to properly manage the next extent for this table. And how > can I properly manage the remaining 33 extents. I am running SAP with Informix > Dynamic Server Version 9.40.FC5XS. > > Thanks. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > --0015175ccf3a72f383049bd8ed6d

Glossary