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

Similar Messages

Can i convert logical standby database to physical standby database

Dear All,
Can i convert a logical standby database to physical standby database?
If yes, what are the steps to follow?
Thanks
Mahipal

I never needed or tested something like this, but below maybe usefull -
Transient Logical Standby
Users can convert a physical standby to a transient logical standby database to effect a rolling database upgrade, and then revert the standby to its original state as a physical standby database once the upgrade is complete - using the KEEP IDENTITY clause. This benefits physical standby users who wish to execute a rolling database upgrade without investing in redundant storage otherwise needed to create a logical standby database.
http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardOverview.html
But opposite is documented - http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm#BEIGJCAC
best regards.

Cascading physical standby from another physical standby for primary rac

my supplier told me that is possible mount a cascade physical standby from a physical standby for my rac installation.
but according the note "409013.1" seems not:
"Cascading a logical or physical standby database from a physical standby database is supported as long as the primary database is not a RAC database and is not part of a Data Guard Broker configuration - the support status of this configuration is unchanged from previous documentation."
before was possible? do you know why not now?
has anyone mounted? can I allow my provider to mount?
oracle version: 10.2.0.2.0

Is it possible this scenario?YES

How to convert logical standby database to Physical Standby Database

Hi,
Does anyone know how to convert logical standby database(10.2.0.3) to Physical Standby Database(10.2.0.3)? Is this possible? If so,please give me steps for it.
Thanks.
Regards,
RJ.

I don't believe this to be possible. One of the steps invloved in the creation of a logical standby is the following:
ALTER DATABASE OPEN RESETLOGS;
This makes the logical standby a different incarnation of the db from the primary.
A physical standby is a binary copy of a primary db, a logical standby is a completely seperate db that just happens to get sql statements applied to it that are generated from a primary db, but is open read/write.
One avenue, though would be if you had flashback database enabled and you flashed back all the way to when the db was a physical standby and then rolled forward with the archived redo logs.
It's somewhat unlikely you are in that situation, but that is a possibility.
Indeed the 11g snapshot standby does this sort of thing:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#sthref740
jason.
http://jarneil.wordpress.com

Restore primary database using physical standby

hi,
i am taking rman backup on production database,we have physical standby.coming month i have to take backup from standby instead of prod db.pls advise me, is it possible to restore and recover production database using standby database backup.if production crashed.pls advise me .i am new to dba.if possible pls provide proper steps.
Regards
Faruk

Faruk.m wrote:
hi,
i have to take backup on standby instead of production.failover i can do.but i need to know the recovery procedures from standby.and thank u for reply.i want, is it possible to restore my production controlfile with controlfile backup from standby.
i tested with my local database ,that below:
1.backup with controlfile from standby (rman>backup current controlfile)
2.manual deleted my test db controlfile,tried to restore from backup taken from standby(rman>restore controlfile from '*****************';)
3.rman>restore database
3.but it shows error (datafile already exists) ,controlfile tried to create datafiles on standby location.
my conclusion:above my cmds used to create datafiles on standby becoz i restored with standby controlfile.
my question:what is wrong with my steps? and how to restore my (prod) controlfile from standby.and bring backup my prod db.
regards
farukHi Faruk,
Sorry my late.
I can share with you my test.
It is my standby database, I connecting with RMAN
SQL> select database_role, db_unique_name, name from v$database;
DATABASE_ROLE      DB_UNIQUE_NAME           NAME
PHYSICAL STANDBY       stldb                    ADMDB
[oracle@oel62-x64 oradata]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Apr 23 12:23:00 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (DBID=4063877183, not open)
RMAN> backup current controlfile;
Starting backup at 23-APR-13
Starting implicit crosscheck backup at 23-APR-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=29 device type=DISK
Finished implicit crosscheck backup at 23-APR-13
Starting implicit crosscheck copy at 23-APR-13
using channel ORA_DISK_1
Finished implicit crosscheck copy at 23-APR-13
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 23-APR-13
channel ORA_DISK_1: finished piece 1 at 23-APR-13
piece handle=/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_04_23/o1_mf_ncnnf_TAG20130423T122310_8qdfq19x_.bkp tag=TAG20130423T122310 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 23-APR-13
RMAN> exit
Recovery Manager complete.
[oracle@oel62-x64 oradata]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Apr 23 12:23:26 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> shut immediate;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount;
ORACLE instance started.
Total System Global Area 551165952 bytes
Fixed Size              2230232 bytes
Variable Size            167774248 bytes
Database Buffers       377487360 bytes
Redo Buffers              3674112 bytes
SQL>
SQL>
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@oel62-x64 oradata]$ rman target /
Recovery Manager: Release 11.2.0.3.0 - Production on Tue Apr 23 12:34:58 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: ADMDB (not mounted)
RMAN> restore controlfile from '/u01/app/oracle/fast_recovery_area/stldb/STLDB/backupset/2013_04_23/o1_mf_ncnnf_TAG20130423T122310_8qdfq19x_.bkp';
Starting restore at 23-APR-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oracle/oradata/stldb/control01.ctl
Finished restore at 23-APR-13
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN> exit
Recovery Manager complete.
[oracle@oel62-x64 oradata]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Apr 23 12:35:31 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select database_role, db_unique_name, name from v$database;
DATABASE_ROLE      DB_UNIQUE_NAME           NAME
PRIMARY       stldb                    ADMDB
As show here, you can backup standby control file, and restore as primary .
Regars
Mahir M. Quluzade
http://www.mahir-quluzade.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.

Create logical standby from existing physical standby on 9i

I have physical standby database 9i running.
I want to try to convert the physical standby to logical standby. i follow the step by step in metalink document no. 748595.1
But I cannot do the 6th step:
6. Issue command to switch physical standby to logical standby after changing db_name in pfile to logical standby name. Shutdown the standby database if mounted and mount the database again. In this configuration, logical standby database name is LGSTDBY.
sql>alter database recover to logical standby LGSTDBY;
alter database recover to logical standby LGSTDBY;
Error at line 1:
ORA-00905: missing keyword
I have tried to create pfile from spfile on stanby and change the db_name to lgstdby.
I started nomount using pfile. I still cannot run the command.
I tried to mount the standby database but error occured:
ORA-01103: database name 'PRIMARY' in controlfile is not 'LGSTDBY'
The document in metalink is for 10.2.0.4
Is it possible to do it at 9i??
Thx for the help...

FEDORA 6 & ORACLE 10.2.0
alert_stb.log:
alter database start logical standby apply
Wed Jun 17 22:46:58 2009
ALTER DATABASE START LOGICAL STANDBY APPLY (stb)
Wed Jun 17 22:46:58 2009
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=22, OS id=4156
Wed Jun 17 22:46:59 2009
Completed: alter database start logical standby apply
Wed Jun 17 22:47:01 2009
LOGSTDBY status: ORA-16111: log mining and apply setting up
Wed Jun 17 22:47:01 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, reader process P000 started with pid=23 OS id=4158
LOGMINER: session# = 1, builder process P001 started with pid=24 OS id=4160
LOGMINER: session# = 1, preparer process P002 started with pid=25 OS id=4162
Wed Jun 17 22:47:02 2009
LOGMINER: Begin mining logfile: /u01/app/oracle/flash_recovery_area/STB/archivelog_3/1_3_689731882.arc
Wed Jun 17 22:47:02 2009
LOGMINER: Turning ON Log Auto Delete
Wed Jun 17 22:47:02 2009
LOGMINER: End mining logfile: /u01/app/oracle/flash_recovery_area/STB/archivelog_3/1_3_689731882.arc
LOGSTDBY Analyzer process P003 started with pid=26 OS id=4164
LOGSTDBY Apply process P008 started with pid=31 OS id=4174
LOGSTDBY Apply process P007 started with pid=30 OS id=4172
LOGSTDBY Apply process P004 started with pid=27 OS id=4166
LOGSTDBY Apply process P006 started with pid=29 OS id=4170
LOGSTDBY Apply process P005 started with pid=28 OS id=4168

Can you convert a Logical standby to a Physical Standby?

Is it possible to convert a Logical Standby database back to a Physical Standby database? The reason I am asking is that I would like to convert my Physical Standby database to a Logical Standby database, do a rolling upgrade from 10.2.0.1 to 10.2.0.2 then convert the standby back to a Physical. Does anyone know if this is possible?

I would consider logging a TAR with Oracle support for suggestions.
Here's mine:
Install 10.2.0.2 into new, separate Oracle homes(10.2.0.1 & 10.2.0.2 patch & CPU2006Apr & 4516865 patch) on Prime and SB Nodes.
Create a New 10.2.0.2 database.
Then transport the tablespaces from Old Primary to New Primary.(short downtime)
Drop current DR Configuration.
Stop and Drop the 10.2.0.1 databases, then rename the 10.2.0.2 to same SID as old one (short downtime) .
Search for and follow the "create standby with minimal downtime" document from metalink.(use "minimal" as search string).
Your Total downtime should now only be a few minutes.
Test the whole idea first though, using 'toy' sized databases. (All care, no responsibility etc)
regards, Vin.

Standby redologs on Physical Standby

Hi all,
Oracle 10gR2
I'd already created Standby redolog files @Primary then take rman backup of datafiles,archivelogfiles and control file for restoration standby
do i still need to create standby redolog files @Physical standy (after rman restoration completes)
RMAN> DUPLICATE TARGET DATABASE FOR STANDBY NOFILENAMECHECK;
Kindly suggest.
Regards & thanks to all
Muhammad Shakeel Azeem

Hello;
No.
If you create the SRL on the Primary and then take an RMAN backup for duplicate they will be part of that backup.
Example :
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
}Restore example
run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
}Best Regards
mseberg
Double Check ( To be clear on Oracle 11, but I think it work the same on 10 )
I checked my test Standby which I created using RMAN- The SRL's are there.
But you are 10 so use this to check for them :
select * from v$standby_log;If they are not there and the database is mounted create them as follows :
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 '/u01/app/oracle/oradata/PRIMARY/redo04.log' SIZE 100M;Change path, size, names and groups as needed.
Edited by: mseberg on Mar 24, 2012 8:29 AM
Edited by: mseberg on Mar 24, 2012 8:32 AM

Flashback database and Physical Standby databases

Hi,
We are thinking about the following scenario in our Production Standby databases. We are trying to do this to avoid number database cloning situations.
When we require live data to test data fixes :-
1. Switchover/failover the standby database.
2. opened this database in read write mode.
3. Apply the fix and test.
4. Flashing back the database prior to the SCN which did the switchover/failover.
5. Activate the standby again using a new standby controlfile.
Would you experts please comment on this idea?
Is this is possible? If so, would you please guide through the steps/some documentation.
Thanks in advance

This will not work according to me,
1)U can give previous SCN in rollback and gets the data till that SCN, but it will not become standby unless u make it a standby again manually by creating standy controlfile etc(may be this will be succesfull and limited up to check the data fixes).
2)Iif your first step succesfull then what about the fixes u test by applying patches using opatch and patchsets that cannot be rollbacked using flashback because they are copying new version files and adding some more configuration files to oracle home?.
There are lots of pitfalls and loop holes needed to be checked
Regards
Kaunain

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

RE logical/physical standby database

1. Why logical standby database is SQL apply, and Physical standby database is redo apply? What ‘s the meaning/objective for that? (pls don’t tell me what is SQL/redo apply)
2. As we know, a logical standby database can be used for reporting and querying if primary database is down, why we still need a physical standby database (it can’t do that during recovering process, it just a same copy of primary database)? Why not just go ahead to set up only a perfect logical standby database? (just because logical one can’t accommodate all kinds of data type???)
3. Combined with Real time Apply and maximum protection, we can achieve a zero data loss, but could we achieve a zero downtime? Why or why not?

Go Through Below link
>>>Can you convert a Logical standby to a Physical Standby?

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

Physical standby database to Logical standby

Can I convert a physical standby database to Logical standby,

Go Through Below link
>>>Can you convert a Logical standby to a Physical Standby?

Issue on physical standby database

Hi
I've a problem on standby database.
I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
I get following message in my alert log
WARNING! Recovering data file 88 from a fuzzy file. If not the current file
it might be an online backup taken without entering the begin backup command.
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
how can I fix this now.
We keep physical standby database 2 day behind, and apply logs manually.
Physical standby database is maintained manually.
Could someone help me in getting out of this problem.
Oracle 9.2.0.7
solaris

Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
Note:
If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
Specifying a Time Delay
You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
Canceling a Time Delay
You can cancel a specified delay interval as follows:
For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
For logical standby databases, specify the following SQL statement:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
Section 12.8, "Using a Physical Standby Database with a Time Lag"
Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

Logical standby database to physical standby database

Similar Messages

Maybe you are looking for