ERR 51080 SYSERROR -9407 unexpected error

[Former Member]

Hello All,

Can anyone help me out? I am getting the following error in knldiag.err whilre performing restore + recovery. The backups are Full backup, Trans log , Trans log, Translog.

The below error occurs when I try to run "db_warm -f" cli command.

OS:Linux

2009-01-15 15:21:37 15774 ERR 51080 SYSERROR -9407 unexpected error

2009-01-15 15:21:37 15774 ERR 3 Admin Database state: OFFLINE

2009-01-15 15:21:37 15774 ERR 8 Log + Log- and data area are not compatible because 'Restart position not found'.

2009-01-15 15:21:37 15774 ERR 7 Log + IOSequence 1556273 not in interval of 1591367 - 1719969.

2009-01-15 15:21:37 15774 ERR 20028 Admin + Initialization of log for 'restart' failed with 'LogAndDataIncompatible'

2009-01-15 15:21:39 0 ERR 12009 DBCRASH Kernel exited due to signal 0(Killed after timeout with state SERVER_KILL)

2009-01-15 15:21:39 ___ Stopping GMT 2009-01-15 14:21:39 7.6.05 Build 012-123-198-275

Thanks for your time.

[carsten_esser]

Hello,

I know my answer is too late to help prince s on his problem. But for all that google this thread I am posting the sequence that worked in my case. It was originally posted by Natalia Khlopina somewhere else.

dbmcli -d <SID> -u control,<PWD>

dbmcli on <SID>>db_admin

dbmcli on <SID>>db_connect

dbmcli on <SID>>db_execute clear log <<< that lasted a few minutes

dbmcli on <SID>>db_online

dbmcli on <SID>>exit

Again, thanks to Natalia.

Best regards

Carsten

[markus_doehr2]

Did you execute a "db_activate recover"? If not, then the logvolume is not formatted and still contains log entries of the old instance...

Markus

[Former Member]

Hello Markus,

I have not used "db_activate recover" i have used `recover_start BACKDP-Archive LOG ExternalBackupID "CSS 09011541:1 Stream"'.

Please advice me.

Thanks

Prince.

[lbreddemann]

Hi there "Prince"....

looks like someone played around with the data- or logvolumes.

Anyhow, the don't fit together anymore.

To start the database with the current data area, you can do this:

dbmcli -d <DBSID> -u control,<pw> 
> db_admin
> util_connect
> clear log
> db_online

To be on the safe side, perform a log backup before deleting the log area.

If you messed around with the data area instead and want to keep the log information, recover a data backup (or put the correct data volume files back into place) and try to restart again.

regards,

Lars