Oracle RMAN recovery catalog database in a Primary and Standby mode

Hello All,
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..?
Thanks in advance..
Regards,
Abhijit

"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"
Hi,
i think you can achieve HA for the catalog DB. (Rac and Asm should work fine)
There's no way (afaik) to use TAF with the rman backup. If you have a failure during a backup it simply fails.
There is no TAF in this situation.
Hope this helps.
Regs,
Drew

Similar Messages

Shell script to find MAX(SEQUENCE#) of primary and standby DB.

Hi All,
AIX 5.3 64bit DB:10.2.0.3.0
I am looking for a shell script which does the following:
Use SQL*Plus to query the MAX(SEQUENCE#) from both databases i.e., Primary and standby V$LOG_HISTORY view. If the STANDBY appears to be falling behind by 2 archive log files,then send alert mail to: [email protected]
We should be able to connect to primary DB from standby DB using ssh
For example: ssh ora<user>@hostname.domain
I use the following query to find out MAX(SEQUENCE#):
col logseq_on_standby new_value V_STDBY_LOGSEQ
select /*+ rule */ max(h.sequence#) logseq_on_standby
from v\$log_history h,
v\$parameter p
where h.thread# = to_number(decode(p.value,'0',1,p.value))
and p.name = 'thread';
Thanks for your time!!
Regards,

sent the shell script..
By the way is this hssawan!!!
Please check the shell script and let me know the following:
AIX 5.3 64bit DB:10.2.0.3.0
I am looking for a shell script which does the following:
Use SQL*Plus to query the MAX(SEQUENCE#) from both databases i.e., Primary and standby V$LOG_HISTORY view. If the STANDBY appears to be falling behind by 2 archive log files,then send alert mail to: [email protected]
We should be able to connect to primary DB from standby DB using ssh
For example: ssh ora<user>@hostname.domain
I use the following query to find out MAX(SEQUENCE#):
col logseq_on_standby new_value V_STDBY_LOGSEQ
select /*+ rule */ max(h.sequence#) logseq_on_standby
from v\$log_history h,
v\$parameter p
where h.thread# = to_number(decode(p.value,'0',1,p.value))
and p.name = 'thread';
Thanks for your time!!
Regards,

Config recovery catalog database

dear all.
i had read several documents about "create recovery catalog", but all of that start with statement
CREATE TABLESPACE
...and continue with CREATE USER, etc.
I want to create a NEW database for recovery catalog, this database what characteristics must to have ?? Anyone have a link or document where explain me how to create a database (only i need database creation) for recovery catalog.???
thanks
The version is ORacle 10gr2

hi,
the recovery catalog is just a normal database with a schema called rman or whatever you choose.
it should ideally be on a separate server to your target database. The RMAN database as with any other database should have multiplexed control files and redo files.
schema creation assumming windows O/S
-- Create tablepsace to hold repository
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
-- Create rman schema owner
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
then create the recovery catalog
C:>rman catalog=rman/rman@w2k1
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
C:>
then register your database
C:>rman catalog=rman/rman@w2k1 target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: W2K2 (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete
RMAN>
let us know how you get on.
rgds
alan

Error while rman recovery of database

We are using rman recovery for database clone.
I am getting the following error,
restoring datafile 00442 to /d05/u10/oracle/ndevdata/applsysd06.dbf
channel dup1: reading from backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u19ku1onq_t702604026_s15401_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u19ku1onq_t702604026_s15401_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1aku1ou5_t702604229_s15402_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u1aku1ou5_t702604229_s15402_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
ORA-19870: error reading backup piece /db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1
ORA-19505: failed to identify file "/db05/PROD_BACKUPS/inc0_dPROD_u1bku1pnr_t702605051_s15403_p1"
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
Additional information: 3
failover to previous backup
How to resolve this?
Thanks,
Kavitha

hi;
Please follow:
Re: erros while clong a db
Also check:
http://kr.forums.oracle.com/forums/thread.jspa?threadID=546746
Re: rapid clone from RMAN backup
Regard
Helios

Taking RMAN backup of primary and standby databases.

Hi,
I am going to setup a Standby for Primary two node RAC to single node standby.
My doubt is, in standby both primary and standby will have the same db_name. So how can i take the RMAN backup of both primary and standby by using a single catalog.
That is, we can register the primary DB with catalog using it's db_name. But how can we register the standby with catalog using same db_name as it is already registered.
Thanks,
Mahi

Are you using a physical or logical standby?
If its a physical standby why do you need to back up both databases? backup the standby and you are done, the backup from the standby can be recovered to either the live serever or the standby if needed, andt hen the archivelogs used to bring it up to date.
If its a logical standby then change the database name for the standby and you can back both up to the same catalog, or alternativly cretae a new catalog for the standby, either as a new database or a new schema in your existing catalog.

Query to identify the recovery catalog database name from target database

Hi,
How to get the recovery catalog database name from the registered target database?
i dont know my recovery catalog database for my target database.
I know we can use the query
select * from rc_database;
from recovery catalog database to know all the registered database with the recovery catalog but I want to know is there any way or query to identify the recovery catalog database name from target database to which the target database is registered
With Regards
Boobathi P

You can check the backup scripts which you use to backup your target database to get the catalog database name.
And check the corresponding connect string in TNSNAMES.ORA file or tnsping to get the server details of the catalog database.
Edited by: gopal on Apr 12, 2013 12:59 PM

Oracle data guard configuration for primary and standby db_name

I am working on configuring an active data guard for one primary DB and one standby DB. I have a few questions:
1. Can I use different db_name, db_unique_name and instance_name for primary and standby. For example: primary(db_name, db_unique_name and instance_name)=chicago. When I create standby DB with Rman backup and copy of pfile and control file from primary DB or use Grid control to create standby database. Oracle document or Grid control all keep standby db_name=chicago. Only make standby db_unique_name and instance_name=boston. Due to my application system condition, I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?
2. In primary datafiles, application system generate datafile name like this: hr_chicago_01.dbf, fn_chicago_01.dbf. When I move datafiles to standby server, if I plan to use db_name=boston for standby DB, can I rename datafiles as
hr_boston_01.dbf, fn_boston_01.dbf? In this way, datafile name match up with db_name. but I will create standby log group and members on primary and standby identically. If in future switching over, DB will not have problems.
3. If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standby. Then "alter database backup controlfile to trace" from promary and also " create pfile='/xxx/initSTANDBY.ora' from primary. Then modify init.ora and controlfile. Then run control.sql to bring standby DB up. After that, configure redo log shipping and apply with data guard or SQL. Is this a acceptable way to create physical standby DB?
Please advise your comments. Thanks in advance.

I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?NO. DB_NAME must be the same ("chicago") at both sites. The Standby will be using a different DB_UNIQUE_NAME (e.g. "boston") and can be using a different Instance name / SID (e.g. "boston").
can I rename datafiles Yes. The database file names can be changed.
If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standbyWhat is the difference between the first sentence (a backup of the primary) and the second sentence (a copy of the primary) ? A Copy is a backup.
Are you intending to differentiate between an RMAN Backup and a User-Managed (aka "scripted") backup ?
Normally, for DataGuard, tou can use non-RMAN methods to copy the database but there's no value add in this.
You'd still have to setup DataGuard ! (and I wonder if you'd have complications setting up Active DataGuard).
But remember that you MUST create the Standby controlfile from the Primary and copy it over to your Standby -- particularly as you are planning to use DataGuard. This is not created by 'alter database backup controlfile to trace' , but by 'ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename''
Hemant K Chitale

How to re-synch primary and standby database?

Hello everyone,
Working on 10g R2/windows server 2003, I have configured a physical standby database but, I have an issue, and don't know how to resolve it.
We were making an update that made some DDL and DML on our application, and for security reason we
1. we ensure that primary and standby are in sync
2. We made a cold backup of the primary database
3. We Deferred the redo shipping between primary and standby
4. We applied changes on primary database
But the big issue is that, for any reason my colleague did the following.
a) made above steps 1,2,3,4
b) after the update he kept the resulted archived log files generated during to another location
c) He restore the cold backup before the update(step 2 above)
c) he applied again the update.
Now the issue is
At the first update step(2), the sequence# 553 was applied to the stand by before the update
At the second update step(c) above another sequence# 553 was created but stored localy in the primary database, because the both servers were deverged (step 3 above).
Technically both servers cannot be in sync again,because sequence# 553 at the first update has next_change# 80307804 and sequenc# 553 at the second update has next_change# 80461356.
Question:
How Can I do to rollback the the first sequence# 553 ( before the first update) on the standby database? in order to apply the sequence#553 generated at the second update and then re-sync both servers to roll forward subsequent sequence#? 554,etc...
Thank you for your help

Hello,
I have just tried the FLASHBACK DATABASE TO SCN XXXXXXXX;
but it doesn't work.
Here are steps used from my local dev envirronnment
From the stand by I retrieved the following information.
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# FIRST_TIM NEXT_TIME
95 707168 707906 15-AUG-08 15-AUG-08
96 707906 708653 15-AUG-08 15-AUG-08
97 708653 709359 15-AUG-08 15-AUG-08
100 710951 711794 15-AUG-08 15-AUG-08
98 709359 710179 15-AUG-08 15-AUG-08
99 710179 710951 15-AUG-08 15-AUG-08
101 711794 712762 15-AUG-08 15-AUG-08
102 712762 713720 15-AUG-08 15-AUG-08
103 713720 714748 15-AUG-08 15-AUG-08
104 714748 715920 15-AUG-08 15-AUG-08
105 715920 739430 15-AUG-08 15-AUG-08
106 739430 800525 15-AUG-08 16-AUG-08
107 800525 875810 16-AUG-08 17-AUG-08
108 875810 916527 17-AUG-08 18-AUG-08
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database activate standby database; --> prepare to open stby in R/W mode
Database altered.
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 180358020 bytes
Database Buffers 423624704 bytes
Redo Buffers 7135232 bytes
Database mounted.
SQL> alter database set standby database to maximize performance;
Database altered.
SQL> alter database open;
Database altered.
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 180358020 bytes
Database Buffers 423624704 bytes
Redo Buffers 7135232 bytes
Database mounted.
Now I tried to mimic the flashback database as in the production, to bring it back to sequence# 105 above
SQL> flashback database to scn 739430;
flashback database to scn 739430
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38761: redo log sequence 75 in thread 1, incarnation 2 could not be
accessed
I'm reverted back the physical standby to its function
SQL> alter database convert to physical standby;
Database altered.
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 180358020 bytes
Database Buffers 423624704 bytes
Redo Buffers 7135232 bytes
Database mounted.
SQL> alter database recover managed standby database using current logfile disconne
Database altered.
Verifying if the MRP is up and running: YES see below
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC3: Becoming the 'no FAL' ARCH
ARC3: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Clearing online redo logfile 1 C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO11.LOG
11 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\local_destination1_orcl
Oldest online log sequence 110
Next log sequence to archive 0
Current log sequence 110
So, how can I reslove this issue? without creating the standby from scratch?
Thanks Again for your help

How to configure Enterprise Manager Database Control (EMDC) to make it work on 2 servers working (primary and standby) under DG rules

Hello everybody i use Oracle Database EE 11.2.0.4 with DG.
In those cases i need to get Enterprise Manager Database Control running against DB with no RAC and no DG i perform the following steps:
I Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:
DECLARE
CURSOR c1 IS
SELECT owner, synonym_name name
FROM dba_synonyms
WHERE table_owner = 'SYSMAN';
BEGIN
FOR r1 IN c1 LOOP
IF r1.owner = 'PUBLIC' THEN
EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;
ELSE
EXECUTE IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name;
END IF;
END LOOP;
END;
DROP USER mgmt_view CASCADE;
DROP ROLE mgmt_user;
DROP USER sysman CASCADE;
After that i run
emca -config dbcontrol db -repos recreate
But what should i do in cases i have 2 servers working (primary and standby) under DG rules?

Hi ,
It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control. This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality). In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
You can use EM 12c cloud control to monitor and manager Standby DB effectively
Ref to below link for details
Set Up and Manage Oracle Data Guard using Oracle Enterprise Manager Cloud Control 12c
Regards,
Rahul

Standby database(11g) was still in sync after stopping the primary and standby database listener.

Hello !!!
I have noticed that my standby database(11g) was still in sync after stopping the primary and standby database listener.
If this is the case then how log is transferring from primary to standby ? it is not using listener service ? kindly clarify

Read this Metalink Note:407040.1

How to sync primary and standby database in 11GR2 on linux

Hi ,
How to sync primary and standby database in 11GR2 on linux . Both my primay and standby are 3 node cluster each.
Can you please suggest a good link and brief steps .
Thanks

Are you trying to setup a new standby or sync an existing standby database?
OK I see it
"standby is behind the primary"
So you have a gap.
I would check both alert logs for a cause. You might find something like this
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.Look for ORA-00308 and ORA-27037 and ORA-16055.
There's no sense fixing the gap unless the cause is fixed too.
Also check out this post from a few days ago its dealing with similar issues.
How to sync the standby database with the primary?
If you find this helpful please mark it so.
Edited by: mseberg on Jul 20, 2011 4:37 PM

SCN number difference in primary and standby databases

Hi All,
Is it possible that primary database SCN is 20 and standby database SCN is 22 ? If yes , how it works ?
Thankyou !

I agree that it is possible depending on your setup. However, I read your posting and BLOG entry but it does not address out the Standby database has a GREATER SCN than the Primary.
The answer will depend on the type of standby database you have configured (LOGICAL vs PHYSICIAL) and perhaps if it is a SNAPSHOT Standby that has been used and not rolledback.
In what I would consider "Normal" situations the SCN of the standby database would always either be at the same SCN or be lagging.
I have not tested it but I could see where if you had a standby database that you converted to a SNAPSHOT Standby (11g ability), made changes to the standby and had not converted it back to a normal Standby then your SCN can be ahead in the standby because the changes had not been discarded yet.
Regards.
Tim

Require 9i Primary and Standby redo logs files same size?

Hi,
We have 9.2.0.6 Oracle RAC (2 node) and configured data guard (physical standby).
I want to increase redo log files size, but i can't this do same time primary and standby side.
Is there a rule, primary and standby database instances have same size redo log files?
If I increase only primary redo log files, is there any side effect? However I try this issue on test system. I increased all primary redo log files(if status='INACTIVE' drop redo log group and add redo log group, switch logfile,...)
, but i couldn't changed standby side. So the system is work well. Is this correct solution or not? How can i increase both sides redo log files?
Thank you for helps..

Thank you for your helps.. I found this issue answer:
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010448
Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
Add or drop an online redo log file:
To add an online redo log file, use a SQL statement such as this:
SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
To drop an online redo log file, use a SQL statement such as this:
SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
Repeat the statement you used in Step 3 on each standby database.
Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
bye..

Logfile groups for Primary and Standby

Hi,
Oracle documents say that the size of Log files should be the same for primary and Standby. Presently it is not the case. I have logfile 100M for Primary (PROD) and 50M for Standby. To change them I should add new groups with file of 100M to standby. And then drop the small logs(50M). in this case the group number would not be the same. Would it be a problem ? Any other solution ? Thank you.

.Oracle documents say that the size of Log files should be the same for primary and Standby. It is only a recommendation, but, not mandatory. However, a messaage will be written to the standby alertlog file when standby database log file size is smillar than its primary database log file size.
in this case the group number would not be the same. Would it be a problem It won't be a problem.
Jaffar

Can I have primary and standby in same OS but different releases.

All,
Can I have primary and standby DBs in same OS but in different releases?
i.e. primary is in RHEL 5 and standby is in RHEL 4, is it ok to setup or do we see any issues?
Thanks,
Mahi

In 10g, dataguard started to support different binaries on primary and standby database servers with the same OS family. For example Microsoft Windows 64-bit on primary and Microsoft Windows 32-bit or Microsoft Windows 64-bit for AMD on standby database server. However with 11g, dataguard also supports different OS on primary and standby servers
Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries [ID 414043.1]
Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]

Oracle RMAN recovery catalog database in a Primary and Standby mode

Similar Messages

Maybe you are looking for