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

Similar Messages

How to apply Oracle patch when physical standby database in place

Dear All,
I want to apply Oracle patchset 8 on 10.2.0.5 when physical standby database in place. What are the steps for Primary site and for standby site.
Thanks in advance
Kamran Laeeq

Hi Kamran,
You will not upgrade or patch the standby database by importing offline redologs. On the contrary, there is a procedure to do this. Please note that you will not transitiate the role from standby to primary or startup the database. You will just startup the database by executing "startup mount" and "startup upgrade", during the upgrade. It means that you will not change database role standby to primary and you will be able to continue to the log shipment after the respective upgrade.
But, it is very important that you should stop the log shipment and apply all the offline redologs, before the upgrade. Technically, you can import offline redologs after the upgrade, by changing "compatibility" parameter in oracle, but regarding to my experiences it may cause some problems after you transitiate the role from standby to primary.
In short;
In order to stop log shipment, at the primary site;
alter system set log_archive_dest_state_2=defer;
In order to import all the offline redologs without a delay, at the standby site;
alter database recover managed standby database cancel;
alter database recover managed standby database nodelay disconnect from session;
I hope that I clarified the issue,
Best regards,
Orkun Gedik

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

Applying cpu with a physical standby in place - 11g

187242.1 covers this wrt 9i. Is this topic covered for 11g specifics somewhere? Can't google/metal ink it anywhere. Thanks.

The "readme" for Patch 9369783 (which covers the AprilCPU for our 11.1.0.7 HPUX-IA64 environment) includes this short reference to DataGuard:
If you are using a Data Guard Physical Standby database, you must first install this patch on the primary database before installing the patch on the physical standby database. It is not supported to install this patch on the physical standby database before installing the patch on the primary database. For more information, see My Oracle Support Note 278641.1.
When checking that note 278641.1 we see that it also appears to only cover 10.2. Although this note has more detail, it is clearly the same procedure as discussed in 813445.1. Therefore, the conclusion that I make is: OPatch works exactly the same with DataGuard in 11g as it did in 10g.
We will be upgrading our DataGuard enviornment to 11g in one-month. At this point, I am completely expecting our OPatch procedures to remain unchanged from what we have done for years with 9i and 10g. I would also note that the upgrade procedures we have tested (involving DG from 10.2.0.4 to 11.1.0.7) are nearly identical to the above mentioned support notes.
Hope that helps,
Stan

Applying patches to physical standby node(Data Guard 10.2.0.3)

Hello,
I have a data guard 10.2.0.3 environment (1 primary and 1 physical standby on a separate node) on solaris 10 and i want to document the procedure in applying patches to this environment.
I saw the article in Metalink Note 278641.1 which describes the procedure in applying a patchset to both nodes. It looks like both nodes need to be down before applying the oracle patchset.
Can we not apply the patches on only the standby while the primary stays up and running? My guess is you can't if the patches are significant i.e. it changes versions of the oracle binaries. But i want to confirm this.
Also, if we are applying solaris patches, i.e. nothing related to Oracle, we should be able to just apply them to the standby while keeping the primary up and running right?
The following has worked so far but i wanted to find some documentation that confirms it's ok.
1. shutdown oracle on standby node.
2. apply solaris patches...
3. restart oracle on standby node and put in managed recovery mode.
Any comments are appreciated.
Thanks.

Hi
Did you get an answer for your question yet? I have the same problem with one of our databases. Would be very nice, if you could tell me.
Regards
Felix

Who has Docs for (RAC) 10.2.0.5 CPU Patches with Physical Standby db ?

thanks
Edited by: ROY123 on Nov 8, 2010 1:08 PM
Edited by: ROY123 on Nov 8, 2010 1:16 PM

Hi,
you can see this link for more details
http://www.myoraclesupports.com/content/patch-9952230-102051-patch-set-update

Upgrading to 10g with a Physical Standby in Place

I am looking through Oracle note 278521.1 for upgrading my Oracle database with stand by database and I have problem with step 15:
15. In order to optimize performance the 10g Release 1 and lower versions of the Database Upgrade Assistant will disable archive log mode during the upgrade process. As this will invalidate the standby we must disable this option.
       a) Within the new 10g home open the following file:      ?/rdbms/admin/utlu101x.sql
       b) Ssearch for a line with the text DisableArchiveLogMode and change the value to false. For instance:
               Modify the line
              '<DisableArchiveLogMode value="true"/>');
                    to
                   '<DisableArchiveLogMode value="false"/>');
       c) Save the file.
     RESULT: This will cause the database to be upgraded in Archive log mode
I am upgrading to 10.2.0.2 and I can not find these lines for disabling archivelog Mode. Is it that I am looking into wrong files or in 10.2.0.2 DBUA is not switched off during upgrading.

Hi Andrija,
The DBUA asks at step 3 if you want to disable Archiving or not.
Best Regards,
JC Llanes.

Apply CPUOCT2008 with both a physical and logical standby in place

Hello All,
I'm trying to compile a decent set of steps for applying the CPUOCT2008 patch to our production RAC cluster which has both a logical and physical standby in place. I've read a tonne of documentation, including the CPU readme, DOCID 437276.1 and 278641.1. I''ve also read through the Upgrading Databases in a Data Guard Configuration chapter of Dataguard Concepts and Administration. The last doc mentioned is really for upgrading a full version of Oracle rather than applying a CPU (at least I think that's the case). DocID 437276.1 is rather sparse on details.
I guess what I'm trying to understand is the proper method for applying the patch with the logical standby in place. The physical standby looks pretty straightforward. After running opatch on it as well, it will basically have all of the changes applied to the primary shipped over and applied as per the normal primary/standby relationship. Will the same be true for the logical (having applied the patch, and then re-enabling SQL apply)? Should I aim to have it work that way? By that I mean start it up and re-enable sql apply and then upgrade the primary. Or, am I to apply the catcpu.sql script to it as well before re-enabling the sql apply? Am I wrong in regards to the physical standby as well i.e. should the catcpu also be applied directly to it?
Thanks very much in advance.
Cheers,
Chris

Given the fact that your system is far from main-stream I'd recommend opening an SR with Oracle Support Services (metalink) and asking them.
If you would like to publish a White Paper on your experience after you have successfully completed the project let me know off-line.

Patch 9205 to 9208 on production and physical standby

Hi all
I have to apply patch on production db and as wellas on standby db can anyone provide me the steps or a metalink on how to apply the patch in scenario like mine.
I am on win2003 server with 9205 and have to apply 9208 patch
Is it advisable to apply the patch on both the servers or first we shoulsd apply the patch on production and if everything went fine then we should apply the patch on physical standby
Please advice me on the pros and cons as per the above scene
thanks in advance
ajay

Thanks for the reply..
I have checked the readme file it is not of much help. I shall be greatful if you can provide something else other than README file.
Thanks
ajay

Getting errors when creating physical standby.

Hello All,
i am getting following error when i creating a physical standby for production,
i used below command to do it
duplicate target database to standby dorecover;
after some time it throwed this error.
Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+DATA/solfho2/datafile/system.382.764328493'
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/12/2011 13:04:06
RMAN-03015: error occurred in stored script Memory Script
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/arch/SOLFHO2/PROLHO01_1_25224_740461103.arc'
ORA-16145: archival for thread# 1 sequence# 25224 in progress

Hello;
Looks like a do over.
I have my short notes here:
http://www.visi.com/~mseberg/duprman2.html
This has been tested several times.
Best Regards
mseberg

Error raised when opening physical standby in read only

Hi,
I've a physical standby 11.2.0.2 created using RMAN duplicate from active database which is configured with data guard. When I open the database in READ ONLY mode
SQL> alter database open read only;
Database altered.
SQL> select open_mode from v$database;
OPEN_MODE
READ ONLY
I get this error in the alert log
Physical standby database opened for read only access.
Fri Aug 12 15:14:01 2011
db_recovery_file_dest_size of 256000 MB is 4.72% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Errors in file /oradata/admin/ORAINT/diag/diag/rdbms/oraintsb/oraintsb/trace/ora intsb_ora_8692.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00931: missing identifier
ORA-06512: at "SYS.DBMS_UTILITY", line 156
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 72
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 84
ORA-06512: at "SYS.PROC_PKGS_KEEP", line 26
ORA-06512: at line 2
Completed: alter database open read only
the tracefile is showing this,
Trace file /oradata/admin/ORAINT/diag/diag/rdbms/oraintsb/oraintsb/trace/oraintsb_ora_8692.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /opt/oracle/product/11.2.0/ORAINT
System name: Linux
Node name: c4p-db01
Release: 2.6.18-194.0.0.0.3.el5xen
Version: #1 SMP Mon Mar 29 18:27:00 EDT 2010
Machine: x86_64
VM name: Xen Version: 3.4 (PVM)
Instance name: oraintsb
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 8692, image: oracle@c4p-db01 (TNS V1-V3)
*** 2011-08-12 15:14:03.367
*** SESSION ID:(24.1) 2011-08-12 15:14:03.367
*** CLIENT ID:() 2011-08-12 15:14:03.367
*** SERVICE NAME:(SYS$USERS) 2011-08-12 15:14:03.367
*** MODULE NAME:(sqlplus@c4p-db01 (TNS V1-V3)) 2011-08-12 15:14:03.367
*** ACTION NAME:() 2011-08-12 15:14:03.367
Error in executing triggers on database startup
*** 2011-08-12 15:14:03.367
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
----- Error Stack Dump -----
ORA-00604: error occurred at recursive SQL level 1
ORA-00931: missing identifier
ORA-06512: at "SYS.DBMS_UTILITY", line 156
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 72
ORA-06512: at "SYS.DBMS_SHARED_POOL", line 84
ORA-06512: at "SYS.PROC_PKGS_KEEP", line 26
ORA-06512: at line 2
if I disable the system triggers using
ALTER SYSTEM SET "_system_trig_enabled"=FALSE scope=both;
The error doesn't appear but when trying to switch to active dataguard the open_mode goes from READ ONLY to MOUNTED rather than READ ONLY WITH APPLY
Any help much appreciated
Edited by: phil74 on 12-Aug-2011 07:22

Have you checked what your guard status is set to?
SQL> SELECT guard_status from v$database;I've had a similar issue before but with a standby, whereby the status was set to ALL. This means all users apart from SYS are unable to make changes on the database.
My resolution was to set the status to standby:
SQL> ALTER DATABASE GUARD STANDBY;You may wish to set the guard status to NONE however.
I took some notes:
http://juniororacledba.wordpress.com/2011/07/17/oracle-logical-standby-dataguard-error However, I do not have a link to any Oracle documentation on the subject to hand. But might give you a head start.

Deleting archives with RMAN when physical database is in place

hi all,
i want to backup and remove archvie logs using RMAN on one of my system which is having a physical standby database.how can i ensure RMAN backup and delete only archive logs which are shipped to DR site(physical standby database).when ever i fire my rman script it should delte only the archvies which are alredy shipped.i appreciate your valueble inpus in this regard.
regards
SAngeeth

Hi,
@sangeeth +" what if my database has no flash recovery area confgured. "+
This is introduced in Oracle Database 11g R1. Please check http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/wnbradv.htm#sthref6
Archived log deletion policy enhancements
When you CONFIGURE an archived log deletion policy, the configuration applies to all archiving destinations, including the flash recovery area. Both BACKUP ... DELETE INPUT and DELETE ... ARCHIVELOG obey this configuration, as does the flash recovery area. You can also CONFIGURE an archived redo log deletion policy so that logs are eligible for deletion only after being applied to or transferred to standby database destinations. You can set the policy for mandatory standby destinations only, or for any standby destinations.
Regards,
Vaibhav

Upgrading with a physical standby database in place

Hi all
I am planning to upgrade my database which is 11.2.0.1 (Windows 32 platform) to 11.2.0.3. It has a primary standby database. I only have 1 server for testing the primary database, so I am looking for some help.
I was reading http://docs.oracle.com/cd/B28359_01/server.111/b28294/upgrades.htm#CHDBJAGG and I confuse about step 4 and 5
+4. Install the new release of the Oracle software into a new Oracle home on the physical standby database system, as described in the Oracle Database Upgrade Guide.+
+5. Mount the physical standby database.+
My question is in step 5, when I mount the physical standby database, does it mounted using new Oracle binary or still using the old version? From my understanding what is step 4 doing is to copying files to new home only. Changing the service to use the new oracle binary is done by dbua. I know this when I test upgrading the primary database.
Regards
Stanley.

Hello;
new Oracle binary or the new Oracle home if you will.
So you install the new software on the standby only, all the upgrade SQL gets done on the Primary and then you ENABLE and startup mount on the new oracle home and the standby gets upgraded from the Primary redo.
Its pretty simple ( My exact plan )
1. Disable log shipping from the Primary
2. Shutdown Standby
3. Install 11.2.0.3 on Standby - Just the software
4. Startup Standby in recovery mode - do NOT run r any SQL at the standby
5. Shutdown Primary
6. Install 11.2.0.3 on Primary
7. Run Upgrade SQL or DBUA at Primary
8. Re-enable log shipping
9. Monitor the redo apply from Primary to Standby - this will also upgrade the Standby data dictionary
Make sure your tnsnames and listener files move to the new Oracle home and edit as needed.
Another oracle note is 278641.1
Best Regards
mseberg
Edited by: mseberg on Jan 29, 2013 8:21 PM

What happens at backend when we fire alter database commit to switchover to physical standby

Hi,
What exactly happens at backend when we fire alter database commit to switchover to physical standby.
how the transition happens?
Thanks

Hi,
The following will happen at the backend
1.) Notifies the primary database that a switchover is about to occur
2.) Disconnect all users from the primary database
3.) Generate a special redo record that signals the End of Redo (EOR)
4.) Converts the primary database into a standby database
5.) Once the standby database applies the final EOR record, guaranteeing that no data loss has been lost, converts the standby database into the primary database.
The new standby database (old primary) starts to receive the redo records and continues process until we switch back again. It is important to remember that both databases receive the EOR record so both databases know the next redo that will be received.
Regards,
Pradeep. V

Got RMAN error when running RMAN backup of archivelogs on physical standby database

Got below error when running RMAN backup of datafiles and archivelogs on physical standby database.
RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database:
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist
Could anyone help me? Thanks,

Hello;
When you connect RMAN to the source database as TARGET you must specify a password even if RMAN uses operating system authentication.
So the errors ORA-17627 and ORA-00942 appear to be cause and effect.
What version of Oracle? ( 11.2.0.4 according to the tag )
Can you post your backup script?
Best Regards
mseberg
Update
According to :
Database Error Messages 11g Release 2 (11.2) E17766-03
RMAN-06820: WARNING: failed to archive current log at primary database
Cause: An attempt to switch the archived log at the primary database failed.
So I would check my Primary alert log for an issue.
Message was edited by: mseberg

Appying patches when Physical standby in place.

Similar Messages

Maybe you are looking for