Post restoration error

[Former Member]

Hi Gurus ,

We have done a restoration from the Production to Quality for system refresh .

We have got the restoration sucessfully .

After the restoration , we have changed the

a.) liveCache Name

b.)liveCache Server

for both LCA and LDA settings in Integration Tab of LC10.

Now when starting the Live Cache ,we get the following error

"Error DBMCLI_COMMAND_EXECUTE_ERROR when starting"

and

Server: gaqscm

Users: BASIS001

Logical Command: DBMRFC

Parameter: exec_lcinit restart

Name and Server : GLQ - gaqscm

DBMRFC Function : DBM_EXECUTE

Command : exec_lcinit restart

Error : DBM Error

Return Code : -24964

Error Message : ERR_EXECUTE: error in program execution

Also , we have checked the file Knldiag, following are its logs

************

2007-08-02 17:11:01 115 ERR 20029 Log DBIdentifier of DataVolume (glpscm:

KLP_20060920_111005) and LogVolume (gaqscm:GLQ_20060530_124209) does not match

2007-08-02 17:11:01 115 11000 vdetach '/sapdb/GLQ/saplog/DISKL001' devno

5 T103

2007-08-02 17:11:01 11 12822 TASKING Thread 259 joining

2007-08-02 17:11:01 259 11566 stop DEVi stopped

2007-08-02 17:11:01 115 WNG 20026 Admin Initialization of log for 'restart'

failed with 'LogAndDataIncompatible'

2007-08-02 17:11:01 115 20040 Admin Kernel state: 'OFFLINE' reached

2007-08-02 17:11:01 115 12696 DBSTATE Change DbState to 'SHUTDOWN'(25)

+++++++++++++++++++++++++++++++++++++++ Kernel Exit ++++++++++++++++++++++++++++

2007-08-02 17:11:17 0 12845 DBSTATE Kernel exited normal

2007-08-02 17:11:17 0 12808 DBSTATE Flushing knltrace pages

2007-08-02 17:11:18 0 11560 COMMUNIC Releasing T103

2007-08-02 17:11:18 0 12696 DBSTATE Change DbState to 'OFFLINE '(29)

********

also , the logs file lcinit.log has the following error

***********

installation path: /sapdb/GLQ/db

operating system : SunOS

OK State OFFLINE

Starting GLQ into ADMIN

OK

OK DBMServer 7.5.0 Build 035-123-123-944

Starting GLQ into ONLINE

ERR

-24895,ERR_SHUTDOWN: shutdown of database occured

-71,connection broken server state 6

restart not possible (please check knldiag)

ERROR : liveCache GLQ not restarted (see /sapdb/data/wrk/GLQ/lcinit.log)

**************************

Please suggest

Regards

Anthony

Message was edited by:

Anthony D'souza

[former_member229109 · Accepted solution]

Hello Anthony,

Please review the SAP note::

457425 Homogenous liveCache copy using backup/restore

you got the following error in the knldiag::

2007-08-02 17:11:01 115 ERR 20029 Log DBIdentifier of DataVolume (glpscm:

KLP_20060920_111005) and LogVolume (gaqscm:GLQ_20060530_124209) does not match

The reason is, that your data backup is not compatible to the actuall log on your target system. So you have to perform the explained instance install procedure or go with 'Recovery After Initializing a Database Instance' in DBMGUI to clear the log there.

This is called the 'db_activate' what initializes the old used volumes.

-> What version of the DBMGUI do you have?

And if you carry out a restart before the restore, the error

'-8003: log and data must be compatible' will occur after the restore.

The error means that there is a mismatch between the DBindentifier of the log and datavolume, as you know.

As you saw in the note 457425, which explains the procedure for a homogenous liveCache copy:

"In Version 7.4, a normal recovery is NOT sufficient to import a backup from another system. You must install a liveCache database instance beforehand. You MUST begin at point 1 if you are using this version."

You could create a liveCache (with the option 'restore') and then restore the backup of the source liveCache before the restart, for exmple. The detailed procedure is given in note 457425.

Or if you used the DBMGUI, please go with 'Recovery After Initializing a

Database Instance', you will find a description for using the wizards in the MAXDB documentation:

You could review the documents at : http://maxdb.sap.com/currentdoc/default.htm

If you would like to use DBMGUI to create the instance for the recovery on the target server or use Restoring After Initializing a Database Instance,

see the info at

Tools -> Database Manager GUI -> Creating a Database Instance ->Custom

OR

"Restoring After Initializing a Database Instance" at

http://maxdb.sap.com/currentdoc/30/5ada35596211d4aa83006094b92fad/content.htm

Thank you and best regards, Natalia Khlopina