Register Standby Database On Catalog Server For RMAN Backup
Jun 12, 2012
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?
I have created database with 11.2.0.3 in RHEL 5. I have catalog database(RMAN) with version 10.2.0.1 and 5 databases with different versions(10.2.0.1,10.2.0.3,10.2.0.5) registered with this catalog databases.
Now I want to register the 11.2.0.3 database with catalog (RMAN) database.
Am getting error while I register :
#rman target / catalog=rman/rman@rman
connected to target database: TEST (DBID=12345678) connected to recovery catalog database
RMAN> register database;
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of register command on default channel at 03/04/2013 10:27:12 RMAN-10015: error compiling PL/SQL program RMAN-10033: error during compilation of job step 1: ORA-04023: Object RMAN.DBMS_RCVCAT could not be validated or authorized
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..?
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 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
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 started restoring and testing all the backups. So far I did good and I wanted to restore and test in different host. I couldn't find any online documentation regarding restore full back up in a new different server (With same OS and same version of Oracle) without RMAN catalog database.
for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';sql statement: alter system archive log current noswitch RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitchORA-01109: database not open Recovery Manager: Release 11.2.0.1.0Oracle databaes Release 11.2.0.1.0 64 bitOS:RHEL 6 x86-64 bit Secondly,
do I need to cancel manged recovery while taking rman backups on standby. I scanned thru MOS but could find solutions for rman with active DG.
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'.
Can I register a database say MYDB in datacenter1 with two different catalogs i.e., I have one rman catalog a datacenter1 location and another rman catalog in datacenter2 location. So, can I register MYDB to rman catalogs at datacenter1 and datacenter2. If, so how can we keep rman catalogs at datacenter1 and datacenter2 in sync. For MYDB rman backups I just want to use local rman catalog which is datacenter1. But I just want to keep a redundant copy of the rman catalog.
===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of register command at 08/15/2013 19:48:59RMAN-03014: implicit resync of recovery catalog failedRMAN-03009: failure of full resync command on default channel at 08/15/2013 19:48:59ORA-01580: error creating control backup file +ORALIN_RECO/snapcf_oralin.fORA- [code][....
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
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
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 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 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.
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 One Production and one logical standby database . Due to tape problem we are unable to take backups of primary . And due to business , we cannot take back up on disk in hot period(Bank database ) .
If i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? . Logical standby is in sync with primary .
creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0) Operating System:Linux 5 Error: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52 RMAN-03015: error occurred in stored script Memory Script RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor [code]....
provide any work arounds to proceed further in creating the standby database.
The script has successfully created on standby db all controlfiles and also has copied 2 data files DATA01.DBF and DATA02.DBF into the correct location. Then the errors above kicked in and stopped the rman dup process.
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?