Db crash

Posted by stefano.frosini on 04-Feb-2019 16:38

Hi,

we have installed a VMWARE server with Linux Red Hat Enterprise 7.

In that server there is installed QAD2010SE 2.9.4 and Progress OpenEdge 10.2b08.

In that server we have 6 db, JAPAN, KOREA,THAILAND,MALAYSIA, INDIA and AUSTRALIA.

Sometimes , and in different db, we have received the error below: (that example is for INDPROCUS db)

[2019/02/01@19:38:57.233+2300] P-71276 T-140347883439936 I APPSRV101: (9445) SYSTEM ERROR: read wrong dbkey at offset 3435986944 in file /db/indpro/data/indprocus.d1

found 0, expected 26843648, retrying. area 6

[2019/02/01@19:39:07.234+2300] P-71276 T-140347883439936 I APPSRV101: (4229) Corrupt block detected when reading from database.

[2019/02/01@19:39:07.235+2300] P-71276 T-140347883439936 I APPSRV101: (10560) bkRead: Error occurred in area 6, block number: 838863, extent: /db/indpro/data/indprocus.d1.

[2019/02/01@19:39:07.236+2300] P-71276 T-140347883439936 I APPSRV101: (10561) Writing block 838863 to log file. Please save and send the log file to Progress Software Corp. for investigation.

[2019/02/01@19:39:07.240+2300] P-71276 T-140347883439936 I APPSRV101: (-----) SYSTEM DEBUG: Database buffer block

[2019/02/01@19:39:07.240+2300] P-71276 T-140347883439936 I APPSRV101: (-----) pbktbl = 0x0x7fa4fe7a3fa8

[2019/02/01@19:39:07.240+2300] P-71276 T-140347883439936 I APPSRV101: (-----) pbktbl->qself = 0x000b0000023b0fa8

[2019/02/01@19:39:07.240+2300] P-71276 T-140347883439936 I APPSRV101: (-----) XBKBUF(pbktbl->qself) = 0x00007fa4fe7a3fa8

[2019/02/01@19:39:07.240+2300] P-71276 T-140347883439936 I APPSRV101: (-----) pbktbl->bt_qbuf = 000b00000cabc820

[2019/02/01@19:39:07.240+2300] P-71276 T-140347883439936 I APPSRV101: (-----) XBKBUF(pbktbl->bt_qbuf) = 0x0x7fa508eaf820

In that case I use “idxfix” command and the issue was solved but in anycase that error is very bad.

My question is, RED HAT ENTERPRISE 7 , PROGRESS OPENEDGE 10.2B08 and QAD2010SE 2.9.4 , are supported in that configurations?

If yes, the issue is related to some HARDAWARE problem on the server?

Thanks a lot to help

Regards

Stefano Frosini

OpenEdge General - Forum

All Replies

Posted by George Potemkin on 04-Feb-2019 17:25

Most likely database is not corrupted.

Clear filesystem cash:

echo 3 | sudo tee /proc/sys/vm/drop_caches

Connect the database and check if you can read the block:

find first _file no-lock where recid(_file) eq 26843648 no-error.

Your database is fine if you will not get the error # 1124.

Posted by stefano.frosini on 04-Feb-2019 20:56

Hi George,

Thanks a lot to answer,

I have check the lg file od INDPROCUS db and the error 1124 is there, see below:

[2019/02/01@19:39:07.243+2300] P-71276 T-140347883439936 F APPSRV101: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:07.251+2300] P-71276 T-140347883439936 F APPSRV101: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.290+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.294+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.297+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.301+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.305+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.308+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.312+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.316+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

[2019/02/01@19:39:10.319+2300] P-43032 T-140435794405184 F BROKER 0: (1124) SYSTEM ERROR: Wrong dbkey in block. Found 0, should be 26843648 in area 6.

Regards

stefano

Da: George Potemkin [mailto:bounce-GeorgeP12@community.progress.com]
Inviato: lunedì 4 febbraio 2019 18:27
A: TU.OE.General@community.progress.com
Oggetto: RE: [Technical Users - OE General] Db crash

EXTERNAL

Update from Progress Community

George Potemkin

Most likely database is not corrupted.

Clear filesystem cash:

echo 3 | sudo tee /proc/sys/vm/drop_caches

Connect the database and check if you can read the block:

find first _file no-lock where recid(_file) eq 26843648 no-error.

Your database is fine if you will not get the error # 1124.

View online

You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here.

Flag this post as spam/abuse.

This email was sent from outside the GKN network.
Please ensure that you verify the source of the message is legitimate before taking action on it.

This e-mail and any attachments transmitted with it contain information which is confidential, intended solely for the addressee(s) and which may also be privileged or exempt from disclosure under applicable law. If you are not the addressee(s), or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, print, disclose or use any part of it or its attachments. Internet communications are not guaranteed to be secure or free of any virus. The GKN Group does not accept liability for any loss or damage arising in any way from changes to this e-mail or its attachments which may occur in transmission due to network, machine or software failure or manufacturer or operator error, or from unauthorised access or interference with internet communications by any third party or from the transmission of any viruses. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the GKN Group or any part of it is personal to the sender and is not given or in any way endorsed by the GKN Group or any part of it.
We are committed to using and managing personal information responsibly and ethically. Please see our privacy policy to find out more about how we will use your personal data.

Posted by gus bjorklund on 04-Feb-2019 20:58

I am guessing with insufficient evidence but this smells like a vmware bug.

Posted by Francisco Morales López on 13-Feb-2019 03:56

Has this topic been recent? Maybe it's good to do a health check on your infrastructure, recently I had a problem that ended up being a fiber. If you have support this topic it is better to help them, there are some tools that facilitate the monitoring of the team and can help you to know if it is the database or an issue....

This thread is closed