Error on Import of logical data backup

[ATomlin]

Hello,

MEGA Version : MEGA 2009 SP5 cp5 et Database tyep : ORACLE

I have created a new environment for archive purposes. I did 3 logical backups of our production environnement :

1) Meta-model extensions

2) Technical data extensions

3) Data extensions.

I then imported each file into the archive environment. The first two worked perfectly. However, the Data extensions file (315M) import aborts after around 3 hours with the following message :

CursorPropvSet _ BOOKMARK: The occurrence "96C79AC14EF440BB" (4664408651547645639) does not exist in Table "7221815F3D210049" (20614887413608993) .

When I try to publish my transaction, the following error message appears and my session ends

exception 0xc0000005: EXCEPTION_ACCESS_VIOLATION

try to read at 0x78f5f258

at address 0x78f5f258 : MegaDesktopObjectCreate+0x62d

When I restart MEGA :

reprise de transaction en cours puis

CursorPropvSet _ BOOKMARK: The occurrence "96C79AC14EF440BB" (4664408651547645639) does not exist in Table "7221815F3D210049" (20614887413608993) .

exception 0xc0000005: EXCEPTION_ACCESS_VIOLATION

try to read at 0x78f5f258

at address 0x78f5f258 : MegaDesktopObjectCreate+0x62d.

I haven't been able to find any information on this in Support or knowledge base.

Has anyone faced this problem before ?

All ideas are welcome !

Thanks,

Aoife Tomlin

[ldosorio]

Good day! 

Have you tried translating and compiling?

Cordialment

[ATomlin · Accepted solution]

Hello Jérôme,

I retried the import this morning, and this time it was much faster and it worked !

Aoife

[ATomlin]

Hello Jérôme,

I'll try again tomorrow and see what happens, since this error occured each time I tried, I think its safe to assume that I can replicate it !

Thank you for your reply

Aoife

[ATomlin]

Helo Jérôme,

I'll try again tomorrow and see what happens, since this error occured each time I tried, I think its safe to assume that I can replicate it !

Thank you for your reply

Aoife

[jhorber]

Hello Aoife

This seems to be an error in a specific context.

If you are able to replicate this behavior, I suggest you open a case in support

You can use this form