IDS 9.4

=============== HELP ===================== Hi Everyone, While loading the load file to the database I am getting the following response.Can please tell me what it is and how to fix this issue. I am a new user of informix. Thanks & regards 271: Could not insert new row into the table. 103: ISAM error:illegal key descriptor (too many parts or too long).

More than likely, one or more indices on that table are corrupted. You need to perform oncheck -cIx on the table in question. Take care. Clifton M. Bean Informix DBA / AIX System Admin Currency Technics & Metrics Phone: (972) 812-1411 x244 -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of SYED ALI Sent: Saturday, July 28, 2007 4:16 AM To: ids@iiug.org Subject: IDS 9.4 [9631] =============== HELP ===================== Hi Everyone, While loading the load file to the database I am getting the following response.Can please tell me what it is and how to fix this issue. I am a new user of informix. Thanks & regards 271: Could not insert new row into the table. 103: ISAM error:illegal key descriptor (too many parts or too long). **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.

Dear Mr. Clifton, I have checked the table with oncheck -cIx and the following is the response, which is repeated many times. Validating indexes for baj:swx.log_record... Index dev_pri_tran Index fragment in DBspace bajdbs Index duptran Index fragment in DBspace bajdbs Index isoauth_id Index fragment in DBspace bajdbs ERROR: Bad key information in TBLspace description. ERROR: Index isoauth_id for baj:swx.log_record is bad. Index ix172_30 Index fragment in DBspace bajdbs ERROR:No btree item exists for data row. Fragid 0x2001b5 Rowid 0x5cedc301 contains key value: Key: "ANDC": Index ix172_33 Index fragment in DBspace bajdbs I shall really be gratful if you can suggest someting to fix this. regards

Sorry, I went to sleep after sending the response. The oncheck should have asked you if you wanted to repair any bad indices or tables it found. Did it? Now that you know there are errors, it is probably best to bring down the engine to quiescent mode and run the oncheck -cDI command on either the tables in question or, if you have not done so in a while and have the time available, run the command on the entire database -- and on any other databases within the instance. Take care. Clifton M. Bean Informix DBA / AIX System Admin Currency Technics & Metrics Phone: (972) 812-1411 x244 -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of SYED ALI Sent: Saturday, July 28, 2007 8:05 AM To: ids@iiug.org Subject: Re: RE: IDS 9.4 [9633] Dear Mr. Clifton, I have checked the table with oncheck -cIx and the following is the response, which is repeated many times. Validating indexes for baj:swx.log_record... Index dev_pri_tran Index fragment in DBspace bajdbs Index duptran Index fragment in DBspace bajdbs Index isoauth_id Index fragment in DBspace bajdbs ERROR: Bad key information in TBLspace description. ERROR: Index isoauth_id for baj:swx.log_record is bad. Index ix172_30 Index fragment in DBspace bajdbs ERROR:No btree item exists for data row. Fragid 0x2001b5 Rowid 0x5cedc301 contains key value: Key: "ANDC": Index ix172_33 Index fragment in DBspace bajdbs I shall really be gratful if you can suggest someting to fix this. regards **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.

Dear Mr. Clifton, I sincerely wish to Thank you for your support. Yes, oncheck displayed the msg at the end of the scan, that there are bad indices, and it suggested to drop and recreate the indexes. We have droped and recreated the indexes and it is working fine. I Thank you again. regards