Hot Backups are Failing

I am running Oracle 7.3.4.4 on Compaq Tru64 and Digital Unix 4.0F. Our hot backups are failing with the following errors:
1)from $OBK_HOME/bin/backup_PROD.log
EBU-3135: SQL error during:
select state from obk_bfs where bfsid = :objid and jobid = :jobid
with error:
ORA-03113: end-of-file on communication channel
on 20-AUG-02 01:59 [ 29701 : brsupiopn ]
EBU-3135: SQL error during:
select state from obk_bfs where bfsid = :objid and jobid = :jobid
with error:
ORA-01041: internal error. hostdef extension doesn't exist
on 20-AUG-02 01:59 [ 29701 : brsupiclo ]
2)from brd.log:
Instance Manager (BRD) with pid=32158 successfully started on 20-AUG-02 00:59
EBU-3135: SQL error during:
/* Obtain all jobs that are currently running s[0] */ ...
with error:
ORA-03113: end-of-file on communication channel
on 20-AUG-02 01:59 [ 32158 : brsupiopn ]
EBU-3108: Query error reported from Catalog Database
on 20-AUG-02 01:59 [ 32158 : brdlookjobs ]
EBU-1504: Error while retrieving active jobs from Catalog Database
on 20-AUG-02 01:59 [ 32158 : brdlookjobs ]
We are running Oracle7 Enterprise Backup Utility: Release 2.2.0.6.0. I have tried to reboot both target and catalog databases and machines and still no luck. Anybody have any ideas as to what may be wrong?
Thanks,
Bea Cary
Database Administrator

Similar Messages

Since upgrading to Lion, my time machine backups are failing - error message: The backup disk image "/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska's MacBook.sparsebundle" could not be accessed (error -1). Any ideas?

Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)." I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time. Any suggestions? Thanks

Any new info on this?
I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro. Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
Grrr...

Database backups are failing

Hello Experts,
Database backups are failing due to compatibility issue, The target database version is 10.2.0.1., therefore the RMAN version is running on 10.2.0.4.0, i have no idea how that was happened and who has did that before, now i have to take of this issue .. could you please give me suggestions on how to bring RMANback to 10.2.0.1 version.

Hello Marcus,
Thank you for the update..
here is the output of RMAN
=====================================================
Recovery Manager: Release 10.2.0.4.0 - Production on Mon Jun 3 09:19:38 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN> connect target *
2> run {
3> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
4> CONFIGURE CONTROLFILE AUTOBACKUP ON;
5> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'E:\Oracle\testdb\backup\cf_%d_%F';
6> CONFIGURE BACKUP OPTIMIZATION ON;
7> CONFIGURE DEVICE TYPE disk PARALLELISM 3;
8> CONFIGURE DEFAULT DEVICE TYPE TO disk;
9> CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'E:\Oracle\testdb\backup\b_%d_%U';
10> CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT 'E:\Oracle\testdb\backup\b_%d_%U';
11> CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT 'E:\Oracle\testdb\backup\b_%d_%U';
12>
13> BACKUP DATABASE PLUS ARCHIVELOG DELETE INPUT;
14> }
15>
16> ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
17> CROSSCHECK BACKUP;
18> DELETE NOPROMPT EXPIRED BACKUP;
19> DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
20> CROSSCHECK ARCHIVELOG ALL;
21> DELETE NOPROMPT EXPIRED ARCHIVELOG ALL;
22> DELETE FORCE NOPROMPT OBSOLETE;
23>
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: TEST(DBID=123412352)
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 06/03/2013 09:19:41
ORA-06550: line 1, column 2273:
PLS-00302: component 'GETRANGEALBACKUP' must be declared
ORA-06550: line 1, column 2238:
PL/SQL: Statement ignored
ORA-06550: line 1, column 2453:
PLS-00302: component 'RESTORECMD_T' must be declared
ORA-06550: line 1, column 2424:
PL/SQL: Statement ignored
Recovery Manager complete.

As my computer is telling me my backups are failing why is this happening and what do I do?

What do I do when my computer tells me that my backups are failing and why is this happeneing?

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 pressingcommand-V.
☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
☞ 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.

Dpm 2010 exchange 2010 backups are failing

Hi, I'm getting an error which does not seem to match in the DPM 2010 ID codes. Randomly, I have backups of an exchange 2010 DAG that are failing. The backup will run for a short time (5mints..up to 10minuts) and then will fail with the following error:
Type: Recovery point
Status: Failed
Description: Backup failed as another copy of 'user' database is currently being backed up. (ID 32628 Details: Internal error code: 0x80990D51)
More information
End time: 4/25/2011 10:37:27 PM
Start time: 4/25/2011 10:26:55 PM
Time elapsed: 00:10:31
Data transferred: 0 MB
Cluster node -
Recovery Point Type Incremental Sync
Source details: 06001
Protection group: EXCH2010 - 06001
I've tried restarting the DPM server to troubleshoot. I say this happens randomly because I've had some backups successfully complete against the same exchange server. The only other item that seems odd is when creating protection groups against the DAG,
the intial lookup seems to take forever. Not sure what to try next.

Hello,
As DPM relies on the exchange writer to take the snapshot for the backup, if the backupinprogress flag is set to true and it does not seem get out of this state even when there is no actual backup in place, then at this point DPM is the victim.
As far as I am aware the only way is to clear that flag is to:
a.) Reboot the exchange server
or
b.) Restart the information store
In some cases even:
1.) Either Activate all other databases on another Node except for the Problem Database, and Dismount the Problem database temporarily
Or:
1.)Dismount all Databases on this Node including the problem database
2.)Restart the Exchange Information Store Service.
3.)Mount any dismounted databases
You may want to redirect this question below to the exchange 2010 forum of:
"if the backupinprogress is set to true when it should be set to false as there really is no backup being taken, then how can I reset it without having to perform:
a.) reboot of exchange
b.) restart of the information store"
http://social.technet.microsoft.com/Forums/en-US/exchange2010/threads
Regards, Shane. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. This posting
is provided "AS IS" with no warranties, and confers no rights.

Backups are failing.

Hi Gurus,
We are taking the backup of Essbase application files like .tct, .pag, .ind, .esm, .db. .dbb files, we are facing some issue with the backups from last few days like .esm, .tct, .pag and .ind files are failing while exporting them using windows NT batch. With an error message as these files are used by some other process. where as i am checking in applicaion event logs i found no process are running at that time..
please let me know what are the process(like dataloading, running calculations) will restrict these files to export.
Thanks in advance.

Look ty my MAXL BAckup script (for example )
msh $vWorkDir/ess/_login.mxl ;
spool off ;
shell mkdir $vBackupFolder ;
shell mkdir $vBackupFolder/$vCurrApp ;
shell mkdir $vBackupFolder/bin ;
spool on to "$vBackupFolder/$vLogFileName.$vCurrApp.mxl" ;
set vDbFolder = $ARBORPATH/app/$vCurrApp/$vCurrDB ;
set vBinFolder = $ARBORPATH/bin ;
iferror 'ExitError';
/* Unload Level 0 data */
alter database $vCurrBackAppDB enable cache_pinning;
iferror 'ExitError';
alter system logout session on application $vCurrApp force ;
alter system logout session on application $vCurrApp force ;
alter system logout session on application $vCurrApp force ;
iferror 'ExitError';
alter application $vCurrApp enable startup ;
iferror 'ExitError';
alter application $vCurrApp enable commands ;
iferror 'ExitError';
alter application $vCurrApp enable updates ;
iferror 'ExitError';
alter application $vCurrApp enable connects ;
iferror 'ExitError';
alter application $vCurrApp enable security ;
iferror 'ExitError';
alter system load application $vCurrApp ;
iferror 'ExitError';
alter application $vCurrApp load database $vCurrDB ;
iferror 'ExitError';
alter system logout session on application $vCurrApp force ;
alter system logout session on application $vCurrApp force ;
iferror 'ExitError';
export database $vCurrBackAppDB all data to data_file "$vBackupFolder/$vCurrApp.$vJobNumber.all.txt" ;
iferror 'ExitError';
export database $vCurrBackAppDB level0 data to data_file "$vBackupFolder/$vDb.level0.txt" ;
export database $vCurrBackAppDB input data to data_file "$vBackupFolder/$vDb.input.txt" ;
/* ShutDown Applications */
drop lock on system all ;
iferror 'ExitError';
alter application $vCurrApp disable startup ;
iferror 'ExitError';
alter application $vCurrApp disable commands ;
iferror 'ExitError';
alter application $vCurrApp disable updates ;
iferror 'ExitError';
alter application $vCurrApp disable connects ;
iferror 'ExitError';
alter application $vCurrApp disable security ;
iferror 'ExitError';
alter database $vCurrBackAppDB unlock all objects ;
iferror 'ExitError';
alter system logout session on application $vCurrApp force ;
iferror 'ExitError';
alter application $vCurrApp unload database $vCurrDB ;
iferror 'ExitError';
alter system unload application $vCurrApp ;
iferror 'ExitError';
/* copy system binary files */
shell cp $vBinFolder/\*.sec $vBackupFolder/bin 1>/dev/null 2>/dev/null ;
shell cp $vBinFolder/\*.cfg $vBackupFolder/bin 1>/dev/null 2>/dev/null ;
shell cp $vBinFolder/\*.sh $vBackupFolder/bin 1>/dev/null 2>/dev/null ;
shell cp $vBinFolder/\*.ini $vBackupFolder/bin 1>/dev/null 2>/dev/null ;
/* copy applications binary files */
shell cp $vDbFolder/\*.otl $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.rul $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.txt $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.csc $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.db   $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.dbb $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.ind $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.pag $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.esm $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/\*.tct $vBackupFolder/$vDb 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/../\*.app $vBackupFolder/ 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/../\*.apb $vBackupFolder/ 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/../\*.xml $vBackupFolder/ 1>/dev/null 2>/dev/null ;
shell cp $vDbFolder/../\*.jar $vBackupFolder/ 1>/dev/null 2>/dev/null ;
shell mkdir $vBackupFolder/scripts ;
shell cp $vWorkDir/\* $vBackupFolder/scripts/ 1>/dev/null 2>/dev/null ;
shell mkdir $vBackupFolder/scripts/ess ;
shell cp -r $vWorkDir/ess/\* $vBackupFolder/scripts/ess 1>/dev/null 2>/dev/null ;
/* Deleted tempory files */
shell rm -f $vDbFolder/\*.otn ;
shell rm -f $vDbFolder/\*.inn ;
shell rm -f $vDbFolder/\*.esn ;
shell rm -f $vDbFolder/\*.pan ;
shell rm -f $vDbFolder/\*.tcu ;
shell rm -f $vDbFolder/\*.esn ;
shell rm -f $vDbFolder/\*.pan ;
shell rm -f $vDbFolder/\*.inn ;
shell rm -f $vDbFolder/\*.tcu ;
shell rm -f $vDbFolder/\*.otn ;
/* RESTRUCTURE applications */
alter database $vCurrBackAppDB enable cache_pinning;
iferror 'ExitError';
alter application $vCurrApp enable startup;
iferror 'ExitError';
alter application $vCurrApp enable commands;
iferror 'ExitError';
alter application $vCurrApp enable updates;
iferror 'ExitError';
alter application $vCurrApp enable connects;
iferror 'ExitError';
alter application $vCurrApp enable security;
iferror 'ExitError';
alter system load application $vCurrApp ;
iferror 'ExitError';
alter application $vCurrApp load database $vCurrDB ;
iferror 'ExitError';
alter database $vCurrBackAppDB force restructure ;
iferror 'ExitError';
define label 'ExitError';
/* Start applications */
alter database $vCurrBackAppDB enable cache_pinning;
alter application $vCurrApp enable startup;
alter application $vCurrApp enable commands;
alter application $vCurrApp enable updates;
alter application $vCurrApp enable connects;
alter application $vCurrApp enable security;
alter system load application $vCurrApp ;
alter application $vCurrApp load database $vCurrDB ;
logout;
/* Create Archives */
shell cp "$vBackupFolder/$vLogFileName.$vCurrApp.mxl"   "$vWorkDir/log/bck/$vLogFileName.$vCurrApp.mxl" ;
shell cp "$vBackupFolder/$vLogFileName.$vCurrApp.err"   "$vWorkDir/log/bck/$vLogFileName.$vCurrApp.err" ;
shell tar --remove-files -cz -f $vBackupFolder.tar.gz $vRelativeBackupFolder ;
shell rm -r $vBackupFolder ;
shell scp $vBackupFolder.tar.gz oracle@hypdb:~/backup & ;

LR5 Backups are failing

For a couple of years I've had LR set to ask to back up every day. It still tries to, but about 3 weeks ago it began failing to be able to back up. The "checking catalog integrity" box stays up for a long time (maybe a minute) and maybe the process doesn't even succeed because then that box is replaced by this error message.
I never changed anything about folder permissions and the drive has plenty of free space. (It's my internal drive, which only has a few files and my apps on it; I save most of my files to an EHD.) Choosing a different back up folder gives the same error message. About a week ago I upgraded to OS X Yosemite on my Mac, but the problem persisted exactly the same.
Please can someone help?

Thank you for the quick reply. It didn't work though.
I looked in Finder at the folder where my backups were being stored and it still says "read and write" under privileges.
And I found the disk utility and the button that said "repair permissions" and clicked on that. It took a few minutes and showed many results about other things but not Lightroom. I copied it and saved it in case that would be useful. Let me know; I won't post it now because it's long.
Unfortunately, even after restarting my computer, Lightroom is still failing to back up, giving the same error message as I posted above.
Anything else I can do?
Would a screen shot of the folder where my Lightroom backups are stored help? Next to the Backups folder, which I created 2 years ago, I notice another folder called "Corrupt Catalogs" which I don't think I made myself. According to file info, it was created December 18, 2013. It has 5 catalogs in it, the latest dated July 13, 2014. I have no idea if this is related to my backup problem; just mentioning it just in case.
As for the Backup folder, it has 3 backups in it dated 9/30, 10/02, and 10/05.

My laptop is hooked up to a time capsule via an ethernet network. Recently, my backups are failing due to: "...sparsebundle is already in use." What does this mean and how do I fix it?

Lately my time machine backups have been failing because "...the sparsebundle is already in use." What does this mean, and how can I fix it?

What does this mean
It means that there are bugs in the Time Machine software
how can I fix it?
A rather complex procedure....
Pull the power cord from the back of the Time Capsule
Count to ten
Plug the power cord back into the the back of the Time Capsule

RMAN - Backups are failing *URGENT*

Hi,
I have a 2 10g DB (CM and ODSPROD) on HP-UX B.11.23 and both are on the same box and I have configured different script for individual DB on that BOX
till yesterday the backups were working fine but today it errored as follows:
run
allocate channel c1 type 'SBT_TAPE';
send 'NB_ORA_POLICY=ODSPROD1_RMAN,NB_ORA_SERV=QUEBACKUP';
backup database format 'backup_of_%d_%s_%D_%M_%Y' plus archivelog format 'arch_of_%d_%s_%D_%M_%Y';
restore validate database;
++++++++++++++++++++++++++++++
run
allocate channel c1 type 'SBT_TAPE';
send 'NB_ORA_POLICY=ODSPROD1_RMAN,NB_ORA_SERV=QUEBACKUP';
backup database format 'backup_of_%d_%s_%D_%M_%Y' plus archivelog format 'arch_of_%d_%s_%D_%M_%Y';
restore validate database;
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 04/21/2009 22:24:17
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 04/21/2009 22:52:14
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog
Let me know if you require any info in this regards.

as others have said this is a netbackup media manager error. To be honest though the most likely cause is a bad tape. I still prefer if you've got the space, and I'd hazard a guess that you have since you are backing up the database and archivelogs all in one go by the looks of it, to backup to disk and then let the tape backup pickup the backupsets
Niall

Maintanence plan jobs are failing

Dear All,
We are facing problems with maintenance plan jobs in SQL server 2012. All jobs are failing with Following error
Executed as user: Testdbserver\SQLadmuser. Microsoft (R) SQL Server Execute Package Utility Version 11.0.3431.0
for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 2:35:25 PM
Could not load package "\Maintenance Plans\Db_Backup" because of error 0x80070005.
Description: Access is denied. Source: Started: 2:35:25 PM Finished: 2:35:26 PM Elapsed: 0.094 seconds.
The package could not be loaded. The step failed.
Server details are: windows 2008 server with sql server 2012 ENT with core based licence. And SQL server , agent services are running with user 'SQLadmuser' (Nonadmin windows user). SQLadmuser is
having sysadmin server roleand in windows its nonadmin userid.
SQL Server maintenance jobs are running under sql server agent service account(by default) but jobs are failing. So After that i have created
credentials with proxy account and i have run those jobs with proxy account, all jobs are executing well with proxy.
or If iam changing SQL server, agent service accounts from SQLadmuser to
local system the maintenance jobs are working perfect.
I have cross verified all permissions and assigned SQLadmuser previlizes to the folders,root folders and regisries but still jobs are failing .
Note: I have observed that some of SQL server related groups are not displaying in local groups and iam unable to find tose groups. one below are reflecting.
1. Is there any relation with this sql groups to run the jobs?
2. Why this jobs are not working with sql server agent service account?
3. Does this create problems to whole SQL server instance in future?
4. Running jobs with proxy account will be having any impact on server?
Could you please help me to trouble shoot the maintenance jobs, Also sharing screenshots for reference.
Thanks in advance,
Nagesh
Nagesh

Hi Nagesh,
For many of the maintenance plans which require access to file system you might have to give access for the SQL Server Agent account directly to those folders. Otherwise your SQL Agent wont have access to the file system. This is why your maintenance plan
jobs like backups are failing.
Now the best way of dealing with this issue is what you have done. Using proxy accounts. By using proxy accounts you are not giving any additional privileges to your SQL Agent account. There is no issue for using proxy accounts for SSIS packages or Maintenance
plans where you need access outside of SQL. Infact proxy accounts are introduced for this purpose, so that Agent account can impersonate the credentials in the proxy and run the job in its security context.
The reason why the jobs are successfull when you change your SQL Agent account to local system is that Local System account has access to the local file system.
http://technet.microsoft.com/en-us/library/ms189064(v=sql.105).aspx
HTH
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

I had my hard drive replaced and since my Time Machine backups say failed

I had my hard drive replace and since my Time Capsule backups are failing. The exact message is:
The backup was not performed because an error occurred while copying files to the backup disk.
The problem may be temporary. Try again later to back up. If the problem persists, use disk utility to repair your backup disk.

No, replacing your hard drive has nothing to do with it. There is a problem with your backup drive. As far as Time Machine is concerned replacing a drive is no different than buying a new computer. Time Machine will need to make a brand new backup from scratch.
If you have a large enough backup drive this may not be a problem. Otherwise, you may not have sufficient space to maintain a new backup and keep the old one. So, I would suggest under the circumstances that you erase your backup drive, then start a new Time Machine backup from scratch.
Drive Erase
1. Open Disk Utility in your Utilities folder.
2. After Disk Utility loads select the volume you wish to format from the left side list. Click on the Erase tab in the Disk Utility main window.
3. Set the format type to Mac OS Extended (Journaled.) Click on the Erase button and wait until the process has completed.
For additional help with Time Machine: Visit Pondini's Time Machine FAQ for help with all things Time Machine.

Archive logs are missing in hot backup

Hi All,
We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
=======================
rman target / nocatalog <<EOF
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
run {
allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
#--Switch archive logs for all threads
sql 'alter system archive log current';
backup as COMPRESSED BACKUPSET database include current controlfile;
#--Switch archive logs for all threads
sql 'alter system archive log current';
#--Backup Archive logs and delete what we've backedup
backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
exit
EOF
=======================
Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
=======================
Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
=======================
Regards,
Kunal.

All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/13/2012 04:22:56
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
ORA-00310: archived log contains sequence 28772; sequence 28773 required
ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
Let me try the susggestions provided above.

FULL HOT Backup failing with a 6 on media management layer....

Hi all,
My thanks in advance for reading and any posts. Appologies for the long post, but wanted to make sure I got all information required into the post
*******************The background*************************
We are currently doing full hot backups of all production databases to tape. The database we use is RAC install (9.2.0.6.0) on Linux Redhat Enterprise 4 (database on OCFS). We use a seperate Solaris 8 box with 2 HP Ultium tape drives over a standard Cat5 line (100mb), we use Veritas Netbackup 5.1 as our media manager and we use an RMAN repositry on another box. Currently the backup is taking on average 17 hours to complete (something that I have been through with Oracle).
We use the below rman script to do the full database backup.
DATE=`date +%m%d%Y-%H%M%S`; export DATE
USER=`id | cut -f2 -d"(" | cut -f1 -d")"`
ORACLE_SID=ausl5; export ORACLE_SID
ORACLE_USER=oracle; export ORACLE_USER
ORACLE_HOME=/u01/oracle/product/9.2.0 export ORACLE_HOME
#delete log files older than 35 days
find /var/adm/netbackup -name "auslive*" -mtime +35 -type f -exec rm {} \;
#if [ "${USER}" = "root" ]
#then
# su - ${ORACLE_USER} "cd /rac/DBA/scripts/BACKUP/" #-c "${CMD_STRING}"
# SUCCESS=$?
#else
# eval "/rac/DBA/scripts/BACKUP"
# SUCCESS=$?
#fi
<<EOF su - oracle
<<EOF1 /u01/oracle/product/9.2.0/bin/rman msglog /var/adm/netbackup/AUSLIVE_b
ackup.${DATE} append
connect target sys/fowler@rman_ausl5
connect catalog rman/rman@rman
#change archivelog all validate;
run {
allocate channel ch1 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch2 type sbt_tape PARMS="BLKSIZE=1048576";
#allocate channel ch3 type sbt_tape;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CHANNEL 1 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl5';
#CONFIGURE CHANNEL 2 DEVICE TYPE 'SBT_TAPE' MAXPIECESIZE 100000m
CONNECT = 'SYS/fowler@rman_ausl3';
#CONFIGURE CHANNEL 3 DEVICE TYPE 'SBT_TAPE' CONNECT = 'SYS/fowle
r@rman_ausl4';
change archivelog all validate;
###=============== Veritas Calls =========================
send "NB_ORA_CLASS=ORAhot_AUSLIVE";
#send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_CLIENT=sunatlsunx008";
send "NB_ORA_SCHED=full";
###=====================main backup sections =============
backup
incremental level=0
filesperset 15
format "bk_%s_%p_%t"
tag "hot_${ORACLE_SID}_${DATE}"
database;
sql "alter system archive log current";
change archivelog all validate;
backup
filesperset 10
format "ct_%s_%p_%t"
current controlfile;
sql "alter system archive log current";
backup
filesperset 150
format "al_%s_%p_%t"
archivelog all not backed up 2 times;
change archivelog all validate;
backup
filesperset 50
format "al_%s_%p_%t"
archivelog until time 'SYSDATE-4' delete input;
change archivelog all validate;
release channel ch1;
#release channel ch2;
#release channel ch3;
exit
EOF1
EOF
Now due to the backup taking so long, we often have archive log backups that kick off. We generally get Restore Validates of this backup once a week.
*********************************Problem*******************************
Getting to the problem, the media manager generally completes the job with a 6, which in Veritas means that the backup failed to back up the requested files. I guess that this could be something to do with the media manager layer. But myself and my colleagues are of the opinion that this is something to do with the archive log backups running inbetween (hence the change archivelog all validate; appearing so many times in the script).
Has anyone got any ideas?
Thanks again for any posts / ideas,
Mark.

No I mean, it really tries to backup everything; control file, archive logs etc...
Yeah I will admit its a bit strange, didn't code it myself. The idea was to do a bit a of house keeping at the same time with the archived redo logs (hence the file system stuff with the archived redo logs).
You see we thought that this might be causing the issue.
any ideas are welcomed,
thanks again,
Mark.

Hot backup full disk job Scheduled failed

Hello,
We are facing the issue with hot backup job. Can some one help me on this how to fix.
Here is the error log message..
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 03/20/2014 01:25:20
ORA-19510: failed to set size of 4985610 blocks for file "+DB_FLASH_1/##########"(block size=8192)
ORA-17505: ksfdrsz:1 Failed to resize file to size 4985610 blocks
ORA-15041: diskgroup space exhausted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on c1 channel at 03/19/2014 23:00:01
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 2

Hi,
It doesn't look like a Scheduler issue, but an RMAN one instead.
According to the error, the diskgroup space is exhausted, so perhaps you're running out of space on your disk?

DPM 2012 R2 Backup job FAILED for some Hyper-v VMs and Some Hyper-v VMs are not appearing in the DPM

DPM 2012 R2 Backup job FAILED for some Hyper-v VMs
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
(0x800423F3))
All the vss Writers are in stable state
Also Some Hyper-v VMs are not appearing in the DPM 2012 R2 Console When I try to create the Protection Group please note that they are not part of cluster.
Host is 2012 R2 and The VM is also 2012 R2.

Hi,
What update rollup are you running on the DPM 2012 R2 server ? DPM 2012 R2 UR5 introduced a new refresh feature that will re-enumerate data sources on an individual protected server.
Check for VSS errors inside the guests that are having problems being backed up.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Hot Backups are Failing

Similar Messages

Maybe you are looking for