Backup & Recovery :: Remove Duplicate DBID In RMAN Catalog
Feb 17, 2011
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 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 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 ?.
We are doing RMAN Duplicate set until time to refresh daily our test database for our developers and it taking long time to finish. We noticed on the restore log that RMAN was using a day old old backup pieces to refresh the test database and don't immediately use the latest backup pieces instead.
For additional details here's the rman duplicate command we are using which we run daily(mon-sat) at 4am once daily full backup on production completed.
RMAN Duplicate commands: run { set until time "to_date(to_char(sysdate,'Mon DD YYYY') || ' 04:00:00', 'Mon DD YYYY HH24:MI:SS')"; allocate auxiliary channel ch1 type disk; duplicate target database to testdb; } exit
Is there a way on how to let RMAN use the latest backup pieces instead?
Performing backups on the physical standby via RMAN. We need to restore our test database, and right now it is equivalent to the production. The DUPLICATE command seemed the best bet. We have controlfile and SPFile both on Auto-backup, and the RMAN on a six day retention with weekly 0 level backups and nightly level 1 cumulative backups.
However, when I run the DUPLICATE it chokes being unable to find a current controlfile nor one in backup, even though we have six days worth of supposedly good (validated) backups. We are not using a catalog, rather the DB controlfile.
The solution to this error is reopen the database and try again. however, the physical standby cannot be opened. It is the standby. What if we move the last backup to the primary database, "register" it there, and try this DUPLICATE?
I have seen nothing on this in my searches, and the Oracle documentation does not address this, though it recommends backup from the Physical Standby.
I want to duplicate a prod database in to a dev db.I am using catalog database to connect to target and auxiliary datbase.I copied all backupsets to the local disk on Dev env in the correct path.For RMAN duplicate ,does the backuppeices need to be present on PROD filesystem as well or just DEV filesystem or both.
I have a RUN file within a script to duplicate a database. As part of this RUN file I also run the command configure controlfile autobackup off; as part of this RUN file. However, this command has turned off backup of the control file on the AUXILLARY database (i.e. production) as well as the TARGET database (test). Is this supposed to happen?
My run file is:
rman TARGET sys/XXXX@${DB}-SOURCE AUXILIARY / RUN { allocate AUXILIARY channel a1 type disk; allocate AUXILIARY channel a2 type disk; allocate AUXILIARY channel a3 type disk; allocate AUXILIARY channel a4 type disk;
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.
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 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?
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.
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..?
We have production database and standby database in 11g.
Production db server is taking care by different team even I don't have any access of the production server and I am responsible only for standby server. As of now everything is working fine except database backup on standby server because standby server is not register in catalog.
How to register standby server in catalog for RMAN backup?
