FiveTech Support Forums

Good afternoon to all my dear colleagues: D
I'm going through a situation where my system is simply closed form 'not advised' and causing much inconvenience to my customers. I have observed that it generates a file called 'hb_out.log'. In this aquivo find the timeline happened to the time of error, is always 'burst' in some of the functions 'DB ... ()' (dbcommit (), dbAppend (), etc.). The information is brought to me is that the CDX is corrupted (hb_cdxPageKeyLeafBalance:. Corrupted index). Would like to know if any of your friends or even liniares antonio One can help me.
Already I am grateful to everyone's attention.

Ps: I am Brazilian and I'm using the google translator if my 'english' is not good, I apologize. rsrsrsrsrsrsrs
PS: I use Harbour

i suggest you delete the index file and recreate it

Regards.

not solve, I'm also having the same problem, first thought was the database class, then the harbour, I particionei my dbf parameters created in the harbour dbf minimized, but once a week is the same problem and all this then I switched to harbour in xHarbour did not have that problem. all say the harbour is better and while I could see is that I gained speed network and running the program, however has this inconvenience.

let's wait some guro the harbour.

You can put the expression you create the index?

sorry arthur enjoy your post, but I have the same difficulty

this is what most corrupts the index, is also the most used

          oTxt1:SetText("Arquivo de Clientes")
          USE arqcli NEW EXCLUSIVE
          IF( lPack, hb_dbPack(), )
          nRegCdx := RecCount() / 100
            oMetCdx:SetTotal( RecCount() )
          oTxt2:SetText("Indexando o Arquivo Por Código")
          INDEX ON cod TAG cod EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx
          oTxt2:SetText("Indexando o Arquivo Por Razão Social")
          INDEX ON nom TAG nom EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx
          oTxt2:SetText("Indexando o Arquivo Por Nome do Cliente")
          INDEX ON ape TAG ape EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx
          oTxt2:SetText("Indexando o Arquivo Por C.N.P.J.")
          INDEX ON cgc TAG cgc EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx
          oTxt2:SetText("Indexando o Arquivo Por Município")
          INDEX ON mun TAG mun EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx
          oTxt2:SetText("Indexando o Arquivo Por Ramo de Atividade")
          INDEX ON atv TAG atv EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx
          oTxt2:SetText("Indexando o Arquivo Por Vendedor")
          INDEX ON ven TAG ven EVAL ( oMetCdx:Set(RECNO()), SysRefresh() ) EVERY nRegCdx

I had a similar problem some time ago. At that time, I was using xHarbour.

I changed to Harbour and the problem disappeared.

mine was just the opposite, but I'm reviewing the entire structure of dbf, inclusion, change ... hope FIND the problem.

I'll try and then I report you, use FWH 907 / 1312 + harbour 3.0 / 3.2 and two'm in trouble

I have the same problem, but only on a few customers, most of them do not.

It seems that is related to equipment.

I don't know what to do.

Erro irrecuper vel 9201: hb_cdxPageKeyLeafBalance: index corrupted.
Erro irrecuper vel 9201: hb_cdxPageSeekKey: wrong parent key.

I have the same problem, already used XHB, switched to HB and was otimo for 5 days and after this period continues with the same problem, after deleting the CDX and create problem sometimes back again in 1 hour or 6 hours but it comes back happening, this customer has 40 machines that uses accessing the system, but already reduce usage to 20 machines and the problem continues, if some physical problem on some equipament to identify this problem.

Currently use the HB 3.2 and FHW 13.12 and bcc 5.82

Marcio Tullio,

The problem is in your dbf that is corrupted. You must do this: rename your DBF like yourdbf_old.dbf and create a new one (maybe using DBU or another of your preference) and create the structure manually. After this, import all data from the old dbf. In your app, recreate all CDX files.

Let us know your results.

Kleyber Hello, I've done it and not resolved, I created all dbf in harbour and spends a few hours, sometimes minutes, corrupts the cdx.

I added this function in application start.
If! WIN_OSNETREGOK () // Need ADM rights
If! WIN_OSNETREGOK (.t.,. T.) // First .t. is to adjust XP / ... W98, the second adjusts the view.
MsgInfo ('Registration not set windows!')
EndIf
EndIf

and took the DBINFO (DBI_SHARED, .F.) opening dbf

Only Tomorrow I will have the results.

From my notes:

4/27/2005 7:08 AM

Windows' Oppontunistic Locking

Is well described at:

http://www.dataaccess.com/whitepapers/o ... ching.html

It also appears that you have Win 98 computers on the network--I highly recommend not using those.

The amount of RAM in the computers can be an issue.

Is this a new system, or an existing system that just started generating errors? If it just started, was there an update to the application software or server?

James

Hi James, thanks for answering.

in my case, I dont have computers with w98, machines are core i3 4GB, 3GB 2duo core, but are already two days without problems after the changes.
I'm monitoring and getting everything in order will give the opinion.