jun lopez
1st March 2004, 12:29
We are using BaaN 4c4/Informix 9.21
We have a major problem in reorganizing our finance table gld418, the actual capacity of gld418 is already reached to 2,880,469.92 GB, a total of 35,127,682 no. of records. Everytime we do a reorganization of table using session ttaad4225m000 we always encountering the error 520 which means "error during buffered updates", and when we look at our log file in Informix we also see an error of 1136 which means "No more extents", prior to the reorganization we adjusted our extent in our First and Next extent knowing that we only lack of extents when running the ttaad4225m000.
Value in our inf_storage:
tfgld418:888:T:group:1:10:INITIAL 187 NEXT 20 DBSPACE co888_418dbs LOCK row
tfgld418:888:I::1:10:INITIAL 227 NEXT 20 DBSPACE co888_418idx
Our question now is how are we going to reorganize the big table and how to eliminate the errors. You quick response is very much needed. Right now, we just simply revert back our original backup prior to the reorganization.
log.aad4225
Table M Reference Count More Info
----------- - -------------------- ------- -----------------------
Table D Old New Messages
----------- - -------- -------- ----------------------
tfgld418888 * 35013415 21294300 Commit error 520
Table M Reference Count More Info
----------- - -------------------- ------- -----------------------
We have a major problem in reorganizing our finance table gld418, the actual capacity of gld418 is already reached to 2,880,469.92 GB, a total of 35,127,682 no. of records. Everytime we do a reorganization of table using session ttaad4225m000 we always encountering the error 520 which means "error during buffered updates", and when we look at our log file in Informix we also see an error of 1136 which means "No more extents", prior to the reorganization we adjusted our extent in our First and Next extent knowing that we only lack of extents when running the ttaad4225m000.
Value in our inf_storage:
tfgld418:888:T:group:1:10:INITIAL 187 NEXT 20 DBSPACE co888_418dbs LOCK row
tfgld418:888:I::1:10:INITIAL 227 NEXT 20 DBSPACE co888_418idx
Our question now is how are we going to reorganize the big table and how to eliminate the errors. You quick response is very much needed. Right now, we just simply revert back our original backup prior to the reorganization.
log.aad4225
Table M Reference Count More Info
----------- - -------------------- ------- -----------------------
Table D Old New Messages
----------- - -------- -------- ----------------------
tfgld418888 * 35013415 21294300 Commit error 520
Table M Reference Count More Info
----------- - -------------------- ------- -----------------------