SAP LiveCache / MaxDB error

[former_member199694]

hi,

We are migrating from Solaris 10 to solaris10-Zone / Solaris-11 global configuration. While moving existing LiveCache to new h/w, we experiencing issues of Bad Page / Bad data / Bad log etc. Not sure, if this is due to new h/w and zone config. LiveCache is 7.7.07.46 / Build25. I have gone over Solaris related LiveCache / MaxDB notes.

If any of you had similar issue, would appreciate, if you could share your experience.

Thanks,

Raj

=============This is when taking data backup=================================================

ERR Data       20008:  Bad page - page type 'nil' is invalid,_FILE=Data_BasePage+noPIC.cpp,_LINE=292

ERR SAVE       52012:  error occured, basis_err 6433

ERR SYSERROR   51080:  -9407 unexpected error

ERR Backup         3:  Data backup failed,_FILE=Kernel_Administration+noPIC.cpp,_LINE=1497

ERR IOMan          5:  Failed consistency check on read page,NUMBER3=3,NUMBER2=1,NUMBER1=7,NUMBER=7,BLOCK_NO_1=362254,VOLUME_ID_1=1,BLOCK_NO=362257,VOLUME_ID=1,VOLUME_TYPE=data,_FILE=IOMan_DataVolume+noPIC.cpp,_LINE=160

SrvTasks      17:  Servertask Info: because Error in backup task occured

SrvTasks      10:  Job 6 (Backup / Restore Volume Task) [executing] WaitingT310 Result=6433

KernelComm     6:  Error in backup task occured, Error code 6433 "system_error"

=====================this is when autolog saved log file to filesystem==============================

ERR Kernel     20000:  Bad page - checksums not maching,_FILE=Kernel_Page74+noPIC.cpp,_LINE=46

ERR Kernel     20001:  Bad page - calculated checksum [ 16161 ] header checksum [ 0 ] trailer checksum [ 16816 ],_FILE=Kernel_Page74+noPIC.cpp,_LINE=42

20000:  Bad page - checksums not maching,_FILE=Kernel_Page74+noPIC.cpp,_LINE=46

20029:  EMERGENCY SHUTDOWN,_FILE=IOMan_SingleLogGroup+noPIC.cpp,_LINE=74

[ahmed_ibrahim2]

Hi Raj ,

maybe the following SAPNote will help can you check it ?

http://service.sap.com/sap/support/notes/457425

Best Regards

AhMeD

[former_member199694]

Thanks.. but ours is SCM7.01. We followed the same backup/restore procedure as outlined in the note. - Thanks.,

[former_member188883]

Hi Raj,

Which method is being used to migrate the LiveCache ?

Regards,

Deepak Kori

[former_member199694]

hi Deepak,

Initially file-systems were mounted on new h/w directly. However after seeing errors, we restored the offline data backup with initialization. Both cases, error showed up. No issues with previous settings.

when restarted LiveCache after restore:

AdminMsg       0:  52B864B70004 0000   RST RESTART

ERR SYSERROR   51080:  -9022 BD Corrupted datapage

ERR Admin     3:  Database state:OFFLINE,_FILE=Kernel_Administration+noPIC.cpp,_LINE=736

KernelComm     6:  Internal errorcode, Error code 9163 "corrupted_datapage"

ERR Admin      20017:  RestartFilesystem failed with 'System error: BD Corrupted datapage',_FILE=Kernel_Administration+noPIC.cpp,_LINE=425

ERR Data       20000:  Assertion of state Data_Chain::LastPageNo(): root not found failed!,_FILE=/SAP_DB/SCRATCH/770746_IntPaper_sun_64_01/sys/wrk/incl/SAPDB/DataAccess/Data_Chain.hpp,_LINE=596

Data       20048:  Chain: root 119104 last 2147483647 addressing: dyn recovery: perm

ERR Data       20024:  Data_Page: Data page is not assigned.,_FILE=/SAP_DB/SCRATCH/770746_IntPaper_sun_64_01/sys/wrk/incl/SAPDB/DataAccess/Data_Chain.hpp,_LINE=598

Log        20054:  HistDir: registered files 106, max used are 106

ERR Messages       7:  Begin of dump of registered messages,_FILE=Msg_List+noPIC.cpp,_LINE=3551

Log        20054:  HistDir: registered files 106, max used are 106

Thanks,

Raj

[former_member188883]

Hi Raj,

Please refer below link for the steps to migrate Livecache.

http://scn.sap.com/thread/3426641

http://scn.sap.com/thread/3426642

From the error messages it looks like data is corrupt. Reason may due to faulty disk or faulty backup.

You should try the following

1) Perform disk verification on both the servers

2) Perform new full backup and restore it again

3) Raise an OSS message to SAP Global Support.

Hope this helps.

Regards,

Deepak Kori

[former_member199694]

hi Deepak,

The change is only Solaris-10 ---> Solaris-10 in zone inside Solaris-11 global. I doubt, if this requires any Livecache migration process. The restored data was LiveCache data consistency checked and off-line backup. We made sure, no data inconsistency in the backup.

Unix team checked the disk verification on raw disks volume for data and log. We are not sure,if there any OS level settings causing the error.

Thanks,

Raj