Main   Products   Offshore Outsourcing   Customers   Partners   ContactUs  
JDBC Databases
  HXTT Access v7.1
  HXTT Cobol v5.0
  HXTT DBF v7.1
 
  Buy Now
  Support
  Download
  Document
  FAQ
  HXTT Excel v6.1
  HXTT Paradox v7.1
  HXTT PDF v2.0
  HXTT Text(CSV) v7.1
  HXTT Word v1.1
  HXTT XML v4.0
Offshore Outsourcing
Free Resources
  Firewall Tunneling
  Search Indexing Robot
  Conditional Compilation
  Password Recovery for MS Access
  Password Recovery for Corel Paradox
  Checksum Tool for MD5
  Character Set Converter
  Pyramid - Poker of ZYH
   
   
   
Heng Xing Tian Tai Lab of Xi'an City (abbr, HXTT)

HXTT DBF
Index Corruption
Oscar San Martin
2012-02-04 13:52:57.0
How can I prevent this index corruption ?

Error ejecutaQuery : Failed to update Record 558867 because of corrupted index file:Please reindex index expression CLAVE: Found some recursive information at:16827392.

I reindex and fixed problem, but our table is too big and reindex is very slow in opening hours for public.

Thanks in advance,

Oscar
Re:Index Corruption
HXTT Support
2012-02-04 15:42:02.0
Please use select top 1 reccount() from yourtable, and let us know your table size.
Re:Index Corruption
HXTT Support
2012-02-04 15:57:45.0
BTW, whether your index file is NDX format, which is used by dbase at the same time?
Re:Re:Re:Index Corruption
Oscar San Martin
2012-02-04 18:20:56.0
reccount() = 559451
Index format: IDX
OS : SCO Unix 5.0
JRE : 1.4

Thanks,

Oscar
Re:Re:Re:Re:Index Corruption
HXTT Support
2012-02-06 05:37:00.0
>Index format: IDX
HXTT support three kinds of IDX format (uncompressed IDX foramt, compressed IDX format, FlagShip IDX format).

>OS : SCO Unix 5.0
Whether there's other Xbase program is modifiing the same table?

>I reindex and fixed problem, but our table is too big and reindex is very slow
> in opening hours for public.
>reccount() = 559451
HXTT DBF will lock exclusive that table, and uses external sort for reindex. It shouldn't be so slow.

>Found some recursive information at:16827392.
HXTT DBF allow only max 512 node depth level. Maybe your IDX file is unblance or too bigger so that it beyonded 512 level.

Re:Re:Re:Re:Re:Index Corruption
Oscar San Martin
2012-02-06 05:45:27.0
>Index format: IDX
>>HXTT support three kinds of IDX format (uncompressed IDX foramt, compressed >>IDX format, FlagShip IDX format).

We work under FoxPlus / UNIX...can I send you my IDX file in order to certify the format ?

>OS : SCO Unix 5.0
>>Whether there's other Xbase program is modifiing the same table?
We use lockType=FOXPRO4UNIX property...



Oscar
Re:Re:Re:Re:Re:Re:Index Corruption
HXTT Support
2012-02-06 05:50:06.0
>We work under FoxPlus / UNIX...can I send you my IDX file in order to certify
> the format ?
Needn't. HXTT DBF can detect automatically.
Re:Re:Re:Re:Re:Re:Re:Index Corruption
Oscar San Martin
2012-02-07 12:54:23.0
When I try to reindex all on mytable, I receive :

Error: Timeout Interrupted Exception: beyond 30000 msecs to get result for a remote request, but that request should have been executed by remote server.
SQLState: S1T00
ErrorCode: 721152

I set lockTimeout=120 in url config, in both sides, server and client...

Thanks,

Re:Re:Re:Re:Re:Re:Re:Re:Index Corruption
Oscar San Martin
2012-02-07 13:23:03.0
In addition, we just cleaned our year and today movimien table have 70 mb, yesterday have 340 mb, however today we have 3 transaction with error and reindex fixed problem....

Java app can't find record previously inserted by FoxPlus application....then we reindex under FoxPlus tool and record is found by Java application...we have CGP files correctly configured with all index file name...

Thanks,
Re:Re:Re:Re:Re:Re:Re:Re:Index Corruption
HXTT Support
2012-02-07 20:51:50.0
>I set lockTimeout=120 in url config, in both sides, server and client...
You can try lockTimeout=120000
lockTimeout: To specify DBF driver's timeout in milliseconds to wait until other processes or Xbase applications released record lock or table lock. 0 means a default value, and <0 means no wait.

>In addition, we just cleaned our year and today movimien table have 70 mb,
> yesterday have 340 mb, however today we have 3 transaction with error and
> reindex fixed problem....
>Java app can't find record previously inserted by FoxPlus application....then
> we reindex under FoxPlus tool and record is found by Java application...we
> have CGP files correctly configured with all index file name...
You can use HXTT's PACK TABLE sql to reduce your table. Maybe Foxplus hasn't reindex all of your IDX files automatically after PACK TABLE through Foxplus. CGP is used only for Clipper, not Foxplus. In my memory, Foxplus need a set index to ???.IDX command so that it can maintain that IDX file?

Search Key   Search by Last 50 Questions




Google
 

Email: webmaster@hxtt.com
Copyright © 2003-2019 Heng Xing Tian Tai Lab of Xi'an City. | All Rights Reserved. | Privacy | Legal | Sitemap