CPU patch procedure with physical and logical standby database in place

Hello All,
I've also placed this in the Upgrades forum, but perhaps this is the best place to have put it.
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
Edited by: chris.baron on Dec 12, 2008 11:38 AM

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.

Similar Messages

Difference between physical and logical standby database

What is the difference between physical and logical standby database?

Hi,
Physical Standy where its a read only DB.
Logs are applied.
Logical Standy where it can be Read / Write DB and the logs are applied in terms of SQL Statements.
Thanks & Regards,
Pavan Kumar N

Physical vs Logical standby database

In the Oracle HA guide, it is mentioned that we must take Logical backup "in addition" to Physical backup (not instead of Physical Backup)
If I run have two systems i.e a Primary System and a Logical standby database system , is it not sufficient protection ? If the primary fails, can I not recover the primary system using the nightly backup I take from the Logical Standby Database.
If it is not sufficient protection, what exactly I will lose ?
Assume I take the nightly complete hot backup backup from the Logical Standby Database instead of the Primary System to save CPU cycles of the primary system.
In other words, it is said that "physical standby database provides zero data loss without any allowance for data divergence" -- What exactly is meant here ?

Thanks Werner for the reply.
1. If there is a human error (dropping a table by mistake), it will be applied to the standby database irrespective of whether it is physical standby or Logical standby. I am unable to see any advantage with Logical standby database in this case. Am I missing something here ?
Or are there any other type of user errors where Logical standby provides an advantage ? Can you please name some ?
2. If I backup from the logical database and if I am willing to "restore" (instead of recover) the primary from this backup in case of a primary failure, is it not the same effort ?
3. Can't we set up a Logical Standby with Maximum Protection Mode ?
I am aware physical standby offers a better performance and it has no data type restrictions. I do not care about these two. Also, I am aware of the extra features provided by Logical database.
Overall, I am trying to see whether physical standby database has any "feature" which I will miss with Logical standby database. I tried my best with Oracle documentation, but I could not get a clear answer.
Any help is appreciated.

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.

Time difference between physical and logical standby

Hi,
I have just been tasked on getting some info and setting up dataguard for some users for read-only/reporting purpose.
The 3 questions I am being asked are:
1. What is the time difference in applying changes from primary to physical standby compare to logical standby
2. What is the overhead maintenance of having a standby database?
3.What latency is involved?
I will be glad to have your input on this.
Thanks

Hi,
Physical Standy where its a read only DB.
Logs are applied.
Logical Standy where it can be Read / Write DB and the logs are applied in terms of SQL Statements.
Thanks & Regards,
Pavan Kumar N

Manipulations with physical and logical names

Hello ppl,
Is there any way to see/change phisical and logical names of object in one place/screen? I mean I want to set them to different values and see that change, but without fuzzu, complex way of changing naming and propagate modes.
TIA,
Alex

Mark,
Under project, preferences (from the main console) you can set the naming and also the propagation method. That's what I hate to do :) However, thinking deeper I find it ok - first finish with modelling and physical names, than correct logical names as needed without propaation to physical.
Alex

Physical and Logical Standby

Hi
I just wanted to know can i have one Physical and One Logical Standby for a Single Primary Database. Is there any precautions and steps to be followed .
Thanks

user9366471 wrote:
Hi
I just wanted to know can i have one Physical and One Logical Standby for a Single Primary DatabaseYes this is possible.
See following Oracle 10.2 example which talks also about cascaded standbys:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/cascade_appx.htm#i637055

Help with setting a 2nd Standby Database

Hi,
I have an active DataGuard 11gR2 with a physical standby actively running on Linux.
Now, I need to add a 2nd physical Standby database (for reads only) to this environment, can someone please point to a resource/document which discusses the steps which are involved?
Thanks much
-Sravan

Hello;
One option is to setup a Cascading Standby. I tested this last spring and I'm happy to share my setup notes.
www.visi.com/~mseberg/Data_Guard_Cascading_Standby_Setup_and_Test.pdf
Also worth noting if you have Active Data Guard you don't need a second Standby, ( license for active Data Guard required ).
Best Regards
mseberg
Edited by: mseberg on Nov 22, 2011 7:09 AM
For additional information see :
Data Guard Concepts and Administration
12.1.3 Configuring Both Physical and Logical Standby Databases ( Oracle document B14239-05 )
In this case you could use the Logical Standby as you "Reader" database.

Apply Patches on Oracle Database with Logical Standby Database

Here I am:
I got a primary database with a logical standby database running Oracle 11g. I got two client applications, one is the production site pointing to the primary one, another one is just a backup site pointing to the logical one.Things will only be written into the primary database every mid night and client applications can only query the database but not add, update nor delete.And now, I want to apply the latest patch on both of my databases. I am also the DNS administrator, I can make the name server pointing to the backup site instead of the production one.I want to firstly apply the patch on the logical one, and then the physical one.
I found some reference which explains how to apply patches by adopting "Rolling Upgrade Method". however, I want to avoid doing any "switch over" mentioned in the reference because I can make use of name server. Can I just apply patches as the following way?
1)Stop SQL apply
2)Apply patches on logical standby database
3)let the name server point to the backup site
4)Apply patches on the primary database
5)Start SQL apply
6)Let the name server point back to the production site
Thanks in advance.

Pl follow the steps in MOS Doc 437276.1 ( Upgrading Oracle Database with a Logical Standby Database In Place )
HTH
Srini

Streams Replication:Source database Physical or Logical Standby DB

Can the source database in streams replication be a physical or logical standby database ? If so, is the process of configuring streams the same as a regular database ? Are there any best practices or different configuration if the source is Logical or Physical standby DB ?
Thanks in advance.

Never done it, but I don't see any reason why it should not work.
Streams, at capture site, is only a data dictionary game and in a logical standby your data dictionary is open read write.
Streams, at capture site, never touch the source tables, in fact they may even not exists from Streams point of view,
as it deals only with the redo that are generated.
So Streams horizon is limited to the data dictionary, the log buffer, the archives and, in SYSAUX tablespace, all the LOGMNR_% tables. All these structures are read write in the logical standby. However, for the capture/propagation you may have to set to true the 'include_tagged_lcr' parameters.

Forward physical standby archivelog files to a logical standby database

Hi,
We have a production database (1) and we have a physical standby database (2) for it.
Is it possible to forward the archivelogs files from (2) to a logical standby database (3). We want to use the (3) as a UAT - Ad Hoc read only Database.
Thanks.

Hi,
The following Data Guard configurations using cascaded destinations are supported.
A. Primary Database > Physical Standby Database with cascaded destination > Physical Standby Database
B. Primary Database > Physical Standby Database with cascaded destination > Logical Standby Database
A physical standby database can support a maximum of nine (30 as of Version 11.2) remote destinations.
Physical Standby Forwarding Redo to a Logical Standby :
Advantages :
1. Users can connect to Logical Standby database and they can access
2. Instead of querying primary database they can use logical standby database.
3. without any additional overhead on your primary system, and without consuming any additional transatlantic bandwidth.
Disadvantages :
The following data types will not support in Logical standby database just check your application before implementing logical standby
a. BFILE
b. Collections (including VARRAYS and nested tables)
c. Multimedia data types (including Spatial, Image, and Oracle Text)
d. ROWID, UROWID
e. User-defined types
f. LOBs stored as SecureFiles
g. XMLType stored as Object Relational
h. Binary XML
Thanks
LaserSoft

Creating a new schema in a Logical Standby Database

Hi All,
I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_new
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user new
2 identified by new
3 default tablespace ts_new
4 temporary tablespace temp
5 quota unlimited on ts_new
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to new
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to new
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to new
SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
2 /
GRANTEE PRIVILEGE ADM
NEW CREATE ANY TABLE NO
NEW CREATE TABLE NO
NEW UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect new/new
Connected.
NEW@UATDR>
NEW@UATDR> -- prove ability to create tables
NEW@UATDR> create table new
2 (col1 number not null)
3 tablespace ts_new
4 /
create table new
ERROR at line 1:
ORA-01031: insufficient privileges
NEW@UATDR>
NEW@UATDR>

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

Creating triggers in a logical standby database

Does anyone know if its possible to create and enable a trigger in a logical standby database on a 'guarded' table? I've been able to create the trigger (as an after insert trigger) and it appears to be valid but it never seems to fire, despite inserts taking place. Are there any other steps involved to activate this, or is it just plain not possible in a logical standby? My primary and logical standby databases are 10.2.0.3

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

Physical standby and logical standby

Hi,
Why we mention standby_archive_dest and log_archive_Dest in standby init.ora.
bcz there is no activity at physical standby.so why we set two parameters?
what is difference between physical stand by and logical standby?

Hi,
A logical standby database contains the same logical information as the production database, although the physical organization and structure of the data can be different. The SQL apply technology keeps the logical standby database synchronized with the primary database by transforming redo data received from the primary database into SQL statements and then executing the SQL statements on the standby database. This makes it possible for the logical standby database to be open read-write and accessed for queries and reporting purposes at the same time the SQL is being applied to it.
Logical vs Physical Standby database
http://www.orafaq.com/node/957
Regards,
Tom
Edited by: Soli on 19.8.2009 13:48

What are advantage and disadvantage for Physical Standy and Logical Standby

HI,
What are advantage and disadvantage for Physical Standy and Logical Standby configuration?
Thanks
Ken

Logical standby database
The key advantage for logical standby databases is that they're opened read/write, even while they're in
applied mode. That is, they can be used to generate reports and the like. It is indeed a fully functional
database. Also, additional indexes, materialized views and so on can be created.
However (this being a disadvantage) not all datatypes are supported.
Oracle (or more exactly the log apply services) uses the primary database's redo log, transforms them into
SQL statements and replays them on the logical standby database.
Physical standby database
A physical standby database is a byte for byte exact copy of the primary database. This also means that
rowids stay the same in a physical standby database environment.
Oracle (or more exactly the log apply services) uses the primary database's redo log to recover the
physical database.
A physical standby database might be opened read only; however, the received logs are in this case not
applied. When the logs are applied, the database is not accessible (it is then in a managed recovery state).
Regards,

CPU patch procedure with physical and logical standby database in place

Similar Messages

Maybe you are looking for