Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

MaxDB can't be restarted after restore

Hi experts,

after restoring our MaxDB we have this problem while upgrading 7.9.8.0.23 to .28:

Cannot switch database mode, error during dbm command:

db_online

ERR

-24988,ERR_SQL: SQL error

-9407,System error: unexpected error

3,Database state: OFFLINE

Internal errorcode, Error code 6433 "system_error"

33,The log-iosequencenumber 131120322  could not be found at the expected position 1 on partition 1

20014,OldestNotSaved not found on log

20028,Initialization of log for 'restart' failed with 'InconsistentLogInfoPage'

Looking for error messages in knldiag

...

2015-02-18 08:42:40     0x64EF ERR 51080 SYSERROR -9407 unexpected error

2015-02-18 08:42:40     0x64EF ERR     3 Admin    Kernel_Administration+noPIC.cpp:976

2015-02-18 08:42:40     0x64EF ERR     3 Admin    Database state: OFFLINE

2015-02-18 08:42:40     0x64EF         6 KernelCo Internal errorcode, Error code 6433 "system_error"

2015-02-18 08:42:40     0x64EF WNG    33 Log      The log-iosequencenumber 131120322  could not be found at the expected position 1 on partition 1,LAST_IOSEQUENCE=5,FIRST_IOSEQUENCE=0

2015-02-18 08:42:40     0x64EF ERR 20014 Log      Log_Partition+noPIC.cpp:1099

2015-02-18 08:42:40     0x64EF ERR 20014 Log      OldestNotSaved not found on log

2015-02-18 08:42:40     0x64EF WNG 20028 Admin    Initialization of log for 'restart' failed with 'InconsistentLogInfoPage'

2015-02-18 08:42:40     0x64EF     12651 CONNECT  Connection released (E01, T34, connection obj. 801971d50)

2015-02-18 08:42:40     0x64EF       112 RTEKerne Offline KILL requested

2015-02-18 08:42:40     0x64EF         3 RunTime  State changed from ADMIN to SHUTDOWNKILL

2015-02-18 08:42:40     0x64D0 ERR     7 Messages Msg_Registry+noPIC.cpp:507

2015-02-18 08:42:40     0x64D0 ERR     7 Messages Begin of dump of registered messages

2015-02-18 08:42:40     0x64D0 WNG 20028 Admin    Initialization of log for 'restart' failed with 'InconsistentLogInfoPage'

2015-02-18 08:42:40     0x64D0         6 KernelCo Internal errorcode, Error code 6433 "system_error"

2015-02-18 08:42:40     0x64D0 ERR     3 Admin    Kernel_Administration+noPIC.cpp:976

2015-02-18 08:42:40     0x64D0 ERR     3 Admin    Database state: OFFLINE

2015-02-18 08:42:40     0x64D0         6 KernelCo Internal errorcode, Error code 6433 "system_error"

2015-02-18 08:42:40     0x64D0 WNG    33 Log      The log-iosequencenumber 131120322  could not be found at the expected position 1 on partition 1,LAST_IOSEQUENCE=5,FIRST_IOSEQUENCE=0

2015-02-18 08:42:40     0x64D0 ERR 20014 Log      Log_Partition+noPIC.cpp:1099

2015-02-18 08:42:40     0x64D0 ERR 20014 Log      OldestNotSaved not found on log

2015-02-18 08:42:40     0x64D0 WNG 20028 Admin    Initialization of log for 'restart' failed with 'InconsistentLogInfoPage'

2015-02-18 08:42:40     0x64D0 ERR     8 Messages Msg_Registry+noPIC.cpp:544

2015-02-18 08:42:40     0x64D0 ERR     8 Messages End of the message list registry dump

2015-02-18 08:42:40     0x64D0        61 RTEKerne rtedump written to file 'rtedump'

2015-02-18 08:42:40     0x64D0       111 RTEKerne Tracewriter resumed

2015-02-18 08:42:40     0x64D0        94 RTEKerne Waiting for tracewriter to finish work

2015-02-18 08:42:40     0x64D0       116 RTEKerne Tracewriter termination timeout: 60 seconds

2015-02-18 08:42:40     0x64E8     20000 Trace    Start flush kernel trace

-------------------------------------------- current write position ----------------

===========================================  end of write cycle  ===================

...

End of knldiag

Background is that we don't have a final backup after upgrade from 7.9.8.0.22 to .28, so we restored into a .23 (old server has crashed, so we restored using SWPM).

The last log pages were created in .28. Do we have to clear the log area?

Tags:
Former Member
replied

Hello Daniel,

this sounds strange - can you create an SAP ticket, open the OS connection to the database server and let me know the ticket#?
To get around this, yes, you will likely need to clear the log. However, at the moment I do not fully understand what has happened at your system - can you explain the sequence of events in more detail?


Thorsten

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question