Index dees not match the table, delete the index file and re-create

Index dees not match the table, delete the index file and re-create

Post by Jason Ta » Wed, 10 Mar 1999 04:00:00



Hi,
       When I encounter the problem stated in the title, I cannot open
the table.
        So, I delete the .cdx file. Then, however, VFP complained that
'Primary property is invalid'. Then the case becomes:
    Without opening the table, I cannot drop the primary key.
    Without dropping the primary key I cannot delete the .cdx file.
    Without deleting the .cdx file, I cannot open the table!
    What a deadlock!!!! :~
    Anybody can help me?

Thx for any help
Jason

 
 
 

Index dees not match the table, delete the index file and re-create

Post by Anders Altber » Wed, 10 Mar 1999 04:00:00


Keep a second index file Reserve.CDX at hand. It can be created against an
empty table but it contains exactly the same index keys and indextypes.
Erase the production cdx that is damaged and COPY FILE the backup index file
to take its place. You should now be able to open the table.
-Anders

>Hi,
>       When I encounter the problem stated in the title, I cannot open
>the table.
>        So, I delete the .cdx file. Then, however, VFP complained that
>'Primary property is invalid'. Then the case becomes:
>    Without opening the table, I cannot drop the primary key.
>    Without dropping the primary key I cannot delete the .cdx file.
>    Without deleting the .cdx file, I cannot open the table!
>    What a deadlock!!!! :~
>    Anybody can help me?

>Thx for any help
>Jason


 
 
 

Index dees not match the table, delete the index file and re-create

Post by Anders Altber » Wed, 10 Mar 1999 04:00:00


Keep a second index file Reserve.CDX at hand. It can be created against an
empty table but it contains exactly the same index keys and indextypes.
Erase the production cdx that is damaged and COPY FILE the backup index file
to take its place. You should now be able to open the table.
-Anders

>Hi,
>       When I encounter the problem stated in the title, I cannot open
>the table.
>        So, I delete the .cdx file. Then, however, VFP complained that
>'Primary property is invalid'. Then the case becomes:
>    Without opening the table, I cannot drop the primary key.
>    Without dropping the primary key I cannot delete the .cdx file.
>    Without deleting the .cdx file, I cannot open the table!
>    What a deadlock!!!! :~
>    Anybody can help me?

>Thx for any help
>Jason

 
 
 

Index dees not match the table, delete the index file and re-create

Post by Javier Schneider Torre » Wed, 10 Mar 1999 04:00:00


Use the Windows explorer to delete the cdx. You shouldn't have VFP loaded.
The load VFP, validate the database with the RECOVER clause, and then create
the indexes again.

HTH.
Javier Schneider.

Quote:>Hi,
>       When I encounter the problem stated in the title, I cannot open
>the table.
>        So, I delete the .cdx file. Then, however, VFP complained that
>'Primary property is invalid'. Then the case becomes:
>    Without opening the table, I cannot drop the primary key.
>    Without dropping the primary key I cannot delete the .cdx file.
>    Without deleting the .cdx file, I cannot open the table!
>    What a deadlock!!!! :~
>    Anybody can help me?

>Thx for any help
>Jason

 
 
 

Index dees not match the table, delete the index file and re-create

Post by Albert Bohlmeij » Thu, 11 Mar 1999 04:00:00


how about opening the database without index
set safety off
index on .............to
set safety on

you create a new index without any problem.
you can link it to the errormessage of corrupt index

On Tue, 9 Mar 1999 12:08:28 +0100, "Anders Altberg"


>Keep a second index file Reserve.CDX at hand. It can be created against an
>empty table but it contains exactly the same index keys and indextypes.
>Erase the production cdx that is damaged and COPY FILE the backup index file
>to take its place. You should now be able to open the table.
>-Anders


>>Hi,
>>       When I encounter the problem stated in the title, I cannot open
>>the table.
>>        So, I delete the .cdx file. Then, however, VFP complained that
>>'Primary property is invalid'. Then the case becomes:
>>    Without opening the table, I cannot drop the primary key.
>>    Without dropping the primary key I cannot delete the .cdx file.
>>    Without deleting the .cdx file, I cannot open the table!
>>    What a deadlock!!!! :~
>>    Anybody can help me?

>>Thx for any help
>>Jason

Albert Bohlmeijer
06900 Yan, Kedah MALAYSIA

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQBVAwUBNHqANMlbTSm9v83hAQETrAH+KHSeF/rTZN0+DZyPbqClDrklMDOomefg
/0Qcxi3r3EensOvNZZu12CcpTu5J3duV3jhzRQlUnU2kvHiSOkIJjw==
=Ntt5
-----END PGP SIGNATURE-----

 
 
 

1. Index does not match data file

I have been working with FoxPro for about 6 months, and following this
news group for about 4 months.  I have a problem that I really HOPE
someone out there can help with.

Working with FPW 2.6
As part of a Sales Account Tracking system, I have two extremely
involved forecasting reports which use forecast data plus backlog data
from the separate Sales Order system (also in FPW).  Each report is run
from a screen which offers some selection and sorting options.  Because
of the report complexity (and probably my lack of experience), I use 2
"temporary" files to assemble data for the report.  The files each have
a structural index (.CDX) with multiple keys.  Each time a report is
run, the code performs the following:

Opens the files EXCLUSIVE
Performs a DELETE ALL and PACK on each file.
Gathers the forecast and backlog data.
Generates the report.

Here (finally) is the problem.  On some occasions, with no pattern I
have been able to find, the following error occurs on BOTH files:
"Index does not match data file.  Rebuild Index" or words to that
effect.
Fortunately, copying the .CDX files from my test database gives me a
quick recovery, but this is an extremely irritating error to my users
and therefore to me.  Can anyone shed some light?
Oh, one more thing.  The data files have always been empty when the
error occurs, which may suggest a problem with DELETE ALL and/or PACK.

TIA for any help, and thanks for the patience to read this far.

Bill Plette

2. applet is working in the debug mode not in the web site.

3. table requires rebuild - secondary index does not match ...

4. USA-NE-Oracle 11i

5. Network error: index does not match table

6. New User problem with the add table feature

7. ERROR #114: Index does not match the table.

8. Cross Platform tools?

9. drop and recreate index vs large insert with index

10. pg_restore does not restore/recreate indices

11. (create index) vs (create index ... online)

12. Help: must drop and recreate system table index

13. Temporary Table: Implicitely created index not