Patch applied primary/standby - when to upgrade standby

I am following metalink document *278641.1*
STEP-6: I have applied patch on both databases.
STEP-7: Started OracleSercivce, Listener.. on standby database.
I have confusion in step 8,9 and 10.. the confusion is when should I upgrade the databases? and which datatabse should be upgraded first? I want to upgrade using DATABASE UPGRADE ASSSISTANT (DBUA).... please help
OPTION-1 should I follow below steps...
STEP-8: startup nomount.
STEP-9: recover managed standby database nodealy disconnect.
and then I upgrade the standby database using DBUA
STEP.10 start primary lisnter, primary instance.
and then I upgrade the primary database using DBUA
OPTION-2 OR should I follow below steps...
STEP-8: startup nomount.
STEP-9: recover managed standby database nodealy disconnect.
STEP.10 start primary lisnter, primary instance.
and then I upgrade both Primary and Standby using DBUA
which one should be upgraded first.?
Can any body explain me... what steps I should follow, and when should I upgrade the database using database upgrade assistant.....its not mentioned clearly in the document... I am stuck in...
waiting for your replies...

it doesn't.... again, my question is same... when should I upgrade the database using DBUA... and which database should be upgraded first?
you want to say... I should follow steps as below..
8. (standby database) startup nomount
9. (standby database) recover managed standby database nodelay disconnect;
10. (primary database) start primary listner, oracle instance
10.1 (primary database) start oracle instance startup command at primary database...right?
10.2 (primary database) upgade using DBUA
10.3 (standby database) upgrade using DBUA
I didnt understand with startup upgrade command.... should I use DBAU to upgrade the database instead ? again my question is which database should be upgraded first with DBAU.

Similar Messages

Oracle 10 upgrade - Primary & standby database

Hi Expert,
I need some information on your project experience. We're currently planning a oracle 10 upgrade. Have a few question:
1. We're planning to upgrade the primary database first and a week later the standby database. Will the archive log which is sent from primary to standby database will still work? Will the recovery still work?
2. Is this the right patch to go 10.2.0.4? I'm currently on 4.7 ext 2
3. Will there be a performance issue known of oracle 10 running on 32-bit machine, since it has the limitation of the memory (3G). Do I need to set AWE option on windows?
Thanks in advance.

Hello Sean,
please let me go more in detail with some of your comments.
> I actually posted my experience with doing a rolling upgrade of a PHYSICAL standby database.
This statement is wrong. You can't do a rolling upgrade with a physical standby database. You have to convert the database to a logical standby database .. and then you can perform a rolling upgrade. But if you have done the conversion, it is not a physical anymore.
This is also described and mentioned in this white paper:
http://www.oracle.com/technology/deploy/availability/pdf/maa_wp_10gr2_rollingupgradebestpractices.pdf
Data Guard SQL Apply (logical standby database) is required in order to perform a database rolling upgrade. You can also do a rolling upgrade when starting with a physical standby by temporarily converting the physical standby to a logical standby. If starting with 11g, see the Rolling Database Upgrades for Physical Standby Databases using Transient Logical Standby 11g paper for details on doing a rolling upgrade when starting with a physical standby. If starting with 10g, see MetaLink note 300479.1.
> It WILL work, and is fairly straight forward.
In this point you are almost correct, because of a standard SAP system is not using the unsupported data types, etc. (afaik)
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/data_support.htm
To be honest if a sap basis admin asks such a question, i would not recommend to perform an unsupported way, because i am in doubt about his dataguard know how.
Regards
Stefan

Physical stndby doesn'1 apply redo or primary standby didn't transport redo

I setup physical standby (OEL5.0, DB 11.2), every things seem right. But when i create table on primary DB, it does not appear on standby database. The Physical standby doesn'1 apply redo or primary standby didn't transport redo to standby Datadase
Please consider mine configuration
----Standby :
SQL> select database_role, protection_mode, log_mode from v$database;
DATABASE_ROLE PROTECTION_MODE LOG_MODE
PHYSICAL STANDBY MAXIMUM PERFORMANCE ARCHIVELOG
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 38
Next log sequence to archive 40
Current log sequence 40
------Primary :
SQL> select database_role, protection_mode, open_mode from v$database;
DATABASE_ROLE PROTECTION_MODE OPEN_MODE
PRIMARY MAXIMUM PERFORMANCE READ WRITE
SQL> create table test_stby (
2 cot_1 number,
3 cot_2 number);
Table created.
SQL> insert into test_stby values (10,11);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
---- Standby :
SQL> SELECT MAX(SEQUENCE#), THREAD# FROM V$ARCHIVED_LOG GROUP BY THREAD#;
no rows selected
SQL> SELECT PROCESS, STATUS,SEQUENCE#,BLOCK#,BLOCKS,DELAY_MINS FROM V$MANAGED_STANDBY;
PROCESS STATUS SEQUENCE# BLOCK# BLOCKS DELAY_MINS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MRP0 WAIT_FOR_LOG 40 0 0 0
- Standby cancel redo apply, open read only and query for table test_stby, it does not have this table
Please help
Ch

I did solved this problem :)

Which patch to apply when live upgrading to a new OS

Hello Guys,
when you use live upgrade to upgrade to a new OS level , which patches do you apply before performing the upgrade? I used prerequired patches from 10REC when performing a live upgrade patching . Do you use these same prerequired patches when upgrading to a NEW OS LEVEL?
Your response will be truely appreciated.
Thanks

Hi.
I hope it's help:
http://docs.oracle.com/cd/E26505_01/html/E28038/preconfig-17.html#luplanning-7
Ensure that you have the most recently updated patch list by consulting http://support.oracle.com (My Oracle Support). Search for the knowledge document 1004881.1 - Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support.
The patches listed in knowledge document 1004881.1 - Live Upgrade Software Patch Requirements (formerly 206844) on My Oracle Support are subject to change at any time. These patches potentially fix defects in Live Upgrade, as well as fix defects in components that Live Upgrade depends on. If you experience any difficulties with Live Upgrade, please check and make sure that you have the latest Live Upgrade patches installed.
If you are running the Solaris 8 or Solaris 9 OS, you might not be able to run the Live Upgrade installer. These releases do not contain the set of patches needed to run the Java 2 runtime environment. You must have the recommended patch cluster for the Java 2 runtime environment recommended to run the Live Upgrade installer and install the packages. To install the Live Upgrade packages, use the pkgadd command. Or install, for the Java 2 runtime environment, the recommended patch cluster. The patch cluster is available on http://support.oracle.com (My Oracle Support).
For instructions about installing the Live Upgrade software, see Installing Live Upgrade.
Required patches available via MOS ( My Oracle Support: http://support.oracle.com).
But for access to this site you must have active service contract.
Regards.

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

Logs not applying on Standby Database

I am afraid I am back.
I now have a primary database and a standby database and logs are being shipped but not applied. Done some research and I have got to the point where in my alert log I find the following when I try to start MRP:
Fri Jun 29 15:03:40 2012
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (SAPDS)
Fri Jun 29 15:03:40 2012
MRP0 started with pid=29, OS id=23272
MRP0: Background Managed Standby Recovery process started (SAPDS)
started logmerger process
Fri Jun 29 15:03:45 2012
Managed Standby Recovery not using Real Time Apply
Read of datafile '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' (fno 2) header failed with ORA-01206
Rereading datafile 2 header failed with ORA-01206
MRP0: Background Media Recovery terminated with error 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
Recovery Slave PR00 previously exited with exception 1110
Errors in file /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc:
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01122: database file 2 failed verification check
ORA-01110: data file 2: '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
ORA-01206: file is not part of this database - wrong database id
MRP0: Background Media Recovery process shutdown (SAPDS)
Completed: alter database recover managed standby database disconnect from session
My question therefore is how can I get out of this and get my logs to apply on standby?

Hello again;
Do you think if I tried to repeat the duplicate?
Yes I think you should do this.
Give me a few minutes and I will review my Word document and provide a step by step overview here as insurance.
I always cleanup the standby before trying another dup
OVERVIEW
Step 1 - Password file fro standby - Copy from primary and rename
Step 2 - Directory Structure on the remote server - Make sure noting is missing
Step 3 - Oracle Net Setup - entry for the CLONE in your TNSNAMES.ORA on both servers
Step 4 - SID_LIST_LISTENER addition ( assumes listener named LISTENER )
Step 5 - Timeouts set in listener.ora and sqlnet.ora Both Servers
Step 6 - Initialization Parameter File for the Auxiliary Instance
Step 7 - Set SID for Auxiliary Instance
Step 8 - Create an SPFILE for the new database by using a pfile with the INIT settings
Step 9 - Shutdown and startup nomount on new Spfile ( Auxiliary Instance )
Step 10 - Start RMAN and run the DUPLICATE Command
SID_LIST_LISTENER Example from mine
SID_LIST_LISTENER =
   (SID_LIST =
       (SID_DESC =
       (SID_NAME = PLSExtProc)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
       (PROGRAM = extproc)
       (SID_DESC =
       (global_dbname = CLONE.hostname)
       (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
       (sid_name = CLONE)
Prevent Timeouts
Add these to both servers
To listener.ora
INBOUND_CONNECT_TIMEOUT_ = 120
To sqlnet.ora
SQLNET.INBOUND_CONNECT_TIMEOUT = 120
Then stop and start the listener.
RMAN
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
Connect should return something like this
connected to target database: RECOVER9 (DBID=3806912436)
connected to auxiliary database: CLONE (not mounted)RMAN>duplicate target database for standby from active database NOFILENAMECHECK;
INIT Extras
To avoid ORA-09925 make sure the PFILE has audit_file_dest and core_dump_dest set
Best Regards
mseberg
Edited by: mseberg on Jun 29, 2012 11:12 AM

Dataguard the achivelog not transfort between primary & standby db

Dear all Dataguard gurus
i tried to install oracle 10g dataguard on 2 machines with Centos 4.6 for development
after finish the installation, i 've got some "STRANGE" ..when i do a query at dataguard1
dataguard1 is primary database
dataguard2 is standby database
sys@dataguard1> select sequence#, first_time, next_time from v$archived_log;
SEQUENCE# FIRST_TIM NEXT_TIME
16 24-JUL-09 24-JUL-09
17 24-JUL-09 24-JUL-09
18 24-JUL-09 24-JUL-09
19 24-JUL-09 24-JUL-09
20 24-JUL-09 24-JUL-09
21 24-JUL-09 24-JUL-09
22 24-JUL-09 11-AUG-09
23 11-AUG-09 12-AUG-09
24 12-AUG-09 12-AUG-09
25 12-AUG-09 12-AUG-09
26 12-AUG-09 12-AUG-09
sys@dataguard1>select sequence#,applied
2 from v$archived_log
3 order by sequence#;
SEQUENCE# APP
16 NO
17 NO
18 NO
19 NO
20 NO
21 NO
22 NO
23 NO
24 NO
but if i do the same quey on standby database
sys@dataguard2> select sequence#, first_time, next_time from v$archived_log;
nothing archive...and not applied
what could be the problem????
thanks for u'r attention & help
Edited by: kang dadang on Aug 12, 2009 7:22 PM

thanks for response jerald
everything is same, all pass for sys on primary & standby are the same, password file on both machine are same
here my parameter file[not all parameter included]
[primary db]..on dataguard1 machines [dbname : dgtest]
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest'
*.log_archive_dest_2='service=dgtest2 lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest2'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.service_names='dgtest'
*.standby_file_management='auto'
[standby] on dataguard1 machines..[dbname : dgtest2]
*.db_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest'
*.db_name='dgtest'
*.DB_UNIQUE_NAME='dgtest2'
*.fal_client='dgtest2'
*.fal_server='dgtest'
*.log_archive_config='DG_CONFIG=(dgtest,dgtest2)'
*.log_archive_dest_1='LOCATION=/u02/oradata/archive/dgtest/
valid_for=(all_logfiles,all_roles)
db_unique_name=dgtest2'
*.log_archive_dest_2='service=dgtest lgwr async
valid_for=(online_logfiles,primary_roles)
db_unique_name=dgtest'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.log_archive_format='%s_%t_%r.arc'
*.log_file_name_convert='/u01/app/oracle/oradata/dgtest','/u01/app/oracle/oradata/dgtest',
'/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/','/u01/app/oracle/flash_recovery_area/DGTEST/onlinelog/'
*.remote_login_passwordfile='EXCLUSIVE'
*.service_names='dgtest'
*.standby_file_management='auto'
thanks for all...jerald
Edited by: kang dadang on Aug 12, 2009 11:52 PM

RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!

i get RMAN-08120: WARNING: archived log not deleted, not yet applied by standby on primary You already have answer by post of Mseberg.
but when i run below query i get the same result from primary and standby
SQL> select max(sequence#) from v$archived_log;
MAX(SEQUENCE#)
44051
SQL>
standby is one log switch behind only!this is wrong query used on primary & standby. even if any one of archive gap available lets suppose sequence *44020* , this archive not transported to standby due to some network problem and so on. later if archives from *44021* all the archives transported on standby upto *44051* , then it shows the maximum sequence transferred to standby, It wont shows applied sequence.
Check the below queries.
Primary:-
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
Standby:-
SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group by thread#;
HTH.

Primary & standby db on same OS plaform but having different OS version

Hi,
I have primary & standby database 10.2.0.4 on AIX 5.3 Operating System platform .
I would like to Upgrade my Operating System(AIX) of standby databse server from 5.3 to 6.0.
Will diffenet Operating System version for primary & standby databases support ?
Thnaks.

so, if my primary db on aix 5.3 & standby db on aix 6.1 plaform, then it will not work
or oracle db will not support for this differnent os versions.
is it right?Yes, along with that I'm asking why you want to choose different versions/releases of OS?
I seen there some issues even if some RPM's are missing. So if the complete version changes then think of it.
Moreover check the certification in support.oracle.com
Recently i checked for Linux 6, it's not yet certified. I'm not sure of unix here. So please do refer http://support.oracle.com
Thanks.

Patching with physical standby document

There is this old document targeting 9i. Is there anything for 11g of a similar nature:
Applying Patch Sets / Interim Patches with Physical Standby Database in Place in Oracle 9i [ID 187242.1]

You require others to search for free on your behalf?
Shame on you!
Sybrand Bakker
Senior Oracle DBA

Switchover_status "FAILED DESTINATION" on both primary-standby databases

Hi,
I setup primary-standby databases and try to test the switchover functionality between them using the following commands:
alter database commit to switchover to primary with session shutdown;
alter database commit to switchover to physical standby with session shutdown;
Currently, both DBs are showing
open_mode= READ WRITE for "select open_mode_from v$database;" and
switchover_status = FAILED DESTINATION for "select switchover_status from v$database"
When both databases get into these states, how can I return them back to primary and standby roles? Could you please provide me a sequence of steps that I can execute to return them back to normal primary-standby states?
Thanks in advance for your suggestion.

The OS is Red hat 4.1.2-500.
Oracle version is 11g.
Here is the sequence of steps that lead to this issue:
1. switchover_status on primary = to standby, switchover_status on secondary = not allowed
So on primary, I execute
alter database commit to switchover to physical standby with session shutdown;
and could be shutdown/startup mount ( I don't remember exactly)
2. switchover_status on secondary = to primary
So on secondary, I execute
alter database commit to switchover to primary with session shutdown;
alter database open;
3. Now on secondary, the switchover_status = FAILED DESTINATION
On primary, I execute
alter database commit to switchover to primary with session shutdown;
and could be "alter database open" ( I don't remember exactly)
The switchover_status in step 1) and 2) above should indicates that the data guard is working. At the end of the above steps, I cause both databases to get into switchover_status = "FAILED DESTINATION".
I hope to get one of the DBs back into standby role.
If I execute "alter database commit to switchover to physical standby with session shutdown", I will get
"ORA-16416: No viable Physical Standby switchover targets available"
In this situation, is there any recommendation for rescue?

Prevent LBFO Primary/Standby fallback

Hi All,
I have a client requirement to implement network redundancy on a Windows Server 2012 R2 platform. So enter two switches, firewalls, routers etc.
As part of this I have set up an LBFO team on NIC 1 & 2.
The client has since informed me that they have (in the past) had flakey inter-site links which resulted in the NIC team flapping between the Primary and Standby NIC as the primary network interface went up and down. Consequently, one of the tests that
I need to implement and pass is that if the active primary interface fails, the standby picks up the active role until such a time as the secondary interface fails rather than swapping back to the primary interface when the connection is restored
TIA
Jason

The best way to avoid this problem with Active/Standby is to not use it. Generally Active/Active mode is better than Active/Standby.
As you've noticed, Active/Standby mode forces an additional failover event:
An active NIC goes down, so there is a failover to the standby NIC.
The previously-active NIC is restored, so there is a failover from the standby NIC back to the newly-restored NIC.
This additional failover is by design. The design of Active/Standby is to designate a standby NIC, and the team tries to keep that NIC on standby as much as possible.
Because of this additional failover, Active/Active mode actually gives you better fault-tolerance than Active/Standby. And of course, Active/Active also makes better use of your available bandwidth, since you get to use the bandwidth of the redundant
NIC when there is no fault. Finally, note that Active/Standby does not have any advantage in failover latency or "effectiveness"; the failover performed by Active/Active is just the same as that performed in Active/Standby.
Therefore, I actually reccomend that Active/Active is your configuration of first resort. Active/Active is better or equal to Active/Standby in most respects. (Exception: If you have a configuration where one NIC
really is worse than the others, e.g., it has a lower link speed, then Active/Standby may be appropriate.)

How tyo know that primary & standby are syncronyzed(SCN)

Dears,,
If i have data guard solution (Primary and physical standby) databases
How to make sure that both primary & standby are syncronyzed(SCN)
Please,help,,

Hi,
Compared across the sequences applied on standby with primary archive logs generation generation
select max(sequence#) from v$archived_log where applied='YES';
- Pavan Kumar N

Redo Log Apply after Standby Restarts

hi all,
To start my learning on Data Guard, I've successfully followed the manual steps to create a physical standby database. What I noticed is when I restart the standby database, the received redo log aren't automatically applied until I issued the following command:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;Is that normal? If yes, is there a way to make redo application remains automatic after standby database restarts?
Thanks in advance.

When you configure the DataGuard in an SQL environment you need to manually start the redo apply process after the Standby Database is mounted. You can script the database startup and include that when "select database_role from v$database" is Physical Standby then "ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;"
OR
Yo can configure the DataGuard under the broker control which will start the redo apply process automatically when the Standby Server starts.
Sudhir.

How to Refresh UAT Primary/standby from Production primary/standby

Hi ,
We have the following setup :
Primary/standby - Production
Primary/Standby - UAT
I need to know the process on how to refresh the UAT primary/standby .
I'm thinking on the following lines :
1] If we have the export dump of production , can we go ahead and drop the schemas to be refreshed on both UAT Primary and UAT Standby UAT then perform the schema import on Primary UAT .
2] In case if I have to do a full refresh of UAT , do I need to rebuild the UAT environment from the proudction backups Ie,
(i) Drop both the UAT primary and UAT standby database .
(ii) using the produciton backup built the UAT Primary . Take the UAT primary backup and build the UAT standby .
Appricaite if any one can provide some best practices to refresh UAT from Production.

That setup seems to be rare. We assume that the Standby Database is used for testing and have a feature for that called Snapshot Standby.
But in your scenario, you need to develop your own techniques for "refreshment of the UAT Primary".
An easy way (if your Primary is not too large): Throw away your UAT env each time the "Production Primary" changes and RMAN clone it to "UAT Primary" then.
Then RMAN duplicate "UAT Standby" again. Could be relatively easily scripted.
But again: Why not just create an ordinary Standby on your UAT hardware and use it for testing with Snapshot Standby feature? Much easier to maintain.
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Patch applied primary/standby - when to upgrade standby

Similar Messages

Maybe you are looking for