Upgrading Standby Database

Hello Expert !!
Once again I need you expert advice. We have a production database on 9.2.0.5, which we would like to upgrade to 10.2.0.3. A Physical Data Guard configuration is present for this database. The size of the database is more than 1 TB.
Upgrading Primary database is straight forward but how do I upgrade the standby database and continue the Data Guard configuration.
While upgrading the primary we would startup database with upgrade option and then startup-shutdown database couple of times. While upgrading standby how do I startup-shutdown it? (I mean normally we would normally mount the database and then open it as standby database and then place it in recovery mode).
Thanks for sharing your expertise !!!
Regards

Please read it, rather than asking others to abstract it for free.
This is a forum where people exchange their experiences, if you are really looking to make money then please this is not the place you should be in.
If you are not capable enough or haven't performed yourself then its better to be quiet.
Metalink document (Note Id: 316889.1 Complete checklist for manual upgrades to 10gR2) discusses on upgrading from 9i to 10g but unfortunately doesn't mention a word about Standby Databases. So, I was looking for people who has actually performed the upgrade themselves and who could actually point to a URL which discusses more on this issue. I dont want you to walk-in and perform the upgrade for me.
Please, never ever take time to answer any of my questions. Remember my username "Oracle_Lover".
Thanks anyways....

Similar Messages

How to upgrade standby database

All,
how to upgrade standby DB if we are going to upgrade Primary DB from 9.2.0 to 10.2.0.4?
what will be the steps to upgrade stand by?

Upgrading Oracle Database with a Physical Standby Database In Place
=> http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/upgrades.htm#sthref2051
Upgrading Oracle Database with a Logical Standby Database In Place
=> http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/upgrades.htm#sthref2056
Nicolas.

Upgrading the primary and physical standby database

Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835

Read this Metalink Note:407040.1

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

Upgrading Installations that use Standby Databases

I have applied patch 6810189 and upgraded Oracle10g Database on my local machine, Now I am planing to apply it on test machine for that I need additional steps for upgrading Physical Standby database as said in README.html of p6810189_10204_Win32.zip
*7.1.2 Upgrading Installations that use Physical or Logical Standby Databases*
For information about physical standby databases, review document 278641.1.
Can anybody forward me this document or any suggestions for upgrading physical standby database..
THanks.

thanks :)
but I am looking for complete steps, starting from applying patch to production then at standby database.... etc..etc

Standby database upgrade process

Hi
I have a 11gR1 database with dataguard setup.I have successfully upgraded the primary database to 11gR2 using dbua.
Although 11gR2 software is installed on standby server,I realized archivelogs were not shipped to standby server during the database upgrade.
When I switch logfile in primary, I see below errors in standby alertlog:
RFS: 'Attach' request version mismatchWhat is the best way to sort out standby database regarding database upgrade ?
Do I need to manually add oratab entry, new pfile, etc in standby server ?
or
Do I have to rebuild DR ?

Both primary and standby compatible parameter is 11.1.0.0.0
However, rman is giving this error:
rman target sys/sys@orcl auxiliary sys/sys@orcl_std
Recovery Manager: Release 11.2.0.3.0 - Production on Sun Dec 11 08:53:34 2011
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1297219823)
Recovery Manager incompatible with AUXILIARY database: RMAN 8.0.4.0 to 11.1.0.7 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: AUXILIARY database is not compatible with this version of RMANLike I said, after the database upgrade pirmary became 11.2.0.3, standby is still 11.1
I upgraded primary with dbua.
Do I need to mount standby from new 11.2 home , copy pwd file, add oratab entry etc ?
These were done automatically on primary via dbua

Upgrade PHYSICAL STANDBY database to 10g from 9i

Hello everybody,
Please can you provide me the details for Manual upgrading 9i STANDBY database to 10g. Any special parameters that we have to set on the Primary database..
Any sites with the information available would be great.
Thanks everybody for your help.

There is no in-place upgrade process to move from 9i to 10g. You have to upgrade your primary and then reinstantiate your standby (using Oracle10g). You may like to keep your 9i standby in tact until your upgrade of 9i primary to 10g is completely successful.....just to ensure that you have a fast, easy and reliable fall-back plan.
Thanks
Chandra

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

Upgrade of standby database

I'd like to upgrade my standby database form 8.0.6 to 9.2.
Is anyone having a manual or procedure to upgrade a standby database ?
Thank you.
Eric

I believe that the process is basically identical to the process outlined in the Migration Guide http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96530/toc.htm.
For a standby database, though, you have to ensure that you apply all the 8.0.6 log files first, then upgrade the primary, then update the standby, then start applying the 9.2 log files.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Upgrading Physical standby database

Hi Gurus,
we are having Data Guard setup in 9.2.0.6 with 5 databases in windows 2000 now we are planning to upgrade it to 10.2.0.4 can you please give me ur valuable suggestions or best possible ways to upgrade these database.
kk

When all else fails, Read The Fine Manual
http://download.oracle.com/docs/cd/B19306_01/install.102/b14316/toc.htm
IIRC, first you need to upgrade to either V9.2.0.7 or V9.2.0.8 which will be documented in manual above

Standby database upgrade scenario

Hi all
I have to databases. One 10.1.3 and second 10.1.5
I created standby database for 10.1.3 database. And now want to create second standby database for my second 10.1.5 database...
How I must do it?
Can I convert (or how can I convert) my installed 10.1.3 standby database to preapre creating another 10.1.5 standby database?
Thanks...

I have to say that's not very clear for me.
You have one 10.1.3 database with a standby.
You have one 10.1.5 database you want to build a standby on.
Right ?
So, why do you need to "convert" the 10.1.3 standby to 10.1.5 ?
Keep in mind, it's better having the standby database in same verion/release/patchset as the primary db.
Nicolas.

Standby database can't work !!!

hi,
i set up a standby db for my production db .
However, below error occurs while i perform "recovery managed standby database" :
ORA-00283: recovery session canceled due to
errors
ORA-16016: archived log for thread 1
sequence# 436 unavailable
i tried to fix the problem with the following method:
1) apply "alter system archive log current"
on production server;
2) download the log 436 to standby host;
3) recover standby database until the time
generated the log 436;
4) re-apply the command;
BUT, this time it asked for log 437 !!!!!!!!
can anybody help ???
Thanks a lot
stephen

If the standby hasn't work for years, it's not quite possible to sync it with primary. Of course if you have all the archive logs in these years, you could but it's not as efficient and fast as rebuilding it.
Follow the Oracle doc to build a new standby.
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76995/toc.htm
btw, it's time to plan upgrade your server.

Can I have a primary database and standby database with a different windows version?

Hi
I need your help.
We need to increase the memory in the server where is the standby database , but first, we need to upgrade the windows version.
The actual version is windows 2003 standard edition 64 bits
The new version will be windows 2003 enterprise edition 64 bits
This difference in windows version between primary and standby servers can cause a problem in the synchronization between primary and standby databases ??
What do you recommend? Have both servers in the same windows version?
The databases are in SQL SERVER 2005.
Thanks.
Loreinn

This difference in windows version between primary and standby servers can cause a problem in the synchronization between primary
and standby databases ??<o:p></o:p>
There is no issue with database synchronization as long as SQL Server is of same version.<o:p></o:p>
What do you recommend? Have both servers in the same windows version?<o:p></o:p>
OS(Windows version) has no restriction for using SQL server 2005 database mirroring/log shipping. You can go with upgrade without any worries on SQL
database side.<o:p></o:p>

Standby database failover flashback restart as standby gap 1-100

Hi,
I have setup a physical standby database for a 3 node RAC primary database and configured the database to run in MAXIMUM AVAILABILITY mode. Both the primary and standby databases use ASM for managing the IO. I have enabled FLASHBACK ON on both the databases.
I did failover to standby database with primary db SHUTDOWN for doing some testing. After testing is done, I flashbacked the (standby, currently primary)database to the point when it became primary and start it as standby again and the old primary as primary.
Following are the steps:
Failover steps
.Shutdown the primary database
To finisish the recovery at standby
SQL>alter database recover managed standby database finish;
To start as primary
SQL>alter database commit to switchover to primary;
do some DML on the new primary
SQL>flashback database to scn <standby_became_primary_scn>;
SQL>alter database create standby controlfile as '/backup/standby.ctl';
Changed the spfile to point control_files to '/backup/standby.ctl';
Restarted the standby db in mount mode and
created the required stanbdy logs on it.
Then issued
SQL>alter database recover managed standby database using current logfile disconnect;
I have the following message in v$dataguard_status at standby db;
Fetching gap sequence in thread 1 branch(resetlogs_id) 653234404, gap seq 1-100
DBID 2651011616 branch 653234404
GAP - thread 1 sequence 1-100
FAL[client]: Failed to request gap sequence
FAL[client]: All defined FAL servers have been attempted.
The same error is found in alert log file also.
The status of the varioud managed standby db are as follows.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CLOSING
ARCH CLOSING
ARCH CLOSING
MRP0 WAIT_FOR_GAP
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
PROCESS STATUS
RFS IDLE
RFS IDLE
RFS IDLE
RFS IDLE
15 rows selected.
SQL>
Could you please help me how to resolve the above error.
Thanks,
Sreekanth

Sreekanth,
I think your steps are right on for your requirement, except instead of
alter database create standby controlfile as '/backup/standby.ctl';
you can do this:
ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
(although perhaps it achieves the same thing internally but you don't need to repoint to new controlfile).
So far as the GAP - thread 1 sequence 1-100
Let me guess, your current sequences are probably well ahead of this reported gap?
If so, this is a bogus gap in a sense that your standby has long ago applied them, but for some reason standby controlfile gets a little confused and starts asking for them again.
I have had this issue and opened multiple TAR's with Oracle since 10.2.0.1, got a few patches and advises to upgrade, but still occasionally get it now in 10.2.0.3
I strongly believe this is related to combination of RAC (i.e. multiple threads of redo) and dataguard.
It is also pretty hard to reproduce (I have not figured out how to reproduce this reliably, if you have, let me know), so I can understand why Oracle has so far been unable to fix this.
Anyway, the workaround is to re-create standby controlfile with a copy generated on primary, and move it in place of the existing (and confused) controlfiles on standby.

Need help on Standby database v8.1.7 on Windows

Hello All,
Our current setup to create a standby database consists of a bunch of scripts. I'm trying to convert this such that we can use OEM 9.2 and have jobs to do the backup and be able to create the standby database using point and click. Does anyone have this setup?
This is where I am....I've created the primary database and the standby database. They both work well and next i try to do a failover. The failover works and my new primary database is now active. I want to recreate the standby database now (old primary).
I do a backup of the new primary database do say D:\backup\. I go on the standby and I restore the controlfile. Next when I attempt to do the restore, I get the following error: RMAN-03002: failure during compilation of command
RMAN-03013: command type: IRESTORE
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 1 found to restore.
How can i fix this? Is there a way to tell RMAN that the backup is under D:\Backup\? How do I catalog the files? I remember on 10g you could do this..but that's if you use a recovery catalog. In this case, i'm using the controlfile to do the restore...not using Recovery Catalog.
Any assistance is appreciated.
Thanks!

Upon reading the document i am not clear on upgrade path like do i need to upgrade clusterware as well or not?You need to upgrade the clusterware before RDBMS....therefore it is not optional. You first need to upgrade the clusterware and then the RDBMS.
The steps listed by you seems to be in order (from a high-level).

Upgrading Standby Database

Similar Messages

Maybe you are looking for