I am running the following command to backup my archive logs and want to keep at least two hours of .arc files on disk.
rman < connect target login/password
connect catalog login/password
show all;
sql "alter system archive log current";
backup filesperset 5 archivelog until time 'sysdate-2/24'
format $FILE_DEST_ARCH
delete input ;
resync catalog;
EOT
On some occassions, there will not be any archive logs that meet this criteria and I get the following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 12/01/2010 12:50:58
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specificati
on does not match any archive log in the recovery catalog
Is there anything I can do to the rman command above that will prevent this error from happening but yet keeping same functionality?
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> }
There is an incident that in production database 1000 archive log files generated.From 1000 files, 100 archive log files have been removed.When i take incremental backup next day , what will happen in database?
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.
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>
I am using Oracle RAC 11gR2.I am planing to move my old trace files to an archive location.
I have the below questions concerning the users and groups used by Oracle RAC when moving the trace files.It is related to the permissions but it is about oracle behavior.
The trace files of database (oracle user) are created as below:
284 -rw-r----- 1 oracle asmadmin 283571 Aug 20 18:08 PPRD1_mmon_13893716.trc 4 -rw-r----- 1 oracle asmadmin 125 Aug 20 18:10 PPRD1_gcr0_11730998.trm 4 -rw-r----- 1 oracle asmadmin 2833 Aug 20 18:10 PPRD1_gcr0_11730998.trc 580 -rw-r----- 1 oracle asmadmin 588489 Aug 20 18:12 PPRD1_lmhb_15859792.trm
[code]....
when moving the files using the oracle user it will be created as oracle:oinstall and not oracle:asmadmin since asmadmin is not a group of the oracle user.
1. How oracle created my trace and log files with permission oracle:asmadmin?
2. How should I move these files? I moved it using the Oracle user and it was created as oracle:oinstall with Operating system error "unable to duplicate owner and mode after move"
Is there any way I can get all the archive log files present in a backup piece. I tried following but it always gives me all the log files for each piece:
**** SQL> select s.set_stamp, s.set_count, s.PIECES, s.backup_type, s.controlfile_included from v$backup_set s, v$backup_piece p where s.set_stamp=p.set_stamp and s.set_count=p.set_count and p.handle='5mjv4do0_1_1';
Actually, i have test database open in read only and i want to apply archive files carry from production database at daily level. When i'm going for recovery, since database is already in consistent state, it is not asking for recovery.
ora-00257 archiver error. connect internal only until freed
when we tried to remove the unwanted arc files thro ASMCMD,we are getting below error:
ASMCMD> rm -ef 2011_04_05/ Unknown option: e usage: rm [-rf] <name1 name2 . . .> ASMCMD> rm -rf 2011_04_05/ ORA-15032: not all alterations performed ORA-15028: ASM file '+XCOM_BACKUP_DG/TXCOM/ARCHIVELOG/2011_04_05/thread_2_seq_27215.1143.747641143' not dropped; currently being accessed (DBD ERROR: OCIStmtExecute) ORA-15032: not all alterations performed ORA-15028: ASM file '+XCOM_BACKUP_DG/TXCOM/ARCHIVELOG/2011_04_05/thread_3_seq_21762.826.747641143' not dropped; currently being accessed (DBD ERROR: OCIStmtExecute) ORA-15032: not all alterations performed ORA-15177: cannot operate on system aliases (DBD ERROR: OCIStmtExecute)
I'm facing problem with archive log file size, Archive logs are generated with only of 90m or 92m or 94m(Variable sizes of less than 100m), Although i had set 100m for each of my redo log file. Here i'm providing my create db script for your reference. I want to know why the log switches before it reaches 100m.Is there any connection of intial 10m for my .dbf files.
There is a archive log backupset,and the backup set contains many archive log file,and now i want extract to a directory,how can i do?
BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 3 86.20M DISK 00:00:21 02-JUN-12 BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20120602T113622 Piece Name: /u02/rman_bak/20120602/archive_log_t784899382_s4_p1
I am having a issue, we are trying to restore our db from control files using Symantec Backup exec, but job fails giving me error go to table spaces select all table spaces and unchecked roll forward.
i am unable to find way to uncheck the table spaces. Here is the complete description.
Cause
The system catalog tablespace "syscatspace" contains all of the system catalog information for the tables. Syscatspace needs to be rolled forward first, and then the other tablespaces must be rolled forward.
Solution
Workaround:
When the restore operation is run from a tablespace level backup, perform the rollforward for the syscatspace tablespace first and then for other tablespaces.
Execute the rollforward operation as a DBA operation. The sequence of the recovery process should be as follows:
1. Select all tablespaces, uncheck the rollforward option and run the restore job. 2. Run the rollforward operation as a DBA initiated operation:
rollforward syscatspace to point in time / end of logs. e.g. db2 => rollforward database UEXIT to end of logs and complete Tablespace (SYSCATSPACE) online
3. Perform rollforward of all other tablespaces.
e.g. db2 => rollforward database UEXIT to end of logs and complete tablespace (SYSTOO LSPACE,USERSPACE1) online
Refer to IBM DB2 documentation for more information on DBA-initiated operations.
I have an oracle autoback of controlfile and spfile. I am trying to restore the production database using this backup, into a new server with a different directory structure.
I have completed the following steps in the restore process.
1. Creating a pfile from spfile
2. Changing the the location of cdump, udump, bdump and the control files ( there are three )
3. Then creating a spfile from this pfile
I am stuck on the next step where to rename all the datafiles and tempfile and restore the database. Following is what I did.
After mounting the database in RMAN, tried to run the following.
RMAN> run 2> { 3> allocate channel c1 device type disk 4> ; 5> @/home/oracle/rman_scripts/newloc.rman 6> SET NEWNAME FOR DATAFILE 1 TO '/u02/oradata/dorian/system01.dbf'; 7> SET NEWNAME FOR DATAFILE 2 TO '/u02/oradata/dorian/undotbs01.dbf'; 8> SET NEWNAME FOR DATAFILE 3 TO '/u02/oradata/dorian/sysaux01.dbf'; 9> SET NEWNAME FOR DATAFILE 4 TO '/u02/oradata/dorian/users01.dbf';
[code]....
I am getting the following error message.
Starting restore at 25-JAN-2012 21:26:48 released channel: c1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 01/25/2012 21:26:49 RMAN-06026: some targets not found - aborting restore RMAN-06100: no channel to restore a backup or copy of datafile 30 RMAN-06100: no channel to restore a backup or copy of datafile 29 RMAN-06100: no channel to restore a backup or copy of datafile 28
The problem is at times there may not be any archive files that meet this criteria and RMAN throws an error
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archived log in the recovery catalog
I was considering using the following code to see if there are any available .arc files that meet the backup criteria.
set pagesize 0 feedback off verify off heading off echo off; select count(1) from v$archived_log where COMPLETION_TIME < sysdate-$KEEP_ARCHIVE_HOURS/24 and backup_count = 0 and name is not null;
While testing on several systems, I found that the above-mentioned query picked up some redo-logs (*.rdo) I can only assume that these redo logs were used for a DB recovery.
1) Is my assumtion correct about the .rdo files in the v$archived_logs table
2) I would hate to add special logic and look for something like name substr(name, *.arc) (pardon the syntax). Therefore, is there a way to get rid of these *.rdo files?
My operation system is Linux,there is a database on it . the other server's operation system is windows.
SQL> SELECT * FROM V$VERSION;
BANNER ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod PL/SQL Release 10.2.0.1.0 - Production CORE 10.2.0.1.0 Production TNS for Linux: Version 10.2.0.1.0 - Production NLSRTL Version 10.2.0.1.0 - Production
SQL>
Now,i want to implement hot backup on my oracle database which install the linux operation system ,but i expect the hot backup files can storage on the servers of the Windows operation system directly.
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.
Starting restore at 18-AUG-11 released channel: c1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of restore command at 08/18/2011 09:20:21 RMAN-06004: ORACLE error from recovery catalog database: RMAN-20242: specification does not match any archive log in the recovery catalog
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.
My supervisor wants to remove all the archivelogs since it was just a test for 1 year the DB is not actually YET been used. Problem is they want it to be used as soon as possible w/o recreating again the database and just removing some data on tables and removed archive logs. how to safely removed the existing archived logs and create a full backup with archived fresh to sequence 1.
We are using the following commands to take hot backup of our RAC 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 [code]...... ======================= 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 =======================
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.
