How to convert a Logical Standby DB to a Primary

Hi,
I have an issue with our Data Guarded cluster (two nodes, one Primary and one Logical Standby Oracle 10i DBs running on HP-UX 11.23)
The issue is that for some reasons the Primary and the Standby are out of sync in terms of archive log sequences.
For instance the primary shows:
Date: Feb-27-2009 14:02:33
ID DESTINATION STATUS ARCHIVED_THREAD# ARCHIVED_SEQ#
1 /db05/oradata/NSMS/archive/ VALID 1 864
2 stdby VALID 1 10
3 /db05/oradata/NSMS/archive/DR/ VALID 1 11
11 /db05/oradata/NSMS/archive/DR/ VALID 1 864
Report on Redo Log Gaps between Primary and Standby.
Date : Feb-27-2009 14:02:33
LAST_SEQ_RECD LAST_SEQ_SENT
863 864
But the STANDBY shows in the alert log:
LOGMINER: Begin mining logfile: /db05/oradata/NSMS/archive/DR/arch673877647_1_304.log
Fri Feb 27 12:51:36 2009
LOGMINER: End mining logfile: /db05/oradata/NSMS/archive/DR/arch673877647_1_304.log
Fri Feb 27 12:51:36 2009
LOGMINER: Begin mining logfile: /db05/oradata/NSMS/archive/DR/arch673877647_1_305.log
Fri Feb 27 12:51:39 2009
LOGMINER: End mining logfile: /db05/oradata/NSMS/archive/DR/arch673877647_1_305.log
since the DBA_LOGSTDBY_LOG contains on the STANDBY:
$ is_db_apply_current.sh
1 300 595040838 595042886 YES
1 301 595042886 595042919 YES
1 302 595042919 595096418 CURRENT
1 303 595096418 595127201 CURRENT
1 304 595127201 595159342 CURRENT
1 305 595159342 595207457 CURRENT
At this point I don't know how to cleanup the situation on the Standby.
I tried to resync completely form primary copying all datafiles and archives but still cannot reset the archive sequence on the STANDBY, so that it keeps looking for the wrong archives.
Thanks in advance !
Mike

Hi
Problem seems different then post heading."How to convert a logical standby to primary" stepts are follow.
On primary site.
1.On primary site "alter database prepare to switchover to logical standby".
2.On standby site "alter database prepare to switchover to parimary;
3.Check "select switchover_status from v$database to both sites.
4.At primary site When status becomes to_standby then "alter database commit to switchover to logical stanedby".
5.At stndby site "alter database commit to switchover to parimary".
6.After successfully switchover at new logical standby site "alter database stard logical standby apply".
For you problem ,Can you paste following from standby site.
1.select applied_sequence#,last_sequence# V$logstdby_progress.
2.select * from V$logstdby_stats
3.select * from v$archived_log
Also from primary site,
1.select * from v$log.
hope this will help U.
Tinku
Edited by: Tinku on Feb 27, 2009 8:39 PM

Similar Messages

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.

How to convert from Logic 7.2 to older Logic on PC

I met a producer who wants to work his magic on a track of mine. He uses an older Logic on a PC. I assume I'll give him all my tracks as audio files (Wave?), but it would be nice to keep the MIDI regions as well. Any suggestions for the best process for this?
Thanks in advance!
George

Export a MIDI file containg the tempo, and any MIDI regions, together with the audio files exported track by track starting from 1 1 1 1, together with some docs to tell the guy what's included and what goes where etc.

Logical standby not synced with primary!

Dear All,
I am in a new environment. Oracle 10g database is running on windows 2003 server. This is the primary database and there is a logical database 10gR2 also on windows.
Since yesterday all SCN were applied on standby and it was 100% synced with production.
Just not I have seen quering this view "SELECT APPLIED_SCN, NEWEST_SCN, NEWEST_SCN-APPLIED_SCN LAG, READ_SCN, APPLIED_TIME FROM DBA_LOGSTDBY_PROGRESS;
That the last update was on 9/30/2013 7:56
This is a new environment for me, where should i start troubleshooting from?
Kindly help
Regards

Hi, This is what I have found in alert log file
LOGSTDBY stmt: ALTER USER KAMRAN IDENTIFIED BY VALUES '***************'
LOGSTDBY status: ORA-28007: the password cannot be reused
LOGSTDBY id: XID 0x0009.014.0016c1e2, hSCN 0x0000.7bfb3c98, lSCN 0x0000.7bfb3c98, Thread 1, RBA 0x53a56.0000023d.144, txnCscn 0x0000.7bfb3c9c, PID 320, ORACLE.EXE (P004)
LOGSTDBY Apply process P004 pid=21 OS id=320 stopped
Mon Sep 30 07:57:04 2013
Errors in file c:\oracle\ora10gr2\admin\logstby\bdump\logstby_lsp0_2532.trc:
ORA-12801: error signaled in parallel query server P004
ORA-28007: the password cannot be reused
LOGSTDBY Analyzer process P003 pid=26 OS id=2704 stopped
LOGSTDBY Apply process P007 pid=30 OS id=2412 stopped
LOGSTDBY Apply process P008 pid=31 OS id=2656 stopped
LOGSTDBY Apply process P006 pid=29 OS id=2676 stopped
LOGSTDBY Apply process P005 pid=28 OS id=2688 stopped
Mon Sep 30 08:00:39 2013""
Since this command was issued on standby the sync process is stoped.
When i query :
SEQUENCE#, FIRST_TIME, APPLIED FROM DBA_LOGSTDBY_LOG ORDER BY SEQUENCE#; I get
Row# SEQUENCE# FIRST_TIME APPLIED
33 342614 9/30/2013 7:56:11 AM CURRENT
34 342615 9/30/2013 8:00:39 AM NO
Please help

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.

How to run automated maintenance task on a logical standby database ?

Hi
I realize that i do not see any job runs for automated maintenance tasks on my logical standby database.
Which are the conditions that must be fulfilled for automated maintenance tasks to run?
Thanks
Christoph

Hi,
In an Oracle Data Guard environment, the Scheduler includes additional support for two database roles: primary and logical standby. You can configure a job to run only when the database is in the primary role or only when the database is in the logical standby role. To do so, you set the database_role attribute. This example explains how to enable a job to run in both database roles. The method used is to create two copies of the job and assign a different database_role attribute to each.
By default, a job runs when the database is in the role that it was in when the job was created. You can run the same job in both roles using the following steps:
Copy the job
Enable the new job
Change the database_role attribute of the new job to the required role
The example starts by creating a job called primary_job on the primary database. It then makes a copy of this job and sets its database_role attribute to 'LOGICAL STANDBY'. If the primary database then becomes a logical standby, the job continues to run according to its schedule.
More Information please cheek below link:
Examples of Using the Scheduler
Thank you

ORA-01403 - Logical Standby Apply ends on delete/update statement

- This thread is relocated to this forum; advice from Daniel Roy -
After implementing 2 logical standby databases and running pretty smooth for a while 'strange' errors occur which puzzle me. Sometimes I skip a transaction or exclude a schema from replication and hold my breath for what next roars its ugly head.
Despite fulfilling all logical standby prerequisites and maintaining primary keys on tables I now run into ORA-01403 errors. The updated table only contains 1 row and has a foreign key to another small table.
I could instantiate these tables, but I want to understand why these errors occur and prevent them form happing or learn how to resolve them best.
Anyone around who dealt with these matters and won?
I'm running this implementation with Oracle 9.2.0.7 on Tru64 51.b
I'm able to create the logical standby databases manually and with aid of the Data Guard Creation Wizard (EM10g 10.1).
Can anyone also help me out with refining the faulty transaction from e.g. V$LOGMNR_CONTENTS? (Without disrupting the data guard setup).
I've already retrieved redo info from archivelogs, but there must be an easy way.
Regards,
Erik

Any way for you to turn tracing on for the DB where you see this ORA-01403 error? We could then probably find out exactly what goes wrong. It's very hard for us to know exactly what might be wrong, since we don't know your exact setup (except for this table). Let me know if that's not possible, and I could construct a logical DB setup to test (even tho it would be on Windows, I don't have Tru64).
Daniel

Logical Standby recover with RMAN

Hi All,
I have a test environment with Primary DB Server, Physical Standby and Logical Standby.
The Logical Standby DB (cur_log_stdb) is backed up every evening by RMAN and I have a question:
If I recover my Logical Standby DB from backup and switch replication to new Logical Standby DB (new_log_stdb) it will work or not?
My steps e.g.:
1. Make a new server for my new_log_stdb and repair structure of catalogs;
2. Repair listener.ora and tnsnames.ora files from cur_log_stdb to new_log_stdb;
3. Restore DB with RMAN from backup to new_log_stdb;
4. On cur_log_stdb execute "alter database stop logical standby apply";
5. Change a DNS name from cur_log_stdb to new_log_stdb;
6. On new_log_stdb execute "alter database start logical standby apply immediate";
I'm not sure that archivelogs will apply to the new_log_stdb for period since rman backup was created.
But if this plan won't work how can I restore Logical Standby DB from RMAN backup and resume replication from Primary?
Configuration:
Oracle Linux 6.4
Oracle Database 11.2.0.3
Primary and Physical with Data Guard

Hello;
The only way to know for sure is to test it. You are asking somebody you don't know to confirm a recovery test for you. You have to perform the test yourself to be certain.
If your plan does not work you can always rebuild the Standby.
Best Regards
mseberg

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.

SQL apply is very slow on Logical Standby..!!

Hello all,
We are having Data Guard setup in our environment where we are having Primary, Physical Standby as well as logical standby databases..
DB Version : 10.2.0.1 in all databases (Pri, Phy and Logical)
OS : RHEL4
Only Oracle is running on this Box..
Since last month we are facing problems in Logical Standby database where it seems SQL apply has become very slow..
Archive log files are successfully transferring from Primary but since SQL apply has become slow logical standby is lagging behind primary by two days..
How do i speed up this SQL apply..?? Any ideas and suggestions are most welcome..
I checked TOP command to find out which oracle processes are consuming maximum CPU and i have found ora_p000_oracle, ora_p001_oracle, ora_p002_oracle, ora_p003_oracle, ora_p004_oracle, ora_p005_oracle, etc processes are consuming highest CPU and Load Average has always been above 1..
Any help would be greatly appreciated..
Thanks - HP

Hello;
These Oracle notes might help :
Slow Performance In Logical Standby Database Due To Lots Of Activity On Sys.Aud$ [ID 862173.1]
Oracle10g Data Guard SQL Apply Troubleshooting [ID 312434.1]
Developer and DBA Tips to Optimize SQL Apply [ID 603361.1]
Best Regards
mseberg

Logical standby process

Hi,
how can configure the logical standby process to start automatically after i restart database?
thanks

What do you consider the "logical standby process"? The process that copies log files from the primary to the standby? Or the process that applies the log files to the standby database?
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

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?

Logical standby Slow after starting auditing

Hi:
I have logical standby, which was keeping with the primary database, then we started auditing on the primary database(Database auditing.) , After starting auditing my Logical standby not keeping with primary, after doing reasearch we found out that there are so many sql statement from sys schema on AUD$ table, and they are doing full tablescan on it, which is of 3GB as off now. Also This table is own by sys and by default all sys objects should be excluded from logical standby apply. But this is not, when I tryed to skip it by my self, then apply process gives ora-600 and stops.
I think it is a bug or what ???
Any help on this will be appriciated.
Regards
Bhushan

Hi Guys:
After taking my time we decided to truncate the sys.AUD$ on the LOGICAL STANDBY and that solved our problem.Now LS is catching up fast as I can see the progree is verry fast.
Still if anybody from "ORACLE CORP" is reading this thread they should give us the reason why the sys.aud$ table is beging replicated on the LOGICAL STANDBY site. is this a BUG in oracle?
Regards
Bhushan

Logical standby DB with unsupported datatype

Hello,
Has anyone setup the following Data Guard Configuration, although it is not recommended by Oracle:-
Setup a logical standby DB from a Primary DB with unsupported Data Types. I'm need (and want) to save time and effort to configure a database for the purpose of Reporting and avoid Oracle Streams or Change Data Capture or even the new middleware Product Data Integrator
Data is sent from the Productive DB, and with logical standby DB, I (hope) can still get it to run even with unsupported data types using DBMS_LOGSTDBY.SKIP procedure, to skip unwanted and unsupported attributes in the primary DB.
I would appreciate any comments and experience using Logical Standby DB for Reporting Purposes.
regards
Sahba

Hello Anantha,
thanks for your reply.
unfortunately the Productive database uses dartatypes such as DMSYS.SDO_GEOMERTY.
these datatypes are not supported by the Logical standby DB.
I thought, i could skip those tables with such datatypes when applying redodata in the logical standby db, dbms_logstdby.skip procedure allow such mechanism.
the reason why i need logical stndby db ist due to READ/WRITE during apply process. as I mentioned, i need an up-to-date replica of the productive db for reporting purposes, without such tables with unsupported datatpes. because these are tables are not part of the reporting procedure, i thought of skipping them from appling in logical stndby db .
so, has anyone have had any complications with Logical stndby db even when using dbms_logstdby.skip procedure?
are there any other problems encountered with logical stndby db to share here?
thanks
regards
Sahba

Stop/start logical standby db

Version 10203 on AIX
Have to stop/start logical standby db, new to data guard, Please confirm these are the steps to do that
on primary db
SQL > alter system switch logfile ;
SQL > alter system archive log current ; ( to make sure current transactions come thru)
check tail of alert log of standby to make sure these redologs shipped & mined
standby db
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY; (stop SQL Apply)
SQL> shutdown immediate;
Lsnrctl stop listener_corp_remrpt-haprimary db
SQL > shutdown immediate ;
Lsnrctl stop listener_corp_remprd-ha
Dont shutdown abort for any case, if both dbs are going down, first stop SQL apply on standby, take primary down and then take standby down)
Startup
primary
SQL>startup;
Lsnrctl start listener_corp_remprd-ha
Standby
SQL > startup
SQL > alter database start logical standby apply immediate ;
Lsnrctl start listener_corp_remrpt-ha

Hi
As you posted ,you are using Real Time Sql apply,So,it is LGWR who transfer changes to standby site.It is very safe to follow these steps for new user.
1.Stop logical standby apply(Standby Database).
2.Shutdown Primary Database.
3.Shutdown logical standby Database.
At startup
1.Start Logical Standby Database.
2.Start Primary Database.
3.Start logical standby apply.
At the case when primary database is taking long time to shutdown processed ,You can also use
shutdown abort,but before doing abort be sure you have stop logical standby apply.When your primary database started,it automatically perform instance recovery.Primary site have to resolve gap in this case.
At the case when you must have to perform shutdown abort at primary database,you can do it.By doing it you will not loose anything.Primary database has to resolve gap and it will take time to be consistent with primary site.
Tinku

How to convert a Logical Standby DB to a Primary

Similar Messages

Maybe you are looking for