Skip to Content
author's profile photo Former Member
Former Member

Issue with backups

Hi All,

We have been observing that backups are failing.

Getting a message saying that 0003 Error during initialization

BR0051I BRBACKUP 7.20 (3)

BR0055I Start of database backup: beehthla.anf 2010-10-11 03.00.02

BR0484I BRBACKUP log file: /oracle/DB2/sapbackup/beehthla.anf

BR0071E BRBACKUP currently running or was killed

BR0072I Please delete file /oracle/DB2/sapbackup/.lock.brb if BRBACKUP was killed

BR0073E Setting of BRBACKUP lock failed

BR0056I End of database backup: beehthla.anf 2010-10-11 03.00.02

BR0280I BRBACKUP time stamp: 2010-10-11 03.00.03

BR0054I BRBACKUP terminated with errors

When i open the file it has oradb2 2> more /oracle/DB2/sapbackup/.lock.brb

FULL PID=14801

When i check for the same at the os level i get the below output.Could anyone help regarding the same.Thanks.

<hostname>:oradb2 3> ps -ef | grep -i 14801

oradb2 14801 14678 0 Oct09 ? 00:00:01 brbackup -u / -c -t online_cons -a -c -cds

oradb2 14802 14801 0 Oct09 ? 00:00:00 [oracle] <defunct>

oradb2 14805 1 0 Oct09 ? 00:00:46 /usr/sap/DB2/SYS/exe/run/brconnect -O 14801

oradb2 14806 14801 0 Oct09 ? 00:00:00 sh -c ( /usr/sap/DB2/SYS/exe/run/backint -u DB2 -f backup -i /oracle/DB2/sapbackup/.beehjluw.lst -t file_online -p /oracle/DB2/102_64/dbs/initDB2.utl -c ) 2>&1

oradb2 30910 30775 0 17:40 pts/2 00:00:00 grep -i 14801

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    Posted on Oct 11, 2010 at 05:34 PM

    Hello,

    so the message did tell you

    >BR0071E BRBACKUP currently running or was killed

    You did check

    > When i open the file it has oradb2 2> more /oracle/DB2/sapbackup/.lock.brb

    > FULL PID=14801

    >

    > <hostname>:oradb2 3> ps -ef | grep -i 14801

    > oradb2 14801 14678 0 Oct09 ? 00:00:01 brbackup -u / -c -t online_cons -a -c -cds

    and you obviously found a backup still running...

    Now you decided to fiddle with this semaphor file! WHY ?

    Your backup was still active for whatever reason.

    Your doing a backup to an external backup utility and may be your session was still waiting for a mount confirm or whatever.

    Now the correct solution would have been to check out your external backup tool.

    If anything had been blown there, your next approach should have been to kill the running "brbackup"

    and not by giving it a "kill -9 " headshot as so many people do, but just a calm friendly standard "kill"

    which will send a SIGTERM and allows brbackup to clean up all things to the finest,

    which includes a proper deletion of this semaphor file.

    You should only delete these .lock files if you are very certain, that the action that these .locks are

    protecting are really completed or really aborted.

    This is even worse with RMAN backups and 3rd party tools, because you can still have active sessions

    in ST04 while brbackup is already dead. In this case you need to terminate these first even if brbackup

    is already able to start again!

    So how many brbackups do you have active, now that you deleted the lock file and I guess you

    give a try (or two?) for a restart ....

    Volker

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 11, 2010 at 06:49 AM

    Hi,

    As mentioned in the log, delete the file .lock.brb from the location /oracle/DB2/sapbackup and then re-execute the backup(make sure that there are no backups being executed).

    The .lock.brb sets a lock such that the database will not be backed up until the current backup completes. Once the backup is completed, this file will be removed from that location allowing us to backup the DB again.

    In case if the backup is disturbed abruptly the .lock.brb remains and thus not allowing us to take a backup.

    Hope this clarifies.

    Regards,

    Varadharajan M

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      >Whats with the defunct process

      I suspect some sql qury is running in background.

      If sqlplus is running as background process and it become idle (no active SQL) will be not finished until it will be killed or taken to foreground using fg (UNIX command).

      Be aware if you want to shutdown database and you have some sqlplus'es in background

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.