![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 6 of 6 total |
![]() |
Thu, Feb 2 2006 5:01 AM | Permanent Link |
"Petter Topp" | Hello!
I have read in another thread how to handle a situation when the repair function will not solve a corrupt IDX file. Today we have had such a case, and running Dbsys repair fails with the message: DBISAM Engine Error # 9217 Error reading from the table or backup file 'xxxxx'. As far as I know the only solution now would be to delete the IDX file and recreate it with the proper indexes. Apparently this works in our case! So for the boneheads like me Tim, can you please spell it out, so that I can understand why this is a bad solution? Thanks Petter Topp ATC Data as DBISAM Ver. 4.19 |
Thu, Feb 2 2006 8:55 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Petter,
<< So for the boneheads like me Tim, can you please spell it out, so that I can understand why this is a bad solution? >> It's a bad solution because you're erasing the index definitions along with the data. If you can send me the table in question, I can make sure that the repair will handle the problem in the next build. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Feb 2 2006 9:58 AM | Permanent Link |
Sean McCall | Tim,
Just curious... is there a procedure/option anywhere that will allow us to completely replace the current indices with another set without first dropping the existing indices and that works even if the current indices are corrupt or missing/deleted? The purpose would be to handle corrupt indices in one shot or to update the index structure without worrying about what the existing indices are. Also, I seem to recall that if I drop all the indices a primary index will be created on the internal row id. Sean Tim Young [Elevate Software] wrote: > Petter, > > << So for the boneheads like me Tim, can you please spell it out, so that I > can understand why this is a bad solution? >> > > It's a bad solution because you're erasing the index definitions along with > the data. If you can send me the table in question, I can make sure that > the repair will handle the problem in the next build. > |
Fri, Feb 3 2006 3:21 AM | Permanent Link |
"Petter Topp" | Here it is.
Regards Petter Topp ATC Data as "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i melding news:00ADEBDB-12E2-4401-A205-ED27B1897B71@news.elevatesoft.com... > Petter, > > << So for the boneheads like me Tim, can you please spell it out, so that > I > can understand why this is a bad solution? >> > > It's a bad solution because you're erasing the index definitions along > with > the data. If you can send me the table in question, I can make sure that > the repair will handle the problem in the next build. > > -- > Tim Young > Elevate Software > www.elevatesoft.com > > Attachments: Ordre_defekt.idx Ordre_defekt.dat |
Fri, Feb 3 2006 5:20 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Sean,
<< Just curious... is there a procedure/option anywhere that will allow us to completely replace the current indices with another set without first dropping the existing indices and that works even if the current indices are corrupt or missing/deleted? The purpose would be to handle corrupt indices in one shot or to update the index structure without worrying about what the existing indices are. Also, I seem to recall that if I drop all the indices a primary index will be created on the internal row id. >> If you copy a new .IDX over the old .IDX and then call RepairTable, it will essentially do what you want. However, again, this is not recommended. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Feb 3 2006 5:20 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Petter,
<< Here it is. >> Thank you very much. I will make sure that it is corrected in the next build. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |