cancel
Showing results for 
Search instead for 
Did you mean: 

MaxDb backup won't run because thinks one is already running but is not!

Former Member
0 Kudos

I'm trying to backup my production livecache maxdb database, but am getting errors (-104, -7079) indicating a backup or other dbm command is already running, but IT IS NOT!

Is there any way to clear this condition so a backup can be taken, without bouncing this production db?

Thanks!

Jesse

Accepted Solutions (1)

Accepted Solutions (1)

former_member207465
Participant
0 Kudos

This sounds like old versions (< 7.5.00) bug. Try the following:

Define a backup medium of type FILE with a path that does not exist so

that it cannot be accessed. Start a log backup with this medium. The

suspended task is released during backup error handling, and the backup

can then be executed with the correct mediums.

Answers (2)

Answers (2)

Former Member
0 Kudos

az18u3387 DR for az18u248:/ # su - adpadm

az18u248:adpadm> dbmcli inst_enum

OK

7.6.00.35 /sapdb/ADP/db

az18u248:adpadm> dbmcli db_enum

OK

ADP /sapdb/ADP/db 7.6.00.35 fast running

ADP /sapdb/ADP/db 7.6.00.35 quick offline

ADP /sapdb/ADP/db 7.6.00.35 slow offline

ADP /sapdb/ADP/db 7.6.00.35 test offline

az18u248:adpadm>

az18u248:adpadm> xinstinfo ADP

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

InstallationPath : /sapdb/ADP/db

Kernelversion : KERNEL 7.6.00 BUILD 035-123-139-084

Rundirectory : /sapdb/data/wrk/ADP

az18u248:adpadm>

dbmcli on ADP>medium_getalll

OK

log_backup_tsm /sapdb/ADP/backup/log_backup_tsm PIPE LOG 0 8 NO NO 20101217070405 20101217070405 BACK

backup_to_filesystem /sapdb/ADP/sapdata2/temp_log_backup/log_backup_fs FILE AUTO 0 8 NO NO 20101217071653 20101217071653 NONE

data_backup_tsm /sapdb/ADP/backup/data_backup_tsm PIPE DATA 0 8 NO NO 20110614222320 20110614222320 BACK

TSM_backup /sapdb/ADP/backup/tsm_medium PIPE DATA 0 8 NO NO 20110620093743 20110620093743 BACK

BACKORA /sapdb/ADP/backup/medium PIPE DATA 0 8 NO NO 20110620094357 20110620094357 BACK

BACKLOG /sapdb/ADP/backup/medium_log PIPE LOG 0 8 NO NO 20110620094414 20110620094414 BACK

az18u248:adpadm> x_cons ADP show active

SERVERDB: ADP

ID UKT UNIX TASK APPL Current Timeout Region Wait

tid type pid state priority cnt try item

T73 4 -1 BUPvol -1 Vsuspend (203) 0 0 1662580(s)

az18u248:adpadm>

Above is in answer to the 1st questions asked in the last post.

Not sure how to answer question 3...

3. What command did you run & what error exectly did you get?

Check dbm.prt and knldiag &lt; KnlMsg as of 7.7 &gt; files.

...I was taught to use the dbm.ebp file for troubleshooting.

Errors were -104 and -7079

former_member229109
Active Contributor
0 Kudos

Hello,

Run http://maxdb.sap.com/webpts -> Advanced Search

Search PTS by number :: 1141926

Then display it.

You hit the old bug.

Preconditions and circumstances for this issue:

A logbackup into a pipe has been interrupted due to a broken pipe.

You could use recommended Workaround:

Define e backupmedium of the type FILE , which cannot been accessed properly (e.g. containing a non exisiting path). Start a logbackup onto this medium. During the errorhandling the suspended task will be resumed properly.

You have quit old version of database - 7.6.00.35. Update the database to the new patch, as you saw in PTS the issue already fixed.

Regards, Natalia Khlopina

Former Member
0 Kudos

I've tried the recommended work-around suggested by you and one other person who posted here.

It did not clear the error condition ... still getting -7079.

Bounced the database. NO HELP!!!

Previously a bounce resolved this!

Any more suggestions appreciated.

former_member229109
Active Contributor
0 Kudos

Hello,

1. Could you stop the database, start in admin & create the log backup using the medium definition - FILE.

Let me know if the logbackup was created successfuly.

Check the dbm.prt, Knldiag and dbm.knl files.

2. If you have not log_full issue => update the database.

Are you SAP customer => if yes, then open the SAP message, it will be helpful to check the database logs and the backup's medium definitions.

Regards, Natalia Khlopina

former_member229109
Active Contributor
0 Kudos

Hello Jesse,

1. What is the version of your database?

Post output of the commands:

dbmcli inst_enum

dbmcli db_enum

xinstinfo <SID>

and output of dbm command:

medium_getall

2. Please post the output of the command:

x_cons <SID> show active

3. What command did you run & what error exectly did you get?

Check dbm.prt and knldiag < KnlMsg as of 7.7 > files.

Thank you and best regards, Natalia Khlopina