Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 3 of 3 total |
Indexes do not match record data and are invalid... |
Thu, Jun 23 2011 5:13 AM | Permanent Link |
Luis Conception Gonzalez | Hi!
I'm using DBISAM 4.30 Build 5 I have noticed that I'm getting a weird warning when verifying/repairing some tables with indexes. I have rebuild the indexes, repaired, etc... and that's what is happening: 1) After rebuilding indexes, I recreate the indexes 'manually' 2) After creating the indexes, I verify the table and the warning appears again. So I created the indexes 'one by one' to see which of them is the invalid one... AND... If I add a text index (single string field), then the warning appears. The table field is a CHAR(255) field. It seems not to be damaged data on the table. I can open the table, navigate, etc... with no problem. There are no more than 100 records. I can EVEN order the table by this field!!!! Is it really a damaged table or data? Thanks! |
Thu, Jun 23 2011 5:21 AM | Permanent Link |
Luis Conception Gonzalez | Hi again...
I have tried the following... 1) Changed the index 'Compression' property from None to Full. 2) Verified the table. No errors!!! 3) Changed again the index compression from Full to None. 4) Verified the table. No errors!!! Does this have any sense? What index compression should I use for this kind of fields? "Luis Conception Gonzalez" escribió en el mensaje de noticias:F0201348-D63A-4DC7-8F1A-8FE6668177BF@news.elevatesoft.com... Hi! I'm using DBISAM 4.30 Build 5 I have noticed that I'm getting a weird warning when verifying/repairing some tables with indexes. I have rebuild the indexes, repaired, etc... and that's what is happening: 1) After rebuilding indexes, I recreate the indexes 'manually' 2) After creating the indexes, I verify the table and the warning appears again. So I created the indexes 'one by one' to see which of them is the invalid one... AND... If I add a text index (single string field), then the warning appears. The table field is a CHAR(255) field. It seems not to be damaged data on the table. I can open the table, navigate, etc... with no problem. There are no more than 100 records. I can EVEN order the table by this field!!!! Is it really a damaged table or data? Thanks! |
Mon, Jun 27 2011 4:52 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Luis,
Per email: this issue was caused by the same bug that caused this: http://www.elevatesoft.com/incident?action=viewrep&category=dbisam&release=4.30&incident=3461 and has been fixed in 4.30 B6. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, September 17, 2024 at 04:19 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |