Data Guard :: Oracle Application 12.1.1 / Database 10.2.0.4 - Disaster Recovery Site
Aug 18, 2012
We have an Oracle application 12.1.1 running with oracle database 10.2.0.4 and we're using HP-UX itanium 11i v3 servers for both application and database, our requirement is to establish a Disaster Recovery site out of our building to ensure data protection.
What is the best option we can use to reduce the cost and to implement the DR site? can we use data guard ? and will be the configurations and requirements for it?
Do we have any plan to create DR ( disaster site) for ORACLE 10G standard version. Since, Data Guard is not available with Standard version, can we have any another plan for the same.
1.What are the basic things we need to analyze before we recommend the business to go for oracle Dataguard for DR setup?
2. Do you know any technology that will replicate the schema from one datacenter[one primary database ] to another datacenter [secondary or replication database]?
3. What are the various option to configure the disaster recovery plan at schema level?
I have a SAN systems with primary and secondary interfaces. i need to know what is best practice of oracle to use disaster recovery features, with automatic or manual failover concept.
example.
Primary Server Duty Station 1 New York
Secondary Server Duty Station 2 Los Angelous
requirement : If primary server in DS 1 gets fire and completed get down then secondary server DS 2 should become primary server and reply to client request with AUTO or Manual failover concept.
1) How to find archive log gap from Primary Database site? 2) Do I need the DB_UNIQUE_NAME when setting the LOG_ARCHIVE_DEST_2 ? What is the purpose of DB_UNIQUE_NAME in LOG_ARCHIVE_DEST parameter? 3) If archivelog gap happens standby db goes out of sync with the primary database. What does out of sync actually mean? 4) Primary DB knows where to transport redo data based on the location mentioned in LOG_ARCHIVE_DEST_n of Primary DB. Am I correct in my understanding?
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 found an issue regarding log archiving on dest1. yesterday one sequence number 76871 not archive to dest1.alert logfile content as follow. i configure standby and ship archive manually with window copy command. i need this archive to complete recovery on standby database.
Mon Oct 21 09:29:28 2013 ARC2: Completed archiving log# 3 seq# 76869 Mon Oct 21 09:39:28 2013 Thread 1 advanced to log sequence 76871 Current log# 2 seq# 76871 mem# 0: D:ORACLEORADATAORC1REDO02.LOG [code]....
I have an application that writes blobs via pro*c. It is running at several sites without errors for a few years now. One of the newer sites has started reporting "ora-01578 ORACLE data block corrupted".
I've tried using rman backup validate - it does not report any errors.
I've tried using rman restore and recover to correct the problem.
I've tried deleting the file with the corrupt block and using rman restore and recover to recreate it.
In any of the above cases, I do not see any errors being encountered, and when I restart the application, it works for a while and then starts reporting "ora-01578 ORACLE data block corrupted".
I've had the client do a physical check of the disk and it indicated the media was okay.
We've failed over to the standby system, so I have a wee bit of breathing room - but I'm going to be away for 4 days and will have to get back on this when I get back. I'm a little puzzled that I can fix it for a short while and then it breaks again.
I got a primary database with a logical standby database running Oracle 11g. I got two client applications, one is the production site pointing to the primary one, another one is just a backup site pointing to the logical one.Things will only be written into the primary database every mid night and client applications can only query the database but not add, update nor delete.And now, I want to apply the latest patch on both of my databases. I am also the DNS administrator, I can make the name server pointing to the backup site instead of the production one.I want to firstly apply the patch on the logical one, and then the physical one.
I found some reference which explains how to apply patches by adopting "Rolling Upgrade Method". however, I want to avoid doing any "switch over" mentioned in the reference because I can make use of name server. Can I just apply patches as the following way?
1)Stop SQL apply 2)Apply patches on logical standby database 3)let the name server point to the backup site 4)Apply patches on the primary database 5)Start SQL apply 6)Let the name server point back to the production site
I am planning to use Data Guard facility in Oracle 10g database.
1) I would like to have a standby database, which can be used if the primary goes down and also for reporting and other queries (read-Only). 2) What is the difference between Physical and Logical standby database. I have to explain non-technical users (management) regarding this. 3) What is Sync and Async redo log apply? 4) When i manipulate data (Insert,Delete,Update) in logical standby database, will these changes reflect in Primary database synchronously? 5) Which type of REDO APPLY is better: Managed Recovery Process(MRP) or Real Time Apply(RTA)? 6) can the redo data be deleted if its obsolete or is it deleted automatically by oracle? 7) If i want to take backup, should i take it from primary or standby database? If standby, then the database should be in which mode (Read-only or Recovery Mode)
my customer wants to create a standby database for his production database (Oracle Standard Edition 11g R2 @ Windows 2008 R2 64 Bit). Now any proof-of-concept which explains shortly the concept and how to achieve it.
I'm trying to create a physical standby database on my Oracle9i DB runing on WinXP.
Note: I have both Primary and Standby on the same system.
Actually everything went well .... I did created the standby DB but the problem is I can not start my primary DB if my standby DB is mounted. I get this error:
ORA-01102: cannot mount database in EXCLUSIVE mode
And when I read about the error message I learnt that I should start my DB in compatible mode ...
in a RAC multi-node environment with single instance dataguard..Recovery is not running automatically I have to re-run the recovery command to make them sync and this command works for already archived log files no upcoming archive log file applied I have to re-run the recovery command again for newly archived log files.
My standby database was working fine which was running in maximum performance mode .Suddenly i found that logs are not being applied though archived logs are received from primary database.i issued the command in mount mode: alter database recover managed standby database disconnect from session;
altered database this command runs successfully. but MRP process in not initiated which i confirmed with the query (select process,status from v$managed_standby;)
I'd like to stop Recovery in specific time. For instance ; My db works Day-1 and Every day Recovery starts 20:00 and finish 05:00. If it is possible that when DB time reach to sync 03:00, I'd like to stop recovery.
I have created dataguard between two instances hosted in two different servers. I have done switchover from primary to standby & then again standby to primary with DGMGRL utility.
1- When I done switchover to primary & trying to open standby database in readonly mode it was giving below error-
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
Why this error was coming ?
2- As I was not able to open standby database in read only mode, I have executed below command-
alter database recover managed standby database disconnect from session;
which return an error as-
ORA-01153: an incompatible media recovery is active
After this I have executed-
alter database recover managed standby database cancel;
which executed successfully.
& then after standby database open in read only mode.
Why above error was coming ?
3- After this I had tried to check the checkpoint_change# & controlfile_change# from primary database and result shows both number were different.
I noticed that my standby server was behind the prduction one.In the error log I noticed: ORA-00600: internal error code, arguments: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], []
then MRP0: Background Media Recovery terminated with error 448 Recovered data files to a consistent state at change 286116915
This error happens in sequence: Recovery of Online Redo Log: Thread 1 Group 4 Seq 8830 Reading mem 0I found this archive log in standby and it is same size as in the production one.
I have set the physical standby database to open read mode for a short while.
according to [URL] in order to set db in for from open read-only to applying redo data
Quote:
To change the standby database from being open for read-only access to performing Redo Apply:
Terminate all active user sessions on the standby database. Restart Redo Apply. To start Redo Apply, issue the following statement:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE 2> DISCONNECT FROM SESSION;
To enable real-time apply, include the USING CURRENT LOGFILE clause:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE 2> USING CURRENT LOGFILE;
this is what happen
SYS@ngdr> alter database recover managed standby database disconnect session; alter database recover managed standby database disconnect session * ERROR at line 1: ORA-00274: illegal recovery option SESSION SYS@ngdr> alter database recover managed standby database using current logfile;
okay since I encountered the illegal recovery options session, I decided to use alter database recover managed standby database using current logfile; now the session seems to be hanging forever.
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 ?
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.
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 have configured physical standby in my local system, to check logshipping i created a table at primary db, wen i tried to check in standby, it says table does not exist..below are primary & standby alert entries..
Primary alert log
Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.0.98)(PORT=1522))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=STAND)(SERVER=dedicat ed)(CID=(PROGRAM=d:oracle11gappadministratorproduct11.1.0db_1inORACLE.EXE)(HOST=A960M)(USER=SYSTEM))(SERVER=dedicated))) VERSION INFORMATION: TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
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]....
IN M.V. SITE , and i am getting following error while creating REPGROUP CODE SQL> BEGIN 2 DBMS_REPCAT.CREATE_MVIEW_REPGROUP ( 3 gname => 'emp_repg', 4 master => 'orc1',
1) scn differs wrt primary in standby (i checked, 1day difference), how to make scn same?
2)i created a table in primary, its not refelecting in standby, (below i ve pasted alertlog entries)
ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) The system cannot find the file specified. Errors in file d:oracle11gappadministratordiag dbmsstandstand racestand_dbw0_6916.trc: ORA-01157: cannot identify/lock data file 2 - see DBWR trace file ORA-01110: data file 2: 'D:ORACLE11GAPPADMINISTRATORORADATASTANDSYSAUX01.DBF'
[code]....
3)wen i try to open standby database in read only mode gives below error..
ERROR at line 1: ORA-16004: backup database requires recovery ORA-01157: cannot identify/lock data file 1 - see DBWR trace file ORA-01110: data file 1: 'D:ORACLE11GAPPADMINISTRATORORADATASTANDSYSTEM01.DBF'
