Accidentally primary database convert to physical standby

Hi ,
Accidentally the primary database was converted to physical standby .Is there any way where it can be revert back to primary other than using the activate command.
Thanks and Regards,
Hussain

Well although I said "alter database open;" and the same is written into the alert.log, the sequence# again starts with 1 - only the bad word "resetlogs" is no longer mentioned :-)
SQL> select * from v$log;
    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         2          1          5  104857600          1 YES CLEARING_CURRENT
       383710 16-JUN-09
         1          1          4  104857600          1 YES CLEARING
       383708 16-JUN-09
SQL> alter database activate standby database;
alter database activate standby database
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
SQL> recover managed standby database cancel
Media recovery complete.
SQL> alter database activate standby database;
Database altered.
SQL> alter database open;
Database altered.
SQL>  select * from v$log;
    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS
FIRST_CHANGE# FIRST_TIM
         1          1          1  104857600          1 NO  CURRENT
       383714 16-JUN-09
         2          1          0  104857600          1 YES UNUSED
            0But it seems to me as if you have no other option anyway.

Similar Messages

  • Creating physical standby database from another physical standby database

    hi,
    We have one production database and one physical standby of the production. Now we have situation where we need to create one database from either production or from standby. As production is loaded we can not do it using active database option. Now we have the only option to copy the database from standby.
    As of now we open the standby and copy it using rman duplicate database and again we put it back to standby mode.
    Is it possible to create standby database from standby database only?
    Oracle version : 11.1.0.7.0
    I have seen procedure allowing to do the same in version 11.2.0.3. I have tried searching for the difference but didn't find when this feature was introduced.
    Thanks,
    Ketul Patel

    Hello;
    Active duplicate should work when connected to Standby as source Database. However there's a bug 11715084 which is not fixed until version 11.2.0.4.
    If patch 11715084 is available for your version it may work, but all the 11.1.0 are gone so I have no way to test.
    RMAN ACTIVE DUPLICATE WHEN CONNECTED TO STANDBY AS TARGET [ID 1343515.1]
    Understanding ORA-01671 error during controlfile creation / backup [ID 461121.1]
    Best Regards
    mseberg
    Edited by: mseberg on Feb 13, 2013 8:59 AM

  • Is there shutdown of primary database needed when creating standby by Grid?

    I want to create physical standby database
    using EM Grid Control. Is there neccessary during
    the process to shutdown primary database, e.g.
    when creating backup of primary database?
    Thanks for advise,
    M.

    Yes you need to shutdown the database while,
    Backup all database files.
    After changing the entries in pfile you need to start the database through pfile.
    After changing the listener, reload the listener file.

  • Problem with data guard Creating a Physical Standby Database turorial

    There is a tutorial of Creating a data guard Physical Standby Database:
    http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
    I tried to install it on two servers. One for primary database second for physical standby.
    I have error on C. Creating the standby database over the network, action #6:
    "On the standby system, set the ORACLE_SID environment variable to your <physical standby SID> (i.e. orclsby1) and start the instance in NOMOUNT mode with the text initialization parameter file."
    When I try to connect to idle instance there is an error pops up:
    C:\>sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.7.0 - Production on Thu May 21 16:28:10 2009
    Copyright (c) 1982, 2008, Oracle. All rights reserved.
    ERROR:
    ORA-12560: TNS:protocol adapter error
    I'v checked listener and it is runned. There is no service for database because there is no database yet.
    The question is did some one installed data guard configuration using this tutorial? Is there any errors in it? What should I do to finish this installation?

    On Windhose for every instance a service must have been created using the oradim command.
    Oracle tutorials are usually Unix-centric, as Windhose is an odd man out, so they don't discuss that bit.
    'Kindly do the needful' and create the service prior to starting the instance in nomount mode
    Hint: oradim is documented and has a help=y clause.
    IIRC there is an option in database control (in the maintenance part) which automates everything.
    Sybrand Bakker
    Senior Oracle DBA
    Experts: those who do read documentation

  • Stand by database to primary database creation

    Hi
    I want to create Primary (new database) from my standby database by using RMAN. kindly tell me how this is possible.
    Thanks
    Krishna

    Never done it. The document covers it : (assumes failover )
    Data Guard Concepts and Administration E10700-02
    "13.7.1 Converting a Failed Primary into a Physical Standby Using RMAN Backups"
    I know this is not what you asked for however its worth a look too:
    Flashing Back a Failed Primary Database into a Physical Standby Database
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17022/scenarios.htm#i1049997
    Best Regards
    mseberg
    My last failover test if it helps:
    http://www.visi.com/~mseberg/Data_Guard_Failover_Test_using_SQL.pdf
    Edited by: mseberg on Nov 19, 2011 8:57 AM

  • Re-instantiate Primary Database with 10g Release 1

    How do you re-instiate the primary database with 10g Release 1. I am investigating how the failover process works and have successfully failed over to a standby.
    I now want to re-instantiate the Primary... I know in Release 2 there is a DGMGRL command to re-instantiate... but there is no such command in Release 1 as far as I can see.

    See 10.3 Using Flashback Database After a Failover - http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10823/scenarios.htm#1017193 but it requires that you had flashback database enabled BEFORE you failed over. Also, there are a couple of Alerts out there for early versions of 10.1 and this procedure in the event you did a failover where there was data loss. See Note 388516.1 ALERT: Flashing Back a Primary Database into a Physical Standby May Fail and Note 376340.1 ALERT: Reinstating old primary database as a logical standby database after a Data Guard "No Data Loss" Failover for more information.
    The Broker did not have that capability in 10.1 so you have to use the manual method. You will have to remove the failed primary from your Broker configuration first, reinstate it and then add it back in.
    If you did not have flashback database enabled on the Primary before you did the fail over then you must rebuild the old primary as a new standby with a complete new backup from the new primary.
    Larry

  • Issue with physical standby database not in sync with primary

    Hi,
    I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
    SQL> select thread#,max(sequence#) from v$log_history group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 7
    PROCESS STATUS THREAD# SEQUENCE#
    ARCH CONNECTED 0 0
    ARCH CONNECTED 0 0
    RFS OPENING 1 12
    ALERT LOG :
    Tue Mar 20 07:31:32 2012
    alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:32 2012
    Attempt to start background Managed Standby Recovery process (PRIMARY)
    MRP0 started with pid=18, OS id=16370
    Tue Mar 20 07:31:32 2012
    MRP0: Background Managed Standby Recovery process started (PRIMARY)
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 8 processes
    Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
    Tue Mar 20 07:31:39 2012
    Completed: alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:54 2012
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 9677325080303
    Tue Mar 20 07:31:54 2012
    MRP0: Media Recovery Complete (PRIMARY)
    Tue Mar 20 07:31:55 2012
    MRP0: Background Media Recovery process shutdown (PRIMARY)
    Thanks,
    Rakesh

    HI CKPT,
    Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
    SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
    Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
    Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
    Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
    Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
    Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
    36 rows selected.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oracle/STDBY/arch/
    Oldest online log sequence 13
    Next log sequence to archive 0
    Current log sequence 14
    SQL> ho ls -ltra /oracle/STDBY/arch/
    total 3754456
    drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
    -rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
    -rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
    -rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
    -rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
    -rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
    -rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
    -rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
    -rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
    -rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
    -rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
    -rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
    drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
    SQL>

  • 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.

  • 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

  • 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.

  • What happens at backend when we fire alter database commit to switchover to physical standby

         Hi,
    What exactly happens at backend when we fire alter database commit to switchover to physical standby.
    how the transition happens?
    Thanks

    Hi,
    The following will happen at the backend
    1.) Notifies the primary database that a switchover is about to occur
    2.) Disconnect all users from the primary database
    3.) Generate a special redo record that signals the End of Redo (EOR)
    4.) Converts the primary database into a standby database
    5.) Once the standby database applies the final EOR record, guaranteeing that no data loss has been lost, converts the standby database into the primary database.
    The new standby database (old primary) starts to receive the redo records and continues process until we switch back again. It is important to remember that both databases receive the EOR record so both databases know the next redo that will be received.
    Regards,
    Pradeep. V

  • Backing up primary and physical standby

    We have a DG setup with a single instance primary node and a physical standby db. They both use their own FRA's and their own disks. Nothing is shared. Also the datafiles use OMF on both the db's. My questions are
    1. Can i register the primary with the rman catalog and still backup the standby?
    2. Should i backup the archive logs on primary? If so what rman settings should i use on both for the archive logs?
    3. We wanted to back up both the dbs as it will be faster to restore since we wont have to convert filenames (cause of OMF) when we have to resotore backup taken on primary to standby or vice versa.
    Any advise related to this scenario is highly appreciated.
    Thanks.

    Hi All,
    you should have same rman format setting and log_archive_format on primary and standby database >to avoide any confusion at the time of restore. if you have different log_archive_format on standby then >primary, you might have to rename your archivelogs from standby to log_archive_format on primary.It is not required to have same log_archive_format for primary and standby database.
    The database can be restored and recovered successfully even if the format is different.
    Primary database
    ============
    SYS @ oraprim> show parameter log_archive_format
    NAME TYPE VALUE
    log_archive_format string ARC%S_%R.%T
    Standby database
    =============
    SYS @ orastdby> show parameter log_archive_format
    NAME TYPE VALUE
    log_archive_format string ARC_STDBY%S_%R.%T
    Standby database
    =============
    C:\> set ORACLE_SID=orastdby
    C:\>rman target / catalog recat/recat@recat
    RMAN> backup archivelog all delete input;
    channel ORA_DISK_1: starting archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=98 recid=15 stamp=631239054
    input archive log thread=1 sequence=99 recid=16 stamp=631239055
    input archive log thread=1 sequence=100 recid=17 stamp=631239055
    input archive log thread=1 sequence=101 recid=19 stamp=631239111
    input archive log thread=1 sequence=102 recid=18 stamp=631239110
    channel ORA_DISK_1: starting piece 1 at 22-AUG-07
    channel ORA_DISK_1: finished piece 1 at 22-AUG-07
    piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
    tag=TAG20070822T001717 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
    channel ORA_DISK_1: deleting archive log(s)
    archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00098_0630878042.001 recid=15 stamp=631239054
    archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00099_0630878042.001 recid=16 stamp=631239055
    archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00100_0630878042.001 recid=17 stamp=631239055
    archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00101_0630878042.001 recid=19 stamp=631239111
    archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00102_0630878042.001 recid=18 stamp=631239110
    Finished backup at 22-AUG-07
    RMAN>
    Primary Database
    =============
    -- deleted users datafile and did complete recovery
    C:\>set ORACLE_SID=oraprim
    C:\>rman target / catalog recat/recat@recat
    RMAN> run{
    2> startup mount;
    3> restore database;
    4> recover database;
    5> }
    Oracle instance started
    database mounted
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=98
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=99
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=100
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=101
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=102
    channel ORA_DISK_1: reading from backup piece C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP tag=TAG20070822T001717
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
    archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00098_0630878042.001 thread=1 sequence=98
    archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00099_0630878042.001 thread=1 sequence=99
    archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00100_0630878042.001 thread=1 sequence=100
    media recovery complete, elapsed time: 00:00:07
    Finished recover at 22-AUG-07
    RMAN>
    Regards,
    Vaibhav

  • Error while trying to open physical standby database - (DATA GUARD)

    Hi Everyone,
    I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
    Primary Database spec: (2 Node Rac on ASM)
    Oracle Version : 10.2.0.3.0
    O/s : HP-UX B.11.23
    Standby Database spec: (Single Node)
    Oracle Version : 10.2.0.3.0
    O/s: HP-UX db01 B.11.23
    Error:
    alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database open
    2 ;
    alter database open
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+DATA/dprod/datafile/system01.dbf'
    Parameters :
    log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
    FOR=(ONLINELOGFILES,PRIMARY_
    ROLE) DB_UNIQUE_NAME=PROD
    remote_archive_enable string true
    fal_client string DPROD
    fal_server string PROD1, PROD2
    Steps tried so far:
    Changed log_archive_dest_2 = DEFER on both the primary nodes
    Standby :
    startup nomount
    alter database mount standby database;
    alter database recover managed standby database disconnect;
    alter database recover managed standby database cancel;
    alter database open/readonly (tried both)
    Same error.
    On Primary:
    SQL> select max(sequence#) from v$log_history;
    MAX(SEQUENCE#)
    55702
    on Standby:
    MAX(SEQUENCE#)
    33289
    Primary Database:
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    55700 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55702 13-JUN-11 13-JUN-11
    60824 rows selected.
    Standby Database:
    SEQUENCE# FIRST_TIME NEXT_TIME
    55698 13-JUN-11 13-JUN-11
    55699 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    15206 rows selected.
    Additional Information :
    There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
    Any help will be highly appreciated. Thanks in advance
    Sadiq

    Hi,
    Primary Database:
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    STATUS CHECKPOINT_COUNT
    ONLINE 57717
    ONLINE 57717
    57 rows selected.
    Standby Database;
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    STATUS CHECKPOINT_COUNT
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    STATUS CHECKPOINT_COUNT
    ONLINE 30723
    ONLINE 30723
    57 rows selected.
    Archieve log list :
    Primary database:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 49111
    Current log sequence 49111
    Standby Database:
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 0
    Current log sequence 49111
    I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

  • Physical standby database standby redo log problem

    Hello
    We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
    their status in v$stanby_log view is UNASSIGNED
    and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
    while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
    and archive log file will be created in standby database
    I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
    Do you know what is problem ?
    elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
    group#     THREAD#      BYTES       STATUS
    1                   0                   524288000                   UNASSIGNED                  
    2                   0                   524288000                   UNASSIGNED                  
    3                   0                   524288000                   UNASSIGNED                  
    8                   0                   524288000                   UNASSIGNED                  
    9                   0                   524288000                   UNASSIGNED                  
    10                   0                   524288000                   UNASSIGNED                  
    select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
    group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
    4                   1                   524288000                   2                   CLEARING                  
    7                   1                   524288000                   2                   CLEARING_CURRENT                  
    6                   1                   524288000                   2                   CLEARING                  
    5                   1                   524288000                   2                   CLEARING                  
    thanks

    Hello Anurag
    Thank you for your reply
    I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
    RFS[782]: Assigned to RFS process 3919
    RFS[782]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    RFS[782]: No standby redo logfiles selected (reason:6)
    Sun Jan 31 13:59:43 2010
    Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:59:48 2010
    RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
    Sun Jan 31 13:59:50 2010
    and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc"  is below :
    +/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
    System name:    Linux
    Node name:      linserver2.com
    Release:        2.6.9-42.ELsmp
    Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
    Machine:        i686
    Instance name: tehrep
    Redo thread mounted by this instance: 1
    Oracle process number: 58
    Unix process pid: 3919, image: [email protected]
    *** SERVICE NAME:() 2010-01-31 13:59:43.865
    *** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
    KCRRFLAS
    KCRRSNPS
    No space in recovery area for active standby redo logs
    The primary database is operating in MAXIMUM PROTECTION
    or MAXIMUM AVAILABILITY mode, and the standby database
    does not contain adequate disk space in the recovery area
    to safely archive the contents of the standby redo logfiles.
    ORA-16086: standby database does not contain available standby log files
    when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
    by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
    alert_log :
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:30:34 2010
    LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
    Thread 1 advanced to log sequence 6512
    Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
    Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
    LNSc started with pid=53, OS id=11451
    Sun Jan 31 13:36:34 2010
    Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:36:34 2010
    LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
    Thread 1 advanced to log sequence 6513
    Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
    Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
    */u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
    Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
    +)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
    ORA-16086: standby database does not contain available standby log files
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
    +)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
    *** 2010-01-31 13:30:34.712 58941 kcrr.c
    kcrrfail: dest:3 err:16086 force:0 blast:1
    Receiving message from LNSc
    *** 2010-01-31 13:30:34.718 55444 kcrr.c
    Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
    NetServer pid:11196
    *** 2010-01-31 13:30:38.718 55616 kcrr.c
    upidhs done status 0
    *** 2010-01-31 13:36:31.062
    LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
    *** 2010-01-31 13:36:31.062 53681 kcrr.c
    +Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
    NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
    LNSc is not running anymore.
    New SYNC LNSc needs to be started
    Waiting for subscriber count on LGWR-LNSc channel to go to zero
    Subscriber count went to zero - time now is <01/31/2010 13:36:31>
    Starting LNSc ...
    Waiting for LNSc to initialize itself
    *** 2010-01-31 13:36:34.116 53972 kcrr.c
    +Netserver LNSc [pid 11451] for mode SYNC has been initialized+
    Performing a channel reset to ignore previous responses
    +Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
    +521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
    *** 2010-01-31 13:36:34.116 54475 kcrr.c
    +Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
    Waiting for LNSc to respond to upiahm
    *** 2010-01-31 13:36:34.266 54639 kcrr.c
    upiahm connect done status is 0
    Receiving message from LNSc
    Receiving message from LNSc
    Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
    Receiving message from LNSc

  • How to change the database character set on physical standby database?

    Hi,
    We have a database with character set WE8ISO8859P1 and migrated the character set to WE8MSWIN1252 using csscan/csalter scripts. This database has a physical standby database setup also and after the migration, the physical standby database is still showing the character set as WE8ISO8859P1. How can I change the characterset on the physical standby? I raised a Service Request with Oracle, and they said that recreating the standby database is the only supported way of changing the char set on the standby database. Is this true?
    Thanks,
    Sreekanth

    Thank you, Robert, for your reply.
    The standby is in sync with the primary.
    see below
    SYS@sisprod>select * from v$dataguard_stats;
    NAME VALUE UNIT TIME_COMPUTED
    apply finish time +00 00:00:00.0 day(2) to second(1) interval 12-NOV-2009 14:02:46
    apply lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
    estimated startup time 11 second 12-NOV-2009 14:02:46
    standby has been open N 12-NOV-2009 14:02:46
    transport lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
    SYS@sisprod>
    I am selecting from v$nls_parameters;
    I don't know how to restore the controlfile from primary. Could you please tell me how to do it?
    Thanks,
    Sreekanth

Maybe you are looking for