cancel
Showing results for 
Search instead for 
Did you mean: 

Migration from MaxDB 7.7.06 to 7.9.09.10 fails. Kernel crash.

thomas_huebner2
Explorer
0 Kudos

Hello,

please be patient if I miss something as this is my first ask for help here.

I have a backup created on 7.7.06.:
After having installed 7.9.09.10 I do the following steps (which worked brilliant for 7.7.06.):

db_create
param_rmfile
param_startsession
param_init OLTP
param_put CACHE_SIZE 32768
param_put MAXDATAVOLUMES 5
param_put MAXUSERTASKS 75
param_put _PACKET_SIZE 131072
param_checkall
param_commitsession
param_addvolume 1 DATA "C:\sapdb\DISKD0001" F 52428
param_addvolume 1 LOG "C:\sapdb\DISKL001" F 5120
db_admin
db_activate dba,*****
medium_put completeF "C:\sapdb\my.backup" FILE DATA 0 8 YES
db_connect
db_activate recover completeF data
-> Runs successful
medium_delete completeF
db_online

DEBUG [RunCommandEx]: STDOUT - ERR
DEBUG [RunCommandEx]: STDOUT - -24994,ERR_RTE: Runtime environment errordb_ac
DEBUG [RunCommandEx]: STDOUT - 4,connection broken
DEBUG [RunCommandEx]: STDOUT -
DEBUG [RunCommandEx]: STDERR -
DEBUG [RunCommandEx]: exitcode=1

When I look to knldiag I see an EXCEPTION while doing the automatic catalog migration:

Thread 0xE44 Task 93 2019-01-28 23:40:37 MIGRAT 51381: COLUMNS
Thread 0xE44 Task 93 2019-01-28 23:40:37 MIGRAT 51381: recreated views : 205
Thread 0xE44 Task 93 2019-01-28 23:40:37 MIGRAT 51381: migrating indexes
Thread 0xE44 Task 93 2019-01-28 23:40:37 MIGRAT 54000: migrating db-procedure surrogates...
Thread 0xE44 Task 93 2019-01-28 23:40:37 MIGRAT 54000: updating SYSCATALOG.DEPENDENCIES...
Thread 0xE44 Task 93 2019-01-28 23:40:37 MIGRAT 51381: invalidating procedures ...
Thread 0xE44 Task 93 2019-01-28 23:40:37 ERR DIAG 0: EXCEPTION caught, PID: 5608, thread: TaskScheduler11, code 0xc0000005 (Access violation) at IP 0x0000000140AEA370, write of address 0x0000000000000020
Thread 0xE44 Task 93 2019-01-28 23:40:37 RTEKernel 61: rtedump written to file 'rtedump'
Thread 0xE44 Task 93 2019-01-28 23:40:37 RunTime 3: State changed from ADMIN to ABORT
Thread 0xE44 Task - 2019-01-28 23:40:37 RTEKernel 60: Kernel aborts

Is there someone who can push me into the right direction?

Thanks a lot to all of you,

Thomas

Accepted Solutions (0)

Answers (4)

Answers (4)

ralf_wahlen3
Active Participant
0 Kudos

Hi Christoph. Here it is, directly from SMP launchpad

763972-laden-von-systemtabellen-scheitert-mit-dem.txt

Greets

ralf_wahlen3
Active Participant
0 Kudos

Solved?

Check that SAP Note out! Hinweis 763972 - Laden von Systemtabellen scheitert mit
dem Fehler -8022

Lösung
Bitte ändern Sie den Benutzer SUPERDBA, wie im Hinweis 754140 beschrieben
ist, und wiederholen Sie das Laden vom Systemtabellen.
Wenn das Laden von Systemtabellen innerhalb der Catalog-Migration bei dem
Upgrade gescheitert ist, setzen Sie bitte zwei folgende Kommandos
nacheinander ab:
dbmcli -d <SID> -u control,<pwd> load_systab -u superdba,<pwd> -ud
domain
dbmcli -d <SID> -u control,<pwd> load_systab -u superdba,<pwd> -m
In anderen Fällen reicht es aus, nur das erste von oben angeführten
Kommandos abzusetzen.
Wichtig: Sollte das Laden der Systemtabellen innerhalb des Software Updates
(SDBUPD) abgebrochen sein, schließen Sie den Update unbedingt durch
erneutes Ausführen des SDBUPD erfolgreich ab. Ansonsten kann der nächste
Update scheitern.

That was our error in 2012 during the upgrade of the DB. Try to solve!

Greets

thomas_huebner2
Explorer
0 Kudos

Hello Ralf,

the issue is NOT solved and I just created a new question with more or less same content.

With a regular account it seems I don't have access to the mentionned SAP note.
Would it be possible some how to get a copy of it here? Would ease my life a lot!

Thank you very much for your effort!

thomas_huebner2
Explorer
0 Kudos

So many experts and no hint?
(Is my problem really that uncommon? I tried and tried but I don't make any progress.)

thomas_huebner2
Explorer
0 Kudos

(Same issue by the way when updating to 7.8.)

If I try to update using sdbsetup.exe the upgrade run but at the end the same error arises when bringing database to ONLINE state.