Logical Standby to Physical Standby

Hi Group,
Please clarify. Is it possible to return from a Logical Standby to Physical standby without copying the datafiles from Primary enviroment again?.
If yes, how?
Thanks a lot.
Oracle 10.2.0.4
SO: AIX 6.1
We also have all archives generated by primary database on disks

user12215372 wrote:
Hi Group,
Please clarify. Is it possible to return from a Logical Standby to Physical standby without copying the datafiles from Primary enviroment again?.
If yes, how?
Thanks a lot.
Oracle 10.2.0.4
SO: AIX 6.1
We also have all archives generated by primary database on disksAFAIK, it is not possible, you have to create a fresh physical standby database.

Similar Messages

Creation of logical standby by shipping the redologs from physical standby

Hi all,
I have to create a logical standby database using redo shipping from my PHYSICAL STANDBY while it is in mounted state .Is it really possible to do it??
Please send me any docs regarding this to my mail id ([email protected])
Thanx in advance

It is possible to do what you ask by using cascaded destinations. See the Data Guard Manual (online at OTN) http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/cascade_appx.htm#i636046
for the information. This relies on the standby creating and re-transmitting redo log data.
Hope this helps

Logical standby database to physical standby database

I already start my logical standby database and I want to return it again to physical standby database. So what should I do?

>
The "may be" is because I have tested flashback of a physical standby to before resetlogs, but not a logical standby.
>
A physical standby keeps the DBID of the primary - a logical standby does not. That is exactly the problem that restricts the reconversion into physical from logical, and you did not encounter that problem.
>
I haven't used "keep identity" but from what I read it relates to "convert to physical" not "flashback database".
>
Exactly. And that is what the OP wants to do: convert to physical (from logical).
You mentioned that this might be possible with flashback.
Problem: During the conversion from physical to logical, the DBID gets changed unless you specify (in 11g) KEEP IDENTITY. This would make it possible to reconvert into phyiscal from logical.
In short: If there is no solution for the changed DBID of the logical standby in order to flashback it into physical as you suggested, then it is not possible .
When I saw your first answer, I thought that you might have a solution in mind in order to solve that obvious problem. Sorry for having bothered you.
Kind regards
Uwe
http://uhesse.wordpress.com

Local logical standby and remote physical standby

Dear All,
My database version is 10.2.0.1.0(production) and Operating System Linux x86-64 OS Version Red Hat Enterprise 4
Below is my configuration details:
Rprimary Database:Two Nodes RAC
StandBy Database LOCAL:Standalone database
Standby Database Remote:Two Node RAC
So,my question is, i want my local physical DR to convert into logical standby and
Remote DR will operate as physical standby as it IS.
sql>EXECUTE DBMS_LOGSTDBY.BUILD
After executing the above statement in my production primary database will there be any performance HIT.
And another important is that my above statement shouldn't affect my remote physical DR database.
Just the local DR should get converted into logical standby database
Thanks and Regards
Monoj Das

monoj wrote:
Dear All,
My database version is 10.2.0.1.0(production) and Operating System Linux x86-64 OS Version Red Hat Enterprise 4
Below is my configuration details:
Rprimary Database:Two Nodes RAC
StandBy Database LOCAL:Standalone database
Standby Database Remote:Two Node RAC
So,my question is, i want my local physical DR to convert into logical standby and
Remote DR will operate as physical standby as it IS.
sql>EXECUTE DBMS_LOGSTDBY.BUILD
After executing the above statement in my production primary database will there be any performance HIT.
And another important is that my above statement shouldn't affect my remote physical DR database.
Just the local DR should get converted into logical standby database
Thanks and Regards
Monoj DasIn any Data Guard environment, you can have either physical or logical or even mixed[physical + logical]
There will be no performance issue if you run the package for logical standby DBMS_LOGSTDBY.BUILD , This package provides you to manage even logical standby database.

Configuration of the Physical & Logical standby servers on the same machine

I've encoutered a problem to connect to one of the standby servers .
I created a DataGuard in 10.2. Primary on 1 machine, 1 physical standby and 1 logical standby on another machine (both phy and logical in same machine)
I first created a primary then a physical standby. I've got no problem at all.
But when I created a logical standby server on the same machine with the physical then I could not connect to both phy and logical . I can connect to either one of them.
According to DataGuard setup, the db_name must be the same in primary and all standby servers. This is fine when each of the primary or the standby installed in a separate machine.
The db_name of the physical = rolex
The db_name of the logical = rolex
When we have more than one instance in the same machine, we just set the ORACLE_SID = db_name ( or instance), then connect to it.
If I connect to the physical, then I try to connect to the logical, it goes to the physical or vice versus.
Does anyone have the solution ?
QN

DB_UNIQUE_NAME parameter will be the seperator.
give DB_UNIQUE_NAME parameters different names and set ORACLE_SID with DB_UNIQUE_NAME name you gave
DB_NAME is the primary instances database name DB_UNIQUE_NAME is given for standby instances database name

How to Create Primary DB and Physical/Logical Standby DB on the same host?

Now I encounter a issue. I want to create one Primary DB and one Physical standby DB and one Logical standby DB on the same host.
Create this env on the same host aims to test whether we can using EM Patching DP to apply patches on Primary/Physical/Logical DB successfully.
I try to setup this env but fails. I want to know more related issues about create Primary DB /Physical DB/Logical DB on the same host and how to configure between them.
Below steps is my try:
1. Create Primary DB on the /scratch/primary_db
2. Create Physical Db software only on the /scratch/physical_db
3. Create Logical Db software only on the /scratch/logical_db
4. Using EM Wizard to create physical standby database and logical standby database, and these two targets can show up on the "All Targets" Page.
5. But when using EM Patching DP, it fails and the reason is the listener of physical and logical db cannot configured well.
Issues:
So I want to know about how to configure physical db and logical db's listener using EM or manually?
If the listener name of Primary Db is LISTENER and the port is 1521,and the listener.ora is under the /scratch/primary_db/network/admin directory, then how to config physical db and logical db's listener's name and port?

Hi,
As this a test case then you need to create two more listener for each Oracle Home (/scratch/physical_db & /scratch/logical_db) make sure that they have different names and ports.
Then add the new listeners manually using GC?
Try it and let me know
Regards
Amin

Is that possible to convert logical standby to physical standby ?

Hi guys,
My steps for testing as below:
1.create a primary database
2.duplicate a physical standby database;
3.turn on flashback on both databases.
4.record SCN xxx on physical standby database.
5.convert physical standby to logical standby (using keep identity statement)
6.flashback to logical standby to xxx
7.convert logical standby to physical standby
8.using real time apply
I got errors:
Fast Parallel Media Recovery enabled
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery waiting for new incarnation during transient logical upgrade procedure
Errors in file /home/ora/app/oracle/diag/rdbms/ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:
ORA-19906: recovery target incarnation changed during recovery
Managed Standby Recovery not using Real Time Apply
Errors in file /home/ora/app/oracle/diag/rdbms/ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:
ORA-19906: recovery target incarnation changed during recovery
Errors appears every 10 seconds. Seems MPR0 is waiting for new incarnation for a long time. So am I.
Standby database incarnation:
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
1 1 ORA11GR1 3853851354 CURRENT 1 08/09/2013 01:02:18
2 2 ORA11GR1 3853851354 ORPHAN 2127877 08/28/2013 19:22:01 BGV

Hello;
Because of limitations for specific data types and objects with a logical database I going to say no.
Best Regards
mseberg

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.

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.

Status of Logical Standby In case of Failover to Physical Standby

I am using oracle 9.2.0.8 database . I have one logical and one physical standby database in place. If I perform failover to my physical standby, will my logical standby still continue to work with new primary database?

Thank you for your kind reply.
I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
ERROR at line 1:
ORA-01287: file is from a different database incarnation

Creation of logical standby in 9i from physical standby

Hi all,
I want to create logical standby from physical standby in 9i. can anyone send a doc for this

As per the Oracle documents "You create a logical standby database by first creating a physical standby database and then transitioning it to a logical standby database"
Please take a look at the below URL.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm
Regards,
Sabdar Syed.

Physical Standby database Vs. Logical Standby database

I have few questions regarding capability of Logical Standby Database against Physical Standby database.
1. How efficient is Logical Standby database in terms of Physical Standby Database?? How both differ from each other and can I use Logical Standby Database for disaster Recovery?? Can It be use for recovering the failed Primary Instance?? If yes how efficient and reliable it is??
2. What are the known bugs and roadblocks for logical standby database on Oracle 10.2.0.1 on Soalris X86-64?
3.As logical standby database not going to replicate each and every schema of Primary database?? how is the change management effects to the logical standby from primary?? I mean there are some parameters and job that we create on primary how can it be transferred over to the logical standby??

1. How efficient is Logical Standby database in terms
of Physical Standby Database?? How both differ from
each other and can I use Logical Standby Database for
disaster Recovery?? Can It be use for recovering the
failed Primary Instance?? If yes how efficient and
reliable it is??I'm not sure what sort of "efficiency" you're talking about here...
Physical standby is just the old, tried and true application of archived logs to recover a database. Very solid, very old school.
Logical standby, on the other hand, is parsing the redo log, extracting logical change records, and applying them to the standby database. This obviously takes a bit more processing effort, it's newer technology, it doesn't have quite the level of support that physical standby does (i.e. certain data types are excluded), etc. You certainly can use it for failover, but it isn't quite as robust as a physical standby. Of course, this is getting better and better all the time and is definitely a focus of Oracle's development efforts.
On the other hand, logical standby systems can do things other than act as a warm standby. They can be open serving reports, for example. You can create additional structures (i.e. new materialized views) to support reporting. A physical standby is pretty much always going to be in managed recovery mode, so it cannot be queried.
2. What are the known bugs and roadblocks for logical
standby database on Oracle 10.2.0.1 on Soalris
X86-64?a) You'll want to do a Metalink search
b) If you're talking about a high-availability solution, why are you looking at a base release of the database? Why wouldn't you apply the latest patchset?
3.As logical standby database not going to replicate
each and every schema of Primary database?? how is
the change management effects to the logical standby
from primary?? I mean there are some parameters and
job that we create on primary how can it be
transferred over to the logical standby??I'm not sure I understand... Changes made to the primary generate redo. Oracle parses that redo, generates a LCR, and sends that to the standby database where that change record gets applied.
Justin

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.

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.

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

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.

Logical Standby to Physical Standby

Similar Messages

Maybe you are looking for