on 06-26-2007 2:05 PM
Hello experts,
We have a problem with brbackup stopping during the backup with the error in the subject. It is always at he same point in the backup procedure. Sometimes the backup finishes OK, other times we get the signal 13.
A search on Google didn't help...just a few hits with the big difference that in those cases brbackup crashed immediately with signal 13. In our case the backup starts fine and we get the signal 13 later on.
Has anyone encountered this error before?.
We have an oracle database (10.2.0.2.0) en we do a backup (allonl+log) with backint into TSM
Examples from logfiles:
Backup OK
...
BKI0021I: Elapsed time: 05 h 46 min 06 sec .
BKI0024I: Return code is: 0.
BR0280I BRBACKUP time stamp: 2007-06-23 03.46.46
BR0232I 17 of 17 files saved by backup utility
BR0230I Backup utility called successfully
BR0280I BRBACKUP time stamp: 2007-06-23 03.46.50
-
BR0317I 'Alter database end backup' successful
BR0280I BRBACKUP time stamp: 2007-06-23 03.46.51
BR0340I Switching to next online redo log file for database instance <Instance> ...
BR0321I Switch to next online redo log file for database instance <Instance> successful
BR0117I ARCHIVE LOG LIST after backup for database instance <Instance>
Backup Wrong
...
BKI0021I: Elapsed time: 07 h 06 min 18 sec .
BKI0024I: Return code is: 0.
BR0280I BRBACKUP time stamp: 2007-06-22 05.07.04
BR0232I 17 of 17 files saved by backup utility
BR0230I Backup utility called successfully
BR0280I BRBACKUP time stamp: 2007-06-22 05.07.05
-
BR0261E BRBACKUP cancelled by signal 13
BR0280I BRBACKUP time stamp: 2007-06-22 05.07.07
BR0317I 'Alter database end backup' successful
BR0056I End of database backup: bdvnothr.anf 2007-06-22 05.07.06
BR0280I BRBACKUP time stamp: 2007-06-22 05.07.07
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2007-06-22 05.07.07
BR0291I BRARCHIVE will be started with options '-U -jid ALLOG20070621220000 -d util_file -c force -p init<Instance>.sap -cds'
BR0280I BRBACKUP time stamp: 2007-06-22 05.16.05
BR0292I Execution of BRARCHIVE finished with return code 0
tnx for your time..
Regards
Dirk Visser
It seams that signal 13 is resolved.
The backups are made now directly to the tape and DASD pool is not used any more.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
refer Note 375252 - SAPDBA: "brtools canceled by signal 13"
Regards,
Suraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Signal 13 is "SIGPIPE" (Broken pipe), the backup process gets stopped because the pipe is closed.
I could imagine this to be a timing problem between brbackup starting to write to the pipe and TSM having created the pipe and closing it too early.
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.