Standby recovery

Hi
I have a primary database (oracle 9i ) and another database in mount state. ( not a dataguard standby)
I transfer the archivelogs manually.
I will rebuild dictionary managed tablespaces as locally managed in primary database.
My statements are like:
alter index ... rebuild tablespace..
drop tablespace aaa;
create tablespace aaa .....;
The thing is since it is not normal standby, During recovery,I have to issue the following statement in mount state database.
ALTER DATABASE CREATE DATAFILE '< >' as '<>';
recovery
ALTER DATABASE CREATE DATAFILE '< >' as '<>';
Do I need to issue this statement everytime, is there an easier way, such as copying controlfile, etc...?

Hi,
Actually, it is a standby database, just not automatically managed by data guard.
So, you should act as it was a normal standby.
The thing with standby database is that it doesn't create files automatically. Once you create datafiles on the primary, you need to create the files on the standby.
After that, all the "alter index" commands will be performed on the standby as part of the recovery process.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Similar Messages

  • Managed Standby Recovery not active

    Dear All,
    My database version is:
    SQL> select banner from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    OS:RedHat 5.5
    My current configuration is:
    We have two node RAC primary database and a local standby database.
    And TWO NODE RAC DR (REMOTE)STANDBY DATABASE
    while checking (REMOTE WHICH IS TWO NODE RAC)dr synchronization we found archive since yesterday has not been applied.
    But local dr is fully sinc with the primary database.
    When i have executed 'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL' it says
    SQL> alter database recover managed standby database cancel;
    alter database recover managed standby database cancel
    ERROR at line 1:
    ORA-16136: Managed Standby Recovery not active
    I manually copied the archive log which where missing in the remote standby database and then register those archive log.
    after that when i manually tried to recover the standby database it has given me following error.
    sql>recover automatic standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery
    ORA-01110:data file 1: '/database/ctmis/system01.dbf'
    please please help me to resolve the issue.
    Thanks and Regards
    Monoj Das

    according to my understand
    Node1,Node2 is having node1-standby node2-standby in RAC environment right?
    on which node logs ur trying to apply on which node standby? (node1 ==>node1-standby or node2 ==>node2-standby)
    check it...hope it will work or not sure :)
    standby side...
    rman target /
    RMAN>crosscheck archivelog all
    then try to recover..will see ..
    if not
    check with support.oracle.com through SR.

  • ORA-16136: Managed Standby Recovery not active

    Hi
    I am trying implement the dataguard in the windows platform. And this is my first time. Right now iam trying on physical standby. i have done everything as per the document. But iam getting some error. After giving the
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    SQL> recover managed standby database cancel;
    // I am getting error
    ORA-16136: Managed Standby Recovery not active
    When just like that i tried to open the standby database in read only mode, i am getting error
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\SYSTEM01.DBF'
    When i checked the alert log file of Primary Database, it shows:
    PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
    Wed Sep 01 14:10:27 2010
    Thread 1 advanced to log sequence 337 (LGWR switch)
    Current log# 2 seq# 337 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\REDO02.LOG
    Wed Sep 01 14:10:28 2010
    Deleted Oracle managed file C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\DB1\ARCHIVELOG\2010_02_25\O1_MF_1_224_5RD10Z5V_.ARC
    Wed Sep 01 14:14:53 2010
    Error 1031 received logging on to the standby
    Wed Sep 01 14:14:53 2010
    Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
    ORA-01031: insufficient privileges
    PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
    Wed Sep 01 14:19:53 2010
    Error 1031 received logging on to the standby
    Wed Sep 01 14:19:53 2010
    Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
    ORA-01031: insufficient privileges
    And when i checked alert log file of stand by database:
    Wed Sep 01 14:13:19 2010
    Errors in file c:\oracle\product\10.2.0\standbyy\admin\db2\bdump\db2sby_dbw0_3060.trc:
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'C:\TSUNDO12.DBF'
    ORA-27086: unable to lock file - already in use
    OSD-00001: additional error information
    O/S-Error: (OS 101) The exclusive semaphore is owned by another process
    --> The above error of Standby was coming for each datafile such as system, users etc.
    Kindly Help me.
    Shiyas M

    here is the pfile of Primary Database:
    db1.__db_cache_size=188743680
    db1.__java_pool_size=4194304
    db1.__large_pool_size=4194304
    db1.__shared_pool_size=83886080
    db1.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/db1/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/db1/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\db1\control01.ctl','C:\oracle\product\10.2.0\oradata\db1\control02.ctl','C:\oracle\product\10.2.0\oradata\db1\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/db1/cdump'
    *.db_16k_cache_size=4194304
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='db1'
    *.DB_UNIQUE_NAME='db1prim'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db1prim'
    *.LOG_ARCHIVE_DEST_2='SERVICE=db2sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db2sby'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=ENABLE
    *.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    *.FAL_SERVER=db2sby
    *.FAL_CLIENT=db1
    *.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=95420416
    *.processes=150
    *.recyclebin='OFF'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=287309824
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/db1/udump'
    *.utl_file_dir='OCM_CONFIG_HOME/state'
    Here is the Pfile of standby database:
    db1.__db_cache_size=188743680
    db1.__java_pool_size=4194304
    db1.__large_pool_size=4194304
    db1.__shared_pool_size=83886080
    db1.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\Standbyy\oradata\db2\control001.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control002.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control003.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2'
    *.db_16k_cache_size=4194304
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='db1'
    *.DB_UNIQUE_NAME='db2sby'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db2sby'
    *.LOG_ARCHIVE_DEST_2='SERVICE=db1 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db1'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=ENABLE
    *.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    *.FAL_SERVER=db1
    *.FAL_CLIENT=db2sby
    *.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area\DB2SBY'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=95420416
    *.processes=150
    *.recyclebin='OFF'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=287309824
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\udump'
    *.utl_file_dir='OCM_CONFIG_HOME/state'

  • Physica standby recovery problem

    Hi,
    I am trying to recover physical standby database manually
    I am getting below error:
    alter database recover standby database parallel (degree 32);
    alter database recover standby database parallel (degree 32)
    ERROR at line 1:
    ORA-01153: an incompatible media recovery is active
    I have tried to cancel managed recovery, but no managed recovery is active.
    alter database recover managed standby database cancel;
    alter database recover managed standby database cancel
    ERROR at line 1:
    ORA-16136: Managed Standby Recovery not active
    select distinct recovery_mode from v$archive_dest_status;
    RECOVER
    IDLE
    Please help me to resolve this. Thanks in advance.
    regards,
    Narendra

    Apparently this is bug 5084496, related to parallel recovery on 10.1 and below (ML note 361883.1). You may avoid this bug if you don't use parallel recovery. It looks like there are no one-off patches available, so you are stuck with either serial recovery or upgrade to 10.2 or higher :-(
    Regards,
    Jeremiah Wilton
    ORA-600 Consulting
    http://www.ora-600.net

  • Standby recovery error on data guard

    Hi,
    I am creating data guard of Oracle 9i in windows server 2003. I have copied all the primary datafiles with created standby control file to standby server and issued
    recover automatic standby database I am getting the below error.
    SQL> recover automatic standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'.
    File is present at OS level and since these are standby i have changed the directory name to orcl1 to orcl2.
    Db version: 9.2.0.6.0
    OS version: windows server 2003
    Edited by: user10724679 on Feb 1, 2012 1:16 PM

    I am creating data guard of Oracle 9i in windows server 2003. I have copied all the primary datafiles with created standby control file to standby server and issued
    recover automatic standby database I am getting the below error.
    SQL> recover automatic standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF'.
    File is present at OS level and since these are standby i have changed the directory name to orcl1 to orcl2.
    Db version: 9.2.0.6.0
    OS version: windows server 2003
    Edited by: user10724679 on Feb 1, 2012 1:16 PMWell, As per the primary/source controlfile , All datafile location points to ORCL1, But now you copied them to ORCL2, Then how oracle knows that you have changed location? So before starting MRP, you have rename all those files as
    SQL> alter database rename file 'D:\ORACLE\ORADATA\ORCL1\SYSTEM01.DBF' to 'D:\ORACLE\ORADATA\ORCL2\SYSTEM01.DBF';
    Like that rename all the datafiles & log files.
    Then start MRP. Post if any errors.

  • Standby recovery problem

    i have a production and standby db
    9i release 2 on oralinux
    on my production database
    select name from v$datafile;
    NAME
    /oracle/oradata/eims/system01.dbf
    /oracle/oradata/eims/undotbs01.dbf
    /oracle/oradata/eims/cwmlite01.dbf
    /oracle/oradata/eims/drsys01.dbf
    /oracle/oradata/eims/example01.dbf
    /oracle/oradata/eims/indx01.dbf
    /oracle/oradata/eims/odm01.dbf
    /oracle/oradata/eims/tools01.dbf
    /oracle/oradata/eims/users01.dbf
    /oracle/oradata/eims/xdb01.dbf
    /oracle/oradata/eims/INVENTORY01.dbf
    NAME
    /oracle/oradata/eims/APR_DATA11.dbf
    /oracle/oradata/eims/APR_DATA21.dbf
    /oracle/oradata/eims/APR_MMS1.dbf
    /oracle/oradata/eims/APR_MVIEWS1.dbf
    /oracle/oradata/eims/HR_DATA21.dbf
    /oracle/oradata/eims/DTS_DATA11.dbf
    /oracle/oradata/eims/dts_data12.dbf
    /oracle/oradata/eims/undotbs0.dbf2.dbf
    /oracle/oradata/eims/APR_DATA22.dbf
    /oracle/oradata/eims/INVENTORY11.dbf ( this file not present on standby db)
    21 rows selected.
    on my standby db:
    select name from v$datafile;
    NAME
    /oracle/oradata/eims/system01.dbf
    /oracle/oradata/eims/undotbs01.dbf
    /oracle/oradata/eims/cwmlite01.dbf
    /oracle/oradata/eims/drsys01.dbf
    /oracle/oradata/eims/example01.dbf
    /oracle/oradata/eims/indx01.dbf
    /oracle/oradata/eims/odm01.dbf
    /oracle/oradata/eims/tools01.dbf
    /oracle/oradata/eims/users01.dbf
    /oracle/oradata/eims/xdb01.dbf
    /oracle/oradata/eims/INVENTORY01.dbf
    NAME
    /oracle/oradata/eims/APR_DATA11.dbf
    /oracle/oradata/eims/APR_DATA21.dbf
    /oracle/oradata/eims/APR_MMS1.dbf
    /oracle/oradata/eims/APR_MVIEWS1.dbf
    /oracle/oradata/eims/HR_DATA21.dbf
    /oracle/oradata/eims/DTS_DATA11.dbf
    /oracle/oradata/eims/dts_data12.dbf
    /oracle/oradata/eims/undotbs0.dbf2.dbf
    /oracle/oradata/eims/APR_DATA22.dbf ( the recovery error come with this datafile)
    20 rows selected.
    but when I
    SQL> recover standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01110: data file 20: '/oracle/oradata/eims/APR_DATA22.dbf'
    ORA-01157: cannot identify/lock data file 20 - see DBWR trace file
    ORA-01110: data file 20: '/oracle/oradata/eims/APR_DATA22.dbf'
    the diffrence in both primary and standby db is
    /oracle/oradata/eims/INVENTORY11.dbf (present on primary) but not on standby db. the error message when i recover standby database should with this datafile
    however in recovery the error message is (data file 20: '/oracle/oradata/eims/APR_DATA22.dbf') not with
    (/oracle/oradata/eims/INVENTORY11.dbf)
    how i can over come with this
    regards
    rehan
    Edited by: user10204771 on Feb 6, 2009 12:18 AM

    /oracle/oradata/eims/APR_DATA22.dbf this also created in standby and production db at 15-jan-09.
    /oracle/oradata/eims/INVENTORY11.dbf this file is created on primary db on 15-jan-09 but not on standby.
         /oracle/oradata/eims/system01.dbf system
    /oracle/oradata/eims/undotbs01.dbf RECOVER
         /oracle/oradata/eims/cwmlite01.dbf
         /oracle/oradata/eims/drsys01.dbf
         /oracle/oradata/eims/example01.dbf
         /oracle/oradata/eims/indx01.dbf
         /oracle/oradata/eims/odm01.dbf
         /oracle/oradata/eims/tools01.dbf
         /oracle/oradata/eims/users01.dbf
         /oracle/oradata/eims/xdb01.dbf
         /oracle/oradata/eims/INVENTORY01.dbf
         /oracle/oradata/eims/APR_DATA11.dbf      /oracle/oradata/eims/APR_DATA21.dbf
         /oracle/oradata/eims/APR_MMS1.dbf
         /oracle/oradata/eims/APR_MVIEWS1.dbf
         /oracle/oradata/eims/HR_DATA21.dbf
         /oracle/oradata/eims/DTS_DATA11.dbf
         /oracle/oradata/eims/dts_data12.dbf
         /oracle/oradata/eims/undotbs0.dbf2.dbf
    /oracle/oradata/eims/APR_DATA22.dbf RECOVER
    the staus of these two files is recover , all other datafile status is onlline.
    regards rehan

  • Manual Standby Recovery

    Hi Friendz,
    Oracle Db 9i
    I have configured a manual standby database(I am not using Dataguard or "create standby database" command ) I only copy the cold backup to the target recovery server. I have been applying archive logs to it for a week now. I use the "recover automatic database using backup controlfile" command.
    My problem is, when I try to "alter database open resetlogs" so I can test if I can open it, It is asking for the next archive log and message "that the system01.dbf needs recovery". How can I open my standby database and force it to stop recovery?
    Thanks a lot
    Ms Inday

    ALTER DATABASE RECOVER  automatic database using backup controlfile
    Media Recovery Start
    Sun Dec 19 18:33:14 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40621.dbf
    Sun Dec 19 18:33:14 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40622.dbf
    Sun Dec 19 18:33:18 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40623.dbf
    Sun Dec 19 18:33:22 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40624.dbf
    Sun Dec 19 18:33:25 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40625.dbf
    Sun Dec 19 18:33:26 2010
    Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
    Errors with log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
    ORA-279 signalled during: ALTER DATABASE RECOVER  automatic database using b...
    Sun Dec 19 18:33:26 2010
    ALTER DATABASE RECOVER    CANCELThis is the alert when I try to open it using resetlogs.
    ALTER DATABASE   MOUNT
    Sun Dec 19 19:29:56 2010
    Successful mount of redo thread 1, with mount id 4188096816
    Sun Dec 19 19:29:56 2010
    Database mounted in Exclusive Mode.
    Completed: ALTER DATABASE   MOUNT
    Sun Dec 19 19:29:56 2010
    ALTER DATABASE OPEN
    ORA-1589 signalled during: ALTER DATABASE OPEN...
    Sun Dec 19 19:30:51 2010
    alter database open noresetlogs
    Sun Dec 19 19:30:51 2010
    ORA-1588 signalled during: alter database open noresetlogs...
    Sun Dec 19 19:31:18 2010
    alter database open resetlogs
    Sun Dec 19 19:31:20 2010
    ORA-1113 signalled during:  alter database open resetlogs...
    Sun Dec 19 19:32:00 2010
    ALTER DATABASE RECOVER  database
    Sun Dec 19 19:32:00 2010
    Media Recovery Start
    Sun Dec 19 19:32:00 2010
    Media Recovery failed with error 1610
    ORA-283 signalled during: ALTER DATABASE RECOVER  database  ...
    Sun Dec 19 19:32:56 2010
    ALTER DATABASE RECOVER  database using backup controlfile
    Sun Dec 19 19:32:56 2010
    Media Recovery Start
    ORA-279 signalled during: ALTER DATABASE RECOVER  database using backup cont...
    Sun Dec 19 19:33:12 2010
    ALTER DATABASE RECOVER    CANCEL
    Sun Dec 19 19:33:12 2010
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER    CANCEL
    Sun Dec 19 19:33:31 2010
    alter database open resetlogs
    Sun Dec 19 19:33:31 2010
    ORA-1113 signalled during: alter database open resetlogs...
    Sun Dec 19 19:34:15 2010Thanks

  • Standby recovery mode

    hi all,
    how we can find that standby database is in recovery mode using a query.
    when i checked status it is shown mount. but not sure it is in recovery mode or not.
    please let me know.
    thanks

    Hi.
    More info...
    The physical standby database uses several processes to achieve the automation necessary for disaster recovery and high availability. On the standby database, log apply services use the following processes:
    Remote file server (RFS)
    The remote file server (RFS) process receives redo logs from the primary database either in the form of archived redo logs or standby redo logs.
    Archiver (ARCn)
    If standby redo logs are being used, the ARCn process archives the standby redo logs that are to be applied by the managed recovery process (MRP).
    Managed recovery process (MRP)
    The managed recovery process (MRP) applies information from the archived redo logs or standby redo logs to the standby database.
    Log apply services, in coordination with log transport services, manage the standby database by automatically applying archived redo logs to maintain transactional synchronization with the primary database.
    Log apply services can apply logs to a physical standby database when the database is performing recovery (for example, in managed recovery mode), but not when it is open for reporting access (for example, in read-only mode).
    For physical standby databases, you can easily change between managed recovery mode and read-only mode. In most implementations of a Data Guard environment, you may want to make this change at various times to either:

  • Physical Standby - Recovery error

    Hi,
    Windows XP, 10.2.0.1.0
    I m getting the error like
    SQL> alter database mount standby database;
    alter database mount standby database
    ERROR at line 1:
    ORA-01103: database name 'PRIM' in control file is not 'STBY'
    Please suggest me
    Thanks
    KSG
    Edited by: KSG on Jun 15, 2010 1:15 PM

    Hi,
    Hope I have some issue with the parameter file. Please find my parameter files
    initPRIM.ora
    PRIM.__db_cache_size=411041792
    PRIM.__java_pool_size=4194304
    PRIM.__large_pool_size=4194304
    PRIM.__shared_pool_size=163577856
    PRIM.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/PRIM/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\PRIM\control01.ctl','C:\oracle\product\10.2.0\oradata\PRIM\control02.ctl','C:\oracle\product\10.2.0\oradata\PRIM\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='PRIM'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=PRIMXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=197132288
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=591396864
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/PRIM/udump'
    *.log_archive_dest_1='location=C:\oracle\archiveprim'
    *.log_archive_format='ARCH_%r_%t_%s.ARC'
    initstby.ora
    stby.__db_cache_size=411041792
    stby.__java_pool_size=4194304
    stby.__large_pool_size=4194304
    stby.__shared_pool_size=163577856
    stby.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/stby/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/stby/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\CONTROL_SB01.CTL'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/stby/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='stby'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=stbyXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=197132288
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=591396864
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/stby/udump'
    *.log_archive_dest_1='location=C:\oracle\archivestby'
    *.log_archive_format='ARCH_%r_%t_%s.ARC'
    *.standby_archive_dest='C:\oracle\archiveprim'
    *.db_file_name_convert='C:\oracle\product\10.2.0\oradata\PRIM','C:\oracle\product\10.2.0\oradata\stby'
    *.log_file_name_convert='C:\oracle\product\10.2.0\oradata\PRIM','C:\oracle\product\10.2.0\oradata\stby'
    *.standby_file_management=AUTO
    *.remote_archive_enable=TRUE

  • StandBy Recovery with a click?!

    Hi and thanks for reading.
    I have noticed that if I leave my MACBOOK PRO with Lion OS alone and let it going in energy saving mode, I need to click on the touchpad in order to recover it.
    On the contrary on Snow Leopard a gentle touch on the trackpad was enough...
    Is there a way to set again that nice feature?
    Tnxs cheers

    You can also try the java way: play around with the
    ClassLoader class
    ClassLoader.defineClass(String name, byte[] b, int
    off, int len)Yes, doing this using the API is far better than falling back on Runtime exec. There is a class called Compiler, to which you can pass string filenames... this seems a far better solution.

  • Standby database is not completing recovery.

    All,
    I applied a PSU to 10.2.0.4 (8576156) patch this afternoon on both the primary and standby oracle_home(s). Upon starting up the standby database, I no longer see the “media recovery waiting” message in the alert log when an archive log is sent from the primary.
    Not sure if I have an issue with the patch or DG is configured or started.
    Perhaps another set of eyes can lead me to an issue I am not seeing.
    The standby database was started as follows:
    alter database RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
    Example alert log message before:
    Sun Sep 13 02:20:39 2009
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[2]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Sun Sep 13 02:20:47 2009
    Media Recovery Waiting for thread 1 sequence 52 (in transit) <<== NOTE
    Sun Sep 13 02:20:47 2009
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 52 Reading mem 0
    Mem# 0: /oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log
    Mem# 1: /oradat2/cwsiqa2/cwsiqa2_sb_redo04_b.log
    Example alert log message after:
    Primary database is in MAXIMUM PERFORMANCE mode
    Tue Sep 15 15:56:27 2009
    RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Tue Sep 15 15:56:27 2009
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
    Tue Sep 15 15:57:05 2009
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[5]: Assigned to RFS process 29772
    RFS[5]: Identified database type as 'physical standby'
    Tue Sep 15 16:12:56 2009
    The same messages are listed in v$datagurd_status
    1* select message from v$dataguard_status
    SQL> /
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARC9: Becoming the 'no FAL' ARCH
    ARC9: Becoming the 'no SRL' ARCH
    ARC0: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery starting Real Time Apply
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 28316
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 28318
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 29693
    RFS[3]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 29691
    RFS[4]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[5]: Assigned to RFS process 29772
    RFS[5]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 4: '/oradat1/cwsiqa2/cwsiqa2_sb_redo04_a.log'
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: Successfully opened standby log 6: '/oradat3/cwsiqa2/cwsiqa2_sb_redo06_a.log'
    I also have a “gap” that is not getting resolved.
    SQL> select * from v$archive_gap
    2 /
    THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
    1 53 53
    SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT
    2* FROM V$ARCHIVED_LOG R, V$LOG L WHERE R.DEST_ID=2 AND L.ARCHIVED='YES'
    SQL> /
    LAST_SEQ_RECD LAST_SEQ_SENT
    54     58
    Any insight would be appreciated.

    Problem has been resolved.

  • Recovery process applies old archivelogs on standby database

    Right now my standby database is in sync with my primary database and is waiting for the archived log sequeuence# 8378 to arrive.
    But when I stop the recovery process (alter database recover managed standby database cancel;) and re-start it (alter database recover managed standby database disconnect), it starts all over again and starts applying archive logs starting from the sequence# 5739 (looks like its scanning thru the logs). To catchup with primary it takes 2+ hours as it need to skim thru all the logs starting from 5739 to 8377.
    Please let me know if you need any further information to fix this.
    Thank you
    Sunny boy
    Details:
    Database version: 11.2.0.3
    OS : RHEL 5
    On Standby Database
    SQL> SELECT THREAD#, MAX(SEQUENCE#) AS "LAST_APPLIED_LOG"
    FROM V$LOG_HISTORY
    GROUP BY THREAD#; 2 3
    THREAD# LAST_APPLIED_LOG
    1 8377
    Alert log
    alter database recover managed standby database disconnect
    Attempt to start background Managed Standby Recovery process (MNODWDR)
    Tue May 08 16:13:09 2012
    MRP0 started with pid=28, OS id=26150
    MRP0: Background Managed Standby Recovery process started (MNODWDR)
    started logmerger process
    Tue May 08 16:13:15 2012
    Managed Standby Recovery not using Real Time Apply
    Parallel Media Recovery started with 8 slaves
    Waiting for all non-current ORLs to be archived...
    All non-current ORLs have been archived.
    Completed: alter database recover managed standby database disconnect
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/arch/mnodw_1_5739_765032423.arc
    Tue May 08 16:13:48 2012
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5740.1466.781015749
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5741.1468.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5742.1474.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5743.1473.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5744.1477.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5745.1478.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5746.1472.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5747.1475.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5748.1469.781017203
    Media Recovery Log +MNODW_FRA_GRP/mnodwdr/archivelog/2012_04_19/thread_1_seq_5749.1470.781017203
    Tue May 08 16:13:57 2012
    Edited by: Sunny boy on May 8, 2012 5:29 PM

    Hello;
    V$LOG_HISTORY is the information from the control file. I would use a different query to check :
    From the Primary :
    SET PAGESIZE 140
    COL DB_NAME FORMAT A10
    COL HOSTNAME FORMAT A14
    COL LOG_ARCHIVED FORMAT 999999
    COL LOG_APPLIED FORMAT 999999
    COL LOG_GAP FORMAT 9999
    COL APPLIED_TIME FORMAT A14
    SELECT
       DB_NAME, HOSTNAME, LOG_ARCHIVED, LOG_APPLIED, APPLIED_TIME, LOG_ARCHIVED-LOG_APPLIED LOG_GAP
    FROM
    ( SELECT
       NAME DB_NAME
    FROM
       V$DATABASE
    SELECT
       UPPER(SUBSTR(HOST_NAME,1,(DECODE(INSTR(HOST_NAME,'.'),0,LENGTH(HOST_NAME), (INSTR(HOST_NAME,'.')-1))))) HOSTNAME
    FROM
       V$INSTANCE
    SELECT
       MAX(SEQUENCE#) LOG_ARCHIVED
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=1
    AND
       ARCHIVED='YES'
    SELECT
       MAX(SEQUENCE#) LOG_APPLIED
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=2
    AND
       APPLIED='YES'
    SELECT
       TO_CHAR(MAX(COMPLETION_TIME),'DD-MON/HH24:MI') APPLIED_TIME
    FROM
       V$ARCHIVED_LOG
    WHERE
       DEST_ID=2
    AND
       APPLIED='YES'
    );Change DEST_ID as needed for your system. I would also bump the parameter LOG_ARCHIVE_MAX_PROCESSES assuming its set to default to a higher value up to 30.
    Maybe instead of stopping the recovery process you should DEFER on the Primary
    alter system set log_archive_dest_state_2=defer;Change the _n from 2 to what your system requires. I use this and have watch DG catch up 200 archives in about 15 minutes.
    You have Standby Redo setup and are using the same size as your redo right?
    Have never seen the Standby try to apply twice.
    ORA-600 [3020] "Stuck Recovery" [ID 30866.1] ( But I do not see your issue )
    Metalink Note 241438.1 Script to Collect Data Guard Physical Standby Diagnostic Information
    Metalink Note 241374.1 Script to Collect Data Guard Primary Site Diagnostic Information
    Best Regards
    mseberg
    Edited by: mseberg on May 8, 2012 5:16 PM

  • Standby db in RECOVERY NEEDED switchover status

    HI,
    (db version:10.2.0.4
    linux 64bit)
    My primary data guard is in
    SQL> select DATABASE_ROLE,switchover_status from v$database;
    DATABASE_ROLE    SWITCHOVER_STATUS
    PRIMARY          SESSIONS ACTIVEThe standby database shows:
    SQL> select DATABASE_ROLE,switchover_status from v$database;
    DATABASE_ROLE    SWITCHOVER_STATUS
    PHYSICAL STANDBY RECOVERY NEEDEDHow to set standby db (session active) and primary db (to_standby)?
    thanks
    abdul

    [on primary]
    paceview.__db_cache_size=754974720
    paceview.__java_pool_size=4194304
    paceview.__large_pool_size=4194304
    paceview.__shared_pool_size=301989888
    paceview.__streams_pool_size=0
    *.control_files='/PGHProdDB/oradata/paceview/control1.ctl','/PGHProdDB/oradata/paceview/control2.ctl','/PGHProdDB/oradata/paceview/control3.ctl'
    *.db_block_size=8192
    *.DB_FILE_NAME_CONVERT='STANDBY','paceview'
    *.db_name='paceview'
    *.FAL_CLIENT='paceview'
    *.FAL_SERVER='STANDBY'
    *.log_archive_dest_1='location=/PGHProdDB/archive/paceview/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=paceview'
    *.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_FILE_NAME_CONVERT='STANDBY','paceview'
    *.sga_max_size=1073741824#one gig
    *.sga_target=1073741824#one gig
    *.shared_pool_size=300000000
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'[on standby]
    standby.__db_cache_size=754974720
    standby.__java_pool_size=4194304
    standby.__large_pool_size=4194304
    standby.__shared_pool_size=301989888
    standby.__streams_pool_size=0
    *.control_files='/backup/rman/standby/STANDBY.ctl'
    *.db_block_size=8192
    *.DB_FILE_NAME_CONVERT='paceview','STANDBY'
    *.db_name='paceview'
    *.FAL_CLIENT='standby'
    *.FAL_SERVER='paceview'
    *.log_archive_dest_1='location=/PGHProdDB/archive/standby/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby'
    *.log_archive_dest_2='SERVICE=paceview LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=paceview'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='defer'
    *.LOG_FILE_NAME_CONVERT='paceview','STANDBY'
    *.sga_max_size=1073741824#one gig
    *.sga_target=1073741824#one gig
    *.shared_pool_size=300000000
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'

  • Standby stopped recovery

    Hi everyone;
    10.2.0.4 Standby database stopped recovery with the following error on alertlog.
    Wed Jun 2 13:38:45 2010
    RFS[4]: Archived Log: '/...../RCDB_2_1_720616127.arc'
    RFS[4]: Physical Standby in the future of Branch(resetlogs_id) 720616127
    RFS[4]: Standby database SCN: 2304:-276361630 Primary branch SCN: 2304:-1502231553
    RFS[4]: New Archival REDO Branch(resetlogs_id): 720616127 Prior: 550946190
    RFS[4]: Archival Activation ID: 0x5dfe4ed2 Current: 0x58adeb9a
    RFS[4]: Effect of primary database OPEN RESETLOGS
    Wed Jun 2 13:38:45 2010
    There were no RESETLOGS operation on the primary side. What may be the cause of this error? Have any ideas?
    Thanks..

    After trying to start recovery again:
    MRP0: Background Managed Standby Recovery process started (RCDB)
    Managed Standby Recovery not using Real Time Apply
    Warning: Recovery target destination is in a sibling branch
    of the controlfile checkpoint. Recovery will only recover
    changes to datafiles.
    Datafile 1 (ckpscn 9899623255650) is orphaned on incarnation#=1
    MRP0: Background Media Recovery terminated with error 19909
    Wed Jun 2 13:55:57 2010
    Errors in file /.../rcdb_mrp0_16180.trc:
    ORA-19909: datafile 1 belongs to an orphan incarnation
    ORA-01110: data file 1: '/.../system01.dbf'
    Wed Jun 2 13:55:57 2010
    Errors in file /.../rcdb_mrp0_16180.trc:
    ORA-19909: datafile 1 belongs to an orphan incarnation
    ORA-01110: data file 1: '/.../system01.dbf'
    Wed Jun 2 13:55:57 2010
    MRP0: Background Media Recovery process shutdown (RCDB)

  • 11g standby database media recovery failed due to ora-600

    hi friends,
    DB: 11g 11.1.0.6
    OS: Windows server 2003 ent
    I've setup datagaurd using 11g. but for last 2 days, not able to start media recovey on standby database.
    here's my alertlog file
    alter database recover managed standby database using current logfile disconnect from session
    Sat Jan 03 11:23:04 2009
    MRP0 started with pid=18, OS id=648
    Fast Parallel Media Recovery enabled
    Managed Standby Recovery starting Real Time Apply
    Media Recovery apply datafile 5 offline range
    parallel recovery started with 2 processes
    Waiting for all non-current ORLs to be archived...
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_30\BACKUP\O1_MF_1_297_4ON23Q00_.ARC
    Completed: alter database recover managed standby database using current logfile disconnect from session
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\BACKUP\O1_MF_1_298_4OP3CLWS_.ARC
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc (incident=544158):
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Incident details in: c:\app\administrator\diag\rdbms\goldsby\gold\incident\incdir_544158\gold_mrp0_648_i544158.trc
    Errors with log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\BACKUP\O1_MF_1_298_4OP3CLWS_.ARC
    MRP0: Background Media Recovery terminated with error 600
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Managed Standby Recovery not using Real Time Apply
    Shutting down recovery slaves due to error 600
    Recovery interrupted!
    Sat Jan 03 11:23:15 2009
    Trace dumping is performing id=[cdmp_20090103112315]
    Sat Jan 03 11:23:16 2009
    Recovered data files to a consistent state at change 92419435
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Sat Jan 03 11:23:17 2009
    Sweep Incident[544158]: completed
    MRP TRACE FILE
    ** 2009-01-03 11:05:36.140 1095 krsh.c
    MRP0: Background Managed Standby Recovery process started
    *** 2009-01-03 11:05:41.140
    *** 2009-01-03 11:05:41.140 1295 krsm.c
    Managed Recovery: Initialization posted.
    Started 11g Parallel Media Recovery
    Fast Parallel Media Recovery enabled
    *** 2009-01-03 11:05:41.156 1095 krsh.c
    Managed Standby Recovery starting Real Time Apply
    *** 2009-01-03 11:05:41.671
    Recovery target incarnation = 5, activation ID = 0
    Influx buffer limit = 31623 (50% x 63246)
    Successfully allocated 2 recovery slaves
    Start recovery at thread 1 ckpt scn 92413878 logseq 297 block 2
    *** 2009-01-03 11:05:43.281
    Media Recovery add redo thread 1
    *** 2009-01-03 11:05:43.296 1295 krsm.c
    Managed Recovery: Active posted.
    *** 2009-01-03 11:05:43.500
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_30\O1_MF_1_297_4ON1Y6NZ_.ARC
    *** 2009-01-03 11:05:44.093
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\O1_MF_1_298_4ON74ROZ_.ARC
    *** 2009-01-03 11:05:44.906
    Incident 520220 created, dump file: c:\app\administrator\diag\rdbms\goldsby\gold\incident\incdir_520220\gold_mrp0_4044_i520220.trc
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    *** 2009-01-03 11:05:45.687 1095 krsh.c
    MRP0: Background Media Recovery terminated with error 600
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    *** 2009-01-03 11:05:45.687 1095 krsh.c
    Managed Standby Recovery not using Real Time Apply
    kcrrgaptime: no snapshot information available
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 21376Kb in 2.55s => 8.19 Mb/sec
    Total redo bytes: 23424Kb Longest record: 14Kb, moves: 17/62299 moved: 0Mb (0%)
    Longest LWN: 804Kb, reads: 2357
    Last redo scn: 0x0000.05823f03 (92421891)
    Change vector header moves = 8621/118937 (7%)
    *** 2009-01-03 11:05:45.828
    Media Recovery drop redo thread 1
    Completed 11g Parallel Media Recovery
    Starting in-flux buffer recovery from SCN 0.92413878 to SCN (non-inclusive) 0.92419435
    *** 2009-01-03 11:05:46.265
    Influx Media Recovery add redo thread 1
    *** 2009-01-03 11:05:47.531
    *** 2009-01-03 11:05:47.531 1295 krsm.c
    Managed Recovery: Not Active posted.
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    error 473 detected in background process
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    could you help on this...?
    waiting for your favorable reply,
    thanks in advance..
    Regards

    Hi;
    This error occurs when you have run a switchover/ failover, you may have two parallel standby's but when you pass the command for switchover the one standby is not aware of what you have done.
    The point is that all standby should know who is your primary & standby's should also be aware of each other in their "pfiles" now, you should either recreate the standby or open with reset logs.
    ora-600 occurs due to different incarnation.
    Hope this will help you
    if you switch multiple logfiles in primary, & run >>
    alter database recover managed standby database disconnect;
    your standby will start syncing.
    Hope this will help you

Maybe you are looking for

  • Passing Session Values to the Tabular Form Element of a Report Column

    Hello, I'm running application express version 2.0 with a 10.2.0.2.0 database on a 32 bit windows box. I'm trying to figure out sneaky a way to pass the &APP_PAGE_ID., #APP_PAGE_ID# or V('APP_PAGE_ID'); as an element attribute of a Report Tabular For

  • Video quality of Flash animation in iWeb

    I'm inserting a flash movie (html snippet) into my iweb 08 site, but the resolution of the video is not as high as the original .swf file. This is my workflow: -Go to LiveType and create a scrolling banner. -Export the movie, then open it in Compress

  • Issue in Mapping _PO Create

    Hi XI experts , Thsi is  XML (SOAP) mapped to PO BAPI(ZMM_IBX_RFC_CREATE_CABIN_ORDER) .Standard BAPI  with commit statement. The External partner through xml sends the data  of :Purchase Order The XMl contains the COST CENTRE , GL ACCOUNT  , WBS ELEM

  • Video loading into iphoto as black screen

    I have loaded videos from two different cameras. One is fine. The other loaded the videos as black screens. I have downloaded a divx converter per the owner of the camera but it still doesn't work. When I go to Macintosh HD from my desktop and go to

  • Using EL How to Write a Customize tag

    I want to write a tag wich takes input and output as it is.Like when i pass an primitive types then it directly pass no transfer as we are puting "" literial to the values and pass it. For Example: <fun:add i1=10 i2=20 /> check my code as i write tld