Forum - Database Damaged

Database Damaged

Gastón Salomone

12-3-18

Hi,

I recently migrated a client from versión 7.1 to SERP 8.3 2017-08-31 (build 83250901)

We do several tests during a long time and no error in customer code were found.
But once the client start using new versión with almost 10 users logged, a D4 error apperar and system hangs.

2018-11-26 09:33:26 /THREAD(13) FindSegment oldfirst incorrect 1
2018-11-26 09:33:26 /THREAD(13) ADVERTENCIA: La base de datos puede estar dañada. Si ha intentado realizar un backup normal sin éxito, le sugerimos crear y guardar una exportación de Datos Sin Procesar en el siguiente paso
2018-11-26 09:33:29 33MSC Login @150.100.20.111
2018-11-26 09:33:38 /THREAD(13) GetThreadRepCancel() = true -- SendROData(): SendDataSV() Failed 2
2018-11-26 09:34:26 /THREAD(13) Level 1 processed -64.69 percent, found 43 996 records
2018-11-26 09:35:26 /THREAD(13) Level 1 processed -55.26 percent, found 43 998 records
…

After that another error appear related to one user

2018-11-26 09:47:58 21AGB/THREAD(14) FindSegment oldfirst incorrect 2
2018-11-26 09:47:58 21AGB/THREAD(14) Base de Datos Dañada: Strange D4SegmentGetSize non existing block
2018-11-26 09:47:58 21AGB/THREAD(14) D4BlockGetSize failed
2018-11-26 09:47:58 21AGB/THREAD(14) bln = CYBlock
2018-11-26 09:47:58 21AGB/THREAD(14) too large or too small malloc

Once this error happens, all system became unstable and, for example, all invoices shows incorrect amount of decimal digits.

After Expo/Impo process and one or two days after, same error ocurres.

Is this a Hal programming error (nothing on log file shows that), is this a Memmory problem, a Hard Disk problem, a Product bug.

I was not able to finde any message error on forum like this one.

I´m not able to discovery the reason of this error and database size is 16GB so customes is very angry because during test this not happens, and Expo/impo Procedure takes too long.

Regards

David Delač

12-6-18

Hello Gastón,

Thank you for your enquiry and sorry for the delayed response.

Information that you provided has been forwarded to one of our programmers. As soon as I get an update on your case I will reply here.

Thank you for your patience.

Best Regards,
David D.
HansaWorld Support

David Delač

12-14-18

Hello Gastón,

Do you know when this started happening for the first time? Did you make any modifications which might be causing issue that you described? Your database is corrupted and exporting/importing it does not change anything because we still have the same corrupted data that we use.

What I would suggest you to do is to try to remember when was the first time that this occurred and if possible try to import older data and see if that fixes it.

Best Regards,
David D.
HansaWorld Support

Gastón Salomone

12-14-18

This code was tested during a long time but not with a high amount of users using the system.

There was no modifications at database structure and only some about reports.

Once the client decided to go alive, we only import updated backup and go alive.
But as soon the users start to work, randomly the system crash in that way.

The question is:
* Is this a Memory problem because some data inside the database ?
* This is not a D4Index, so if Expo/Impo does not solve the problem, How I can detect wich is the data that is damaging the database.
How I can know in wich register is the record ?
* D4SegmentGetSize and all errors shown below are related to Memory, Index, Database Structure, massive Cache ?

* Why is this message appearing and What is counting backwards ? "Level 1 processed -64.69 percent, found 43 996 records" ….

* There is no similar bug/error/message in all HW reference about D4Index/D4Disk so I´m not able to understand the source of the problem.
Can HW tell me to what process this error is related ?

regards

David Delač

1-21-20

Hello Gastón,

This is a follow up message to some database corruption that happened before, we would need to find what happened before this to have a slight clue of where the problem is and how it happened.

My suggestion is that you update to our latest 8.5 version and see if problem persists and if it does please let me know.

Best regards,
David D.

Back to the list

New Message
Open Questions My Questions