Corrupting the block to continue recovery in physical standby

Hi,
Just like to inquire how I will be able to corrupt the block to be able to continue the recovery in the physical standby.
DB Version: 11.1.0.7
Database Type: Data Warehouse
The setup we have is primary database and standby database, we are not using dataguard, and our standby setup is another physical copy of production which act as standby and being sync using script that being run from time to time to apply the archive log came from production (its not configured to sync using ARCH or LGWR and its corresponding configurations).
Then, the standby database is not sync due to errors encountered while trying to apply the archive log, error is below:
Fri Feb 11 05:50:59 2011
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log /u01/archive/<sid>/1_50741_651679913.arch
Fri Feb 11 05:52:06 2011
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0, kdr9ir2rst0()+326]
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc (incident=631460):
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Incident details in: /u01/app/oracle/diag/rdbms/<sid>/<sid>/incident/incdir_631460/<sid>pr0028085_i631460.trc
Fri Feb 11 05:52:10 2011
Trace dumping is performing id=[cdmp_20110211055210]
Fri Feb 11 05:52:14 2011
Sweep Incident[631460]: completed
Fri Feb 11 05:52:17 2011
Slave exiting with ORA-10562 exception
Errors in file /u01/app/oracle/diag/rdbms/<sid>/<sid>/trace/<sid>pr0028085.trc:
ORA-10562: Error occurred while applying redo to data block (file# 36, block# 1576118)
ORA-10564: tablespace <tablespace name>
ORA-01110: data file 36: '/u02/oradata/<sid>/<datafile>.dbf'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 14877145
ORA-00607: Internal error occurred while making a change to a data block
ORA-00602: internal programming exception
ORA-07445: exception encountered: core dump [kdr9ir2rst0()+326] [SIGSEGV] [ADDR:0x7FFFD2F18FF8] [PC:0x60197E0] [Address not mapped to object] []
Based on the error log it seems we are hitting some bug from metalink (document id 460169.1 and 882851.1)
my question is, the datafile # is given, block# is known too and the data object is also identified. I just verified that object is not that important, is there a way to set the block# to corrupted to be able the recovery to continue? Then I will just drop the table from production so that will also happen in standby, and the block corrupted will be gone too. Is this feasible?
If its not, can you suggest what's next I can do so the the physical standby will be able to sync again to prod aside from rebuilding the standby?
Please take note that I also tried to dbv the file to confirm if there is marked as corrupted and the result for that datafile is also good:
dbv file=/u02/oradata/<sid>/<datafile>_19.dbf logfile=dbv_file_36.log blocksize=16384
oracle@<server>:[~] $ cat dbv_file_36.log
DBVERIFY: Release 11.1.0.7.0 - Production on Sun Feb 13 04:35:28 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
DBVERIFY - Verification starting : FILE = /u02/oradata/<sid>/<datafile>_19.dbf
DBVERIFY - Verification complete
Total Pages Examined : 3840000
Total Pages Processed (Data) : 700644
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 417545
Total Pages Failing (Index): 0
Total Pages Processed (Other): 88910
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 2632901
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 3811184883 (1.3811184883)
Any help is really appreciated. I hope to hear feedback from you.
Thanks

damorgan, i understand the opinion.
just new with the organization and just inherit a data warehouse database without rman backup. I am still setting up the rman backup thats why i can't use rman to resolve the issue, the only i have is physical standby and its not a standby that automatically sync using dataguard or standard standby setup, i am just checking solution that is applicable in the current situation

Similar Messages

Related to recovery in Physical standby database in RAC

In Physical Standby database all instance involved in recovery processes or any one instance will be their in in recovery mode
If is like this another instance will be for high availabily can any one in forum explain me it will be help full

With your Primary database being RAC, the Physical Standby does not have to be RAC, although, obviously it would be preferred to have scalability as required at a DR site.
Whether your Standby is RAC or non-RAC, the automatic Recovery that is done at the Standby is done by one instance only. It would be applying the ArchiveLogs from all the threads (i.e. instances) of the Primary.
Database Recovery is always done by a single instance.
Hemant K Chitale
http://hemantoracledba.blogspot.com

Cancelling recovery on Physical standby.

Hi ALL,
recovery is cancel and i am looking following error in alert log file
how can solve this problem
database version 11gr2
aix 6.1 64 bit
physical standby datbase
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:27 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:47 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)

ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:27 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)
Tue Jun 05 12:25:47 2012
Errors in file /u01/oracle/diag/rdbms/sfxdb/sfxdb1/trace/sfxdb1_pmon_14614728.t
c:
ORA-03170: deadlocked on readable physical standby (undo segment 65535)You cancelled recovery or it is terminated?
Try to start once again, I have seen some listed bugs with the same error but those are applicable for 11gR1, but you are in 11gR2.
Refer ORA-03170: Deadlocked on Readable Physical Standby [ID 846324.1], better you submit an SR to Support.
Thanks.

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

Problem in identifying control file when creating physical standby

hi there,
(database version: 10.2.0.4
plateform linux)
I'm using the command as below to create physical standby database from backup:
rman target / auxiliary sys/tiger@paceview
Recovery Manager: Release 10.2.0.4.0 - Production on Tue Sep 4 18:05:53 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PACEVIEW (DBID=2092349485)
connected to auxiliary database: PACEVIEW (not mounted)
run {
allocate auxiliary channel c1 device type DISK;
set until sequence 38;
duplicate target database for standby dorecover nofilenamecheck;
released channel: ORA_DISK_1
allocated channel: c1
channel c1: sid=35 devtype=DISK
allocated channel: c2
channel c2: sid=36 devtype=DISK
executing command: SET until clause
Starting Duplicate Db at 04-SEP-12
contents of Memory Script:
   set until scn 138180211934;
   restore clone standby controlfile;
   sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 04-SEP-12
channel c1: restoring control file
ORA-19625: error identifying file /backup/rman/paceview/DEL1_standby.ctl
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
ORA-19600: input file is control file (/backup/rman/paceview/DEL1_standby.ctl)
ORA-19601: output file is control file (/PGHProdDB/oradata/paceview/control1.ctl)
failover to previous backup
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/04/2012 18:01:44
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restorei have already tried crosscheck but still giving same error
thanks

Hello;
So this is what I would do :
Backup Primary ( change to your directory as need )
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
}Move the backup and duplicate like this :
rman target sys/password@PRIMARY auxiliary /
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}For complete details of this method see :
http://www.visi.com/~mseberg/duprman2.html
Best Regards
mseberg

Question-Recovering tablespace in physical Standby...Oracle 10g?

Hello:
I have an interesting issue. I thought I will ask the group.
I have a physical standby database in 10g. Once of the datafile is in inconsistent state due to a crashed DB during recovery from the last time around.
I do not have any archivelogs, either on standby or primary .. Unfortunately.
However, the primary database is alive and well.
How do I recover my datafile selectively? Is a complete restore/recreation of the standby is the only option?
Any ideas?
Thanks in advance.
Ganesh

read that link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#CIHIAADCKhurram

How to identify that my physical standby database in use real time apply?

Hi,
Can any one give me the SQL to identifiy that my physical standby database is in real time applying redo logs?
Its urgen please....
Thanks.

You could just look at the alert log. Look for "Recovery of Online Redo Log"
Or you could select from v$standby_apply_snapshot to see if the standby is up-to-date.
select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;

Failover to Physical Standby

Hi All,
I have a configured data guard in my local system . Please find the below configuration of the Data guard
Data Guard Type : - Physical Standby (Oracle version 11g)
Service Responsible for Log Transport : - ARCH
No Standby Redo log : - Neither in Primary Nor in Standby
I am trying to fail over by using command "alter database recover managed standby database finish"
Please find the below alert log info after this command .
Tue Dec 03 01:42:14 2013
alter database recover managed standby database finish
Attempt to do a Terminal Recovery (PRD)
Media Recovery Start: Managed Standby Recovery (PRD)
Fast Parallel Media Recovery enabled
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery timestamp is '12/03/2013 01:42:15'
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 145 redo required
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery: End-Of-Redo log allocation
Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
This standby redo logfile is being created as part of the failover
operation. This standby redo logfile should be deleted after the
switchover to primary operation completes.
Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
Terminal Recovery: log 3 reserved for thread 1 sequence 145
Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
Identified End-Of-Redo for thread 1 sequence 145
Incomplete recovery applied all redo ever generated.
Recovery completed through change 559773 time 11/23/2013 13:38:13
Media Recovery Complete (PRD)
Terminal Recovery: successful completion
Resetting standby activation ID 1895332757 (0x70f87b95)
Completed: alter database recover managed standby database finish
Tue Dec 03 01:42:50 2013
alter database commit to switchover to primary
ALTER DATABASE SWITCHOVER TO PRIMARY (PRD)
Maximum wait for role transition is 15 minutes.
Backup controlfile written to trace file /apps/oracle/diag/rdbms/stand/PRD/trace/PRD_ora_9466.trc
tkcrrxms: Killing 3 processes (all RFS)
Standby terminal recovery start SCN: 559772
RESETLOGS after complete recovery through change 559773
Online log /data/PRD_DR/REDOLOG11.LOG: Thread 1 Group 1 was previously cleared
Online log /data/PRD_DR/REDOLOG21.LOG: Thread 1 Group 2 was previously cleared
Standby became primary SCN: 559771
Tue Dec 03 01:42:53 2013
Here my question is , why oracle implicitly creates a standby redo log in Standby database for successful completion of 'alter database recover managed standby database finish'.
Thanks,

Terminal Recovery timestamp is '12/03/2013 01:42:15'
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 145 redo required
Media Recovery Waiting for thread 1 sequence 145
Terminal Recovery: End-Of-Redo log allocation
Terminal Recovery: standby redo logfile 3 created '/data/PRD_DR/arch/arch_1_0_831359165.arch'
This standby redo logfile is being created as part of the failover
operation. This standby redo logfile should be deleted after the
switchover to primary operation completes.
Media Recovery Log /data/PRD_DR/arch/arch_1_0_831359165.arch
Terminal Recovery: log 3 reserved for thread 1 sequence 145
Recovery of Online Redo Log: Thread 1 Group 3 Seq 145 Reading mem 0
Mem# 0: /data/PRD_DR/arch/arch_1_0_831359165.arch
Identified End-Of-Redo for thread 1 sequence 145
Looks like, its due to the following bug.
Bug 5889025 : FINISH FAILOVER GENERATES INCORRECT STANDBY REDO LOG.

Accidentally primary database convert to physical standby

Hi ,
Accidentally the primary database was converted to physical standby .Is there any way where it can be revert back to primary other than using the activate command.
Thanks and Regards,
Hussain

Well although I said "alter database open;" and the same is written into the alert.log, the sequence# again starts with 1 - only the bad word "resetlogs" is no longer mentioned :-)
SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         2          1          5 104857600          1 YES CLEARING_CURRENT
       383710 16-JUN-09
         1          1          4 104857600          1 YES CLEARING
       383708 16-JUN-09
SQL> alter database activate standby database;
alter database activate standby database
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
SQL> recover managed standby database cancel
Media recovery complete.
SQL> alter database activate standby database;
Database altered.
SQL> alter database open;
Database altered.
SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         1          1          1 104857600          1 NO CURRENT
       383714 16-JUN-09
         2          1          0 104857600          1 YES UNUSED
            0But it seems to me as if you have no other option anyway.

Physical Standby Online Redo log files,

Hi,
I'm trying to create a physical standby database (10.2.0.3). I'm a little confused about the requirement for online redo logs on the standby.
in my standby alert log I get the following when I issue:
SQL> alter database recover managed standby database disconnect from session
"ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/appl/oradata/prod/prod_1_redo_01_02.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3"
/appl/oradata/prod/prod_1_redo_01_02.log is the path to the location of the online redo logs on the production system. This file does not exist on the standby filesystem so the error is correct.
I assume that it gets this information from the standby control file I created on the production system and copied over to the standby.
Do I need to copy the online redo logs from the primary over to the standby site or do I need to create online redo logs on the standby?
Does the standby need to have redo log files?
I'm not talking about 'standby log files' of the type created using 'alter database add standby log file'. I've not got that far yet.
I just need to establish if a physical standby requires online redo log files?
Thanks in advance,
user234564

I wanted to update this thread since I've been dealing with the exact same errors. The basic question is: "does a physical standby need the online redo logs?"
Answer: Not really, until one wants to switchover or failover (and become a primary database). Furthermore, whenever the MRP process is started, Oracle prepares for a possible switchover/failover by "clearing" the online redo logs (MetaLink note# 352879.1). It is not a big deal, since Oracle will build the actual redo files when the "alter database open resetlogs" is accomplished during a "role transition."
In our situation, we have decided to use our standby for nightly exports. We stop MRP, open the database read-only, then restart MRP. We built these standby DBs with RMAN. The RMAN duplicate process will not build the online redo log files until the database is opened for read/write (with resetlogs). However, we haven't had a need for read/write (i.e. a switchover).
Thus, every morning we have been getting the same errors that "user234564" posted above. At first the errors seemed scary, then we realized they were just a nusiance. In order to clean things up, all I did was just "cp" our stanby redo logs (SRL) into our online redo directories ensuring the names matched what was in v$logfile. When I restarted MRP, the alert log clearly showed Oracle clearing these "newly found" online redo logs.

Will logical standby database be replaced by physical standby database?

Will logical standby database be deprecated or replaced by physical standby database because of Real Time Query?
As far as I know, because of the emergence of Real Time Query, physiacl standby database is easier to work than logical standby database. There are so many restrictions on using logical standby database.
Will logical standby database be deprecated in the future?
Message was edited by:
frank.qian

Good question - you are right that with the advent of Real Time Query, physical standby databases can provide the 'reporting database' functionality that you used to have to use a logical standby database for.
But remember that logical standby databases allow additional schema objects, like materialized views and indexes, that you can't have with a physical standby (for the reasons Hans mentions). For example, you could have a index-light primary database for OLTP style workload, and an index-heavy logical standby, with MVs and dimensions for reporting, DW, etc.
For this reason I don't expect logical standby will become deprecated.

Cannot Clear Critical Alert for Physical Standby Databases

10.2.0.4.0 Grid Control monitoring 10.2.0.4.0 databases and standby databases with 10.2.0.4.0 agents.
The standby databases are running on Xen guests. The O/S is Red Hat 4 Advanced Server.
I had a failure of Xen guest on Saturday that caused me to have to rebuild the standby servers. EM Grid Control successfully verifies the configurations and the status is normal for both physical standby databases. (A rebuilt logical standby database shows no alerts.)
Grid Control database targets page shows a single critical alert for each physical standby database. The alert is for "number of missing media files is 4". The metric graph shows the count as 0 since before the rebuilds. I cannot clear the alerts from the Critical Alerts page. Grid Control reports "The selected alert(s) cannot be manually cleared. They will clear automatically once the metric is no longer in a critical or warning state.".
Any suggestions?
Thanks,
Ray Westphal

Thanks for the reply Anthony.
The result of the query on both standby databases is '0'. The metric graph also shows the value at '0' since before rebuilds.
And the OMS db and agents have been reset several times since I posted this.
Ray Westphal.

Problem with data guard Creating a Physical Standby Database turorial

There is a tutorial of Creating a data guard Physical Standby Database:
http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
I tried to install it on two servers. One for primary database second for physical standby.
I have error on C. Creating the standby database over the network, action #6:
"On the standby system, set the ORACLE_SID environment variable to your <physical standby SID> (i.e. orclsby1) and start the instance in NOMOUNT mode with the text initialization parameter file."
When I try to connect to idle instance there is an error pops up:
C:\>sqlplus / as sysdba
SQL*Plus: Release 11.1.0.7.0 - Production on Thu May 21 16:28:10 2009
Copyright (c) 1982, 2008, Oracle. All rights reserved.
ERROR:
ORA-12560: TNS:protocol adapter error
I'v checked listener and it is runned. There is no service for database because there is no database yet.
The question is did some one installed data guard configuration using this tutorial? Is there any errors in it? What should I do to finish this installation?

On Windhose for every instance a service must have been created using the oradim command.
Oracle tutorials are usually Unix-centric, as Windhose is an odd man out, so they don't discuss that bit.
'Kindly do the needful' and create the service prior to starting the instance in nomount mode
Hint: oradim is documented and has a help=y clause.
IIRC there is an option in database control (in the maintenance part) which automates everything.
Sybrand Bakker
Senior Oracle DBA
Experts: those who do read documentation

Clarification on creating a Physical Standby Database

I'm practicing with data guard with Oracle 10.2.0.1.0 on two Windows 2003 servers.
I'm in the process of creating a physical standby database by following the steps outlined in the guide http://www.filibeto.org/sun/lib/nonsun/oracle/10.2.0.1.0/B19306_01/server.102/b14239/create_ps.htm
I've created the primary database and did a cold backup of all the datafiles and copied them to the standby server using OS commands. I've created a pfile from the spile in primary database and changed the needed parameters for the standby database.
What I don't understand is this statement I think is creating a control file for the standby database: SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tamp/standby.ctl'
Exactly what I don't understand is what to do with this control file. I'm thinking that if I try to use it as the controlfile for the standby database, the standby database will refuse to open since the database name in the control file wont match the one the server expects.
I don't want to proceed until this becomes clear. So my question is what to do with the output of the above statement that seems to create a control file for the standby database.
Any help would be appreciated.
Dula

>
You're thinking wrong.
Please clarify the difference between db_name and
db_unique_name.
Db_unique_name needs to be identical for both primary
AND standby database.
If db_unique_name differs, you'll get errors.
Sybrand,
Perhaps, you meant DB_NAME has to be identical for both databases.
DB_NAME name has to be the same for both primary and physical standby database.
DB_UNIQUE_NAME should be unique for each database in the standby configuration.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i68626
If you configure Logical Standby Database, DB_NAME may be different.
For the original poster: Chapter 3 - Creating a Physical Standby Database of Oracle® Data Guard Concepts and Administration has all the steps you have to do in order to configure a physical standby database.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
Cheers,

Appying patches when Physical standby in place.

Kindly suggest steps for patch application /application upgradation. We dont have any replication tool.What is the standard process to sync standby after patch upgradation . Is there any alternative of rsync/rdist utility.
Is it possible that after applying patch in Primary, On Standby we have to apply as it is, with no Database inclusion as the standby database will be in mount state and will not available for making database changes.
How to find which files to be copied manually to sync the standby with Primary. Will this method reliable?
Apologies to ask many questions but i found no single document covering this detailed process.

Both the links are for applying patches/upgrades for Oracle Database. Apologies i didn't clarify the requirement. It's for EBS R12. So i need to sync the apps tier with primary when physical standby in place.
Kindly validate below procedure with rsync utility
After running the Middle Tier and Database Pre-clone.
To synchronize Synchronize the Appropriate File Systems to Standby,
rsync –av <$APPL_TOP> <standby_host>:<$APPL_TOP>
--rsync-path=/usr/local/bin/rsync
/usr/local/bin/rsync –av <$COMMON_TOP> <standby_host>:<$COMMON_TOP>
/usr/local/bin/rsync –av <$ web ORACLE HOMEs (10.1.2)> <standby_host>:<$ web ORACLE HOMEs (10.1.2)>
/usr/local/bin/rsync –av <$TOOL(10.1.3)> <standby_host>:<$COMMON_TOP>
Synchronize the database tier file system including <RDBMS ORACLE_HOME>/appsutil directory.
/usr/local/bin/rsync –av <RDBMS ORACLE_HOME>/appsutil <standby_host>:<RDBMS ORACLE_HOME>/appsutil
Reconfigure the Standby Middle Tier File Systems
When the file system synchronization is complete, reconfigure the standby file systems. Log onto each of the standby middle tier systems as the APPLMGR user and execute the following commands:
cd <COMMON_TOP>/clone/bin
perl adcfgclone.pl atTechStack <INST_TOP>/appl/admin/<Standby CONTEXT_NAME>.xml
To complete the configuration of environment run AutoConfig using the following commands:
cd <APPL_TOP>/ad/12.0.0/bin
adconfig.sh contextfile=<INST_TOP>/appl/admin/<standby context>.xml run=INSTE8
AutoConfig will report errors regarding to database connection, these errors can be ignored as the database is unavailable.
Step 4.4.11 - Reconfigure the Standby Database File Systems
If you had to synchronize the apps utilities on the database server in the prior step, you should also reconfigure the database server. As the ORACLE user on each database node of standby database tier, first stop the listener if it is running, then execute the following commands:
cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
perl adcfgclone.pl dbTechStack <RDBMS ORACLE_HOME>/appsutil/<Standby CONTEXT_NAME>.xml

Corrupting the block to continue recovery in physical standby

Similar Messages

Maybe you are looking for