Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-13 18:54:23 |
Hi,
I executed an insert on one of my Clipper DBF files and i got one index (.NTX) corrupted...
This DBF file has 8 indexes. The index with the problem is:
ID_CONH3.NTX => OCPNH_EST + OPCNH_DGDT + OPCNH_CONH
This is the only index that got corrupted.
An information that can be important is that the fields OCPNH_EST and OPCNH_DGDT are empty strings. We have another records where this fields are empty strings too but they were inserted by the legacy Clipper system.
Have you any ideia that what can be corrupting this index?
Thanks in advance,
Marcelo
|
Re:Index corrupted after insert |
HXTT Support |
2009-08-13 21:34:54 |
>We have another records where this fields are empty strings too but they were
> inserted by the legacy Clipper system.
You shoul run once "reindex all on thattable;". Then use lockType=Clipper connection property to avoid legacy Clipper system and HXTT DBF do concurrent modification.
|
Re:Re:Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-18 05:38:08 |
Do you mean that I really need to use HXTT reindex once to avoid concurrent modification?
Or should I use reindex every time the corruption happens?
|
Re:Re:Re:Index corrupted after insert |
HXTT Support |
2009-08-18 08:11:52 |
>Do you mean that I really need to use HXTT reindex once to avoid concurrent >modification?
Once to fix that corrupted index. You can use Clipper too.
>Or should I use reindex every time the corruption happens?
You should use lockType=Clipper to avoid new corruption.
|
Re:Re:Re:Re:Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-18 10:08:14 |
Sad, because I'm using lockType=Clipper and still getting corruption.
I'm trying to mount a test case so that I can send to you.
|
Re:Re:Re:Re:Re:Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-18 12:45:06 |
I'm still clueless about the problem that I'm facing. The corruption problem seems to be random and the only thing that is always happening is this error:
DBCOMMIT (0) Unrecoverable error 17: Illegal characters in alias? ??3?J?a?x?Å?ª
?¢?È?Ù???????0?G?^?u?î?��?¦?g ~ �� ¼ + + ��???6?M?d?{?Æ?®?+?Î?¯?P 6203330
1168 ?? 62044273004 X? 62047213053 ? 62052764020
:? 62065980044 (? 62079808087 4? 62088505091 6
62094181049 A 62104683068 V? 62110462000 ?
62111353000 ¥ 62177702020 62177702020 L? 6221166802
0 ¦? 62235419968 Þ? 62315633087 Q 62322923087 Ã?
62334930059 -? 62338080068 ¶? 62848518049 Ù? 623733900
? 62418491072 -? 62442970082 ?? 62517457972 ï? 6253
7989953 Å? 62558749072 »? 62558960997 c 62699750000
¶? 62761790006 ^
62770748068 _? 62791052020 Á? 6291
2615968 y? 62977253068 æ
62977253068 +? 62989731091 ?
|
Re:Re:Re:Re:Re:Re:Index corrupted after insert |
HXTT Support |
2009-08-18 16:31:39 |
>This DBF file has 8 indexes. The index with the problem is:
>ID_CONH3.NTX => OCPNH_EST + OPCNH_DGDT + OPCNH_CONH
>This is the only index that got corrupted.
>An information that can be important is that the fields OCPNH_EST and OPCNH_DGDT
>are empty strings. We have another records where this fields are empty strings
>too but they were inserted by the legacy Clipper system.
Please send us your corrupted dbf/ntx sample.
|
Re:Re:Re:Re:Re:Re:Re:Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-19 05:43:40 |
Ok, I've sent via email. Now I look forward your review.
Thanks
|
Re:Re:Re:Re:Re:Re:Re:Re:Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-20 05:57:41 |
Do you have any feedback on this problem? We are implementing a huge system we design around your driver and now after the go-live we detected this problem. It's very important for us this solution.
Thank you
|
Re:Re:Re:Re:Re:Re:Re:Re:Index corrupted after insert |
HXTT Support |
2009-08-20 07:23:39 |
|
We're still t recur your issue.
|
Re:Re:Re:Re:Re:Re:Re:Re:Index corrupted after insert |
Marcelo Schwanck Lopes |
2009-08-20 07:33:40 |
Ok, thank you. Meanwhile we are trying to workaround using other index (instead of NTX, trying IDX/CDX now). The same problem didn't happened yet, but we are facing another one:
DBF driver doesn't know what's the meaning of collation sequence . Please email support@hxtt.com a dbf cdx sample file for support
at com.hxtt.global.SQLState.SQLException(Unknown Source)
at com.hxtt.b.s.a(Unknown Source)
at com.hxtt.sql.dbf.b.char(Unknown Source)
at com.hxtt.sql.dbf.b.(Unknown Source)
at com.hxtt.sql.dbf.b.a(Unknown Source)
at com.hxtt.sql.dbf.DBFIndex.a(Unknown Source)
at com.hxtt.sql.dbf.DBFIndex.a(Unknown Source)
at com.hxtt.sql.dbf.DBFIndex.(Unknown Source)
at com.hxtt.sql.dbf.DBFIndex.a(Unknown Source)
at com.hxtt.sql.dbf.i.a(Unknown Source)
at com.hxtt.sql.dbf.c.a(Unknown Source)
at com.hxtt.sql.dbf.c.(Unknown Source)
at com.hxtt.sql.dbf.u.a(Unknown Source)
at com.hxtt.sql.bn.if(Unknown Source)
at com.hxtt.sql.bn.a(Unknown Source)
at com.hxtt.sql.df.a(Unknown Source)
at com.hxtt.sql.bn.a(Unknown Source)
at com.hxtt.sql.bn.a(Unknown Source)
at com.hxtt.sql.ag.a(Unknown Source)
at com.hxtt.sql.dh.execute(Unknown Source)
at com.mercurio.depotrobot.dbf.BaseCrudDAO.store(BaseCrudDAO.java:163)
at com.mercurio.depotrobot.dbf.BaseCrudService.store(BaseCrudService.java:49)
at Teste.main(Teste.java:32)
|
Main
webmaster@hxtt.com