Try a schema check as follows: Set mess on Set err mess on Con DB User owner if applicable Output db.str Unload structure Output screen Discon Ren db to dborig Trace db.str
Often this yields errors that were the result of a corrupt sys_indexes table. If db.str is too big to trace, edit it in a large file editor and break it down into db.tab, the create tables commands, db.vew, the create views commands, db.alt, the alter table commands, and db.end, the rest of the file. Run db.tab to get the tables build, then trace db.alt and again look for errors. Also on the affected tables, compare the values for row counts by doing list table tablename and seeing the row count at the end of the list, and then do select count(*) from tablename for the same table and see if the two counts are equal, if not, you have some index corruption on that table. In 6.5++, you only need to do pack index indexname for selected indexes on the table (while in multi user if you wish) and the problem is often corrected. Harlan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of J. Stephen Wills Sent: Monday, August 26, 2002 10:01 AM To: [EMAIL PROTECTED] Subject: Re: Insert Problem Paul, one thing I forgot. Sometimes I do a PACK prior to the LOAD/INSERT. Unfortunately, based on some recent threads, I can't tell you which PACK-variant is best (SCHEMA/KEYS/ALL), but I'm sure someone else here can. Later, Steve in Memphis ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, August 24, 2002 9:45 PM Subject: Insert Problem > > > I am having a problem with a 4.5++ database when doing inserts to tables. > It started with workstation lock ups when inserting rows using "insert into > ... select ...". Now when I am running an old program that inserts rows into > a table, the process has slowed considerably. I recently did a pack and > reload without a problem. However, there are several tables containing > nearly a million rows and one with nearly 2.5 million rows. Any ideas? > > Paul Hill > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
