Error "ARC0: Unable to archive..." during rman backup

Hello DBA's!
Problem:
When ever I make an archivelog backup with rman it generates the following entry into the alertlog:
Wed Jun 20 21:00:26 2007
ARCH: Evaluating archive thread 1 sequence 9013
Wed Jun 20 21:00:26 2007
ARC0: Evaluating archive thread 1 sequence 9013
ARC0: Unable to archive thread 1 sequence 9013
Log actively being archived by another process
I use the following RMAN-Script:
"backup device type disk tag 'BACKUP_AL1' archivelog all not backed up 1 times;"
The comical thing is when a usual archivlog switch happens it all works fine with no errors or problems.
The backup also runs with no errors and after searching I found the following entry in Metalink:260040.1, it can't help me because the usual archivelog switch is working fine.
The environment which I use is an Oracle 10.1.0.4 Database in a Cluster Environment on Windows Server.
Maybe here is anyone with an idea?

Thanks for the fast answer.
I read the metalink entry "Multiple archiver processes FAQ" Note:73163.1 and now I understand why this comment comes.
The parameter in the database "log_archive_max_processes" is set to 2 (means multiple archive processes).
I will change paramater back to 1 because the database will handle it by itself if it need more then 1 process.

Similar Messages

ARC0: Unable to archive

Hi,
my database stay in mount but can not be open. In alert log I have :
Creating archive destination LOG_ARCHIVE_DEST_1: '/backup/impcnp/archive/1_417704.dbf'
Wed Aug 29 12:41:31 2007
ARC0: Evaluating archive log 6 thread 1 sequence 417703
ARC0: Unable to archive log 6 thread 1 sequence 417703
Log actively being archived by another process
ARC0: Evaluating archive log 3 thread 1 sequence 417704
ARC0: Unable to archive log 3 thread 1 sequence 417704
Log actively being archived by another process
The archive files '/backup/impcnp/archive/1_417704.dbf' are not created.
We have enough disk space on /backup.
Any idea ?
Many thanks.

thank you.
we are in 9.2.0.8 on Linux :
show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_dest string /backup/impcnp/archive
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_duplex_dest string
log_archive_format string %t_%s.dbf
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean TRUE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch
regards.

ARC0: Unable to archive log 1 thread 1 sequence 1292

Hi all,
We are getting error in our alert logfile:
We are using oracle 9.2.0.8 on RHEL5, is there solution to overcome this problem
Thread 1 advanced to log sequence 1293
Current log# 3 seq# 1293 mem# 0: /u01/app/oracle/oradata/icai/redo03.log
Current log# 3 seq# 1293 mem# 1: /oradata/data/redo03a.log
Current log# 3 seq# 1293 mem# 2: /oradata/data/redo03d
Mon Aug 16 11:31:10 2010
ARC0: Evaluating archive   log 2 thread 1 sequence 1291
ARC0: Unable to archive log 2 thread 1 sequence 1291
      Log actively being archived by another process
Mon Aug 16 11:31:28 2010
ARC3: Completed archiving log 2 thread 1 sequence 1291
Mon Aug 16 11:50:44 2010
Thread 1 advanced to log sequence 1293
Current log# 3 seq# 1293 mem# 0: /u01/app/oracle/oradata/icai/redo03.log
Current log# 3 seq# 1293 mem# 1: /oradata/data/redo03a.log
Current log# 3 seq# 1293 mem# 2: /oradata/data/redo03d
Mon Aug 16 11:50:44 2010
ARCH: Evaluating archive   log 1 thread 1 sequence 1292
Mon Aug 16 11:50:44 2010
ARCH: Beginning to archive log 1 thread 1 sequence 1292
Mon Aug 16 11:50:44 2010
ARC3: Evaluating archive   log 1 thread 1 sequence 1292
Mon Aug 16 11:50:44 2010
ARC3: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:50:44 2010
Creating archive destination LOG_ARCHIVE_DEST_3: 'drsite_delhi'
Creating archive destination LOG_ARCHIVE_DEST_2: 'hp'
Mon Aug 16 11:51:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:51:28 2010
ARC3: Evaluating archive   log 1 thread 1 sequence 1292
ARC3: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:52:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:53:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:54:21 2010
ARC0: Evaluating archive   log 1 thread 1 sequence 1292
ARC0: Unable to archive log 1 thread 1 sequence 1292
      Log actively being archived by another process
Mon Aug 16 11:54:37 2010
ARC1: Evaluating archive   log 1 thread 1 sequence 1292
ARC1: Unable to archive log 1 thread 1 sequence 1292

rt noe the value os log_archive_maz_process=4
SQL> show parameter log_arch
NAME TYPE VALUE
log_archive_dest string
log_archive_dest_1 string location=/arch/icai/icai_ mand
atory
log_archive_dest_10 string
log_archive_dest_2 string service=hp optional reopen=15
log_archive_dest_3 string service=drsite_delhi optional
reopen=15
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
NAME TYPE VALUE
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
NAME TYPE VALUE
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s.dbf
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean TRUE
log_archive_trace integer 0
SQL>

Intermittent OCFS2 Heartbeat Errors During RMAN Backup

Hello all. If this is better suited to an OCFS2 list, please let me know.
I have an Oracle 10g RAC (10.2.0.2), on which one node runs an RMAN backup nightly around 10:45 PM. The node is running on RHEL4 x64 with 8 GB of RAM.
About every other night these errors turn up in the messages log in the server:
Apr 19 23:48:23 servername kernel: (4059,2):o2hb_setup_one_bio:371 ERROR: Could not alloc slots BIO!
Apr 19 23:48:23 servername kernel: (4059,2):o2hb_read_slots:507 ERROR: status = -12
Apr 19 23:48:23 servername kernel: (4059,2):o2hb_do_disk_heartbeat:973 ERROR: status = -12
This only seems to happen when the RMAN backup is in progress, and I get these at no other time of the day.
Can anyone point me to a reference for what these error codes mean, and if you've encountered these before can you tell me what impact this has and how it can be resolved? I'm assuming that the read/write load on the block device for the OCFS2 mount is causing issues, but this all conjecture without an explanation of the error code.
Thanks in advance,
Dan

Thanks for the response!
Kernel is: 2.6.9-34.0.2.ELsmp
ocfs2 is: ocfs2-2.6.9-34.0.2.ELsmp-1.2.4-2
To my knowledge it's never lead to a fence, and these are the only ocfs2 messages logged in the system log. When these messages occur, there doesn't seem to be any other symptom and the backup completes.
To be honest, we've never had issues with ocfs2 since we set this RAC node up, so I'm sad to say I don't even know what messages a fencing event would create.

Log Switch during RMAN backup

I have seen in many RMAN backup scripts that a manual log switching is performed in first line of the script? What is it purpose, just to write changes needed to reconstruct the DML/DDL statements to online redo logfiles and start the archiving process if db is running in archive log mode?

918868 wrote:
I have seen in many RMAN backup scripts that a manual log switching is performed in first line of the script? What is it purpose, just to write changes needed to reconstruct the DML/DDL statements to online redo logfiles and start the archiving process if db is running in archive log mode?That could be the only reason but even that is not needed as RMAN would do a log switch automatically to push the current redo log file to make it's archive log and include it in the backup.
Aman....

When I try to backup to a disk I have used many times for backups I get the following error message: "unable to get status of backup disk"

unable to get status of backup disk

Greetings cf83,
It seems you are unable to backup on an existing Time Machine backup drive. I have linked to an article that may help you troubleshooting the issue:
OS X: If you can't back up or restore with Time Machine - Apple Support
Thank you for contributing to Apple Support Communities.
Best,
Bobby_D

Restoring archives from rman backups

i have taken backup of all archive logs as follows
backup archivelog all delete all input;
how to restore th archives at their original location

816669 wrote:
i have taken backup of all archive logs as follows
backup archivelog all delete all input;
how to restore th archives at their original locationWhile you can directly have rman restore the archivelogs, please note that if an archivelog is needed for database recovery, rman will know to restore said archivelog anyway.

RMAN error during auto backup

Hello,
We have crontab to take archivelog backup at every hour at 10 mins. mon-sat incremental and sunday level 0 backup. Today morning I got following error in the log file. (RAC DB 10.2.0.5, OS=RHL)
RMAN-00571:
===========================================================brRMAN-00569: ===============
ERROR MESSAGE STACK FOLLOWS ===============brRMAN-00571:
===========================================================brRMAN-03002: failure of backup
plus archivelog command at 05/21/2012 05:55:59brRMAN-03014: implicit resync of recovery
catalog failedbrRMAN-06004: ORACLE error from recovery catalog database: ORA-03113:
end-of-file on communication channelbrORACLE error from recovery catalog database:
ORA-03114: not connected to ORACLEbrRMAN-00571:
===========================================================brRMAN-00569: ===============
ERROR MESSAGE STACK FOLLOWS ===============brRMAN-00571:
===========================================================brRMAN-03002: failure of
allocate command at 05/21/2012 05:56:00brRMAN-06004: ORACLE error from recovery catalog
database: ORA-03114: not connected to ORACLElist backup of archivelog all; .. while connecting to rman catalog..following are the few lines from the output.
I found almost related MOS note but unfortunately, I am still unable to understand what actually happened or what is trying to be explain in this particular note. RMAN Backup fails with error ORA-3114 [ID 1264084.1]. One more important question for my concern is that if the command failed for example as in my case. The next time when backup command started to take incremental backups, will it cover or backup those archivelog which were not backed up because of the above error?
List of Archived Logs in backup set 2481637
Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
1    67414   27261392224 21-05-2012 05:10:22 27261405217 21-05-2012 05:55:55
1    67415   27261405217 21-05-2012 05:55:55 27261422601 21-05-2012 06:10:07
2    70049   27261392222 21-05-2012 05:10:20 27261405224 21-05-2012 05:55:57
2    70050   27261405224 21-05-2012 05:55:57 27261422604 21-05-2012 06:10:08Thank you.
Best Regards.

A "BACKUP ARCHIVELOG" is not an "Incremental Backup" (ergo, the question of "differential" or "cumulative" doesn't arise).
It is a Backup of the ArchiveLogs specified in archlogspecifier . Since you have specified "ALL" it will attempt to backup all known archivelogs that have not been deleted. The "DELETE ALL INPUT" will delete the files after they have been successfully backed up. If the backup fails, the DELETE is not executed. Therefore, at the next execution, the same (and newer) ArchiveLogs will get backed up.
Why don't you maintain a log of the RMAN Backup run (either with "SPOOL LOG TO .." in the RMAN script or by redirecting STDOUT and STDERR to a custom log file).
Hemant K Chitale

Regarding RMAN backup and recovery using archivelogs during cloning process

Hi there,
We are running 9i database (RAC) in archivelog mode.We are in the process of cloning DEVELOPMENT database using our PRODUCTION database.
For this we planned to take RMAN backup by keeping the production database in MOUNT stage.
In this regard, will it be possible to make use of archivelogs generated during and after this backup (in mount stage), after some days during recovery time, if it asks for recovery after cloning process.
Thanks,
Balu.

Hi Alok,
why there is a need for standby here? you mean to say standby db?
what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..

Log file sync during RMAN archive backup

Hi,
I have a small question. I hope someone can answer it.
Our database(cluster) needs to have a response within 0.5 seconds. Most of the time it works, except when the RMAN backup is running.
During the week we run one time a full backup, every weekday one incremental backup, every hour a controlfile backup and every 15 minutes an archival backup.
During a backup reponse time can be much longer then this 0.5 seconds.
Below an typical example of responsetime.
EVENT: log file sync
WAIT_CLASS: Commit
TIME_WAITED: 10,774
It is obvious that it takes very long to get a commit. This is in seconds. As you can see this is long. It is clearly related to the RMAN backup since this kind of responsetime comes up when the backup is running.
I would like to ask why response times are so high, even if I only backup the archivelog files? We didn't have this problem before but suddenly since 2 weeks we have this problem and I can't find the problem.
- We use a 11.2G RAC database on ASM. Redo logs and database files are on the same disks.
- Autobackup of controlfile is off.
- Dataguard: LogXptMode = 'arch'
Greetings,

Hi,
Thank you. I am new here and so I was wondering how I can put things into the right category. It is very obvious I am in the wrong one so I thank the people who are still responding.
-Actually the example that I gave is one of the many hundreds a day. The respone times during the archive backup is most of the time between 2 and 11 seconds. When we backup the controlfile with it, it is for sure that these will be the response times.
-The autobackup of the controfile is put off since we already have also a backup of the controlfile every hour. As we have a backup of archivefiles every 15 minutes it is not necessary to also backup the controlfile every 15 minutes, specially if that even causes more delay. Controlfile is a lifeline but if you have properly backupped your archivefiles, a full restore with max 15 minutes of data loss is still possible. We put autobackup off since it is severely in the way of performance at the moment.
As already mentioned for specific applications the DB has to respond in 0,5 seconds. When it doesn’t happen then an entry will be written in a table used by that application. So I can compare the time of failure with the time of something happening. The times from the archivelog backup and the failure match in 95% of the cases. It also show that log file sync at that moment is also part of this performance issue. I actually built a script that I used for myself to determine out of the application what the cause is of the problem;
select ASH.INST_ID INST,
ASH.EVENT EVENT,
ASH.P2TEXT,
ASH.WAIT_CLASS,
DE.OWNER OWNER,
DE.OBJECT_NAME OBJECT_NAME,
DE.OBJECT_TYPE OBJECT_TYPE,
ASH.TIJD,
ASH.TIME_WAITED TIME_WAITED
from (SELECT INST_ID,
EVENT,
CURRENT_OBJ#,
ROUND(TIME_WAITED / 1000000,3) TIME_WAITED,
TO_CHAR(SAMPLE_TIME, 'DD-MON-YYYY HH24:MI:SS') TIJD,
WAIT_CLASS,
P2TEXT
FROM gv$active_session_history
WHERE PROGRAM IN ('yyyyy', 'xxxxx')) ASH,
(SELECT OWNER, OBJECT_NAME, OBJECT_TYPE, OBJECT_ID FROM DBA_OBJECTS) DE
WHERE DE.OBJECT_id = ASH.CURRENT_OBJ#
AND ASH.TIME_WAITED > 2
ORDER BY 8,6
- Our logfiles are 250M and we have 8 groups of 2 members.
- Large pool is not set since we use memory_max_target and memory_target . I know that Oracle maybe doesn’t use memory well with this parameter so it is truly a thing that I should look into.
- I looked for the size of the logbuffer. Actually our logbuffer is 28M which in my opinion is very large so maybe I should put it even smaller. It is very well possible that the logbuffer is causing this problem. Thank you for the tip.
- I will also definitely look into the I/O. Eventhough we work with ASM on raid 10 I don’t think it is wise to put redo logs and datafiles on the same disks. Then again, it is not installed by me. So, you are right, I have to investigate.
Thank you all very much for still responding even if I put this in the totally wrong category.
Greetings,

RMAN throwing errors during Tablespace Backup - RMAN-06004 and RMAN-06019

Hi All.
Please help me to fix trail of error message I'm getting while trying backup of a newly added tablespace in database. I'm using RMAN as a recovery method.
Tablespace Name: test
DB Version: Oracle 10g R1.
OS: Red Hat Linux 5
RMAN> report schema;
Report of database schema
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
1 490 SYSTEM YES /u01/app/oracle/oradata/qrcl/system01.dbf
2 25 UNDOTBS1 YES /u01/app/oracle/oradata/qrcl/undotbs01.dbf
3 270 SYSAUX NO /u01/app/oracle/oradata/qrcl/sysaux01.dbf
4 23 USERS NO /u01/app/oracle/oradata/qrcl/users01.dbf
5 40 TEST NO /u01/app/test01.dbf
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
1 20 TEMP 32767 /u01/app/oracle/oradata/qrcl/temp01.dbf
RMAN>
RMAN> backup tablespace "test";
Starting backup at 22-AUG-12
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 08/22/2012 11:57:13
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "test"
RMAN> restore tablespace test;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "test": expecting one of: "double-quoted-string, identifier, single-quoted-string"
RMAN-01007: at line 1 column 20 file: standard input
I tried to update Catalog Server but still no luck:
RMAN> RESYNC CATALOG;
starting full resync of recovery catalog
full resync complete
Please Assist.
Thanks
Prashant Dixit

Hello Prashant;
The main issue is your tablespace name is an RMAN Reserved Word "Test"
http://docs.oracle.com/cd/B13789_01/server.101/b10770/rcmcomma.htm#1006728
Different test
-- Create the tablespace
CREATE TABLESPACE OTN_TEST DATAFILE
'/u01/oradata/RECOVER2/test01.dbf' SIZE 1M AUTOEXTEND OFF
LOGGING
ONLINE;-- Create a user for the tablespace
CREATE USER RMAN_TEST
IDENTIFIED BY RMAN_TEST
DEFAULT TABLESPACE OTN_TEST
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
ALTER USER RMAN_TEST QUOTA UNLIMITED ON "OTN_TEST"; -- Create a table in the tablespace
CREATE TABLE RMAN_TEST.EMP
EMPNO     NUMBER,
ENAME     VARCHAR2(30 BYTE),
JOB       VARCHAR2(30 BYTE),
MGR       NUMBER,
HIREDATE DATE,
SAL       NUMBER,
COMM      NUMBER,
DEPTNO    NUMBER
TABLESPACE OTN_TEST;-- Add some data
SET DEFINE OFF;
Insert into RMAN_TEST.EMP
   (EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO)
Values
   (7369, 'SMITH', 'CLERK', 7902, TO_DATE('12/17/1980 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
    800, 20, 0);
Insert into RMAN_TEST.EMP
   (EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO)
Values
   (5000, 'NOCATALOG', 'DBA', 77902, TO_DATE('04/01/2010 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
    200, 0, 0);
COMMIT;-- start RMAN and backup tablespace
RMAN> BACKUP TABLESPACE OTN_TEST;
Starting backup at 22-AUG-12
starting full resync of recovery catalog
full resync complete
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00007 name=/u01/oradata/RECOVER2/test01.dbf
channel ORA_DISK_1: starting piece 1 at 22-AUG-12
channel ORA_DISK_1: finished piece 1 at 22-AUG-12
piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/backupset/2012_08_22/o1_mf_nnndf_TAG20120822T080711_839pczng_.bkp tag=TAG20120822T080711 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 22-AUG-12
Starting Control File and SPFILE Autobackup at 22-AUG-12
piece handle=/u01/app/oracle/flash_recovery_area/RECOVER2/autobackup/2012_08_22/o1_mf_s_791971633_839pd1bm_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 22-AUG-12
Note
If you dropped the tablespace then you need to recover the database to a point in time, not the tablespace.
Best Regards
mseberg

Error , ORA-19809 & ORA-19804 While restoring RMAN backup .

Hi Experts,
I am restoring production RMAN backup to UAT . Using below steps
1)rman target=/
2)RMAN> startup nomount;
3) RMAN> restore controlfile from '/orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl';
Starting restore at 05-AUG-10
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=3 device type=DISK
channel ORA_DISK_1: copied control file copy
output file name=+DATA_ACME/acme/controlfile/current.256.724845209
output file name=+DATA_ACME/acme/controlfile/current.257.724845209
Finished restore at 05-AUG-10
4) RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
5) RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME1/current/%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/orabkdump/Rman_Bak/ACME/%F';
new RMAN configuration parameters are successfully stored
6) RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/orabkdump/Rman_Bak/ACME/%U';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
7) RMAN> CATALOG START WITH '/orabkdump/Rman_Bak/ACME';
searching for all files that match the pattern /orabkdump/Rman_Bak/ACME
List of Files Unknown to the Database
=====================================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347594_1_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722347939_2_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348365_3_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722348681_4_1
File Name: /orabkdump/Rman_Bak/ACME/ACME_DB_722349076_5_1
File Name: /orabkdump/Rman_Bak/ACME/bkup_CTLFL_2206101206.ctl
File Name: /orabkdump/Rman_Bak/ACME/c-1904932673-20100622-00
List of Files Which Where Not Cataloged
=======================================
File Name: /orabkdump/Rman_Bak/ACME/dbsnap.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.log
RMAN-07517: Reason: The file header is corrupted
File Name: /orabkdump/Rman_Bak/ACME/rman_Tuesday_LVL_0.trc
RMAN-07517: Reason: The file header is corrupted
8) RMAN> run {
2> set until sequence 1789 thread 2;
3> restore database;
4> recover database;
5> sql 'alter database open resetlogs';
6> }
executing command: SET until clause
Starting restore at 06-AUG-10
using channel ORA_DISK_1
Finished restore at 06-AUG-10
Starting recover at 06-AUG-10
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2803
channel ORA_DISK_1: restoring archived log
archived log thread=2 sequence=6051
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=2804
channel ORA_DISK_1: reading from backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/06/2010 23:10:38
ORA-19870: error while restoring backup piece /orabkdump/Rman_Bak/ACME/ACME_AL_726286927_57_1
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 49283072 bytes disk space from 5218762752 limit
** My UAT database should be in noarchival mode . Generally such errors have been observed during backup , but have no clue why they occurred during recovery .Please advice .
Thanks
Edited by: user11981514 on Aug 6, 2010 9:46 AM

Hi,
Since the error ORA-19809 indicates the lack of space in flash recovery area during the media recovery, I suggested increasing the value of the parameter DB_RECOVERY_FILE_DEST_SIZE.
Yes, during the media recovery the RMAN will restore the archived log to the default destination (only if the required archived logs are not already on the disks).You can confirm the restore location of the archived log in RMAN restore log/destination specified by parameters log_archive_dest_1/db_recovery_file_dest.
Regards,
Vaibhav

Rman backup errors..

hi guru's
please tell me the answeres..for this
what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?

user13014926 wrote:
hi guru's
please tell me the answeres..for this
what will happen if we re run the Rman backup due to the job failure...will take a new backup from the begining? or will start from the first backup end where it left ?
You can continue backup from which files not backed up and this is call restartable backup.Please refer below link
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1008543
>
i am deleting some archieved logs on the archieved destination before takeing the RMAN backup, and then running rman backup ...then any error will raised for the missing files during Rman archive log backup for missing files? i have the files like 1 to 10 ...in that 5 and 6 logs are deleted before takeing the Rman backup..how to resolve this?If you manually delete archivelogs then you will get an error so before executing this backup command you have to execute CROSSCHECK ARCHIVELOG ALL and DELETE EXPIRED ARCHIVELOG ALL then your problem will solve.

Rman backup error in 10g rac

hi,
I am backup 10g rac with rman,but there is some error when backup:
input datafile fno=00006 name=+DG1/orcl/datafile/undotbs3.265.623622323
channel c3: starting piece 1 at 13-JUN-07
RMAN-03009: failure of backup command on c1 channel at 06/13/2007 08:40:50
ORA-19504: failed to create file "/oracle/rman/db_ORCL_20070613_0fik5ji0_1_1_L0"
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
channel c1 disabled, job failed on it will be run on another channel
RMAN-03009: failure of backup command on c3 channel at 06/13/2007 08:40:51
ORA-19504: failed to create file "/oracle/rman/db_ORCL_20070613_0hik5jna_1_1_L0"
ORA-27040: file create error, unable to create file
Linux Error: 2: No such file or directory
channel c3 disabled, job failed on it will be run on another channel
released channel: c1
released channel: c2
released channel: c3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of release command at 06/13/2007 08:49:22
RMAN-06012: channel: c1 not allocated

Hi all I have the same problem. We have a 2 node rac with ASM. The archives goes to ASM. I would like to backup the archives from ASM to a filesystem. But i was given a filesystem that is only mounted on one node and it is not accessbile to the other node. When i run the following rman command i get the error on one of the channel that connect to node 2.
My question:
Can i use on channel that is connecting to node1 to backup all the archivelogs generated by node1 and node2 aswell since both the nodes have access to archive logs.
Please assist.
connect target /
connect catalog rmanrep/[email protected]
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/opt/oracle/archive/orcl/rman/cf_%d_%T_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'SYS/oass@orcl1;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oass@orcl2';
BACKUP CURRENT CONTROLFILE;
backup archivelog all format '/opt/oracle/archive/orcl/arch_bkup/%d_AL_%T_%u_s%s_p%p' delete input;
EXIT;
RMAN-03009: failure of backup command on ORA_DISK_2 channel at 03/17/2009 21:00:25
ORA-19504: failed to create file "/opt/oracle/archive/orcl/arch_bkup/SPTDEV_AL_20090317_2kka60j6_s84_p1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
channel ORA_DISK_2 disabled, job failed on it will be run on another channel
Thanks
Kart

Archive files and rman backup

Hi Experts,
For testing, I creates a testing DB. after that, I delete some archive file from physical side.
testing DB works well.
However, I tyr to back up thsi testing DB. I got below error message
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\Oraclebackup\CLS\exports\RMAN\%U
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
Starting backup at 15-JAN-09
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 01/15/2009 15:18:13
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file D:\test\ARC00001_0675529905.001
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
So How to fix this issue?
That means we can not delete any archive log files that we do not need it.
Otherwise there are a problemwhen we try to backup later
JIm

Hi Jim,
change archivelog all crosscheck ;
will do the trick.
You can purge archive files but do it within rman.
Add a line in your rman backup script which makes backup your database and archive files like this.
delete noprompt copy of archivelog all completed before 'SYSDATE-3';
Regards,
Tycho

Error "ARC0: Unable to archive..." during rman backup

Similar Messages

Maybe you are looking for