Tran log backup fail after setting a DB offline

This is strange. SQL 2005 SP3 (build 4340). Full backup job and tran log backup job are separate maint plans/Agent jobs as opposed to multiple steps in one maint plan (don't ask me... I didn't set it up that way.)
I set a database XYZ offline last night at around 9pm. It was last backed up at 8pm (full recovery mode). My tran log backup started failing then. This morning, I detached the database. Tran log backup job still failing.
I finally realized it had something to do with database XYZ so I re-attached it. Tran log backup working now. The weird thing is that XYZ had not been selected only specific databases, and the detached database isn't selected. I
tried setting to simple recovery mode and doing a final full backup before detaching, but tran log job still fails. How can I get rid of database XYZ without the tran job failing? Thanks.

I have encountered this problem. I concur with EA. But you would need to modify the maintenance plan and save it (uncheck and check a database again) to rectify the problem (if you just open the maintenance plan and save it, it will still fail)
Satish Kartan http://www.sqlfood.com/

Similar Messages

Getting error while taking MAX DB trans log backup.

Hi,
I am getting error while taking trans log backup of Maxdb database for archived log through data protector as below,
[Critical] From: OB2BAR_SAPDBBAR@ttcmaxdb "MAX" Time: 08/19/10 02:10:41
Unable to back up archive logs: no autolog medium found in media list
But i am able to take complete data and incremental backup through data protector.
I have already enabled the autolog for MAX DB database and it is writing that log file directly to HP-UX file system. Now i want to take backup of this archived log backup through data protector i.e. through trans log backup. So that the archived log which is on the file system after trans log backup completed will delete the archived logs in filesystem. So that i don;t have to manually delete the archived logs from file system.
Thanks,
Subba

Hi Lars,
Thanks for the reply...
Now i am able to take archive log backup but the problem is i can take only one archive file backup. Not multiple arhive log files generated by autolog at filesystem i.e /sapdb/MAX/saparch.
I have enabled autolog and it is putting auto log file at unix directory i.e. /sapdb/MAX/saparch
And then i am using the DataProtector 6.11 with trans log backup to backup the archived files in /sapdb/MAX/saparch. When i start the trans backup session through data protector it uses the archive stage command as "archive_stage BACKDP-Archive LOGBackup NOVERIFY REMOVE" If /sapdb/MAX/saparch has only one archive file it will backup and remove the file successfully. But if /sapdb/MAX/saparch has multiple archive files it gives an error as below,
Preparing backup.
            Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
            Setting environment variable 'BI_REQUEST' to value 'OLD'.
            Setting environment variable 'BI_BACKUP' to value 'ARCHIVE'.
            Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.
bsi_in -c'.
            Created temporary file '/var/opt/omni/tmp/MAX.bsi_out' as output for Backint for MaxDB.
            Created temporary file '/var/opt/omni/tmp/MAX.bsi_err' as error output for Backint for MaxDB.
            Writing '/sapdb/data/wrk/MAX/dbm.ebf' to the input file.
            Writing '/sapdb/data/wrk/MAX/dbm.knl' to the input file.
        Prepare passed successfully.
        Starting Backint for MaxDB.
            Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.
bsi_in -c >>/var/opt/omni/tmp/MAX.bsi_out 2>>/var/opt/omni/tmp/MAX.bsi_err'.
            Process was started successfully.
        Backint for MaxDB has been started successfully.
        Waiting for the end of Backint for MaxDB.
            2010-09-06 03:15:21 The backup tool is running.
            2010-09-06 03:15:24 The backup tool process has finished work with return code 0.
        Ended the waiting.
        Checking output of Backint for MaxDB.
        Have found all BID's as expected.
    Have saved the Backup History files successfully.
    Cleaning up.
        Removing data transfer pipes.
            Removing data transfer pipe /var/opt/omni/tmp/MAX.BACKDP-Archive.1 ... Done.
        Removed data transfer pipes successfully.
        Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
            #SAVED 1009067:1 /sapdb/data/wrk/MAX/dbm.ebf
            #SAVED 1009067:1 /sapdb/data/wrk/MAX/dbm.knl
End of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
        Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAX.bsi_out'.
        Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
        Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAX.bsi_err'.
        Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAX.bsi_in'.
    Have finished clean up successfully.
The backup of stage file '/export/sapdb/arch/MAX_LOG.040' was successful.
2010-09-06 03:15:24
Backing up stage file '/export/sapdb/arch/MAX_LOG.041'.
    Creating pipes for data transfer.
        Creating pipe '/var/opt/omni/tmp/MAX.BACKDP-Archive.1' ... Done.
    All data transfer pipes have been created.
    Preparing backup tool.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'OLD'.
        Setting environment variable 'BI_BACKUP' to value 'ARCHIVE'.
        Constructed Backint for MaxDB call '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.bsi_
in -c'.
        Created temporary file '/var/opt/omni/tmp/MAX.bsi_out' as output for Backint for MaxDB.
        Created temporary file '/var/opt/omni/tmp/MAX.bsi_err' as error output for Backint for MaxDB.
        Writing '/var/opt/omni/tmp/MAX.BACKDP-Archive.1 #PIPE' to the input file.
    Prepare passed successfully.
    Constructed pipe2file call 'pipe2file -d file2pipe -f /export/sapdb/arch/MAX_LOG.041 -p /var/opt/omni/tmp/MAX.BACKDP-Archive.1 -nowait'.
    Starting pipe2file for stage file '/export/sapdb/arch/MAX_LOG.041'.
        Starting pipe2file process 'pipe2file -d file2pipe -f /export/sapdb/arch/MAX_LOG.041 -p /var/opt/omni/tmp/MAX.BACKDP-Archive.1 -nowait >>/var/tmp/tem
p1283767880-0 2>>/var/tmp/temp1283767880-1'.
        Process was started successfully.
    Pipe2file has been started successfully.
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process '/opt/omni/lbin/sapdb_backint -u MAX -f backup -t file -p SAPDB.13576.1283767878.par -i /var/opt/omni/tmp/MAX.bsi_
in -c >>/var/opt/omni/tmp/MAX.bsi_out 2>>/var/opt/omni/tmp/MAX.bsi_err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    Waiting for end of the backup operation.
        2010-09-06 03:15:25 The backup tool process has finished work with return code 2.
        2010-09-06 03:15:25 The backup tool is not running.
        2010-09-06 03:15:25 Pipe2file is running.
        2010-09-06 03:15:25 Pipe2file is running.
        2010-09-06 03:15:30 Pipe2file is running.
        2010-09-06 03:15:40 Pipe2file is running.
        2010-09-06 03:15:55 Pipe2file is running.
        2010-09-06 03:16:15 Pipe2file is running.
        Killing not reacting pipe2file process.
        Pipe2file killed successfully.
        2010-09-06 03:16:26 The pipe2file process has finished work with return code -1.
    The backup operation has ended.
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes and pipe2file was killed.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes and pipe2file was killed.
    Reply buffer filled.
    Cleaning up.
        Removing data transfer pipes.
            Removing data transfer pipe /var/opt/omni/tmp/MAX.BACKDP-Archive.1 ... Done.
        Removed data transfer pipes successfully.
        Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
End of output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_out)----
        Removed Backint for MaxDB's temporary output file '/var/opt/omni/tmp/MAX.bsi_out'.
        Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
End of error output of Backint for MaxDB (/var/opt/omni/tmp/MAX.bsi_err)----
        Removed Backint for MaxDB's temporary error output file '/var/opt/omni/tmp/MAX.bsi_err'.
        Removed the Backint for MaxDB input file '/var/opt/omni/tmp/MAX.bsi_in'.
        Copying pipe2file output to this file.
Begin of pipe2file output (/var/tmp/temp1283767880-0)----
End of pipe2file output (/var/tmp/temp1283767880-0)----
        Removed pipe2file output '/var/tmp/temp1283767880-0'.
        Copying pipe2file error output to this file.
Begin of pipe2file error output (/var/tmp/temp1283767880-1)----
End of pipe2file error output (/var/tmp/temp1283767880-1)----
        Removed pipe2file error output '/var/tmp/temp1283767880-1'.
    Have finished clean up successfully.
The backup of stage file '/export/sapdb/arch/MAX_LOG.041' was unsuccessful.
2010-09-06 03:16:26
Cleaning up.
    Have encountered error -24919:
        Can not remove file '/var/tmp/temp1283767880-0'.
        (System error 2; No such file or directory)
    Could not remove temporary output file of pipe2file ('/var/tmp/temp1283767880-0' ).
    Have encountered error -24919:
        Can not remove file '/var/tmp/temp1283767880-1'.
        (System error 2; No such file or directory)
    Could not remove temporary output file of pipe2file ('/var/tmp/temp1283767880-1' ).
Have finished clean up successfully.
Thanks,
Subba

Backup Fails after several successful days - errors "Device is not ready" & "The System cannot find the path specified"

Well I am back again, with another backup issue. After fixing one issue with the backup failing after a reboot, I have encountered another which is starting to cause me a lot of headaches.
The setup is thus - the backups run on a host machine running Windows Server 2012, this hosts three VM's (1x Server 2012 and 2x2008 Since the 19th of December a single backup drive has been attached for the backups (not ideal but the company had closed for
the holidays) up until the 26th these backups were working flawlessly.
On the 26th the backup completed with warnings, transferring a good 90% of the data to the backup (2/3 VMs). On the 27th it transferred a bit more at around 95% (2/3 VMs). On the 28th, it didn't completely backup a single VM.
On the 28th this error appeared in the event logs and after checking in the snap-in the same errors appear on the warning days as the errored day.
The backup operation that started at '‎2014‎-‎12‎-‎28T20:30:09.774946400Z' has failed with following error code '0x80780049' (None of the items included in backup were backed up.). Please review the event details for a solution, and then rerun the backup
operation once the issue is resolved.
Thanks in advance/

Hi,
Please check the detailed error message in the backup log files in C:\Windows\Logs\WindowsServerBackup. In additional, you could go through the similar thread to help troubleshoot this issue:
Windows 2012 Backup for HyperV failed with error code '0x80780049'
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f1a0c9c6-7b4c-409c-b4da-c145b8b59eb1/windows-2012-backup-for-hyperv-failed-with-error-code-0x80780049?forum=winserverhyperv
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Redo log backup failed

Hi,
My redo log backup failed and I've no clue on the errors. Below is the job log. Please advise. TIA !
Job started
Step 001 started (program RSDBAJOB, variant &0000000000064, user ID BACKUP_USER)
No application server found on database host - rsh/gateway will be used
Execute logical command BRARCHIVE On host bering
Parameters:-u / -jid LOG__20090313130000 -c force -p initprd.sap -cds
SXPG_COMMAND_EXECUTE(LONG)
COMMANDNAME = BRARCHIVE
OPERATINGSYSTEM = ANYOS
TARGETSYSTEM = bering
DESTINATION = SAPXPG_DBDEST_BERING
BR0002I BRARCHIVE 7.00 (32)
BR0181E Option '-cds' not supported for 'disk'
BR0007I End of offline redo log processing: aeactnyg.log 2009-03-13 13.00.19
BR0280I BRARCHIVE time stamp: 2009-03-13 13.00.21
BR0005I BRARCHIVE terminated with errors
External program terminated with exit code 3
BRARCHIVE returned error status E
Job finished
DL

Hi,
You tried to backup redo log on disk.
Option -cds (create second copy, delete and the first copy serial) is not supported when you do a redolog backup using disk as backup device type.
Try to change the option to -sd (save first copy and delete)
rgds,
fendhy.

Redo log backup failing with BR253E errno 2:

Hi all,
I am able to take online as well as offline backup through sapdba , but unfortunately from last 7 days my redo log backup is failing after online backup is complete with below mentioned error. I also tried to start redo log backup seperately but failed as below...
BR002I BRARCHIVE 6.20 (18)
BR006I Start of offline redo log processing: adwpawsw.sve 2007-11-13 21.33.22
BR280I Time stamp 2007-11-13 21.33.25
BR008I Offline redo log processing for database instance: PRD
BR009I BRARCHIVE action ID: adwpawsw
BR010I BRARCHIVE function ID: sve
BR048I Archive function: save
BR011I 195 offline redo log files found for processing, total size 9469.831 MB
BR112I Files will not be compressed
BR130I Backup device type: disk
BR106I Files will be saved on disk in directory: F:\oracle\PRD\sapbackup
BR126I Unattended mode active - no operator confirmation required
BR202I Saving init_ora
BR203I to F:\oracle\PRD\sapbackup\PRD ...
BR202I Saving o:\orcle\prd\920\DATABASE\initPRD.sap
BR203I to F:\oracle\PRD\sapbackup\PRD ...
BR280I Time stamp 2007-11-13 21.33.26
BR198I Profiles saved successfully
BR252E Function fopen() failed for 'F:\oracle\PRD\sapbackup\.PRD/oraarch/PRDarch
ARC10479.001' at location arch_process-4
BR253E errno 2: No such file or directory
BR121E Processing log file F:\oracle\PRD\sapbackup\.PRD/oraarch/PRDarchARC10479.
001 failed
BR016I 0 offline redo log files processed, total size 0.000 MB
BR007I End of offline redo log processing: adwpawsw.sve 2007-11-13 21.33.26
BR280I Time stamp 2007-11-13 21.33.26
BR005I BRARCHIVE terminated with errors
End of output from program 'BRARCHIVE' -
SAPDBA: Execution of BRARCHIVE failed.
 (2007-11-13 21.33.27)
Press <return> to continue ...
SAPDBA: Last line from BRARCHIVE summary log:
 '#* PRD disk adwpawsw sve 2007-11-13 21.33.22 2007-11-13 21.33.26
 5 ........... -
c 6.20 (18)'
Press <return> to continue ...
Appreciate your quick replies.
Best Regards,
AjitR

Unfortunately backlogs point to directory
'F:\oracle\PRD\sapbackup\.PRD
But i have my logfiles getting archived at D:\oracle\PRD\oraarch
and they are supposed to be backed up at F:\oracle\PRD\sapbackup
Below is my init.sap file for your ref, i cant find where this .PRD folder came from
backup mode [all | all_data | full | incr | sap_dir | ora_dir
| <tablespace_name> | <file_id> | <file_id1>-<file_id2>
| <generic_path> | (<object_list>)]
default: all
backup_mode = all
restore mode [all | all_data | full | incr | incr_only | incr_full
| <tablespace_name> | <file_id> | <file_id1>-<file_id2>
| <generic_path> | (<object_list>)]
redirection with '=' is not supported here - use option '-m' instead
default: all
restore_mode = all
backup type [offline | offline_force | offline_standby | offline_split
| offline_stop | online | online_cons | online_split]
default: offline
backup_type = offline
backup device type
[tape | tape_auto | tape_box | pipe | pipe_auto | pipe_box | disk
| disk_copy | disk_standby | stage | stage_copy | stage_standby
| util_file | util_file_online | rman_util | rman_disk | rman_stage
| rman_prep]
default: tape
#backup_dev_type = tape
backup_dev_type = disk
backup root directory [<path_name> | (<path_name_list>)]
default: %SAPDATA_HOME%\sapbackup
#backup_root_dir = D:\oracle\PRD\sapbackup
backup_root_dir = F:\oracle\PRD\sapbackup
stage root directory [<path_name> | (<path_name_list>)]
default: value of the backup_root_dir parameter
#stage_root_dir = D:\oracle\PRD/sapbackup
stage_root_dir = F:\oracle\PRD\sapbackup
compression flag [yes | no | hardware | only]
default: no
compress = no
compress command
first $-character is replaced by the source file name
second $-character is replaced by the target file name
<target_file_name> = <source_file_name>.Z
for compress command the -c option must be set
recommended setting for brbackup -k only run:
"%SAPEXE%\mkszip -l 0 -c $ > $"
no default
compress_cmd = "@SAPEXE@\mkszip -c $ > $"
uncompress command
first $-character is replaced by the source file name
second $-character is replaced by the target file name
<source_file_name> = <target_file_name>.Z
for uncompress command the -c option must be set
no default
uncompress_cmd = "@SAPEXE@\uncompress -c $ > $"
directory for compression [<path_name> | (<path_name_list>)]
default: value of the backup_root_dir parameter
#compress_dir = D:\oracle\PRD/sapreorg
compress_dir = F:\oracle\PRD\sapreorg
brarchive function [save | second_copy | double_save | save_delete
| second_copy_delete | double_save_delete | copy_save
| copy_delete_save | delete_saved | delete_copied]
default: save
archive_function = save
directory for archive log copies to disk
default: first value of the backup_root_dir parameter
#archive_copy_dir = D:\oracle\PRD/sapbackup
archive_copy_dir = F:\oracle\PRD\sapbackup
directory for archive log copies to stage
should contain <SID> subdirectory
default: first value of the stage_root_dir parameter
#archive_stage_dir = D:\oracle\PRD/sapbackup
archive_stage_dir = f:\oracle\PRD\sapbackup
new database home directory for disk_copy | disk_standby
no default
new_db_home = X:\oracle\C11
stage database home directory for stage_copy | stage_standby
default: value Cof the new_db_home parameter
stage_db_home = /oracle/C11
original database home directory for split mirror disk backup
no default
orig_db_home = /oracle/C11

Time Machine Backup fails after Restore

Had my 500GB HD on my iMac fail. After being replaced by Apple, I performed a restore from 1TB time machine backup. After this was done, I set time machine back up to back up to this 1TB drive. I want it to append to the previous backups. However, the backup fails due to "backup is too large for the backup volume". It doesn't seem to want to append to previous backups but thinks this is an entirely new backup, which I guess is mostly true. I suspect this has to do with UUIDs of the new and old drives, but I'm not sure how to correct it (I'd prefer not to just wipe the backup disk and start over). I migrated backups before from one extenal HD to another but can't remember what I did... If anyone has steps to fix this, let me know em. Thanks.
Here's the time machine log:
Starting standard backup
Backing up to: /Volumes/MyBook-Mac/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Starting pre-backup thinning: 506.55 GB requested (including padding), 502.31 GB available
No expired backups exist - deleting oldest backups to make room
Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
Backup Failed: unable to free 506.55 GB needed space
Backup failed with error: Not enough available disk space on the target volume.
Message was edited by: Delmonte3161

Delmonte3161 wrote:
Had my 500GB HD on my iMac fail. After being replaced by Apple, I performed a restore from 1TB time machine backup. After this was done, I set time machine back up to back up to this 1TB drive. I want it to append to the previous backups. However, the backup fails due to "backup is too large for the backup volume". It doesn't seem to want to append to previous backups but thinks this is an entirely new backup, which I guess is mostly true. I suspect this has to do with UUIDs of the new and old drives,
yes, that's correct. TM will make a full backup after a full system restore on a new hard drive because the UUIDs of the new drive is different from the old one.
you may try the following hack to get around it
http://www.macosxhints.com/article.php?story=20090213071015789
But I make no promises about how well it works.
but I'm not sure how to correct it (I'd prefer not to just wipe the backup disk and start over). I migrated backups before from one extenal HD to another but can't remember what I did... If anyone has steps to fix this, let me know em. Thanks.
Here's the time machine log:
Starting standard backup
Backing up to: /Volumes/MyBook-Mac/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Starting pre-backup thinning: 506.55 GB requested (including padding), 502.31 GB available
No expired backups exist - deleting oldest backups to make room
Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
Backup Failed: unable to free 506.55 GB needed space
Backup failed with error: Not enough available disk space on the target volume.
Message was edited by: Delmonte3161

My iPhone won't back up to iCloud it says backup failed after I increased my storage plan. How can I fix that and which email can I sen to if I want to refund the storage I bought on iCloud. It says I have 15 days to return.

Which email should I send to for a refund on iCloud storage within 15 day period. Also the iPhone won't back up to iCloud it keeps saying backup failed even when I log out of iCloud and log back in how can I fix that?

If your back up continually fails, you might try turning off back up on your mobile device (settings > iCloud > storage & backup) and then deleting the backup file from iCloud by swiping the backup file on the mobile device (settings > iCloud > storage & backup > manage…) and then turning back up on again.
Being able to back up to the cloud can be very useful, especially if you don't have access to a computer or have infrequent access to one, however unless you specifically need to use iCloud for back up, you will find backing up to iTunes significantly more convenient and possibly more reliable.

MaxDB 750 LOG Backup failed

Hello,
the LOG backup of the database crashes with following error:
ERR
-24988,ERR_SQL: sql error
-8888,connection broken [183]
KNLDIAG
2005-12-06 14:18:56 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:18:56 0x370 19651 CONNECT Connection released, T4
2005-12-06 14:18:56 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:18:56 0x370 19651 CONNECT Connection released, T4
2005-12-06 14:19:57 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:19:59 0x370 19615 VOLUMEIO Attaching volume 'F:\sapdb\EXI\saplog\DISKL001'
2005-12-06 14:19:59 0x9C8 19613 DBSTATE I/O thread for 'F:\sapdb\EXI\saplog\DISKL001' started
2005-12-06 14:19:59 0x370 19617 VOLUMEIO Single I/O attach, 'F:\sapdb\EXI\saplog\DISKL001', UKT:3
2005-12-06 14:19:59 0xCB4 19625 IO Async I/O thread started, 'H:\Sicherung_XI\logs\EXI_LOG.017
2005-12-06 14:19:59 0xEE0 52101 SAVE Filetype: file
2005-12-06 14:19:59 0xEE0 52024 SAVE 200 pages -> "erung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:04 0xEE0 52024 SAVE 10800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:09 0xEE0 52024 SAVE 20000 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:14 0xEE0 52024 SAVE 29400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:19 0xEE0 52024 SAVE 39000 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:24 0xEE0 52024 SAVE 48200 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:29 0xEE0 52024 SAVE 57600 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:34 0xEE0 52024 SAVE 66800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:39 0xEE0 52024 SAVE 76400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:44 0xEE0 52024 SAVE 85400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:49 0xEE0 52024 SAVE 94800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:54 0xEE0 52024 SAVE 104000 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:20:59 0xEE0 52024 SAVE 113200 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:21:04 0xEE0 52024 SAVE 122600 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:21:09 0xEE0 ERR 0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
2005-12-06 14:21:09 0xEE0 ERR 18196 DBCRASH vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
current write position -
KNLDIAG.ERR
2005-12-06 14:18:41 --- Starting GMT 2005-12-06 13:18:41 7.5.0 Build 031-123-104-253
2005-12-06 14:21:09 0xEE0 ERR 0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
2005-12-06 14:21:09 0xEE0 ERR 18196 DBCRASH vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
in online mode the database works fine, also a full backup...
Regards,
Domi

Hi,
the reason for the problem might be a partially written logpage on a logvolume, or a non-written, but expected logpage. If this page is not found, the logbackup throws the error you received. This should be a very rare error.
In order to solve this, you could try the following:
1. Then bring the database instance to mode online
2. Then bring the database instance to mode admin
3. Clear the log:
dbmcli -d <SID> -u <controluser>,<controlpasswd> -uUTL <controluser>,<controlpasswd> util_execute clear log
4. Perform full data backup
5. Perform log backup
Regards,
Roland
P.S.: the clear log command is a 'dangerous' command, please don't use it otherwise.

Backup failed after upgrade

I just upgrade the database from 9i to 10.2.0.4. After the upgrade, the backup failed with the following error. What's wrong and how to fix? Thanks!
CBRP:/opt/app/oracle:>rman target / catalog xx/xx@cdbp
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Aug 17 08:51:03 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: CBRP (DBID=2190525556)
connected to recovery catalog database
PL/SQL package RMANNEW.DBMS_RCVCAT version 10.02.00.03 in RCVCAT database is not current
PL/SQL package RMANNEW.DBMS_RCVMAN version 10.02.00.03 in RCVCAT database is not current
RMAN> backup database;
Starting backup at 17-AUG-2009 08:51:40
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/17/2009 08:51:41
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 08/17/2009 08:51:41
RMAN-10015: error compiling PL/SQL program
RMAN-10014: PL/SQL error 0 on line 2138 column 12: Statement ignored
RMAN-10014: PL/SQL error 306 on line 2138 column 12: wrong number or types of arguments in call to 'CHECKPROXYARCHIVEDLOG'
RMAN-10014: PL/SQL error 0 on line 1970 column 12: Statement ignored
RMAN-10014: PL/SQL error 306 on line 1970 column 12: wrong number or types of arguments in call to 'CHECKBACKUPREDOLOG'
RMAN-10014: PL/SQL error 0 on line 1810 column 12: Statement ignored
RMAN-10014: PL/SQL error 306 on line 1810 column 12: wrong number or types of arguments in call to 'CHECKBACKUPREDOLOG'
RMAN-10014: PL/SQL error 0 on line 1618 column 15: Statement ignored
RMAN-10014: PL/SQL error 306 on line 1618 column 15: wrong number or types of arguments in call to 'CHECKARCHIVEDLOG'

Pl see if MOS Doc 312661.1 (Rman Resync Fails Due to Invalid Objects after Upgrading Catalog to 10g) is applicable here
HTH
Srini

Redo log backup failing

Hi everyone,
When I'm scheduling Archive log backup through DB13 the backup are failing.
Here is the logfile of the failed Redo log backup file.
2008-09-03 14:45:05 Job started
2008-09-03 14:45:05 Step 001 started (program RSDBAJOB, variant &0000000000014, user ID ROHANKU)
2008-09-03 14:45:05 Execute logical command BRARCHIVE On host ncsdev12
2008-09-03 14:45:05 Parameters:-u / -jid LOG__20080903144505 -c force -p initRD1.sap -cds
2008-09-03 14:45:53 BR0002I BRARCHIVE 7.00 (24)
2008-09-03 14:45:53 BR0006I Start of offline redo log processing: adystlhx.cds 2008-09-03 14.45.05
2008-09-03 14:45:53 BR0484I BRARCHIVE log file: /hcs/oracle/RD1/saparch/adystlhx.cds
2008-09-03 14:45:53 BR0477I Oracle pfile /hcs/oracle/RD1/102_64/dbs/initRD1.ora created from spfile /lms/oracle/RD1/102_64/dbs/spfileRD1.ora
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.07
2008-09-03 14:45:53 BR0008I Offline redo log processing for database instance: RD1
2008-09-03 14:45:53 BR0009I BRARCHIVE action ID: adystlhx
2008-09-03 14:45:53 BR0010I BRARCHIVE function ID: cds
2008-09-03 14:45:53 BR0048I Archive function: copy_delete_save
2008-09-03 14:45:53 BR0011I 1 offline redo log file found for processing, size 41.846 MB
2008-09-03 14:45:53 BR0130I Backup device type: util_file
2008-09-03 14:45:53 BR0109I Files will be saved by backup utility
2008-09-03 14:45:53 BR0134I Unattended mode with 'force' active - no operator confirmation allowed
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.07
2008-09-03 14:45:53 BR0229I Calling backup utility with function 'backup'...
2008-09-03 14:45:53 BR0278I Command output of '/usr/sap/RD1/SYS/exe/run/backint -u RD1 -f backup -i /lms/oracle/RD1/saparch/.adystlhx.lst -t file -p
2008-09-03 14:45:53 ERROR - Failed to get the policy method type: LNSDQP10-SAP
2008-09-03 14:45:53 ERROR: incorrect format or option in .utl file (-p)
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.52
2008-09-03 14:45:53 BR0279E Return code from '/usr/sap/RD1/SYS/exe/run/backint -u RD1 -f backup -i /lms/oracle/RD1/saparch/.adystlhx.lst -t file -p
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0232E 0 of 1 file saved by backup utility
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.52
2008-09-03 14:45:53 BR0231E Backup utility call failed
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0016I 0 offline redo log files processed, totalsize 0.000 MB
2008-09-03 14:45:53
2008-09-03 14:45:53 BR0007I End of offline redo log processing: adystlhx.cds 2008-09-03 14.45.53
2008-09-03 14:45:53 BR0280I BRARCHIVE time stamp: 2008-09-03 14.45.53
2008-09-03 14:45:53 BR0005I BRARCHIVE terminated with errors
2008-09-03 14:45:53 External program terminated with exit code 5
2008-09-03 14:45:53 BRARCHIVE returned error status E
2008-09-03 14:45:53 Job finished
Can you please help me out.
Thanks in Advance.
Regards,
Rohan

Hi Rohan,
Are you using any backup software to manage SAP Backups? Has anything changed? Any upgrades done to backup software?
2008-09-03 14:45:53 BR0278I Command output of '/usr/sap/RD1/SYS/exe/run/backint -u RD1 -f backup -i /lms/oracle/RD1/saparch/.adystlhx.lst -t file -p
2008-09-03 14:45:53 ERROR - Failed to get the policy method type: LNSDQP10-SAP
2008-09-03 14:45:53 ERROR: incorrect format or option in .utl file (-p)
Cheers,
Nisch

SQL LOG Backup failed in one Cluster Node

I have 02 node SQL fail over cluster, NOD01 and NODE 02. and configure SQL log backup job via SQL Logshipping
When the sql service is mounted to node 02 job backup will work without any issues, Once its connected to node 01 this will provide below issue
Executed as user: <domain>\administrator. The process could not be created for step 1 of job 0xAC90A0F3623AE44285089E9EF53B12C7 (reason: The system cannot find the file specified). The step failed.
could anyone have on fix for this
Thanx

SQL Server Agent on both nodes run under same domain account?
Are you sure that path location is correct?
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Backup failed - Bulk setting Spotlight attribute failed - Ideas?

I just upgraded from 10.4.? to 10.5.4 primarily to use TM. This has been a disaster. I have never had this much trouble with an upgrade since the Mac Plus.
Before the backup fails I get 200+ console messages like:
/System/Library/CoreServices/backupd[294] Bulk setting Spotlight attributes failed.
What does this mean and how can I fix the problem?
From other posts, it seems that Spotlight and TM have some type of incompatibility, particularly on the first full backup. Spotlight indexing seems to create a problem for TM. I have yet to perform a successful backup.
How do I temporarily turn Off Spotlight other than editing the hostconfig file? Should I include both my Backup Drive and my Boot drive in the Spotlight exclusion list, until I can get a successful backup?

Yes,
Before the backup I placed the TM Backup drive in the "Privacy" section of the Spotlight preferences. That did not seem to have an effect.
The bad news is that at least for now, I am using the backup drive to hold data as well. By placing the drive in the Privacy section, I no longer can easily search the contents.
-reed

Time Machine backups fail after initial backup in Yosemite

After upgrading from Mavericks to Yosemite, I was able to run one backup to my trusty USB drive. Subsequent backups all start with "Preparing backup", and will write roughly 900KB to disk (or so it says) and then fails. I created a Time Machine-compatible network drive on my Drobo 5n, and again, the initial backup is successful, and subsequent ones fail. This is concerning and infuriating. I'm hoping someone out there has encountered this problem as well.
Please note: this is regarding backups only. I see a handful of discussions about not being able to perform restores in Yosemite, but that is not my issue.

Same here.
From Time Machine Buddy app:
Starting manual backup
Total content size: 424.3 GB excluded items size: 21.01 GB for volume Macintosh HD
Found 2439814 files (403.3 GB) needing backup
424.87 GB required (including padding), 250.63 GB available
Deleted backup /Volumes/Backupmac/Backups.backupdb/.df. (3)/2014-10-23-120445.inProgress/F8CFC567-7E6E-49B0-B366-88DF31DAF49B containing 4 KB; 250.63 GB now available, 424.87 GB required
Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
Deleted 1 backups containing 4 KB total; 250.63 GB now available, 424.87 GB required
Backup date range was shortened: oldest backup is now Oct 23, 2014
Backup failed with error 7: Not enough available disk space on the target volume.
It wants to do a full backup. Fine... so why doesn't it just delete more of the old backups to do so? I don't want to wipe the backup drive and start over now, but that seems like the only way to go.

Time Machine backups fail after initial drive connection, cannot eject drive

I have a Macbook Pro 13" Retina Display, 8GB running OS X Mavericks 10.9.4 and have set Time Machine backups to a 1TB WD My Passport. When I first connect the drive the backup will run fine, but subsequent backups always fail. In addition I typically cannot eject the drive. I've scoured online forums and have completely reformatted the drive, and have even deleted some backup settings files from the hard drive, none of these has resolved my issue.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Backup fail after kernel patches updated

Hello friends
i have update kernel pathes. then backup is failing cont. now my patch level is 114.
im getting error please suggest.
Job started
Step 001 started (program RSDBAJOB, variant &0000000000235, user ID BASIS1)
Execute logical command BRCONNECT On host sapodev
Parameters: -u / -jid STATS20080731152625 -c -f stats -t ALL
BR0801I BRCONNECT 7.00 (11)
BR0805I Start of BRCONNECT processing: cdymghmx.sta 2008-07-31 15.26.27
BR0252E Function fopen() failed for '/oracle/SAD/sapcheck/connSAD.log' at location main-11
BR0253E errno 13: Permission denied
BR0121E Processing of log file /oracle/SAD/sapcheck/connSAD.log failed
BR0806I End of BRCONNECT processing: cdymghmx.sta2008-07-31 15.26.31
BR0280I BRCONNECT time stamp: 2008-07-31 15.26.31
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finished
thanks & regards
sachin

Hi,
I think some of the answers are partially correct.
For the full and correct solution you must
> Check the owner, group, and access authorizations for BR*Tools and SAPDBA in accordance with Note [113747|http://service.sap.com/sap/support/notes/113747].

Tran log backup fail after setting a DB offline

Similar Messages

Maybe you are looking for