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?
New to oracle FAQ. I'm interested in oracle, waiting to explore more Technic's in 10g with a proper guidance. Hope i'm in the right place.Here is my question.
I need steps for configuring rman cloning with catalog & without catalog.were in prod db the source is in /u01 & in auxiliary db the client want in /u05. how to do it. here i have recreate control file or not
starting full resync of recovery catalog RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of allocate command at 02/18/2013 05:00:06 RMAN-03014: implicit resync of recovery catalog failed RMAN-03009: failure of full resync command on default channel at 02/18/2013 05:00:06 ORA-02291: integrity constraint (REPOSDB.ORL_F1) violated - parent key not found
we have a cluster of two nodes having oracle 11G R2 and another single instance server where RMAN is configured and this is backup server.i have created the service between the the target database and backup server and they are working fine i.e tnsping work fine at both sites.Now i have physical backup scripts written at one of cluster node and scripts run at crontab. The backup include full_backup , archive backup etc.
Now all physical backups work fine that is connecting RMAN and then catalog and then complete the backup but the full_backup do not connect catalog and throw this error that it do not know the SID in the connect descriptor. the tnsping output (from target ) is as followed fedb112 # tnsping bkp
TNS Ping Utility for Solaris: Version 11.2.0.1.0 - Production on 24-JAN-2012 14:11:45 Copyright (c) 1997, 2009, Oracle. All rights reserved. Used parameter files:
Used TNSNAMES adapter to resolve the alias
[code]...
in above scripts " connect catalog rcowner/rcowner@bkp " do not connect while i have other two scripts for incremental backup and archival backup, have the same code but they connect successfully and this one do not
now i run lsnrctl status at backup server , as follows
LSNRCTL for Solaris: Version 11.2.0.1.0 - Production on 24-JAN-2012 13:49:44
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=10.x.x.x)(PORT=1521))) STATUS of the LISTENER ------------------------ Alias LISTENER
[code]...
why it do not connect to RMAN catalog and use control file instead for backup
We are having 2 DB's on separate servers but both the DB is having same DBID and NAME. Also both the backup is planned to execute from one rman catalog DB.
Will the catalog DB confuse, when we execute backup for both the DB at same.
Database version : 11.1.0.7 Applications R12 (12.1.3) Operating system : Redhat linux 5.5
I would like to know how to create recovery catalog database to acheive rman backups as control file will not keep backup info longer. This is for our production database what are the requirements before doing so and what happens to configure retension policy to recovery window.
Initially plan of taking backup to disk and later moving backups to tape device
I want to remove matching dbid's from the rman catalog without compromising te integrity of the catalog. I do however know a single way of removing them and its using the dbid and db_key which in my case are not not unique. The funny thing is they've running normally for a year now.
I am using RMAN with a recovery catalog option on a separate Database. My question is
When we use catalog does RMAN keep the information in Control file of the Target Database as well or only in recovery catalog? I am asking this in case We lost the database which contains the recovery catalog what to do?
I configured recovery catalog and started Full online backup using EMC Networker. In EMC Networker I set three months policy to keep Backup.I didn't change redundancy.
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
My question is, if I need to restore Backup of last 15 days then I can ?.
How one should know whether RMAN is using target database control file or using separate catalog database. Also what one should do if he dont have catalog users credentials.
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 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.
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.
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).
I was trying to backup my database via RMAN and I had deleted a datafile from the database while it was still in open mode.Since I can't return back to mount stage again,I tried to bring the tablespace pertaining to that datafile offline and then restore backup of the tablespace but it's falshing error during recovery.
When I try to restore entire database,it is not even able to restore.
1. My RAC (old RAC) had got a failures from one node, then there was only one existing node now.
2. I configured a RAC (new RAC) on 2 other servers, both of them (old-RAC and new-RAC) has got same OS version, platform and Oracle version release.
3. I took a full backup yesterday plus archivelog in the node of old-Rac, configure NFS in new-Rac to make the backup within remote-share NFS.
The only problem still now that I've restore/recovery/duplicated single instance, not Rac. So, may you guide me to do it?
Information:
Old-Rac & New-Rac: + Cluster 11g: CFS + Database: 2 nodes with same instance name (cbs1-cbs2) + Location for CRS_HOME and ORACLE_HOME: Same to be. + Location of archivelog: Same to be (+ARCHIVE)
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.
I have one database which is fully restored from client backup (RMAN). Database was up and running perfectly. By mistake I have deleted one schema/user and its tablespace using drop command. I have RMAN backup so want to restore that schema's datafile from the backup but when I run below statement it throwing error :
run { allocate channel c1 device type disk ; set newname for datafile 45 to '/ora/oradata/JSIP1/data.dbf'; RESTORE datafile 45; switch datafile 45; recover datafile 45; SQL ' alter database datafile 45 online ' ; } RMAN-20201: datafile 45 not found in recovery catalog
or If I go and try to restore the tablespace of that schemas using below block it throws error:
run { allocate channel c1 device type disk ; RESTORE TABLESPACE DATA; RECOVER TABLESPACE DATA; SQL 'ALTER TABLESPACE DATA ONLINE'; } RMAN - 20202 Tablespace not found in the recovery catalog RMAN -06019 could not transalate tablespace name "DATA"
how to restored drop users and tablespace data from the RMAN backup.
I need to restore entire database(sp+control+datafile) to new host.I have started the instance with nomount( and it has created a dummy parameter file).Now, I need to fire the command to restore spfile.
RUN { ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='...'; RESTORE SPFILE TO PFILE '?/oradata/test/inittrgta.ora' FROM AUTOBACKUP; SHUTDOWN ABORT; }
My questions:-
1.How will RMAN find the location of backupset(Since there is controlfile for neither target or catalog database)?
2.How does RMAN reache the backupset in case of a)tape b)disk?
How to restore database if rman catalog corrupted and we we dont have bacup of catalog db ..all the backup info are stored in catalog db for prod databases.
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..?