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

Similar Messages

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.

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

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

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

How to change COMPATIBLE with a physical standby database?

Hello.
The obvious answer is do it on both the primary and the standby at the same time... since the reference manual says : "When using a standby database, this parameter must have the same value on both the primary and standby databases.".
However, I was wondering, I have a 10.2.0.3 DB with compatible=9.2.0.5. What will happen if I leave the parameter to 9.2.0.5 on the standby and just make the change to 10.2.0.3 on the primary? Would I be able to continue to apply the logs on the physical standby? Would I be able to open it ? (I understand that the transport won't probably work anymore and that I won't be able to switchover)
I guess those 2 questions are stupid but I haven't found any clear statement yet.
Please stay tolerant. Thank you.
Gregory
PS: I know what are the alternatives.

So the answer is obviously: We cannot do that. That completely makes sense btw. I tried with 10.2.0.1 to 10.2.0.4 and I got:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/22/2008 18:35:55
RMAN-11003: failure during parse/execution of SQL statement: alter
database recover logfile '/u01/app/oracle/oradata/WHITE/redo02.log'
ORA-00331: log version 10.2.0.4.0 incompatible with ORACLE version 10.2.0.1.0
ORA-00334: archived log: '/u01/app/oracle/oradata/WHITE/redo02.log'
I should have think about it before I asked. That would have meant we could revert the database from 10g to 9i any time... And the bootstrap changes are not stored in the redo log...
Gregory

Apply missing log on physical standby database

How to apply the missing log on physical standby database?
I already registered the missing log and started the recovery process.
Still...having log on standby that has status ..not applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# APP
16018 YES
16019 YES
16020 NO ---------------------> Not applied.
16021 YES
Thanks

Not much experience doing this, but according to the 9i doc (http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96653/log_apply.htm#1017352), all you need is properly-configured FAL_CLIENT and FAL_SERVER initialization parameters, and things should take care of themselves automatically. Let us know if that doesn't work for you, we might be able to think of something else.
Daniel

Physical standby database Version 11g Creation over grid control 10g

We are useing oracale 11g enterprise edition and want to create a physical standby database on another machine:
On primary host we've installed "standard database" and turned on archive log mode over em.
On the standby host we've installed only oracle without a database and without a listener.
On a third machine we've installed grid control and registered the primary and standby hosts. Using EM with Data Grid I'm attempting to create a Physical Standby on standby host. Everything is working except for the last part as noted here:
SQL*Plus: Release 11.1.0.6.0 - Production on Do Apr 3 11:21:17 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
SQL> SQL> Bei einer nicht hochgefahrenen Instance angemeldet.
SQL> SQL> ORA-32004: obsolete and/or deprecated parameter(s) specified
ORACLE-Instance hochgefahren.
Total System Global Area 535662592 bytes
Fixed Size          1334380 bytes
Variable Size          167773076 bytes
Database Buffers     360710144 bytes
Redo Buffers          5844992 bytes
SQL>
Datenbank wurde geändert.
SQL> Verbindung zu Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options beendet
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSTEM01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSTEM01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\SYSAUX01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\SYSAUX01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\UNDOTBS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\UNDOTBS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\USERS01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\USERS01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\EXAMPLE01.dbf'
dgcreate.DGrenameFiles: SELECT STATUS FROM V$DATAFILE WHERE NAME = 'C:\ORACLE\ORADATA\TTDB1\EXAMPLE01.DBF'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO01.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO01.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO02.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO02.log'
dgcreate.DGrenameFiles: ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\TTDB1\REDO03.LOG' to 'c:\oracle\product\11.1.0\db_1\oradata\dg3\REDO03.log'
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 1
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 2
dgcreate.DGrenameFiles: ALTER DATABASE CLEAR LOGFILE GROUP 3
dgcreate.DGgetRecoverySCN: SELECT MAX(NEXT_CHANGE#) FROM V$ARCHIVED_LOG
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER AUTOMATIC FROM '%ORACLE_HOME%\RDBMS' STANDBY DATABASE UNTIL CHANGE 1061001
dgcreate.DGrecoverStby: ALTER DATABASE RECOVER CANCEL
dgcreate.DGrecoverStby: ALTER DATABASE OPEN READ ONLY
SQL Error: ORA-16004: Sciherungs-Datenbank muss wiederhergestellt werden
ORA-01152: Backup-Datei zum Wiederherstellen der Datei 1 war nicht alt genug
ORA-01110: Datendatei 1: 'C:\ORACLE\PRODUCT\11.1.0\DB_1\ORADATA\DG3\SYSTEM01.DBF' (DBD ERROR: OCIStmtExecute)
What is to do?
What mean's in this case:
"ORA-01152 file string was not restored from a sufficiently old backup
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery."

Thanks for your immediate reply,
but there's a problem: We don't create the standby database manually. The creation is done by data guard over grid control. And the "automatic" creation stopps at this point.
Unfortunatly we don't know, wich steps of a manuall standby database creation are done and wich steps are not done at this point.
The oracle documentation (for release 11g) to create a manuall standby database is "B28294-02". But there's no step 5 "alter database recover managed standby database disconnect from session". Do you mean step 4 of chapter 3.2.6?
Is there no way, to create a standby database automatically over grid control? Or do we have to do something else before creating the physical standby database? Perhaps we have to create a full backup after switching to archive log mode?

RMAN Backup with ASM and Standby in place

Hi All,
We are planning to upgrade our database from 10.2.0.2 to 10.2.0.3. We have ASM as storage on primary and phisical standby is in place.
I want to make a cut of point for backup, i.e if I restore till that poit on primary standby should continue to work. I need not create standby.
We are using rman for backup and primary db uses asm for data,archive and redolog storage.
I have a online complete db backup at 12:00PM. At say 6:00pm i take primary down and apply all archives on standby and cancel recovery on standby along with taking it down. On primary i mount db and take controlfile backup and all archive log backup using rman.
Now i continue with upgrade and many more changes on primary. I will not touch standby. We decide to revertback at 10pm on primary. If I wan to return back to 6:00pm state on primary and standby.
I believe I will restore controlfile backup taken at 6:00pm with db in mount phase. Restore dbfiles from online backup and recover using archives.
My question is do i need to open with resetlogs? Then I will lose my standby which was up to date at 6:00pm. Can I not backup redofiles at 6:00pm with db in mount phase and i restore them then i need not open with reset logs and my stnadby will continue from that point.
Please guide me..Is there way to backup redologs when db is in mount phase and using asm for storage using rman.

There are quite a bunch of steps involved and you need to do some documentation reading.
Do you plan to create the test database on the same machine or different RAC system?
Which version of Oracle are you using? What OS?
There is plenty of information on the web if you search for "duplicate database RAC ASM". Did you try?

How to apply archivelog with gap on standby database

Hi All,
Oracle Database version : 9.2.0.6
Following is my sequence of commands on standby database.
SQL>alter database mount standby database;
SQL> RECOVER AUTOMATIC STANDBY DATABASE UNTIL CHANGE n;
ORA-00279: change 809120216 generated at 07/24/2006 09:55:03 needed for thread
1
ORA-00289: suggestion : D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC
ORA-00280: change 809120216 for thread 1 is in sequence #19921
ORA-00278: log file 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' no longer
needed for this recovery
ORA-00308: cannot open archived log
'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
I have check the last sequence# on standby database which is 19921. And I have archivelog starting from sequence# 20672 onwards. When I am trying to apply archive log starting from sequence# 20672 , it is searching for 'D:\ORACLE\ADMIN\TEST\ARCH\TEST001S19921.ARC' file and cancel the recovery. Please note that I don't have those missing archive on Primary server as well. So How can I apply the remaining archive log which I do have from 20672 onwards.
I hope I am not creating any confusion.
Thx in advance.

Hi Aijaz,
Thx for your answer. But my scenario is bit complex. I have checked my standby database status which is not running in recovery mode. I have tried to find archive_gap which is 0 on standby server. I am copying all archived log from primary to standby thru the script every 2 hour and appying them on standby. After applying, the script is removing all applied log files from primary as well as standby. So it is something like I have archivelog from 1,2,3,7,8,9,10. So 4,5 and 6 archivelog are missing which is required when I am trying to recover standby database. Also note that I want to apply 7,8,9,10. I will loose some data from those missing archive but I have cold back any way. I don't have those missing archivelog files(4,5 and 6) anywhere at all. So how can I recover standby database. I am using standby just for the backup purpose.
I hope my question is clear now.
Thx in advance
- Mehul

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.

Rolling Upgrade of Oracle 10gR2 RAC with Physical Standby (DG)

Hi DBAs,
I want to do a rolling upgrade of Oracle 10.2.0.3 (2 node RAC+ASM) with Physical Standy Dataguard to Oracle 10.2.0.4 also applying CPU (April2009).
Please suggest the best way to perform this upgrade and patching with no downtime.
Thanks
-Samar-

Unfortunately rolling upgrade is only possible with a logical standby in place:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/upgrades.htm#CHDBJAGG
That doesn't help you at this time, but 11g has a way to do it with a physical standby. Even here you need an intermediate logical standby:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/rollup.htm#CHDHCBGA
Werner

10204 Upgrade with Physical Standby Steps

Hi.
I am upgrading from 10204 with a Physical Standby this weekend. Doc 278641.1 mentions the only the Patchset and Interim patching and not the CPU. Should I break out the CPU patching into its own activity or can I do it at the same time as the Patchset and Interim patching? I would like to get all 3 done during the same downtime. Thanks for the help.
RCP

Welcome to the forums !
You can apply the CPU patches after the upgrade is complete - however, I recommend that you do this in a non-production environment first to make sure that there are no unexpected effects :-)
HTH
Srini

Physical Standby: Monitor Transport/Apply Lag

Hello Forum
I'm using 10.2.0.3 and my aim is to ensure having a physical standby db (to an two nodes RAC) to switchover/failover to in (hopefully) every disaster.
What are your best practises regarding to monitor transport/apply lag of a physical standby instance (data guard) within Grid control? How many seconds to set the treshold to? Or is there no need to monitor this? I have to say that I was able to achieve my aim in every (rare) disaster in the past.
I saw that there already two metrics in Grid Control (standard = not set).
Currently I got the following values measured:
Apply Lag (seconds): from 0 - 31
Transport Lag (seconds): from 0 - 8
Thanks for your advice
Casi

Hello Forum
I'm using 10.2.0.3 and my aim is to ensure having a physical standby db (to an two nodes RAC) to switchover/failover to in (hopefully) every disaster.
What are your best practises regarding to monitor transport/apply lag of a physical standby instance (data guard) within Grid control? How many seconds to set the treshold to? Or is there no need to monitor this? I have to say that I was able to achieve my aim in every (rare) disaster in the past.
I saw that there already two metrics in Grid Control (standard = not set).
Currently I got the following values measured:
Apply Lag (seconds): from 0 - 31
Transport Lag (seconds): from 0 - 8
Thanks for your advice
Casi

How to Flashback Primary with Physical Standby

We have a dataguard configuration with one physical standby (which is the FSFO). We had an application cause problems in the primary database (basically what would be considered a user error) and we would like to flashback the primary database without having to drop and re-create the physical standby.
Does anyone have a basic set of procedures for doing this?
We are running 10.2.0.3 on windows 2003 server sp2
Thanks!

We have flashback turned on in both the primary and standby. We want to flashback the primary (and subsequently the standby) to some previous point in time.
In a regular non-data guard setup we would just shutdown and startup mount and issue the flashback database to timestamp (sysdate-1). But with dataguard it's a little more complicated because if we shutdown the primary then the observer will initiate a failover which we don't want. And when we startup mount and flashback the primary, how do we flashback the standby? manually or do we re-start the broker and let data guard do it?
I think it's going to require some specific steps and I was hoping someone had gone through this and could offer some suggestions.

Applying cpu with a physical standby in place - 11g

Similar Messages

Maybe you are looking for