Skip to Content
0

MaxDB 7.9 Log File missing

Mar 03, 2017 at 08:50 AM

242

avatar image

Dear Community,

unfortunately we ran into the following issue on our SAP ECC 6.0 EhP8 Demo System:

In MaxDB 7.9 we activated automatic Log Backup to a System Drive, which ran full yesterday (DB Used space is 134 GB, Backup Drive ran over 200 GB).

Database is now offline, saying that the Logarea could not be opened. According to DB Studio there should be two files DISKL001 and DISKL002, but If I open the Log File Folder, the second File is missing!

I found the following help on research in order to recreate the Log Files.

https://wiki.scn.sap.com/wiki/display/MaxDB/System+errors+category+4

https://archive.sap.com/discussions/thread/1054826

But if I try to create a Full Backup using DB Studio or DBMCLI, I get the message:

message -9209,System error: logpage_not_found 61,The logarea could not be opened

Last Full Backup is too old to recover.

Do you have any ideas how to recreate the Log Files or create a Full Backup in order to make the recovery out of it afterwards?

DB Version is 7.9.09.04, OS is Win Server 2016 64 bit

Thanks in advance,

Robin

screenshot-1.png (10.9 kB)
10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

James Zhang
Mar 06, 2017 at 12:36 AM
0

Hi Robin

Please attach diagpack.tgz file after executing following command?

dbmcli -d <dbsid> -u <username>,<password> diag_pack

Best regards,
James

Share
10 |10000 characters needed characters left characters exceeded
Robin Wennemuth Mar 06, 2017 at 08:47 AM
0

Hi James,

thanks for your Support. File could not be attached, as SCN does not support "tgz" Attachments.

So please use this Link: http://projektraum36.de/files/diagpack.tgz

In case you work for SAP Support - I opened an SAP Incident recently as well.

Thanks for your help!

Best regards,

Robin

Share
10 |10000 characters needed characters left characters exceeded
Robin Wennemuth Mar 10, 2017 at 02:47 PM
0

Just in case someone comes across this issue, SAP Support helped me:

Fortunately, there were no long-running transactions in the log volume. Therefore we were able to recreate the log volume using the dbmcli command 'util_execute clear log' in Admin mode. Afterwards I could bring the database online again and create a Full Backup.

Best regards,

Robin

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Hi Robin,

Log area 2 was added at 2017-03-02 20:29:39, so I assume removing log area 2 parameter from parameter file will also work.

Anyway, glad to know you solved this issue. After log area clear, please run a complete backup as soon as possible.

Best regards,
James

0