while executing a clone script i got the below error : -
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/15/2011 20:07:34
RMAN-12010: automatic channel allocation initialization failed
RMAN-06758: DB_UNIQUE_NAME is not unique in the recovery catalog
Here i understand that RMAN couldn't find which SPFILE to use to restore the target DB.
How do i check for the DB_UNIQUE_NAME in recovery catalog?
The proposed solution that i found was Use the FOR DB_UNIQUE_NAME option to specify the name of the instance whose parameter file you want to restore. how to implement this in my clone script?
While connecting to target database from stand database. I am getting below error.
calhost dbs]$ sqlplus system/oracle@proddb
SQL*Plus: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:10 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options
SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options [standdb@localhost dbs]$ rman target system/oracle@proddb auxiliary system/oracle@standdb
Recovery Manager: Release 10.2.0.1.0 - Production on Sat Jun 22 00:18:22 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
whats the difference between channel and parallelism in RMAN ?
What is the Oracle recommendation for RMAN channel allocation ? I have read some were that RMAN channel allocation must be 4 times of the Server CPU -1. Say for example if there are 2 cpu in the server, then the channel allocation would be 4 * 2 -1 = 7 ?
when i try to connect with the prod database by logging in the server,then it raise the above error.
i want to aware you with what i have done before it--
(1) this database is running on the port 1526 not on 1521, because of some reason new listner have to made.
(2) i can easily access this database without any error from my local machine, then it doesnot raise-ORA-12154: TNS:could not resolve the connect identifier specified
now i am going to take backup from RMAN at my local machine of same database , then
C:UsersNeetesh>rman target /@proddb
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Oct 3 16:29:47 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-00554: initialization of internal recovery manager package failed RMAN-04005: error from target database: ORA-12154: TNS:could not resolve the connect identifier specified C:UsersNeetesh>
One of database, while taking backup using RMAN, it failed with the following error:
RMAN-03009: failure of backup command on DISK4 channel at 11/28/2012 09:47:29 ORA-19566: exceeded limit of 0 corrupt blocks for file <faile_name>
I used DBV to identify the number of blocks corrupted.
I referred the Metalink iD 457422.1 & 336133.1. But it did not work since the corrupted blocks have got object in it.
I could able to find the object as well. it is one of the table in the datafile.
I used 'ALTER TABLE ... MOVE..' command to see if that works. But again getting the same error while taking the backup and corrupted blocks still exists.
When I am issuing below command from auxiliary database, getting ORA-00554.My tnsping is okay from both the side, remote login is exclusion. Password file is also okay.I ran UTLRP.sql twice to compile invalid packages.
From Auxiliary Database [ashish@localhost dbs]$ rman target sys/oracle@suman auxiliary / Recovery Manager: Release 10.2.0.1.0 - Production on Thu Apr 11 19:04:03 2013 Copyright (c) 1982, 2005, Oracle. All rights reserved.
it is necessary to allocate channel for rman back up and during rman back up what should be the state of target database me script for configuration and incremental level 1 daily back up script
and normal oracle secure incremental level bacl up script back up should be done daily
what is the meaning of 'SBT_TAPE' in the following command in RMAN? In the following command, does it refer to a tape drive, or a hard disk backup?
allocate channel t1 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=<a backup server server name>,NSR_CLIENT=<a oracle server>,NSR_DATA_VOLUME_POOL=ORACLE ARCHIVE LOG)';
Backup for database has been working fine until today. Today, about 1/3 of the way through the backup (large database), I got this... RMAN-12005: error during channel cleanup RMAN-10038: database session for channel sbt_4 terminated unexpectedly ...and the backup died.
Never seen before and the research I've done online has been less than useful. This database is an SAP/oracle db with brtools 7.20 (22) and is using the new parameter in its init.sap file, called "_rman_chan_failo = yes", to address disagreement between brtools and oracle about channel drops being ok if all datafiles backed up.
Nothing in the alert log at the time of this error.
We are trying to restore a database on the different server using RAM incremental level 0 and 1 backups. We have weekly Incremental level 0 backups along with incremental backups on daily basis. During recovery of Incremental level 0 backup, RMAN is expecting/looking for Incremental Level 0 backup of prior week as well. Is this the usual process for RMAN to look for prior level 0 backup though we need to restore from the current level 0 backup and roll forward by a week with subsequent Level 1 backup.?
We intend to restore from the Level 0 of 1/16 and roll forward with daily incrementals till 1/22. RMAN is expecting level 0 backupsets from 1/9 backup as well and keep failing since those backups are not available. quick inputs since we are in middle of recovery and trying to resolve if this is even doable.
I took database backup without "change the controlfile configuration autobackup on".. and unfortunately i deleted my controlfile. Then I tried to restore my controlfile but it gives error,now how can i restore controlfile is there any other way to restore controlfile with aautobackup..
I have problem on using "delete obsolete" in RMAN.
First, let describe my backup configuration.
1. Full backup every Monday (17-Oct, 10-Oct, 3-Oct, 26-Sep) 2. Incremental backup for other days 3. Enable autobackup of control file 4. Backup archive log every day 5. RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS 6. Execute "Delete obsolete" every day 7. control file is used instead of catalog
The results observed: 1. Backup of control files older than 30 days will be deleted 2. Backup of archive log files older than 30 days will be deleted. 3. Backup of datafiles older than ~14 days but before 30 days are also DELETED.
In my example, the backup of datafiles created at 26-Sep is deleted at 16-Oct.
I tried "restore database validate until time "sysdate-22"" at 17-Oct. And RMAN reported "datafile xx will be created automatically during restore operation". It seems that RMAN failed to do restoration up to 22 days ago. The retention policy I set seems not effective on datafile backups.
I checked view v$backup_set and the "Keep" is "No" and "Keep until" is empty.
The only thing I can think of, is the settings of "CONTROL_FILE_RECORD_KEEP_TIME". It is marked "7" in the Oracle, which is less than the retention. But I suppose this only causes the backup not deleted, but NOT be deleted earlier.
RMAN-03009: failure of backup command on t1 channel at 12/15/2012 06:15:11 RMAN-10015: error compiling PL/SQL program RMAN-10033: error during compilation of job step 2: ORA-00603: ORACLE server session terminated by fatal error ORA-04030: out of process memory when trying to allocate 400 bytes (PL/SQL DIANA,LISIMA: Add cells)
We received the above error message after the following event:
rman failed to backup because archivelog destination was out of space
We moved SOME of the archivelog file manually using operating system command mv to another location so that our application can run first.When the engineers restarted the rman to backup, we receive the above error.
I have 2 seperate rman backup one backup is of only datafile ,spfile and controlfile which i am able to restore and recover without any problem say bkp1 taken at 10 am
other set of backup is of only archive log files of same day but later time than datafile backup say bkp2 taken at 8pm...if i restore and recover bkp1 and try to restore bkp2 it gives error datafile exist (possibly due to fact both backup have control file)
if i just restore bkp1 and try to restore bkp2 so that i can do one recover at time it gives error datafile permission issue (possibly due to fact both backup have control file)
I want to restore database upto 8pm time how can i use both bkp1 and bkp2 to do it(restore datafiles and apply all archive logs on it)
I run DLY cold backups including controlfile & archivelogs and keep 3 gens of backups and archivelogs to 3 days also. What is the correct procedure to restore back to an old cold backup. Database is backed up Mon,Tue,Wed on Thur we require to bring database back to Tuesday DLY security.
I have tried: startup mount restore database from tag 'DLYTUE' recover database
( this just rolls forward on all archive logs once it restores datafiles, not getting to point to alter database open resetlogs.)
Next tried to :
recover database archivelog tag 'DLYTUE' ( same outcome )
What is the correct rman procedure including should I remove old archive logs from working OS directory ? Also need to know once I restore back and open database to TUE security how do you tidy up the archive logs and dumps which are no longer require i.e. : weds..
I have read about using the set until time option but how to I get absolute time from when cold backup completed if this is the correct procedure.
i have read from documentation but getting some error.
in last
E:Documents and SettingsAdministrator>rman Recovery Manager: Release 11.2.0.2.0 - Production on Sun Sep 30 03:03:09 2012 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. RMAN> connect auxiliary sys/12 connected to auxiliary database: XE (not mounted) RMAN> RMAN> DUPLICATE DATABASE TO xe
[code]...
Backup-Based Duplication Without a Target and a Recovery Catalog Connection?
I have a doubt regarding the process the RMAN follows for restore and recovery of the database.
My Level 0 full backup completes on Saturdays at around 11 am after taking 8 hours (It starts at 3am).On Sunday, I ask RMAN to restore (on a different box) till Saturday 11:30 am.Then, after the restore is successful, I recover it till 11:45 am.
The recovery also goes fine and Iam able to clone to test box.
Till what time is the database restored? I assume its till 11 am since the L0 backup finishes at 11 am though I have asked it to restore till 11:30 am
During the recovery, ONLY the archives generated between Saturday 3 am and till the time i asked for recovery (Saturday 11:45 am ) are required. But, checking the recovery log file, i was surprised to see that RMAN has restored archive files starting from Friday 9:30 pm (Much before the time the Level 0 backup even started).
