Standby Database is Idle

HI There
I have configured Data Guard on oracle 10g (10.2.0.4) on Windows 2007 64 bits Server.
Both Primary DB and Standby DB are on same Server.
When I connect to my Primary DB, It is connected Normally as shown below.
Start --> Run --> CMD --> set oracle_sid=prmdb
c:\> sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Apr 17 09:48:22 2013
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
Now Whenever I connect to my Standby DB, It connects to an Idle Instance. When I issue startup command
it displays a Message as shown below.
Start --> Run --> CMD --> set oracle_sid=stldb
c:\> sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Apr 17 09:48:22 2013
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1258291200 bytes
Fixed Size 2065408 bytes
Variable Size 318770176 bytes
Database Buffers 922746880 bytes
Redo Buffers 14708736 bytes
Database mounted.
ORA-16004: backup database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\STLDB\SYSTEM01.DBF'
Then I issue following commands to overcome this
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT
FROM SESSION;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.
What is wrong with my Standby DB?
What to do to overcome these messages Permanently?
Why Standby DB is Not connected Normally instead of I have to start it?
Regards
Thunders2777

Hi
Thunder2777 wrote:
HI There
I have configured Data Guard on oracle 10g (10.2.0.4) on Windows 2007 64 bits Server.
Both Primary DB and Standby DB are on same Server.
When I connect to my Primary DB, It is connected Normally as shown below.
Start --> Run --> CMD --> set oracle_sid=prmdb
c:\> sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Apr 17 09:48:22 2013
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL>
Now Whenever I connect to my Standby DB, It connects to an Idle Instance. When I issue startup command
it displays a Message as shown below.
Start --> Run --> CMD --> set oracle_sid=stldb
c:\> sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Apr 17 09:48:22 2013
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 1258291200 bytes
Fixed Size 2065408 bytes
Variable Size 318770176 bytes
Database Buffers 922746880 bytes
Redo Buffers 14708736 bytes
Database mounted.In here tyour database mounted, is not opened. Because need media recovery.
ORA-16004: backup database requires recovery
ORA-01196: file 1 is inconsistent due to a failed media recovery session
ORA-01110: data file 1: 'D:\ORACLE\ORADATA\STLDB\SYSTEM01.DBF'
Then I issue following commands to overcome this
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT
FROM SESSION;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
ERROR at line 1:
ORA-01153: an incompatible media recovery is activeit means media recovery process is already started.
you can check with
select process from  v$managed_standby;There must be MRP0.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Database altered.
SQL> ALTER DATABASE OPEN;
Database altered.
Database opened read only mode.
Your Oracle Database version is 10.2.0. It means you can not start redo apply after open read only mode, too.
(Active Data guard able only 11g version)
>
What is wrong with my Standby DB? There have'n problem
What to do to overcome these messages Permanently?
Why Standby DB is Not connected Normally instead of I have to start it?I think, if you stop windows service, then this service automatically stopping standby database.
After start windows service, you must start database manually.
Mahir M. Quluzade

Similar Messages

  • Logs are not getting applied in the standby database

    Hello,
    I have created a physical standby database and in it the logs are not getting applied..
    following is an extract of the standby alert log
    Wed Sep 05 07:53:59 2012
    Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
    Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc
    Attempting refetch
    Media Recovery Waiting for thread 1 sequence 37638
    Fetching gap sequence in thread 1, gap sequence 37638-37643
    Wed Sep 05 07:53:59 2012
    RFS[46]: Assigned to RFS process 3081
    RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638
    RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228
    Wed Sep 05 07:55:34 2012
    RFS[42]: Possible network disconnect with primary database
    However, the archived files are getting copied to the standby server.
    I tried registering and recovering the logs but it also failed..
    Follows some of the information,
    Primary
    Oralce 11R2 EE
    SQL> select max(sequence#) from v$log where archived='YES';
    MAX(SEQUENCE#)
    37668
    SQL> select DEST_NAME, RECOVERY_MODE,DESTINATION,ARCHIVED_SEQ#,APPLIED_SEQ#, SYNCHRONIZATION_STATUS,SYNCHRONIZED,GAP_STATUS from v$archive_dest_status where DEST_NAME = 'LOG_ARCHIVE_DEST_3';
    DEST_NAME RECOVERY_MODE DESTINATION ARCHIVED_SEQ# APPLIED_SEQ# SYNCHRONIZATION_STATUS SYNCHRONIZED GAP_STATUS
    LOG_ARCHIVE_DEST_3 MANAGED REAL TIME APPLY ABC 37356 0 CHECK CONFIGURATION NO RESOLVABLE GAP
    Standby
    Oralce 11R2 EE
    SQL> select max(sequence#) from v$archived_log where applied='YES';
    MAX(SEQUENCE#)
    37637
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> select open_mode, database_role from v$database;
    OPEN_MODE DATABASE_ROLE
    READ ONLY WITH APPLY PHYSICAL STANDBY
    Please help me to troubleshoot this and get the standby in sync..
    Thanks a lot..

    the results are as follows..
    SQL> select process, status, group#, thread#, sequence# from v$managed_standby order by process, group#, thread#, sequence#;
    PROCESS STATUS GROUP# THREAD# SEQUENCE#
    ARCH CLOSING 1 1 37644
    ARCH CLOSING 1 1 37659
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    ARCH CONNECTED N/A 0 0
    MRP0 WAIT_FOR_GAP N/A 1 37638
    RFS IDLE N/A 0 0
    RFS IDLE N/A 0 0
    RFS IDLE N/A 0 0
    RFS RECEIVING N/A 1 37638
    RFS RECEIVING N/A 1 37639
    RFS RECEIVING N/A 1 37640
    RFS RECEIVING N/A 1 37641
    RFS RECEIVING N/A 1 37642
    RFS RECEIVING N/A 1 37655
    RFS RECEIVING N/A 1 37673
    RFS RECEIVING N/A 1 37675
    42 rows selected.
    SQL>
    SQL> select name,value, time_computed from v$dataguard_stats;
    NAME VALUE TIME_COMPUTED
    transport lag +00 02:44:33 09/05/2012 09:25:58
    apply lag +00 03:14:30 09/05/2012 09:25:58
    apply finish time +00 00:01:09.974 09/05/2012 09:25:58
    estimated startup time 12 09/05/2012 09:25:58
    SQL> select timestamp , facility, dest_id, message_num, error_code, message from v$dataguard_status order by timestamp
    TIMESTAMP FACILITY DEST_ID MESSAGE_NUM ERROR_CODE MESSAGE
    05-SEP-12 Remote File Server 0 60 0 RFS[13]: Assigned to RFS process 2792
    05-SEP-12 Remote File Server 0 59 0 RFS[12]: Assigned to RFS process 2790
    05-SEP-12 Log Apply Services 0 61 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 62 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 63 0 Managed Standby Recovery Canceled
    05-SEP-12 Log Apply Services 0 64 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 65 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 66 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 67 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 68 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 69 0 RFS[5]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 70 0 RFS[6]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 71 0 RFS[14]: Assigned to RFS process 2829
    05-SEP-12 Remote File Server 0 72 0 RFS[15]: Assigned to RFS process 2831
    05-SEP-12 Network Services 0 73 0 RFS[9]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 74 0 RFS[16]: Assigned to RFS process 2833
    05-SEP-12 Network Services 0 75 0 RFS[1]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 76 0 RFS[17]: Assigned to RFS process 2837
    05-SEP-12 Network Services 0 77 0 RFS[3]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 78 0 RFS[2]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 79 0 RFS[7]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 80 0 RFS[18]: Assigned to RFS process 2848
    05-SEP-12 Network Services 0 81 0 RFS[16]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 82 0 RFS[19]: Assigned to RFS process 2886
    05-SEP-12 Network Services 0 83 0 RFS[19]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 84 0 RFS[20]: Assigned to RFS process 2894
    05-SEP-12 Log Apply Services 0 85 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 86 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 87 0 Managed Standby Recovery Canceled
    05-SEP-12 Remote File Server 0 89 0 RFS[22]: Assigned to RFS process 2900
    05-SEP-12 Remote File Server 0 88 0 RFS[21]: Assigned to RFS process 2898
    05-SEP-12 Remote File Server 0 90 0 RFS[23]: Assigned to RFS process 2902
    05-SEP-12 Remote File Server 0 91 0 Primary database is in MAXIMUM PERFORMANCE mode
    05-SEP-12 Remote File Server 0 92 0 RFS[24]: Assigned to RFS process 2904
    05-SEP-12 Remote File Server 0 93 0 RFS[25]: Assigned to RFS process 2906
    05-SEP-12 Log Apply Services 0 94 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 95 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 96 0 Managed Standby Recovery starting Real Time Apply
    05-SEP-12 Log Apply Services 0 97 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Log Transport Services 0 98 0 ARCa: Beginning to archive thread 1 sequence 37644 (7911979302-7912040568)
    05-SEP-12 Log Transport Services 0 99 0 ARCa: Completed archiving thread 1 sequence 37644 (0-0)
    05-SEP-12 Network Services 0 100 0 RFS[8]: Possible network disconnect with primary database
    05-SEP-12 Log Apply Services 0 101 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 102 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 103 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 104 0 Managed Standby Recovery Canceled
    05-SEP-12 Network Services 0 105 0 RFS[20]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 106 0 RFS[26]: Assigned to RFS process 2930
    05-SEP-12 Network Services 0 107 0 RFS[24]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 108 0 RFS[27]: Assigned to RFS process 2938
    05-SEP-12 Network Services 0 109 0 RFS[14]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 110 0 RFS[28]: Assigned to RFS process 2942
    05-SEP-12 Network Services 0 111 0 RFS[15]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 112 0 RFS[29]: Assigned to RFS process 2986
    05-SEP-12 Network Services 0 113 0 RFS[17]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 114 0 RFS[30]: Assigned to RFS process 2988
    05-SEP-12 Log Apply Services 0 115 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 116 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 117 0 Managed Standby Recovery starting Real Time Apply
    05-SEP-12 Log Apply Services 0 118 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 119 0 RFS[18]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 120 0 RFS[31]: Assigned to RFS process 3003
    05-SEP-12 Network Services 0 121 0 RFS[26]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 122 0 RFS[32]: Assigned to RFS process 3005
    05-SEP-12 Network Services 0 123 0 RFS[27]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 124 0 RFS[33]: Assigned to RFS process 3009
    05-SEP-12 Remote File Server 0 125 0 RFS[34]: Assigned to RFS process 3012
    05-SEP-12 Log Apply Services 0 127 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 126 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 128 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 129 0 Managed Standby Recovery Canceled
    05-SEP-12 Network Services 0 130 0 RFS[32]: Possible network disconnect with primary database
    05-SEP-12 Log Apply Services 0 131 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 132 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 133 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 134 0 Managed Standby Recovery not using Real Time Apply
    05-SEP-12 Log Apply Services 0 135 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 136 0 RFS[33]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 137 0 RFS[35]: Assigned to RFS process 3033
    05-SEP-12 Log Apply Services 0 138 16037 MRP0: Background Media Recovery cancelled with status 16037
    05-SEP-12 Log Apply Services 0 139 0 MRP0: Background Media Recovery process shutdown
    05-SEP-12 Log Apply Services 0 140 0 Managed Standby Recovery Canceled
    05-SEP-12 Remote File Server 0 141 0 RFS[36]: Assigned to RFS process 3047
    05-SEP-12 Log Apply Services 0 142 0 Attempt to start background Managed Standby Recovery process
    05-SEP-12 Log Apply Services 0 143 0 MRP0: Background Managed Standby Recovery process started
    05-SEP-12 Log Apply Services 0 144 0 Managed Standby Recovery starting Real Time Apply
    05-SEP-12 Log Apply Services 0 145 0 Media Recovery Waiting for thread 1 sequence 37638 (in transit)
    05-SEP-12 Network Services 0 146 0 RFS[35]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 147 0 RFS[37]: Assigned to RFS process 3061
    05-SEP-12 Network Services 0 148 0 RFS[36]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 149 0 RFS[38]: Assigned to RFS process 3063
    05-SEP-12 Remote File Server 0 150 0 RFS[39]: Assigned to RFS process 3065
    05-SEP-12 Network Services 0 151 0 RFS[25]: Possible network disconnect with primary database
    05-SEP-12 Network Services 0 152 0 RFS[21]: Possible network disconnect with primary database
    05-SEP-12 Remote File Server 0 153 0 Archivelog record exists, but no file is found
    05-SEP-12 Remote File Server 0 154 0 RFS[40]: Assigned to RFS process 3067
    05-SEP-12 Network Services 0 155 0 RFS[37]: Possible network disconnect with primary database

  • Error while mounting Standby database

    Hi all,
    I am getting ORA-01102: cannot mount database in EXCLUSIVE mode error when truying to mount the standby database.
    SQL>alter database mount standby database ;
    If anyone faced the same issue please guide me.
    Thanks and Regards
    Salih KM

    This is script for Standby..
    Primary Server Configuration
    1.In the TNSNAMES.ORA of Primary DB add the entry of the Standby DB
    IRCSSTDB(This is the service name in Primary DB to connect to Standby DB) =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = IRDBACK)(PORT = 1512))
    (CONNECT_DATA =
    (SERVICE_NAME = IRCS(This is the actual INSTANCE name of Running DB on Standby DB)
    2. There is no need to Make any Changes in the Listener.ora of PRIMARY DB
    Keep LISTENER.ORA of Primary as it is
    Copy Listener.ora from Primary DB to Standby DB and make following changes
    Delete All the Extra Existing listeners.
    (These Updations are for the STANDBY DB)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = IRDBACK)(PORT = 1521))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /ora01/app/oracle/product/9.2.0)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = IRCS)
    (ORACLE_HOME = /ora01/app/oracle/product/9.2.0))
    3.In the INIT.ORA of Primary DB add Following…
    log_archive_dest_2 = "service=STBY optional/Mandatory scope=BOTH"
    log_archive_dest_2 = Enable
    log_archive_min_succeed_dest = 2
    We can add this Dynamically with the SQL*PLUS..
    Standby DB Server Configuration
    1.In the TNSNAMES.ORA of Standby DB add the entry of the Primary DB
    primary1(ISSL)(This is the service name in Standby DB to connect to Primary DB)=
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (PORT=1521) (HOST=PRIMARY MACHINE NAME))
    (CONNECT_DATA=(SERVICE_NAME=IRCS(This is the actual INSTANCE name of Running DB on Primary DB)
    2.Copy Listener.ora from Primary DB to Standby DB and make following changes
    Same as Above
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = IRDBACK)(PORT = 1521))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /ora01/app/oracle/product/9.2.0)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = IRCS)
    (ORACLE_HOME = /ora01/app/oracle/product/9.2.0))
    3. Connect to Idle instance..
    1.C:\ oradim –NEW –SID ircs –INTPWD pwdfilename –STARTMODE auto –pfile E:\oracle\oradata\pfile\init.ora
    2.     C:\ set oracle_sid=IRCS
    3.     C:\ sqlplus /nolog
    4.     SQL:>connect sys/ircl as SYSDBA
    5.     SQL:>startup nomount pfile= E:\oracle\oradata\pfile\init.ora
    6.     SQL:> alter database mount standby database;
    7. SQL :> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
    4. we can also add these parameter in INIT.ORA of Standby DB
    1.standby_archive_dest= /u00/app/oracle/admin/sec/arch (Same path as in
    (log_archive_dest_1) in init.ora
    2. Fal_client=standby1 (Service Name)
    3. Fal_server=primary1 (Service Name)
    Troubleshooting….
    1. Check Init.ora of Primary DB
    2. Try to open Standby Database in normal mode try to connect it with normal user from different Machine.
    3.check *.logs file on Standby Database
    4.Check v$archive_dest on Primary DB
    5. lsnrctl services <listener name>….For Checking Listener, for service

  • Problem Converting standby database from snapshot to physical

    Any help willl be greatly appreciated...
    I am trying to convert a standby database that is in "snapshot" mode back to "physical" standby and I am encountering problems in the process from the "DGMGRL" command line.
    Both instances are on the same physical machine. Everything was working fine untill I tried to change the db from snapshot to physical. The DGMGRL starts the conversion process and is able to shutdown but when trying to restart the instance is fails and reports that the service is not defined.
    Here is the issue I am facing:
    C:\app\MMJ\product\11.1.0\db_1\BIN>
    C:\app\MMJ\product\11.1.0\db_1\BIN>set ORACLE_SID=I11G1 <======= the primary database
    C:\app\MMJ\product\11.1.0\db_1\BIN>dgmgrl
    DGMGRL for 32-bit Windows: Version 11.1.0.6.0 - Production
    Copyright (c) 2000, 2005, Oracle. All rights reserved.
    Welcome to DGMGRL, type "help" for information.
    DGMGRL> connect sys/password@i11g1sb <===== the standby database currently in snapshot mode
    Connected.
    DGMGRL> connect sys/password@i11g1 <==== the primary database
    Connected.
    DGMGRL> convert database 'i11g1sb' to physical standby;
    Converting database "i11g1sb" to a Physical Standby database, please wait...
    Operation requires shutdown of instance "i11g1sb" on database "i11g1sb"
    Shutting down instance "i11g1sb"...
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    Operation requires startup of instance "i11g1sb" on database "i11g1sb"
    Starting instance "i11g1sb"...
    Unable to connect to database
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Failed.
    You are no longer connected to ORACLE
    Please connect again.
    Unable to start instance "i11g1sb"
    You must start instance "i11g1sb" manually
    Failed to convert database "i11g1sb"
    DGMGRL> show configuration
    Configuration
    Name: DGConfig1
    Enabled: YES
    Protection Mode: MaxPerformance
    Databases:
    i11g1 - Primary database
    i11g1sb - Snapshot standby database (disabled)
    Fast-Start Failover: DISABLED
    Current status for "DGConfig1":
    SUCCESS
    DGMGRL> exit
    C:\app\MMJ\product\11.1.0\db_1\BIN>set ORACLE_SID=I11G1SB
    C:\app\MMJ\product\11.1.0\db_1\BIN>sqlplus /nolog
    SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 25 11:40:16 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    SQL> connect / as sysdba
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 426852352 bytes
    Fixed Size 1333648 bytes
    Variable Size 369100400 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 6086656 bytes
    Database mounted.
    Database opened.
    ==============>>>> as you can see I can start the standby database without any problems and even query the table in which I made some changes. I had added the record with "Region_ID"=30. I have
    SQL> select * from hr.regions;
    REGION_ID REGION_NAME
    30 JAPAC
    1 Europe
    2 Americas
    3 Asia
    4 Middle East and Africa
    SQL>
    The same table on the primary database has the following records in the same table:
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\MMJ>set ORACLE_HOME=c:\app\mmj\product\11.1.0\db_1
    C:\Documents and Settings\MMJ>set ORACLE_SID=i11g1
    C:\Documents and Settings\MMJ>
    C:\Documents and Settings\MMJ>cd %ORACLE_HOME%
    C:\app\MMJ\product\11.1.0\db_1>cd bin
    C:\app\MMJ\product\11.1.0\db_1\BIN>
    C:\app\MMJ\product\11.1.0\db_1\BIN>
    C:\app\MMJ\product\11.1.0\db_1\BIN>sqlplus /nolog
    SQL*Plus: Release 11.1.0.6.0 - Production on Wed Mar 25 11:43:10 2009
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    SQL> connect / as sysdba
    Connected.
    SQL>
    SQL> select * from hr.regions;
    REGION_ID REGION_NAME
    1 Europe
    2 Americas
    3 Asia
    4 Middle East and Africa
    20 JAPAC
    40 JAPAC
    6 rows selected.
    SQL>
    =======> The TNSPING works fine against both the databases.
    C:\app\MMJ\product\11.1.0\db_1\BIN>set O
    ORACLE_HOME=c:\app\mmj\product\11.1.0\db_1
    ORACLE_SID=I11G1SB
    OS=Windows_NT
    C:\app\MMJ\product\11.1.0\db_1\BIN>
    C:\app\MMJ\product\11.1.0\db_1\BIN>tnsping i11g1sb
    TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:56:42
    Copyright (c) 1997, 2007, Oracle. All rights reserved.
    Used parameter files:
    c:\app\mmj\product\11.1.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = MHost)(PORT = 1523))) (CONNECT_DATA = (SERVICE_NAM
    E = I11G1SB)))
    OK (230 msec)
    C:\app\MMJ\product\11.1.0\db_1\BIN>tnsping i11g1
    TNS Ping Utility for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:56:47
    Copyright (c) 1997, 2007, Oracle. All rights reserved.
    Used parameter files:
    c:\app\mmj\product\11.1.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = MHost)(PORT = 1523))) (CONNECT_DATA = (SERVICE_NAM
    E = I11G1)))
    OK (30 msec)
    C:\app\MMJ\product\11.1.0\db_1\BIN>lsnrctl
    LSNRCTL for 32-bit Windows: Version 11.1.0.6.0 - Production on 25-MAR-2009 16:57:01
    Copyright (c) 1991, 2007, Oracle. All rights reserved.
    Welcome to LSNRCTL, type "help" for information.
    LSNRCTL> set current_listener i11g1
    Current Listener is i11g1
    LSNRCTL> services
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=MHost)(PORT=1523)))
    Services Summary...
    Service "I11G1" has 1 instance(s).
    Instance "I11G1", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:1 refused:0
    LOCAL SERVER
    Service "I11G1SB" has 1 instance(s).
    Instance "I11G1SB", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:55 refused:1
    LOCAL SERVER
    Service "I11G1SB_DGMGRL" has 1 instance(s).
    Instance "I11G1SB", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0
    LOCAL SERVER
    Service "i11g1.mhost" has 1 instance(s).
    Instance "i11g1", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:6 refused:0 state:ready
    LOCAL SERVER
    Service "i11g1XDB.mhost" has 1 instance(s).
    Instance "i11g1", status READY, has 1 handler(s) for this service...
    Handler(s):
    "D000" established:0 refused:0 current:0 max:1022 state:ready
    DISPATCHER <machine: MHost, pid: 3944>
    (ADDRESS=(PROTOCOL=tcp)(HOST=MHost)(PORT=1430))
    Service "i11g1_DGB.mhost" has 1 instance(s).
    Instance "i11g1", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:6 refused:0 state:ready
    LOCAL SERVER
    Service "i11g1_XPT.mhost" has 1 instance(s).
    Instance "i11g1", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:6 refused:0 state:ready
    LOCAL SERVER
    Service "i11g1sb.mhost" has 1 instance(s).
    Instance "i11g1sb", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0 state:ready
    LOCAL SERVER
    Service "i11g1sbXDB.mhost" has 1 instance(s).
    Instance "i11g1sb", status READY, has 1 handler(s) for this service...
    Handler(s):
    "D000" established:0 refused:0 current:0 max:1022 state:ready
    DISPATCHER <machine: MHost, pid: 7336>
    (ADDRESS=(PROTOCOL=tcp)(HOST=MHost)(PORT=1931))
    Service "i11g1sb_DGB.MHost" has 1 instance(s).
    Instance "i11g1sb", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0 state:ready
    LOCAL SERVER
    Service "i11g1sb_XPT.mhost" has 1 instance(s).
    Instance "i11g1sb", status READY, has 1 handler(s) for this service...
    Handler(s):
    "DEDICATED" established:0 refused:0 state:ready
    LOCAL SERVER
    The command completed successfully
    LSNRCTL>

    Thanks for the response.
    So, here is the status now....with a little background...
    After my original post, I started to read the manuals and I found the sql command to convert the database back from snapshot to physical standby (sb).
    That worked fine and I had my snapshot sb back to physical sb.
    So when you posted the suggestion, I already had my db in physical sb mode. I said no problem, I will convert it back to snapshot and then back again using dgmgrl instead of sql+
    Well here is how my listener is configured now.
    SID_LIST_I11G1 =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = I11G1.MHOST)
    (ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
    (SID_NAME = I11G1)
    (SID_DESC =
    (GLOBAL_DBNAME = I11G1SB.MHOST)
    (ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
    (SID_NAME = I11G1SB)
    (SID_DESC =
    (GLOBAL_DBNAME = I11G1SB_DGMGRL)
    (ORACLE_HOME = c:\app\mmj\product\11.1.0\db_1)
    (SID_NAME = I11G1SB)
    Then using dgmgrl I tried to change the db from p-sb to s-sb and the results are not good....
    "i11g1 >"dgmgrl
    DGMGRL for 32-bit Windows: Version 11.1.0.6.0 - Production
    Copyright (c) 2000, 2005, Oracle. All rights reserved.
    Welcome to DGMGRL, type "help" for information.
    DGMGRL>
    DGMGRL> connect sys/[email protected]
    Connected.
    DGMGRL>
    DGMGRL>
    DGMGRL> convert database 'i11g1sb' to snapshot standby;
    Converting database "i11g1sb" to a Snapshot Standby database, please wait...
    Database "i11g1sb" converted successfully
    DGMGRL> show configuration
    Configuration
    Name: DGConfig1
    Enabled: YES
    Protection Mode: MaxPerformance
    Databases:
    i11g1 - Primary database
    i11g1sb - Snapshot standby database
    Fast-Start Failover: DISABLED
    Current status for "DGConfig1":
    Warning: ORA-16607: one or more databases have failed
    DGMGRL> show configuration
    Configuration
    Name: DGConfig1
    Enabled: YES
    Protection Mode: MaxPerformance
    Databases:
    i11g1 - Primary database
    i11g1sb - Snapshot standby database
    Fast-Start Failover: DISABLED
    Current status for "DGConfig1":
    Warning: ORA-16607: one or more databases have failed
    DGMGRL> show database 'i11g1sb';
    Database
    Name: i11g1sb
    Role: SNAPSHOT STANDBY
    Enabled: YES
    Intended State: APPLY-OFF
    Instance(s):
    i11g1sb
    Current status for "i11g1sb":
    SUCCESS
    DGMGRL> show database 'i11g1';
    Database
    Name: i11g1
    Role: PRIMARY
    Enabled: YES
    Intended State: TRANSPORT-ON
    Instance(s):
    i11g1
    Current status for "i11g1":
    Error: ORA-16778: redo transport error for one or more databases
    DGMGRL> exit
    Not sure if the following (notice the typo in the service name) in the parameter (log_archive_dest_2) definition on the standby d/b has anything to do with this. I did not get this error when I initially converted to s-sb.
    also I checked all my session notes, I did not type the command to set this parameter on the standby d/b and so it was not a typo on my part. However, it seems to have come from the rman script supplied with the obe. This script is supposed to clone the primary d/b to a standby db and in the process replace the string /i11g1/ with /i11g1sb/.
    SQL> show parameter log_archive_dest_2
    NAME TYPE VALUE
    log_archive_dest_2 string service=i11g1sbsb async valid_
    for=(online_logfile,primary_ro
    le) db_unique_name=i11g1sb
    SQL>
    SQL>
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    i11g1sb
    SQL>
    Given all this, the archive logs seem to be shipping correctly to the sby d/b.
    "i11g1sb >"cd C:\app\MMJ\flash_recovery_area\i11g1sb\ARCHIVELOG\2009_03_30
    "i11g1sb >"dir
    Volume in drive C is Local Disk
    Volume Serial Number is 3189-6472
    Directory of C:\app\MMJ\flash_recovery_area\i11g1sb\ARCHIVELOG\2009_03_30
    30/03/2009 09:05 PM <DIR> .
    30/03/2009 09:05 PM <DIR> ..
    30/03/2009 05:41 PM 35,627,008 O1_MF_1_137_4X2H4JJM_.ARC
    30/03/2009 05:41 PM 1,910,784 O1_MF_1_138_4X2H4LVC_.ARC
    30/03/2009 09:04 PM 10,447,360 O1_MF_1_139_4X2V03RW_.ARC
    30/03/2009 09:05 PM 8,654,848 O1_MF_1_140_4X2V3BWB_.ARC
    4 File(s) 56,640,000 bytes
    2 Dir(s) 39,716,225,024 bytes free
    "i11g1sb >"
    "i11g1 >"dir
    Volume in drive C is Local Disk
    Volume Serial Number is 3189-6472
    Directory of C:\app\MMJ\flash_recovery_area\I11G1\ARCHIVELOG\2009_03_30
    30/03/2009 09:05 PM <DIR> .
    30/03/2009 09:05 PM <DIR> ..
    30/03/2009 04:09 PM 35,627,008 O1_MF_1_137_4X29QHTV_.ARC
    30/03/2009 04:24 PM 1,910,784 O1_MF_1_138_4X2BMOC7_.ARC
    30/03/2009 06:32 PM 10,447,360 O1_MF_1_139_4X2L4J3X_.ARC
    30/03/2009 09:05 PM 8,654,848 O1_MF_1_140_4X2V37KL_.ARC
    4 File(s) 56,640,000 bytes
    2 Dir(s) 39,716,229,120 bytes free
    I am tempted to start all over again, but I'd rather use this opportunity to debug this issue (as a learning exercise). I can always start from scratch. That brings up another Q: What do I need to do to blow away all traces of the stand by database (including all the archive logs etc...) keeping my primary intact. I'd also like to blow away all snapshot and archive logs for the primary as well.

  • Manual Standby Database (10.2.0.2.0) on Windows 2003 R2

    Hi,
    We are setting up a standby database on a remote site for a simple oracle DB. As we already have a standby/master for another Oracle DB (from SAP) we want to stay as close as possible as what already exist.
    For the SAP Oracle standby, we are copying manualy all archive to the stand by and apply them with brarchive. All is working fine.
    For the new standby, we can not use brarchive as there is no SAP install on the standby but we stay with the "manual" copy of the archive from the master to the standby (using robocpy). It means all archive are on the standby (K:\oracle\oradata\archive).
    The creation of the standby DB seems to be OK as i can open it, but i can't manage to apply de redo logs.
    I'm quite new to oracle, so it's maybe a very basic issue, but i've already spent 3 days on it...
    To start the DB, we lauch a bat script :
    sqlplus /nolog @c:\backup\standby.sql
    pause
    the standby.sql:
    connect /@TECDB01 as sysdba
    startup nomount;
    alter database mount standby database;
    exit;
    Then i connect to sqlplus and enter:
    alter database recover managed standby database;
    In another sqlplus session :
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    wich give me :
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MR(fg) WAIT_FOR_GAP 1 45400 0 0
    RFS IDLE 0 0 0 0
    The sequence 45400 seems to be ok regarding the time of the backup restored on the standby.
    The archive is well on the server, but it won't apply it.
    The Alert_TECDB01.log :
    Fri Oct 29 11:03:43 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =121
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.2.0.
    System parameters with non-default values:
    processes                = 999
    sga_target               = 7214202880
    control_files            = I:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, J:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, K:\ORACLE\ORADATA\CNTRL\STANDBY.CTL
    db_block_size            = 8192
    compatible               = 10.2.0.2.0
    log_archive_dest_1       = LOCATION=K:\oracle\oradata\archive
    log_archive_dest_2       = SERVICE=TECDB01
    log_archive_dest_state_1 = enable
    log_archive_dest_state_2 = enable
    standby_archive_dest     = K:\oracle\oradata\archive
    archive_lag_target       = 1800
    db_file_multiblock_read_count= 16
    undo_management          = AUTO
    undo_tablespace          = RBS
    undo_retention           = 10800
    recyclebin               = OFF
    remote_login_passwordfile= EXCLUSIVE
    db_domain                = WORLD
    dispatchers              = (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)
    shared_servers           = 100
    local_listener           = (ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))
    session_cached_cursors   = 300
    utl_file_dir             = \\srvuniway.vrithoff.srwt.tec-wl.be\hotspots
    job_queue_processes      = 10
    audit_file_dest          = I:\ORACLE\ADMIN\TECDB01\ADUMP
    background_dump_dest     = I:\ORACLE\ADMIN\TECDB01\BDUMP
    user_dump_dest           = I:\ORACLE\ADMIN\TECDB01\UDUMP
    core_dump_dest           = I:\ORACLE\ADMIN\TECDB01\CDUMP
    db_name                  = TECDB01
    open_cursors             = 3000
    pga_aggregate_target     = 1086324736
    PMON started with pid=2, OS id=4012
    PSP0 started with pid=3, OS id=3856
    MMAN started with pid=4, OS id=3580
    DBW0 started with pid=5, OS id=1084
    LGWR started with pid=6, OS id=576
    CKPT started with pid=7, OS id=3516
    SMON started with pid=8, OS id=508
    RECO started with pid=9, OS id=3068
    CJQ0 started with pid=10, OS id=2448
    MMON started with pid=11, OS id=2840
    MMNL started with pid=12, OS id=3024
    Fri Oct 29 11:03:44 2010
    starting up 4 dispatcher(s) for network address '(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))'...
    starting up 100 shared server(s) ...
    Fri Oct 29 11:03:45 2010
    alter database mount standby database
    Fri Oct 29 11:03:51 2010
    Setting recovery target incarnation to 2
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=118, OS id=3584
    Fri Oct 29 11:03:51 2010
    ARC0: Archival started
    ARC1 started with pid=119, OS id=3688
    Fri Oct 29 11:03:51 2010
    ARC1: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Fri Oct 29 11:03:51 2010
    ARC0: Becoming the 'no FAL' ARCH
    Fri Oct 29 11:03:51 2010
    Successful mount of redo thread 1, with mount id 3987142355
    Fri Oct 29 11:03:51 2010
    ARC0: Becoming the 'no SRL' ARCH
    Fri Oct 29 11:03:51 2010
    ARC1: Becoming the heartbeat ARCH
    Fri Oct 29 11:03:51 2010
    Physical Standby Database mounted.
    Completed: alter database mount standby database
    Fri Oct 29 11:04:06 2010
    alter database recover managed standby database
    Fri Oct 29 11:04:06 2010
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Media Recovery Waiting for thread 1 sequence 45400
    Fetching gap sequence in thread 1, gap sequence 45400-45499
    +FAL[client]: Error fetching gap sequence, no FAL server specified+
    Fri Oct 29 11:04:37 2010
    +FAL[client]: Failed to request gap sequence+
    GAP - thread 1 sequence 45400-45499
    DBID 3776455083 branch 670241032
    +FAL[client]: All defined FAL servers have been attempted.+
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    Fri Oct 29 11:04:51 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 3452
    RFS[1]: Identified database type as 'physical standby'
    Fri Oct 29 11:04:51 2010
    RFS LogMiner: Client disabled from further notification
    The tecdb01_arc1_3688.trc :
    Dump file i:\oracle\admin\tecdb01\bdump\tecdb01_arc1_3688.trc
    Fri Oct 29 11:03:51 2010
    ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    Windows NT Version V5.2 Service Pack 2
    CPU                 : 8 - type 8664, 2 Physical Cores
    Process Affinity    : 0x0000000000000000
    Memory (Avail/Total): Ph:7467M/9215M, PhPgF:2454M/10796M+
    Instance name: tecdb01
    Redo thread mounted by this instance: 1
    Oracle process number: 119
    Windows thread id: 3688, image: ORACLE.EXE (ARC1)
    *** SERVICE NAME:() 2010-10-29 11:03:51.177
    *** SESSION ID:(1088.1) 2010-10-29 11:03:51.177
    kcrrwkx: nothing to do (start)
    *** 2010-10-29 11:04:51.129
    Redo shipping client performing standby login
    *** 2010-10-29 11:04:51.176 64529 kcrr.c
    Logged on to standby successfully
    Client logon and security negotiation successful!
    kcrrwkx: nothing to do (end)
    *** 2010-10-29 11:05:51.285
    kcrrwkx: nothing to do (end)
    *** 2010-10-29 11:06:51.300
    kcrrwkx: nothing to do (end)
    The initTECDB01.ora :
    # Copyright (c) 1991, 2001, 2002 by Oracle Corporation
    # Archive
    archive_lag_target=1800
    log_archive_dest_1='LOCATION=K:\oracle\oradata\archive'
    # Cache and I/O
    db_block_size=8192
    db_file_multiblock_read_count=16
    # Cursors and Library Cache
    open_cursors=3000
    session_cached_cursors=300
    # Database Identification
    db_domain=WORLD
    db_name=TECDB01
    # Diagnostics and Statistics
    background_dump_dest=I:\oracle\admin\TECDB01\bdump
    core_dump_dest=I:\oracle\admin\TECDB01\cdump
    user_dump_dest=I:\oracle\admin\TECDB01\udump
    # File Configuration
    control_files=("I:\oracle\oradata\cntrl\standby.ctl", "J:\oracle\oradata\cntrl\standby.ctl", "K:\oracle\oradata\cntrl\standby.ctl")
    # Job Queues
    job_queue_processes=10
    # Miscellaneous
    compatible=10.2.0.2.0
    recyclebin=OFF
    # Processes and Sessions
    processes=999
    # SGA Memory
    sga_target=6880M
    # Pools
    #java_pool_size=150M
    # Security and Auditing
    audit_file_dest=I:\oracle\admin\TECDB01\adump
    remote_login_passwordfile=EXCLUSIVE
    # Shared Server
    shared_servers=100
    dispatchers="(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)"
    #dispatchers="(PROTOCOL=TCP) (SERVICE=TECDB01XDB)"
    # Sort, Hash Joins, Bitmap Indexes
    pga_aggregate_target=1036M
    # System Managed Undo and Rollback Segments
    undo_management=AUTO
    undo_retention=10800
    undo_tablespace=RBS
    local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))"
    # NIDA - 28.10.2010 - redo apply
    log_archive_dest_state_1=enable
    log_archive_dest_2 = 'SERVICE=TECDB01'
    log_archive_dest_state_2=enable
    #standby_file_management=auto
    standby_archive_dest=K:\oracle\oradata\archive
    And the TNSNAMES.ora :
    # tnsnames.ora Network Configuration File: C:\oracle\102\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    #this is the standby
    TECDB01.VRITHOFF.SRWT.TEC-WL.BE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.92)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = TECDB01)
    # This file is written by Oracle Services For MSCS
    # on Sat Nov 08 10:44:27 2008
    #this is the master
    PRIMARY.VRITHOFF.SRWT.TEC-WL.BE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.246)(PORT = 1521))
    (CONNECT_DATA =
    (SID = TECDB01)
    EXTPROC_CONNECTION_DATA.VRITHOFF.SRWT.TEC-WL.BE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = TECDB01))
    (CONNECT_DATA =
    (SERVICE_NAME = TECDB01)
    Hope you have all information to bring me in the right way.
    Regards,
    Nicolas

    Hi,
    The recover automatic is working fine, but I still have problems with the recover managed
    Here is the Alert log :(the 46626 was there at 11:30)
    Mon Nov 15 11:31:13 2010
    alter database recover managed standby database using current logfile
    Managed Standby Recovery starting Real Time Apply
    parallel recovery started with 7 processes
    Media Recovery Waiting for thread 1 sequence 46626
    Mon Nov 15 16:36:01 2010
    alter database recover managed standby database cancel
    Mon Nov 15 16:36:05 2010
    Managed Standby Recovery not using Real Time Apply
    Recovery interrupted!
    Mon Nov 15 16:36:06 2010
    Media Recovery user canceled with status 16037
    ORA-16043 signalled during: alter database recover managed standby database using current logfile...
    Mon Nov 15 16:36:07 2010
    Completed: alter database recover managed standby database cancel
    Mon Nov 15 16:36:37 2010
    ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
    Mon Nov 15 16:36:37 2010
    Media Recovery Start
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Mon Nov 15 16:36:39 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46626_0670241032.001
    Mon Nov 15 16:36:45 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46627_0670241032.001
    Mon Nov 15 16:37:11 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46628_0670241032.001
    Mon Nov 15 16:37:30 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46629_0670241032.001
    Mon Nov 15 16:37:48 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46630_0670241032.001
    Mon Nov 15 16:37:59 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46631_0670241032.001
    Mon Nov 15 16:38:15 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46632_0670241032.001
    Mon Nov 15 16:38:28 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46633_0670241032.001
    Mon Nov 15 16:38:47 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46634_0670241032.001
    Mon Nov 15 16:39:34 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46635_0670241032.001
    Mon Nov 15 16:40:43 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46636_0670241032.001
    Mon Nov 15 16:42:03 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46637_0670241032.001
    Mon Nov 15 16:43:18 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46638_0670241032.001
    Mon Nov 15 16:44:38 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46639_0670241032.001
    Mon Nov 15 16:45:45 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46640_0670241032.001
    Mon Nov 15 16:46:37 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46641_0670241032.001
    Mon Nov 15 16:47:48 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46642_0670241032.001
    Mon Nov 15 16:49:07 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46643_0670241032.001
    Mon Nov 15 16:50:04 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46644_0670241032.001
    Mon Nov 15 16:51:13 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46645_0670241032.001
    Mon Nov 15 16:52:16 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46646_0670241032.001
    Mon Nov 15 16:53:07 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46647_0670241032.001
    Mon Nov 15 16:54:28 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46648_0670241032.001
    Mon Nov 15 16:55:47 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46649_0670241032.001
    Mon Nov 15 16:56:35 2010
    Incomplete Recovery applied until change 4037420604
    Completed: ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
    I don't catch why the system wait for a sequence that is available...
    Regards,
    Nico

  • ORA-10458: standby database requires recovery

    hi
    kindly help me... i got error when standby open in read only mode
    SQL*Plus: Release 11.2.0.3.0 Production on Sat Jan 19 14:37:46 2013
    Copyright (c) 1982, 2011, Oracle. All rights reserved.
    Connected to an idle instance.
    SQL> startup mount
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
    ORACLE instance started.
    Total System Global Area 5344731136 bytes
    Fixed Size 2237776 bytes
    Variable Size 1275071152 bytes
    Database Buffers 4060086272 bytes
    Redo Buffers 7335936 bytes
    Database mounted.
    SQL> Alter Database Recover Managed Standby Database Disconnect;
    Database altered.
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Database altered.
    SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-10458: standby database requires recovery
    ORA-01152: file 22 was not restored from a sufficiently old backup
    ORA-01110: data file 22: '/archive/data/undo01.dbf'

    hi CKPT
    I executed the action plan as you recommend and got below information;
    SQL> recover standby database;
    ORA-00279: change 5983485554580 generated at 01/01/2013 19:27:17 needed for
    thread 1
    ORA-00289: suggestion : /archive/PROD_1_750568044_45027.ARC
    ORA-00280: change 5983485554580 for thread 1 is in sequence #45027
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    '/archive/PROD_1_750568044_45400.ARC'
    ORA-00310: archived log contains sequence 45400; sequence 45027 required
    ORA-00334: archived log: '/archive/PROD_1_750568044_45400.ARC'
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 22 was not restored from a sufficiently old backup
    ORA-01110: data file 22: '/archive/data/undo01.dbf'
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01666: control file is for a standby database
    SQL> alter system switch logfile;
    alter system switch logfile
    ERROR at line 1:
    ORA-01109: database not open
    ---------------------------------- and some other activity but still not found any solution-------------
    RMAN> recover database until sequence
    2> 45026;
    Starting recover at 23-JAN-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/23/2013 16:42:47
    RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484595990
    RMAN> recover database until sequence 45027;
    Starting recover at 23-JAN-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/23/2013 16:42:59
    RMAN-06556: datafile 22 must be restored from backup older than SCN 5983485554580
    RMAN> recover database until sequence 45025;
    Starting recover at 23-JAN-13
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/23/2013 16:43:09
    RMAN-06556: datafile 1 must be restored from backup older than SCN 5983484160276
    RMAN> alter database open resetlogs;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of alter db command at 01/23/2013 16:43:25
    ORA-01666: control file is for a standby database

  • Standby database not configure while keep database files in different place

    Dear Friends ,
    I have to successfully configured "PHYSICAL STANDBY DATABASE" within the TWO databases ("PRIM" and "STAN" Database) when I kept datafile, controlfile and redolog files in the same location (like, "/u01/app/oracle/oradata/prim" location .
    In this successful configuration , I have to add the below two lines into the initprim.ora and initstan.ora both server respectively ...
    initprim.ora:
    ========
    DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/stan','/u01/app/oracle/oradata/prim'
    LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/stan','/u01/app/oracle/flash_recovery_area/prim'
    initstan.ora:
    ========
    DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/prim','/u01/app/oracle/oradata/stan'
    LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/prim','/u01/app/oracle/flash_recovery_area/stan'Now , in second scenario , I have to change Primary database server's datafile, controlfile and redolog file in the below folder :
    controlfile --> "/u01/app/oracle/oradata/prim/ctrlfile"
    redologfile --> "/u01/app/oracle/oradata/prim/redofile"
    datafile --> "/u01/app/oracle/oradata/prim/datafile"
    Similarly I have to create same folder in my STAN database server accordingly . and also add the above lines in same way :
    initprim.ora:
    ========
    DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/stan','/u01/app/oracle/oradata/prim'
    LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/stan','/u01/app/oracle/flash_recovery_area/prim'
    initstan.ora:
    ========
    DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/prim','/u01/app/oracle/oradata/stan'
    LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/prim','/u01/app/oracle/flash_recovery_area/stan'Keeping the above situation when I run the below command in STAN database server :
    [oracle@test ~]$ sqlplus /nolog
    SQL*Plus: Release 10.2.0.1.0 - Production on Mon Nov 15 23:15:43 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    SQL> conn / as sysdba
    Connected to an idle instance.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 599785472 bytes
    Fixed Size 1220772 bytes
    Variable Size 163581788 bytes
    Database Buffers 427819008 bytes
    Redo Buffers 7163904 bytes
    Database mounted.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    The Command execute successfully but in the alert log of the STAN database server ,I get the below error :
    Completed: alter database recover managed standby database disconnect from session
    Mon Nov 15 22:46:52 2010
    Clearing online redo logfile 1 complete
    Mon Nov 15 22:46:52 2010
    Errors in file /u01/app/oracle/admin/stan/bdump/stan_mrp0_3695.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/prim/redofile/redo02.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Mon Nov 15 22:46:52 2010
    Errors in file /u01/app/oracle/admin/stan/bdump/stan_mrp0_3695.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/prim/redofile/redo02.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3But I already created the above mention folder "'/u01/app/oracle/oradata/prim/redofile" successfully and the redo log files are also created there successfully , but I cannot understand why this error is showed ? And also no archivelogs are shifted from PRIM database server to STAN database server .
    Would u plz suggest me , why I cannot configure Physical Standby Database when I keep my database fles in the separate location ?
    help me plz ... ...

    Hi,
    I'm missing the steps you took renaming/moving the files on the primary.
    Since the location of datafiles is stored in the control file the controlfile of the standby might not know the new location yet.
    I suggest you read this http://www.cs.bris.ac.uk/maintain/OracleDocs/server.816/a76995/standby.htm#23603 and see if that helps
    Success,
    FJFranken

  • Standby Database  in Prod

    Hi all,
    BANNER----------------------------------------------------------------
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bi
    PL/SQL Release 10.2.0.2.0 - Production
    CORE 10.2.0.2.0 Production
    TNS for Solaris: Version 10.2.0.2.0 - Production
    NLSRTL Version 10.2.0.2.0 - Production
    OS Version
    SecondaryDB>uname -a
    SunOS 5.10 Generic_138888-03 sun4v sparc SUNW,Sun-Blade-T6320
    I am facing issue in Standby Database ,i had done all recovery from RMAN & morover i had used Primary controlfile as a standby controlfile in standby database . evrything is fine ,RFS is working archives are coming from primary to standby ,but the prblm with the MRP Process ,when i m fired the comm
    SQL>Recover managed standby database disconnect from session ;
    in the alert log file its show below errors:-
    Fri Oct 7 09:03:26 2011
    Completed: ALTER DATABASE RECOVER managed standby database disconnect from session
    Fri Oct 7 09:04:44 2011
    RFS[3]: No standby redo logfiles created
    Fri Oct 7 09:04:55 2011
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 100032-100131
    DBID 3896382872 branch 684626292
    FAL[client]: All defined FAL servers have been attempted.
    SQL> select * from v$archive_gap;
    no rows selected
    SQL> select SEQUENCE#,ARCHIVED,APPLIED,STATUS from v$archived_log;
    SEQUENCE# ARC APP S
    102069 YES NO A
    102067 YES NO A
    102068 YES NO A
    102070 YES NO A
    102071 YES NO A
    SQL> select process,status from v$managed_standby ;
    PROCESS STATUS
    ARCH CONNECTED
    ARCH CONNECTED
    ARCH CONNECTED
    ARCH CONNECTED
    RFS IDLE
    RFS IDLE
    RFS IDLE
    MRP0 WAIT_FOR_GAP
    8 rows selected.
    SQL> select error from v$archive_dest;
    ERROR
    11 rows selected.
    SQL> select MAx(SEQUENCE#) from v$log_history;
    MAX(SEQUENCE#)
    102066
    SQL>
    i don;t know why MRP is not working properly and again & again showing this GAP Squence error .
    Please Help me out i am waiting for your helpful answer.
    Thanks

    yes that 100032 is present in primary but in zip format ,when i extract and go for manul register its give me courputed archive.
    after that i used incremental Rman strategy with the SCN . & i applied all process of rman
    From Primary
    SQL> Select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    102074
    SQL>
    from Physical Standby
    SQL> Select max(sequence#) from v$archived_log where applied='YES' ;
    MAX(SEQUENCE#)
    SQL>
    thanks

  • Standby database failover flashback restart as standby gap 1-100

    Hi,
    I have setup a physical standby database for a 3 node RAC primary database and configured the database to run in MAXIMUM AVAILABILITY mode. Both the primary and standby databases use ASM for managing the IO. I have enabled FLASHBACK ON on both the databases.
    I did failover to standby database with primary db SHUTDOWN for doing some testing. After testing is done, I flashbacked the (standby, currently primary)database to the point when it became primary and start it as standby again and the old primary as primary.
    Following are the steps:
    Failover steps
    .Shutdown the primary database
    To finisish the recovery at standby
    SQL>alter database recover managed standby database finish;
    To start as primary
    SQL>alter database commit to switchover to primary;
    do some DML on the new primary
    SQL>flashback database to scn <standby_became_primary_scn>;
    SQL>alter database create standby controlfile as '/backup/standby.ctl';
    Changed the spfile to point control_files to '/backup/standby.ctl';
    Restarted the standby db in mount mode and
    created the required stanbdy logs on it.
    Then issued
    SQL>alter database recover managed standby database using current logfile disconnect;
    I have the following message in v$dataguard_status at standby db;
    Fetching gap sequence in thread 1 branch(resetlogs_id) 653234404, gap seq 1-100
    DBID 2651011616 branch 653234404
    GAP - thread 1 sequence 1-100
    FAL[client]: Failed to request gap sequence
    FAL[client]: All defined FAL servers have been attempted.
    The same error is found in alert log file also.
    The status of the varioud managed standby db are as follows.
    SQL> select process, status from v$managed_standby;
    PROCESS STATUS
    ARCH CLOSING
    ARCH CLOSING
    ARCH CLOSING
    MRP0 WAIT_FOR_GAP
    RFS IDLE
    RFS IDLE
    RFS IDLE
    RFS IDLE
    RFS IDLE
    RFS IDLE
    RFS IDLE
    PROCESS STATUS
    RFS IDLE
    RFS IDLE
    RFS IDLE
    RFS IDLE
    15 rows selected.
    SQL>
    Could you please help me how to resolve the above error.
    Thanks,
    Sreekanth

    Sreekanth,
    I think your steps are right on for your requirement, except instead of
    alter database create standby controlfile as '/backup/standby.ctl';
    you can do this:
    ALTER DATABASE CONVERT TO PHYSICAL STANDBY;
    (although perhaps it achieves the same thing internally but you don't need to repoint to new controlfile).
    So far as the GAP - thread 1 sequence 1-100
    Let me guess, your current sequences are probably well ahead of this reported gap?
    If so, this is a bogus gap in a sense that your standby has long ago applied them, but for some reason standby controlfile gets a little confused and starts asking for them again.
    I have had this issue and opened multiple TAR's with Oracle since 10.2.0.1, got a few patches and advises to upgrade, but still occasionally get it now in 10.2.0.3
    I strongly believe this is related to combination of RAC (i.e. multiple threads of redo) and dataguard.
    It is also pretty hard to reproduce (I have not figured out how to reproduce this reliably, if you have, let me know), so I can understand why Oracle has so far been unable to fix this.
    Anyway, the workaround is to re-create standby controlfile with a copy generated on primary, and move it in place of the existing (and confused) controlfiles on standby.

  • Physical standby database error

    Hi,
    I try to create physical standby in my local machine using oracle 10g
    version :10.2.0.1.0
    Os: windows xp.
    I followed steps and parameter files
    on primary :-
    sql>alter database force logging;
    orcl.__db_cache_size=155189248
    orcl.__java_pool_size=4194304
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=75497472
    orcl.__streams_pool_size=0
    *.audit_file_dest='D:\oracle\product\10.2.0/admin/orcl/adump'
    *.background_dump_dest='D:\oracle\product\10.2.0/admin/orcl/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='D:\oracle\product\10.2.0\oradata\orcl\control01.ctl','D:\oracl
    e\product\10.2.0\oradata\orcl\control02.ctl','D:\oracle\product\10.2.0\orad
    ata\orcl\control03.ctl'
    *.core_dump_dest='D:\oracle\product\10.2.0/admin/orcl/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_unique_name='orcl'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=80740352
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=244318208
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\oracle\product\10.2.0/admin/orcl/udump'
    *.log_archive_dest_1='LOCATION=D:\oracle\archive
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl'
    *.log_archive_dest_2='SERVICE=stby LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
    *.log_archive_format=%t_%s_%r.arc
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    On standby
    orcl.__db_cache_size=155189248
    orcl.__java_pool_size=4194304
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=75497472
    orcl.__streams_pool_size=0
    *.audit_file_dest='D:\stby\adump'
    *.background_dump_dest='D:\stby\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='D:\stby\ctrl.ctl'
    *.core_dump_dest='D:\stby\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_unique_name='stby'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=80740352
    *.processes=150
    *.remote_login_passwordfile='NONE'
    *.sga_target=244318208
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\stby\udump'
    *.db_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
    *.log_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
    *.log_archive_dest_1='LOCATION=D:\oracle\archive
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
    *.log_archive_dest_2='SERVICE=orcl LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=orcl'
    *.standby_archive_dest='D:\stby\archive'
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    *.standby_file_management='AUTO'
    *.fal_server='orcl'
    *.fal_client='stby'
    SQL> conn / as sysdba
    Connected to an idle instance.
    SQL> startup pfile=D:\stby\initstby.ora nomount;
    ORACLE instance started.
    Total System Global Area 247463936 bytes
    Fixed Size 1248332 bytes
    Variable Size 79692724 bytes
    Database Buffers 159383552 bytes
    Redo Buffers 7139328 bytes
    SQL> alter database mount standby database;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> alter database open read only;
    alter database open read only
    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 open read only;
    Database altered.
    SQL> select sequence#,first_time,next_time from v$archived_log order by sequence
    no rows selected
    No archive s generated in standby ..
    what i mistake.
    Reagrds
    S.Azar

    Anand... wrote:
    Firstly you can use "*select sequence#,first_time,next_time from v$archived_log order by sequence#;"* command in mount stage itself.No need to open the standby database in ready only mode.
    No rows selected in mount stage also.
    The V$ARCHIVED_LOG fixed view on the physical standby database shows all the archived redo log files received from the primary database.
    sql> select * from v$archived_log;
    no rows selected.
    and No archived logs received from primary database to physical standby . i think here i wrongly configure parameter file.
    sql> RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; -- > start Redo Apply
    When you do log switch on the primary are the archive logs getting transferred to the standby database???Is there some error in the alert log file in the primary database.
    No..
    >
    [http://advait.wordpress.com/2007/06/12/setting-up-oracle-dataguard-for-10g/]
    Regards
    S.Azar

  • Configure standby database

    hi all;
    how many system r required to configure standby database
    i m configure standby database in a single(same) system where my primary database already running.if this possible or not
    i have configured my standby
    but when i start "c:\sqlplus sys@orclstdy as sysdba"
    then he create error ora-12154: TNS:could not resolve the connect identifier specified
    and when i start with "c:\set oracl_sid=orclstdy"
    sql>conn as sys/pass as sysdba
    connected to an idle instance
    sql> startup
    ora-02778: Name given for the log directory is invalid
    how can solve this problem . please reply

    Hi user569791
    you can configure standby to multiple destinations(up to 9 different destinations) and it is also possible to configure in same system also.
    you need to create standby controlfile for Physical standby database.
    check whether the standby instance run as a separate service and whether you
    have an relevant entry in tnsnames.ora file. note that the db_name is same for both
    sites but only the instance name differs.
    Ensure that you have a
    1.valid cold backup of datafiles,
    2.valid standby controlfile
    3.standby init parameters with db_file_name_convert and log_file_name_convert
    parameters are valid
    4. a special init parameter called lock_name_space need to be given when you configure standby on same site.
    check all these condition and Try again.
    Regards
    SM

  • 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

  • Standby database SWITCHOVER_STATUS field is always NOT ALLOWED

    standby database:
    SQL> select switchover_status from v$database;
    SWITCHOVER_STATUS
    NOT ALLOWED
    select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
    DB_UNIQUE_NAME          DATABASE_ROLE     OPEN_MODE LOG_MODE     PROTECTION_MODE
    omu0               PHYSICAL STANDBY MOUNTED ARCHIVELOG     MAXIMUM AVAILABILITY
    select process,status,client_process,sequence# from v$managed_standby;
    PROCESS STATUS CLIENT_P SEQUENCE#
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CLOSING ARCH     539
    ARCH     CONNECTED ARCH          0
    ARCH     CLOSING ARCH     540
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    MRP0     APPLYING_LOG N/A     541
    RFS     IDLE     LGWR     541
    RFS     IDLE     ARCH          0
    RFS     IDLE     N/A          0

    primary datase:
    SQL> select switchover_status from v$database;
    SWITCHOVER_STATUS
    SESSIONS ACTIVE
    select db_unique_name,database_role,open_mode,log_mode,protection_mode from v$database;
    DB_UNIQUE_NAME          DATABASE_ROLE     OPEN_MODE LOG_MODE     PROTECTION_MODE
    omu2               PRIMARY          READ WRITE ARCHIVELOG     MAXIMUM AVAILABILITY
    select process,status,client_process,sequence# from v$managed_standby;
    PROCESS STATUS CLIENT_P SEQUENCE#
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CLOSING ARCH     541
    ARCH     CLOSING ARCH     542
    ARCH     CLOSING ARCH     543
    ARCH     CLOSING ARCH     544
    ARCH     CLOSING ARCH     545
    ARCH     CLOSING ARCH     546
    ARCH     CLOSING ARCH     547
    ARCH     CLOSING ARCH     548
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CLOSING ARCH     540
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    ARCH     CONNECTED ARCH          0
    LGWR     WRITING LGWR     549
    31 rows selected.

  • What is Media Recovery Log ..? Physical Standby Database

    Hello All,
    In my physical stdby database alert log I could see the below message, I'm not sure what id Media Recovery Log and why it is dumping ORACLE_HOME Directory..?
    Could any one please help on this..? I need to house keep ORACLE_HOME directory.
    Oracle 11gR2 / RHEL5
    RFS[164]: No standby redo logfiles available for thread 2
    RFS[164]: Opened log for thread 2 sequence 1995 dbid 287450012 branch 760028574
    Fri Nov 11 19:39:05 2011
    Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1992_760028574.dbf
    Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1993_760028574.dbf
    Media Recovery Waiting for thread 1 sequence 5568 (in transit)
    Fri Nov 11 19:39:53 2011
    Archived Log entry 948 added for thread 2 sequence 1994 rlc 760028574 ID 0x1122a1
    FYI : The primary and standby database are in sync.

    Hello;
    The alert log is providing you with information. If you want more run this query :
    select process,status,client_process,sequence# from v$managed_standby;You should see processes like ARCH, RFS and MRP0.
    MRP will tell you if its applying log(s), waiting for a log, or if it thinks there's a gap.
    PROCESS   STATUS       CLIENT_P  SEQUENCE#
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    MRP0      APPLYING_LOG N/A            5051
    RFS       IDLE         N/A               0
    RFS       IDLE         UNKNOWN           0There's a tiny amount of information about this under "9.3.1 Adding a Datafile or Creating a Tablespace" in Oracle document E10700-02.
    If you find this helpful please click the "helpful" button.
    Best Regards
    mseberg

  • Duplicate archivelog sequence on standby database

    Hi,
    In our standby database when i check archivelog (below command), i see 2 duplicate sequence number. One is applied and another is not applied. Is there any problem with dataguard and how to solve it
    TQ
    SQL> sELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG where SEQUENCE# like '369%' order by SEQUENCE#;
    THREAD# SEQUENCE# APP
    1 36900 YES
    1 36901 YES
    1 36902 YES
    1 36902 NO
    1 36903 YES
    1 36903 YES
    1 36904 YES
    1 36904 YES
    1 36905 YES
    1 36905 NO
    1 36906 YES
    1 36907 YES
    1 36908 YES
    1 36909 YES
    1 36910 YES
    1 36911 YES
    1 36911 NO
    1 36912 YES
    1 36912 NO
    1 36913 YES
    1 36913 YES
    1 36914 YES
    1 36914 NO
    1 36915 YES
    1 36915 NO
    1 36916 YES
    1 36917 YES
    1 36918 YES
    1 36919 YES
    1 36919 YES
    1 36920 YES

    Result At primary
    ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
    1 VALID OPEN ARCH IDLE MAXIMUM PERFORMANCE 0 0 38320
    2 VALID UNKNOWN ARCH UNKNOWN MAXIMUM PERFORMANCE 7 7 38318
    archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /xxx/xxx
    Oldest online log sequence 38316
    Next log sequence to archive 0
    Current log sequence 38321
    Result at standby
    ID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE ARCHIVED_SEQ#
    1 VALID MOUNTED-STANDBY ARCH MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE 0 0 38316
    11 VALID MOUNTED-STANDBY ARCH MANAGED REAL TIME APPLY MAXIMUM PERFORMANCE 0 0 38318
    archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /xxx/xxx
    Oldest online log sequence 38316
    Next log sequence to archive 0
    Current log sequence 38321

Maybe you are looking for