cancel
Showing results for 
Search instead for 
Did you mean: 

Backup history file error

former_member233435
Participant
0 Kudos

For some time, error with backup history file is repeating. For example, I have MaxDB 7.9.07.10 on Suse SLES 11SP02. In Database Studio when I want to open backups I get error message:


The backup history file /sapdb/AED/data/wrk/AED/dbm.knl is corrupted in line 231

-24763,ERR_BHIST_INVALID_ENTRY: The line "5251A5280245|DAT_000000048|SAVE WARM|2013-10-06 20:00:08|2013-10-06 20:00:08|2013-10-06 20:00:10|2013-10-07 13:28:05|  19449604|          |NO |2_CompleteDataBackup                                            |  15867400|         1|      -903| " is an invalid line for the backup history

-24757,ERR_FORMAT_SEPARATORNOP: The separator '|' cannot be found 15 times within string "5251A5280245|DAT_000000048|SAVE WARM|2013-10-06 20:00:08|2013-10-06 20:00:08|2013-10-06 20:00:10|2013-10-07 13:28:05|  19449604|          |NO |2_CompleteDataBackup                                            |  15867400|         1|      -903| "

-24762,ERR_FORMAT_SEPARATORMISSING: String " " does not contain the expected separator '|'

The backup history file /sapdb/AED/data/wrk/AED/dbm.knl is corrupted in line 231

-24763,ERR_BHIST_INVALID_ENTRY: The line "5251A5280245|DAT_000000048|SAVE WARM|2013-10-06 20:00:08|2013-10-06 20:00:08|2013-10-06 20:00:10|2013-10-07 13:28:05|  19449604|          |NO |2_CompleteDataBackup                                            |  15867400|         1|      -903| " is an invalid line for the backup history

-24757,ERR_FORMAT_SEPARATORNOP: The separator '|' cannot be found 15 times within string "5251A5280245|DAT_000000048|SAVE WARM|2013-10-06 20:00:08|2013-10-06 20:00:08|2013-10-06 20:00:10|2013-10-07 13:28:05|  19449604|          |NO |2_CompleteDataBackup                                            |  15867400|         1|      -903| "

-24762,ERR_FORMAT_SEPARATORMISSING: String " " does not contain the expected separator '|'

When I check backup log in dbacockpit I see:


*** SAVE/RESTORE result:

ERR

-24988,ERR_SQL: SQL error

-903,Host file I/O error

3,Data backup failed

1,Backupmedium #1 (/mnt/backup/data/2_completeDataBackup.aed)                                     

Backup error occured, Error code 3700 "hostfile_error"

*** SAVE/RESTORE request:

SAVE DATA CANCEL

*** SAVE/RESTORE request accepted:

OK

*** SAVE/RESTORE result:

ERR

-24988,ERR_SQL: SQL error

-104,DBM command impossible at this time

*** DBA Action ends:

Timestamp: 20131230161007   State:    Failure

It disturbs our backup quite a bit, backup can't be continued until I manually delete wrong lines in file /sapdb/AED/data/wrk/AED/dbm.knl, for example:


5251A5280245|DAT_000000048|SAVE WARM|2013-10-06 20:00:08|2013-10-06 20:00:08|2013-10-06 20:00:10|2013-10-07 13:28:05|  19449604|          |NO |2_CompleteDataBackup

                           |  15867400|         1|      -903|^A^@^@^@^@^@^@^@305<U+05CD>^@^@^@^@^@ 1)322300^?^@^@'1)322300^?^@^@01)322300^?^@^@|

Is this MaxDB error or is there something I can do to stop this error happening again?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Folks,         

I'm glad to tell you that the problem is now fixed in Version 7.9.08 - it will be delivered with Patch-Level 18. We had already development close for Patch-Level 17 - therefore the fix won't be part of Patchlevel 17.

If this problem also exists in 7.8 and 7.7 the fix will be released for these versions as well. For this versions7.7.7 and 7.8.02 the patch-level is not known so far.

Regards, Christiane

Former Member
0 Kudos

Hi Christiane,

Glad to hear that it's fixed.

Regards,

Lei

former_member233435
Participant
0 Kudos

This is really good news, I hope the patch will be released soon.

Former Member
0 Kudos


Hi,

we just deleivred 7.9.08.17 which does not include the fix.

Next build which includes the fixed is planned for Q2 2014.

Regards, Christiane

Private_Member_739866
Participant
0 Kudos

Hi,

Use below procedure

1. Go to /sapdb/SRD/data/wrk

2. cp -rp dbm_knl dbm_knl_OLD

3. vi +<Line in which the corruption occured> dbm.knl

  • see there must be a corruption in the given line and it will specified with a green color
  • delete that part and make the format as per the above line

4. save the file

5. execute the procedure again from Database studio or Database Manager

(Note: Make sure that you have taken the backup first of dbm.knl file Because any extra entry may cause another corruption)

(FYI : This file is only log file of successful backups and returns the return-code)

Regards,

Paramvirsinh Jetawat

SAP BASIS Consultant

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

one additional question - after you corrected the lines manually - does the prolbem happens frequently again and the file is corrupted again?

Since when does this error orruc? Did you install a new database version -> Please check parameter hsitory for KernelVersion and does this fit to the errors which occur now?

Are you running the MaxDB on a UNIX SUN system?

There are known issues which happen on SUN and always the Comment column was affected.

When this happens at the same time the backup failed with the error messages like those:

Backup         1:  Backupmedium #1 (/sapdb/C1T/PIPE/NSRC1T_01) mismatch: checked and expected type
KernelComm     6:  Backup error occured, Error code 3700 "hostfile_error"

Unfortunately there is no fix for this error so far (PTS: 1241472).

But it would be interesting if you are also using SUN.

If you are a SAP customer I would ask for opening an error ticket in SAP support system on component BC-DB-SDB.

Regards, Christiane

former_member233435
Participant
0 Kudos

This error is intermittent. The last time it happened it resulted in stuck db - because of errors in this file logs could not be backed up and in combination with some other conditions it almost resulted in loss of db which is very important, that would have significant consequences for me. I repair file manually and unpredictably it get's corrupted again.

I've got support about this error from SAP but not very helpful, what they told me basically was, repair it manually. This makes backup and even maxdb itself unreliable. For sure, such a simple error that is not hard to trace and repair over such a long period of time (from sap notes I saw this error reported since 2012) and that makes maxdb development team look unprofessional.

I have several maxdb 7.9 based system, some of them in the latest version (and patch) and this error still occurs.

As I wrote, we are using SLES 11SP02, specific version for SAP.

This is unacceptable. I wish we could use Oracle in stead.

Former Member
0 Kudos

Hi Sasa,

I understand your problem - I will see what I can do.

Important for me is the ticket number at SAP from 2012.

Regards, Christiane

Former Member
0 Kudos

Hi Sasa,

The same error occurred to our system (SLES 11 SP2, Max DB 7.9.08, SAP ERP EHP6) when I checked the backup tab on MaxDB Studio today. The consequence is that I couldn't display backup history from DB studio and "Automatic log backup" feature is also closed automatically which resulted in DB hang this morning because of full log area. I removed the wrong code from <SID>.knl under /sapdb/<SID>/data/wrk and dbm.knl under ../wrk/<SID> like below but not deleted the whole line. After that I reopened the Studio and can display backup tab successfully.

The possible reason from my side maybe that the file system of the backup destination is full. I'll setup an environment recent days to test and will let you know.

Before:

After:

Regards,

Lei

Former Member
0 Kudos

Hi Folks,

yes we observedsuch corrupted dbm.knl when the file system was full - nevertheless with 1241467

it is planned to fix this issue soon.

Please be a little bit more patient - SAP is working on a fix.

Regards, Christiane

former_member233435
Participant
0 Kudos

Hi Christiane,

Support pointed me to note 1720923 - Corrupt entries in the backup history dbm.knl. Note dates from 22.5.2012. but the problem is not resolved to this date.

Although in my case filesystem was not full, it is important for backup to check and handle gracefully such a condition (file system full, remote file system not accessible, write/read could not be made for whatever reason,...).

I hope it will be resolved soon as you said.

Regards,

Sasha

Former Member
0 Kudos

Hi Sasha,

Ok I cannot tell you when the fix will be available but I know from the responsible developer that he has this issue on his to do list.

I checked the usage of the note and it looks like only one customer had this problem in the past. Now we are knowing about 3 customers.

Regards, Christiane