RMAN :: Oracle Recovery Catalog Database In Primary And Standby Mode
Jul 9, 2013
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?
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?
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.
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?
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 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.
Here we have a data guard environment with db1(db_unique_name) as primary and db2(db_unique_name) as physical standby database. Also we configured one schema on a third machine as catalog database using following steps. The steps executed in catalog database(appsdb):
SQL> create tablespace rmancatlog_tbs datafile '/u01/app/oracle/oradata/NEW/rman_catalog.dbf' size 500M autoextend off extent management local segment space management auto;
SQL> create user rman identified by oracle 2 default tablespace rmancatlog_tbs 3 quota unlimited on rmancatlog_tbs 4 ;SQL> GRANT connect, resource, recovery_catalog_owner TO rman;
RMAN> create catalog; recovery catalog created
Added tns entries of catalog database in primary and standby. Then from primary database we tried to register to catalog database. It is showing that it is registering. But every query afterwards in rman is throwing the error. Below are the steps and error:
[oracle@db1 ~]$ rman target sys/oracle catalog rman/oracle@appsdb Recovery Manager: Release 10.2.0.3.0 - Production on Mon Aug 13 21:39:32 2012 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: NIOS (DBID=1589015669) connected to recovery catalog database [code]....
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 ?.
I have changed from the "ARCH" attribute to "LGWR" attribute of the LOG_ARCHIVE_DEST_n initialization parameter. But I have not changed the protection mode(Maximum Performance). I would like to know whether there is any impact in the behavior of the database, if we do not change the mode from "MAXIMUM PERFORMANCE" to "MAXIMUM AVAILABILITY"?
i have done oracle data guard between two databases (database A is the primary) and (database B is the standby), and it was working fine for two weeks, then the network admin did some changes on the firewall on standby side, which made the primary database can not write on standby redo log , so archives was generated on primary and do not generated on standby by, now we solve the firewall probelm and new archives generated on primary is generated on atandby too, but now i have a gap in archives on standby database and standby database now is not synchronized with primary database, and data changes happen on primary is not reflected on standby, also archives that were generated on primary and did not generated on standby during the problem time is not registered in V$ARCHIVED_LOG neither on primary database nor on standby database
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
If flashback is enable in physical standby database 1. If we failover at 11AM can I flash back NEW primary database to 6 AM ? 2. if I convert physically standby database to snapshot standby database at 11AM , Can I flashback snapshot standby database to 6 AM and do some works on it (DML operations) then converting the snapshot standby database into physical standby database ?
I have installed oracle 11g standard edition one and created both primary and standby database. now i want to know how to switch(convert) primary database to standby database.
I am using RAC to RAC data guard environment. Os hp-unix. during primary(old standby) to standby(old primary) switchover I am ussing:
SQL>ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
I have 11.2.0.1 environment with standby and when performing switch over - it was hanging for more than 2 hours and i had to cancel it. This is what all i see in the database alert.log:
Errors in file /u02/app/oracle/diag/rdbms/drpdb/drpdb1/trace/drpdb1_m000_15160.trc: ORA-01155: the database is being opened, closed, mounted or dismounted Thu Apr 04 17:44:03 2013 Errors in file /u02/app/oracle/diag/rdbms/drpdb/drpdb1/trace/drpdb1_m000_15780.trc: ORA-01155: the database is being opened, closed, mounted or dismounted Thu Apr 04 17:59:03 2013 Errors in file /u02/app/oracle/diag/rdbms/drpdb/drpdb1/trace/drpdb1_m001_16373.trc:
[code]....
ORA-01155: the database is being opened, closed, mounted or dismounted.
we are getting below error on alert log file in logical standby database from May 2013 how can find time of sequence creation and how can restore these sequence redo files and sysnc databases primary and standby
Snipped of alert log: Wed Jun 10 15:29:40 2013 Fetching gap sequence in thread 1, gap sequence 62079-62178 Wed Jun 10 15:29:50 2013 Fetching gap sequence in thread 1, gap sequence 62079-62178 Wed Jun 10 15:30:01 2013 Fetching gap sequence in thread 1, gap sequence 62079-62178
,I have a test environment with Primary DB Server, Physical Standby and Logical Standby.The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?My steps e.g.:1. Make a new server for my new_log_stdb and repair structure of catalogs;2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;3.
Restore DB with RMAN from backup to new_log_stdb;4. On cur_log_stdb execute "alter database stop logical standby apply";5. Change a DNS name from cur_log_stdb to new_log_stdb;6. On new_log_stdb execute "alter database start logical standby apply immediate";I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created. Configuration:Oracle Linux 6.4Oracle Database 11.2.0.3Primary and Physical with Data Guard
