Starting backup at 06-MAY-13
channel ch00: starting compressed incremental level 0 datafile backup set
channel ch00: specifying datafile(s) in backup set
RMAN-03009: failure of backup command on ch00 channel at 05/06/2013 07:09:16
[Code]....
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 05/06/2013 07:09:16
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode
Questions about implementing ARCHIVELOG mode in RAC environment.
Oracle 11gR1 RAC + ASM database. I'd like to implement ARCHIVELOG mode. Each node will have its own archive log.
Does it make sense to place archivelogs on ASM (shared storage)? Or the best practice would be to have some aside "BACKUP" server to place and keep archivelogs from all the RAC nodes there?
Additional question is about archive logs space required estimation. If it's correct to know estimate archive logs space required to get the daily avg number of switch logs
CODEselect round(avg(n_of_switch_logs), 3) avg_num_of_switch_logs from (select trunc(first_time), count(*) n_of_switch_logs from gv$log_history group by trunc(first_time)) and multiply it on size of single redolog?
changing archive mode during DB running.Before in 9.2, 'ALTER SYSTEM ARCHIVE LOG START/STOP' is available for this job. But, after 10g/11g, it cause 'archive log stop has been deprecated'.
However, for my practice, I need to estimate archived logs size before backup them, so I need to stop archive log for a while and enable it later during DB running.
I check Oracle documents, it only mentions changing archive log mode at DB mounted but not open.
I am using oracle 10g. Is there any mechanism to / parameter to enable or disable archive log mode? can I enable arching directly from pfile without touching the startup process?
How after a re-catalog of an archivelog, RMAN knows that the archivelog will be needed and in the right order?
If the re-catalog and subsequent crosscheck has changed the path of the archivelog will RMAN ignore the path and just recognize the archivelog name and format?
We are having an intermittent problem related to failing RMAN archive log backups. Normally everything works fine but once every fortnight or so the archive log backup starts to fail with the below message. We run two Oracle instances on this windows box, so they are using same oracle and TSM client binaries, but it is only of the instances that have this problem - the largest instance though. Restarting the Oracle instance solves the problem and everything is back to normal, until next time ...
This is the error message in the rman log file CODERMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of allocate command on c1 channel at 03/27/2013 11:00:29 ORA-03113: end-of-file on communication channel
Trace file CODE Trace file R:\ORA_DATA\SDC002\diag\rdbms\sdc002\sdc002\trace\sdc002_ora_12328.trc Oracle Database 11g Release 11.2.0.3.0 - 64bit Production Windows NT Version V6.1 Service Pack 1 CPU : 40 - type 8664, 20 Physical Cores Process Affinity : 0x0x0000000000000000 Memory (Avail/Total): Ph:85656M/147445M, Ph+PgF:96175M/157683M Instance name: sdc002 Redo thread mounted by this instance: 1 Oracle process number: 57 Windows thread id: 12328, image: ORACLE.EXE (SHAD)
I have the incident file as well if that is of any use.
Could the problem be related to running two backups in parallel?
We run full backups once a week and both this time and last time the archive log backup failed it was in conjunction to when the full backup also was running.
Is there any other solution to the problem than restarting the oracle instance?
Since this is a busy production instance it is a big problem for us to restart it outside of maintenance windows.
on our 10.2.0.5 database, when we run full backup, my system performance comes to an halt. we run full backup and then do a validate backup to validate the structure of the database etc. Database performance takes a hit and all of the application connections goes in wait mode: On ASH or AWR - this is the top wait i see:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of sql command on default channel at 01/26/2013 22:48:56 RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current ORA-00258: manual archiving in NOARCHIVELOG mode must identify log RMAN>
I am trying to remove archive log file on my standby site but I am getting the following message. There are lots of archive logs are present on the storage but rman is unable to displaying that.
RMAN> list archivelog all;
specification does not match any archived log in the repositoryRMAN>
We are going to implement oracle 11g. Now I wanna use rman to take the incremental backup in the follwing way:
Level-0 backup weekly, in the way:
run { allocate channel c1 type disk; allocate channel c2 type disk; BACKUP incremental level 0 DATABASE TAG 'Weekly_full' FORMAT 'E:RMAN_backupweekly_full_%d_%Y%M%D_s%s_p%p.bak'; backup archivelog all not backed up 1 times delete input TAG 'Weekly_full_arc' FORMAT 'E:RMAN_backupweekly_full_arc_%d_%Y%M%D_s%s_p%p.bak';
[code].....
and RETENTION POLICY TO RECOVERY WINDOW is set to 10 days, so that there is no chance that i will delete expired backup before taking backup.
Now my question is,
1) Is the way is correct that there is no wrong configuration. My main concern is about archive log, is it correct?
2) As i am deleting archive log files with the backup and after that the expired archive log backup is also deleted, so is there any chance of failure in recovery.
3) here how archive log backup will work with 10 days retention policy.
The customer wants the RMAN recovery catalog database to be highly available so that none of the RMAN database backup jobs are impacted at the time of taking the database backups. There are are 200+ databases running on OEL, RHEL and Windows. So we planned to host the recovery catalog database on Oracle Active DataGuard 11.2.0.1 Enterprise Edition on RedHat EL 5.8 version on two physical servers.
The Primary Instance will be in one server in the Primary DC and the Standby Instance will be on another server in another DC. Also all the database datafiles are hosted in ASM Diskgroups on SAN (DATA, FRA, REDO, ARCH diskgroups). Are there any specific RPM/patch/OS user custom/specific settings or configurations needed..?
I trying to backup archive logs using rman in standby database. I'm able to backup archive logs using simple command it get's successfully completed. rman > BACKUP ARCHIVELOG ALL When i'm trying to do with keep command it's getting failed.I'm trying to do on physical standby databaseBACKUP ARCHIVELOG ALL KEEP UNTIL TIME 'SYSDATE+100' TAG = 'TEST'.
I have Oracle 10gR2 database on a windows server, I have scheduled rman backup for this database from Solaris server
set echo onrun { crosscheck archivelog all; backup check logical database plus archivelog; delete noprompt obsolete device type DISK; } exit;
It is deleting the obsolete backup pieces but it is not deleting old archive logs (obsolete archive logs) and it is not even showing old archives as obsolete when I check thru report obsolete
We have a nightly rman backup that was complete and clean.The backup contains a Data File, Control File and a backup Archive Log file.The database server crashed with all the subsequent archive logs lost.
We are trying to recover from the three backup files.We are bumping into the backup piece missing as all the archive logs are done. how to restore with the exising backup files. the lost archive logs are probably salvageable.
If I want to take Rman archive log backup with delete input command , how the archive logs will be copied to standby database
For eg
I am taking archive backup as
RMAN>backup archivelog all delete input;
here consider few archives are not copied to standby database (due to nw issue) then how standby will receives these missing archives as those are deleted by rman backup at primary side.
I am not getting any document related to above query.
I had a production db with archive logging enabled
SQL> select name,status 2 from v$archived_log;
NAME STATUS ---------------------------------------- - D:ORACLEARCHIVE_ORCL11_13.DBF A D:ORACLEARCHIVE_ORCL11_14.DBF A D:ORACLEARCHIVE_ORCL11_15.DBF A
[code]...
So i need to restore archivelogs by using sequence
RMAN>RESTORE ARCHIVELOG FROM SEQUENCE 20 UNTIL SEQUENCE 28; So the restore is completed successfully So its very hard to monitor archivelog files i feel i should have included all archivelog files while taking RMAN backup
RMAN >backup database plus archivelog all delete input;
but the problem is my RMAN backup is already 360GB in size and it takes 4-5 hrs to complete .so i need to schedule RMAN backup at one time (e.g sunday) ,delete the archivelog files older than sundayand now schedule the archivelog backup at another day (e.g wed &sat)
my question is where i have to change my script to backup all avaialbe archivelog files if old archivelog files are deleted at os level?
RMAN> run { 2> allocate channel c1 type disk; 3> sql 'alter system archive log current'; 4> backup archivelog all format 'D:oracleackuplog_t%t_s%s_p%p' delete input; 5> release channel c1; 6> }
rman is used to duplicate database A to database B on another host
the duplicate process worked fine before we started testing encryption
the duplicate process worked fine with database A having an encrypted column in one table in a non-encrypted tablespace
Now, database A has an encrypted tablespace with nothing currently in it. The duplicate process now ultimately fails with ORA-19913, unable to decrypt backup.
I am not using encrypted backups, not specifying encrypt or decrypt anywhere in the duplication process. The only thing that is encrypted is the one tablespace in database A. I have the same wallet files on Host A (database A) and Host B (database B). Wallets are open. So why does the duplication process fail because the backup cannot be decrypted?
I want to run form 10g in mode debug, however when i set break point in code and press shift+ F9 ( or run Debug by click icon on Form 10) then Form still run but not run in mode debug. Now i want to run form 10g in mode debug, how do i do?
I have Oracle loaded on a server. I have three database instances - /db1, /db2, /db3. I want to put the database in backup mode before I take a backup copy of the three database instances.
Is the database put in backup mode just once and then the three instances can be backed up? Or does each instance need its own script to put the database in backup mode?
