Forum - crash on backup

crash on backup

Aldevinas Katkus

3-20-17

In my demo DB I tested it 3 times. Exporting TB via System>>exports>> resulted in a crash in all 3 cases. Interesting what is doing the D4IndexDelete in the backup process...

2017-03-20 16:11:07 8.3 2017-02-12 (build 83250202)

2017-03-20 16:11:37 AD Exporting company 6 Konsolidacija
2017-03-20 16:11:37 AD Exporting blocks
2017-03-20 16:11:37 AD Kopijos darymas baigtas
2017-03-20 16:11:37 AD Duration 6.19 seconds
2017-03-20 16:11:37 AD key: 4,10,14 4|2017-03-20>18 003 801 490 8;: 580 000 000.01|16:11:37.0
2017-03-20 16:11:37 AD D4IndexDelete found wrong record, now dumping index:
2017-03-20 16:11:37 AD new clean node at: 36617728 with 5 atoms and 19512 logical children
2017-03-20 16:11:37 AD key: 4,10,14 0|2005-06-20=58 006 801 488 :59 <80 000 000.04??88|8:37:28.0, daughter: 82723840
2017-03-20 16:11:37 AD new clean node at: 82723840 with 8 atoms and 4113 logical children

Aldevinas Katkus

3-31-17

same with 8.3 2017-03-19 (build 83250402)

Aldevinas Katkus

3-31-17

same with 8.3 2017-03-27 (build 83250500)

Aldevinas Katkus

4-3-17

I made the backup with no errors using the server's exe. Hmm...

Aldevinas Katkus

4-13-17

I made further investigation and found that after export - import there were more records in the register QualConVc than before the export (!!!).
I exported a single register QualConVc via DB Maintenance module from the older version and compared it to the same register exported from the new version which I imported the Text backup into. I can see that after the export-import the last record was a duplicate of the previous record except the SerNr field. In the old version I had 75 records, in the new one - 76 records...

User 1

5-15-17

It seems to be a bug. Please report the steps.

Back to the list

New Message
Open Questions My Questions