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.

Similar Messages

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

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

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

Oracle 10g Linux SLES, Physical Standby, Log Apply Stops

Hi, ia am faced the following problem:
Log applying on standby work perfect N days.
(Managed recovery mode, not real time)
Then just stops, without any (visible) reason.
Cancel recovery does not work. There is nothing in log/ trace/ alert files. In v$ views - just "applying log N (let say) 877" - for hours.
I kill DB Writer process on standby, do startup mount and "alter database recovery managed standby database disconnect from session". ...
It works again N days perfect.
I did not found nothing about that.
Any ideas?
Your help is highly appreciate, thank you in advance

The error message (which you should have BTW looked up beforehand in the online error documentation, and apparently you didn't even do this minimal work) is self explanatory.
Oracle can't reach the second server. You need to establish whether you can ping it on O/S level and whether you can TNSPING it.
Problems will arise if the second server uses NAT and sends it's own IP address back, instead of the IP address it is known under by DNS.
The Net administrators manual contains a troubleshooting chapter, as far as I remember this error is discussed in depth.
Sybrand Bakker
Senior Oracle DBA

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?

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

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

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.

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.

Step by step 10g Dataguard , physical standby database setup metalink notes

On metalink i saw this note, but unable to find now if someone can help....

Note:248382.1 Creating a 10g Data Guard Physical Standby on Linux

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.

DG physical standby 1

Hi
11.2.0.1
We have a DEV database which is also as critical as PROD db since there are lots of critical projects running on it.
This DEV database was configured with dataguard physical standby at the DR server.
Well this is what I read in the documents only, as I am newly taking over as dba. The setup was done outsourced
by 3rd party, and I can not talk to the implentors as they have been long gone.
When I check the DR server only the PROD is running and the DEV was shutdown for the last 12 months.
My question is if the physical standby is shutdown for almost a year, can it still be activated? or will it still be valid?
Will it affect performance of the Primary database? since it might still checking heartbeat to it? or holding up some processes like archivers?
How do you disable physical standby from the primary db?
Thanks
petra k.

Hello;
"if the physical standby is shutdown for almost a year, can it still be activated? or will it still be valid?"
No and no. Even a tiny production database would have generated and remove too much archive in a years time for the old standby to have ANY value. Rebuild it.
How do you disable physical standby from the primary db?
You could just do this: ( On the primary side )
alter system set log_archive_dest_state_2=defer;
And you could clean up all the parameters for DG too.
How to remove a Data Guard Configuration from Primary Database (Doc ID 733794.1)
Best Regards
mseberg

Physical standby crash leads to peculiar process behavior on primary nodes

Hey all, we had an issue early this morning with our physical standby database in our production environment. It's an odd problem and I thought I'd share it to see if anyone else has come across a similar problem.
Our environment consists of a two node RAC cluster running 10.2.0.2 Enterprise on Red-Hat x86-64 Linux boxes. We have implemented a single physical standby at a remote site using real-time log apply.
Upon arrival this morning I discovered that a large portion of the primary database activity was a wait class event(ARCH wait on SENDREQ). The problem was quickly identified as a network issue between our site and the remote standby. However, the physical standby seemed to be running normal, with no messages in the alert logs regarding network disconnects. Further investigation showed that our log-apply had stopped all together early that morning. It seems the DBWR process crashed around 630am, as per this trace dump:
*** 2008-02-27 06:24:53.667
Waited for detached process: DBW0 for 300 seconds:
*** 2008-02-27 06:24:53.667
Dumping diagnostic information for DBW0:
OS pid = 10587
loadavg : 12.11 11.67 8.95
memory info: free memory = 0.00M
swap info: free = 0.00M alloc = 0.00M total = 0.00M
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
0 S oracle 2448 31813 0 78 0 - 13190 wait 06:07 ? 00:00:00 /bin/sh -c /usr/bin/gdb -quiet -x
/tmp/stacknvvano
/proc/10587/exe 10587 < /dev/null 2>&1
0 S oracle 2449 2448 0 78 0 - 38780 wait 06:07 ? 00:00:00 /usr/bin/gdb -quiet -x
/tmp/stacknvvano /proc/10587
/exe 10587
0 D oracle 10587 1 0 76 0 - 43072 - Jan04 ? 00:04:09 ora_dbw0_schclsdb
So what we did was restart the standby server and the database came up fine. We reinitiated log apply services and both databases did sync up. However
we are still seeing the "ARCH wait on SENDREQ" wait event from ARC0 and ARC1 on both the RAC instances.
We tried reseting the connection to the standby database, however did this not clear up the wait event. The system itself, as far as I can tell is not suffering, and redo logs are going across to the standby database without issue. What could be the problem with the ARC0 and ARC1 processes?
It would probably be helpful to mention that we don't actually use the ARCH processes for the log apply unless the standby falls behind. Archiving is handled by the local LNS process and remote RFS service. A quick instance restart would fix it, to be sure, but since this is happening in a production deployment in a 24x7 environment, I'd rather not have any downtime. A service request is of course filed, but since they have not gotten back to me yet and Metalink hasn't been of much help, I thought I'd see if any of you have seen this before. This giant gray blob on my grid control histogram is quite obnoxious. =) Thanks for taking the time to read. Cheers.
-Jim Henaghan

Just as an update to anyone else who may have this problem, we haven't found a good way to clear up our Archiver issue, so a instance restart will take place. Further research indicates the issue came about from a MRP process crash due to a known bug fixed in 10.2.0.4 (https://metalink.oracle.com/metalink/plsql/f?p=130:14:316259464254960300::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_frame,p14_font:NOT,5894403.8,1,0,1,helvetica)

Upgrading to 10g with a Physical Standby in Place

Similar Messages

Maybe you are looking for