Multi-Instance Standby Database

Hi,
Please let me know how to setup multiple-instance dataguard for 2 node RAC.
I want to setup 2 Instance Standby (dataguard) Database for 2 node RAC.
Thanks,

930109 wrote:
Hi,
Please let me know how to setup multiple-instance dataguard for 2 node RAC.
I want to setup 2 Instance Standby (dataguard) Database for 2 node RAC.
Thanks,What is the version?
Yes, you can configure RAC to RAC primary and standby, Please refer MAA document http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimaryracphysicalsta-131940.pdf
Above 10g versions this document is applicable.

Similar Messages

  • How to setup a Multi-instance standby database?

    I was asked to setup a multi-instance standby database for a multi-instance primary database. I understand that only one of the instance will apply redo logs from the primary database, but how about the other instance? Should I mount that instance just to update the standby control file(the control file is not located in shared file system with the cluster server) even if it isn't going to apply any redo logs?
    I am so confused now. Hope somebody will help me on that. Any document or tutorial will be helpful too.
    Note that I am not using dataguard.
    Thanks in advance

    Hi,
    You can set up multiple instance standby..where in each instance will receive the archive logs from correpsonding primary instance. Keep them on shared location (say ASM) so that one of the instances from where recovery is started can access the archive logs and apply it.
    So basically
    Primary instance A <----- send archive to ---> Standby A
    Primary instance B <----- send archive to ---> Standby B
    Start managed recovery on A
    Standby A --- > Apply archives for instance A and B
    -Amit
    http://askdba.org/weblog/
    Edited by: Amit_DBA on Aug 12, 2009 5:16 PM

  • 10.2.0.4 patch on single instance standby database

    Hi All,
    We have production database 10.2.0.3 running with RAC having 2 nodes on Solaris 10. We have patched this
    databases to 10.2.0.4 (both nodes) on production without any issue.
    We have a physical standby database (10.2.0.3) with 2 nodes on solaris 10. But we have stopped node2 sometime
    back and currently it's a single instance standby database. Whe nwe are trying to apply patch to standby dataabse
    it's showing both node during installation and installation fails when it tries to search for node2.
    What's the solution for this problem? Any document on how to patch the single instance standby database when
    production is running in RAC.

    I think you are basically saying that you have a 2 node RAC cluster with 1 node down (possibly permanently) and you want to just patch 1 of the nodes?
    It's not overly a surprise the installer is trying to patch the other node, when as far as your inventory is concerned you have a 2 node cluster.
    Have you tried running the installer with the -local option?
    This should just patch your local node. Obviously the dictionary changes will get applied via MRP from the primary db.
    jason.
    http://jarneil.wordpress.com

  • Single instance standby for 2-node RAC

    Hi,
    Oracle Version:11.2.0.1
    Operating system:Linux
    Here i am planing to create single instance standby for my 2-node RAC database.Here i am creating my single instance standby database on 1-node of my 2-node RAC DB.
    1.) Do i need to configure any separate listener for my single instance standby in $ORACLE_HOME/network/admin in ORACLE user or need to change in Grid user login.
    2.) Below is the error when i am duplicating my primary 2-Node RAC to single instance DB. And it is shutting down my auxiliary instance.
    [oracle@rac1 ~]$ rman target / auxiliary sys/racdba123@stand
    Recovery Manager: Release 11.2.0.1.0 - Production on Sun Aug 28 13:32:29 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: RACDB (DBID=755897741)
    connected to auxiliary database: RACDB (not mounted)
    RMAN> duplicate database racdba to stand
    2> ;
    Starting Duplicate Db at 28-AUG-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=6 device type=DISK
    contents of Memory Script:
       sql clone "create spfile from memory";
    executing Memory Script
    sql statement: create spfile from memory
    contents of Memory Script:
       shutdown clone immediate;
       startup clone nomount;
    executing Memory Script
    Oracle instance shut down
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 08/28/2011 13:33:55
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptorAlso find my listener services.
    [oracle@rac1 ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:24
    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date                18-AUG-2011 10:35:07
    Uptime                    11 days 0 hr. 21 min. 17 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File   /u01/11.2.0/grid/network/admin/listener.ora
    Listener Log File         /u01/app/oracle/diag/tnslsnr/rac1/listener/alert/log.xml
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.123)(PORT=1521)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.127)(PORT=1521)))
    Services Summary...
    Service "+ASM" has 1 instance(s).
      Instance "+ASM1", status READY, has 1 handler(s) for this service...
    Service "RACDB" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Service "RACDBXDB" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Service "stand" has 2 instance(s).
      Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
      Instance "stand", status BLOCKED, has 1 handler(s) for this service...
    Service "testdb" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Service "testdb1" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
    The command completed successfully
    [oracle@rac1 ~]$ lsnrctl services
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:35
    Copyright (c) 1991, 2009, Oracle.  All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    Services Summary...
    Service "+ASM" has 1 instance(s).
      Instance "+ASM1", status READY, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:0 refused:0 state:ready
             LOCAL SERVER
    Service "RACDB" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:3 refused:0 state:ready
             LOCAL SERVER
    Service "RACDBXDB" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
        Handler(s):
          "D000" established:0 refused:0 current:0 max:1022 state:ready
             DISPATCHER <machine: rac1.qfund.net, pid: 3975>
             (ADDRESS=(PROTOCOL=tcp)(HOST=rac1.qfund.net)(PORT=43731))
    Service "stand" has 2 instance(s).
      Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:0 refused:0
             LOCAL SERVER
      Instance "stand", status BLOCKED, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:669 refused:0 state:ready
             LOCAL SERVER
    Service "testdb" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:3 refused:0 state:ready
             LOCAL SERVER
    Service "testdb1" has 1 instance(s).
      Instance "RACDB1", status READY, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:3 refused:0 state:ready
             LOCAL SERVER
    The command completed successfully
    [oracle@rac1 ~]$Tnsnames.ora file content.
    RACDB =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = racdb-scan.qfund.net)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = RACDB)
    #QFUNDRAC =
    stand =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST= racdb-scan.qfund.net)(PORT = 1521))
        (CONNECT_DATA =
          (SERVICE_NAME = stand)
          (UR = A)
      )Please help me how to solve this problem.
    Thanks & Regards,
    Poorna Prasad.S

    Hi,
    Please find the output from v$dataguard_status from primary and standby
    Primary
    SQL> select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_2 after log swit
    ch
    ARCH: Beginning to archive thread 1 sequence 214 (4604093-4604095)
    Error 12514 received logging on to the standby
    ARCH: Error 12514 Creating archive log file to 'stand'
    ARCH: Completed archiving thread 1 sequence 214 (4604093-4604095)
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    MESSAGE
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    MESSAGE
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    MESSAGE
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    ARC2: Becoming the heartbeat ARCH
    ARC7: Beginning to archive thread 1 sequence 215 (4604095-4604191)
    ARC7: Completed archiving thread 1 sequence 215 (4604095-4604191)
    ARC5: Beginning to archive thread 1 sequence 216 (4604191-4604471)
    ARC5: Completed archiving thread 1 sequence 216 (4604191-4604471)
    ARCt: Archival started
    MESSAGE
    ARC3: Beginning to archive thread 1 sequence 217 (4604471-4605358)
    ARC3: Completed archiving thread 1 sequence 217 (4604471-4605358)
    LNS: Standby redo logfile selected for thread 1 sequence 217 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 217
    LNS: Completed archiving log 1 thread 1 sequence 217
    LNS: Standby redo logfile selected for thread 1 sequence 218 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 218
    MESSAGE
    LNS: Completed archiving log 2 thread 1 sequence 218
    ARC4: Beginning to archive thread 1 sequence 218 (4605358-4625984)
    ARC4: Completed archiving thread 1 sequence 218 (4605358-4625984)
    LNS: Standby redo logfile selected for thread 1 sequence 219 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 219
    LNS: Completed archiving log 1 thread 1 sequence 219
    ARC5: Beginning to archive thread 1 sequence 219 (4625984-4641358)
    ARC5: Completed archiving thread 1 sequence 219 (4625984-4641358)
    LNS: Standby redo logfile selected for thread 1 sequence 220 for destination LOG
    MESSAGE
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 220
    LNS: Completed archiving log 2 thread 1 sequence 220
    ARC6: Beginning to archive thread 1 sequence 220 (4641358-4644757)
    ARC6: Completed archiving thread 1 sequence 220 (4641358-4644757)
    LNS: Standby redo logfile selected for thread 1 sequence 221 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 221
    LNS: Completed archiving log 1 thread 1 sequence 221
    MESSAGE
    ARC7: Beginning to archive thread 1 sequence 221 (4644757-4648306)
    ARC7: Completed archiving thread 1 sequence 221 (4644757-4648306)
    LNS: Standby redo logfile selected for thread 1 sequence 222 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 222
    LNS: Completed archiving log 2 thread 1 sequence 222
    ARC8: Beginning to archive thread 1 sequence 222 (4648306-4655287)
    ARC8: Completed archiving thread 1 sequence 222 (4648306-4655287)
    LNS: Standby redo logfile selected for thread 1 sequence 223 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 1 thread 1 sequence 223
    LNS: Completed archiving log 1 thread 1 sequence 223
    ARC9: Beginning to archive thread 1 sequence 223 (4655287-4655307)
    ARC9: Completed archiving thread 1 sequence 223 (4655287-4655307)
    LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 224
    LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
    LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    MESSAGE
    Error 3135 for archive log file 2 to 'stand'
    LNS: Failed to archive log 2 thread 1 sequence 224 (3135)
    ARC3: Beginning to archive thread 1 sequence 224 (4655307-4660812)
    ARC3: Completed archiving thread 1 sequence 224 (4655307-4660812)
    LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 224
    LNS: Completed archiving log 2 thread 1 sequence 224
    LNS: Standby redo logfile selected for thread 1 sequence 225 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 1 thread 1 sequence 225
    LNS: Completed archiving log 1 thread 1 sequence 225
    ARC4: Beginning to archive thread 1 sequence 225 (4660812-4660959)
    ARC4: Completed archiving thread 1 sequence 225 (4660812-4660959)
    LNS: Standby redo logfile selected for thread 1 sequence 226 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 226
    LNS: Completed archiving log 2 thread 1 sequence 226
    ARC5: Beginning to archive thread 1 sequence 226 (4660959-4664925)
    MESSAGE
    LNS: Standby redo logfile selected for thread 1 sequence 227 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 227
    ARC5: Completed archiving thread 1 sequence 226 (4660959-4664925)
    LNS: Completed archiving log 1 thread 1 sequence 227
    LGWR: Error 1089 closing archivelog file 'stand'
    ARC6: Beginning to archive thread 1 sequence 227 (4664925-4668448)
    ARC6: Completed archiving thread 1 sequence 227 (4664925-4668448)
    ARC5: Beginning to archive thread 1 sequence 228 (4668448-4670392)
    ARC5: Completed archiving thread 1 sequence 228 (4668448-4670392)
    MESSAGE
    LNS: Standby redo logfile selected for thread 1 sequence 228 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 228
    LNS: Completed archiving log 2 thread 1 sequence 228
    ARC4: Standby redo logfile selected for thread 1 sequence 227 for destination LO
    G_ARCHIVE_DEST_2
    LNS: Standby redo logfile selected for thread 1 sequence 229 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 1 thread 1 sequence 229
    LNS: Completed archiving log 1 thread 1 sequence 229
    ARC3: Beginning to archive thread 1 sequence 229 (4670392-4670659)
    ARC3: Completed archiving thread 1 sequence 229 (4670392-4670659)
    LNS: Standby redo logfile selected for thread 1 sequence 230 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 230
    LNS: Completed archiving log 2 thread 1 sequence 230
    ARC4: Beginning to archive thread 1 sequence 230 (4670659-4670679)
    ARC4: Completed archiving thread 1 sequence 230 (4670659-4670679)
    MESSAGE
    LNS: Standby redo logfile selected for thread 1 sequence 231 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 231
    LNS: Completed archiving log 1 thread 1 sequence 231
    ARC5: Beginning to archive thread 1 sequence 231 (4670679-4690371)
    ARC5: Completed archiving thread 1 sequence 231 (4670679-4690371)
    LNS: Standby redo logfile selected for thread 1 sequence 232 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 232
    MESSAGE
    LNS: Completed archiving log 2 thread 1 sequence 232
    ARC6: Beginning to archive thread 1 sequence 232 (4690371-4712566)
    ARC6: Completed archiving thread 1 sequence 232 (4690371-4712566)
    LNS: Standby redo logfile selected for thread 1 sequence 233 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 233
    LNS: Completed archiving log 1 thread 1 sequence 233
    ARC7: Beginning to archive thread 1 sequence 233 (4712566-4731626)
    LNS: Standby redo logfile selected for thread 1 sequence 234 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 2 thread 1 sequence 234
    ARC7: Completed archiving thread 1 sequence 233 (4712566-4731626)
    LNS: Completed archiving log 2 thread 1 sequence 234
    ARC8: Beginning to archive thread 1 sequence 234 (4731626-4753780)
    LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 235
    ARC8: Completed archiving thread 1 sequence 234 (4731626-4753780)
    LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
    MESSAGE
    LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Error 3135 for archive log file 1 to 'stand'
    LNS: Failed to archive log 1 thread 1 sequence 235 (3135)
    ARC9: Beginning to archive thread 1 sequence 235 (4753780-4765626)
    ARC9: Completed archiving thread 1 sequence 235 (4753780-4765626)
    LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 235
    LNS: Completed archiving log 1 thread 1 sequence 235
    LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
    MESSAGE
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 236
    LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
    LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Error 3135 for archive log file 2 to 'stand'
    LNS: Failed to archive log 2 thread 1 sequence 236 (3135)
    ARCa: Beginning to archive thread 1 sequence 236 (4765626-4768914)
    ARCa: Completed archiving thread 1 sequence 236 (4765626-4768914)
    LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 2 thread 1 sequence 236
    LNS: Completed archiving log 2 thread 1 sequence 236
    LNS: Standby redo logfile selected for thread 1 sequence 237 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 237
    LNS: Completed archiving log 1 thread 1 sequence 237
    ARCb: Beginning to archive thread 1 sequence 237 (4768914-4770603)
    ARCb: Completed archiving thread 1 sequence 237 (4768914-4770603)
    LNS: Standby redo logfile selected for thread 1 sequence 238 for destination LOG
    MESSAGE
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 238
    LNS: Completed archiving log 2 thread 1 sequence 238
    ARCc: Beginning to archive thread 1 sequence 238 (4770603-4770651)
    ARCc: Completed archiving thread 1 sequence 238 (4770603-4770651)
    LNS: Standby redo logfile selected for thread 1 sequence 239 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 239
    LNS: Completed archiving log 1 thread 1 sequence 239
    MESSAGE
    ARCd: Beginning to archive thread 1 sequence 239 (4770651-4773918)
    ARCd: Completed archiving thread 1 sequence 239 (4770651-4773918)
    LNS: Standby redo logfile selected for thread 1 sequence 240 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 240
    LNS: Completed archiving log 2 thread 1 sequence 240
    ARCe: Beginning to archive thread 1 sequence 240 (4773918-4773976)
    ARCe: Completed archiving thread 1 sequence 240 (4773918-4773976)
    LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 1 thread 1 sequence 241
    LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
    LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Error 3135 for archive log file 1 to 'stand'
    LNS: Failed to archive log 1 thread 1 sequence 241 (3135)
    ARC3: Beginning to archive thread 1 sequence 241 (4773976-4774673)
    ARC3: Completed archiving thread 1 sequence 241 (4773976-4774673)
    LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 1 thread 1 sequence 241
    LNS: Completed archiving log 1 thread 1 sequence 241
    LNS: Standby redo logfile selected for thread 1 sequence 242 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 242
    LNS: Completed archiving log 2 thread 1 sequence 242
    ARC4: Beginning to archive thread 1 sequence 242 (4774673-4776045)
    ARC4: Completed archiving thread 1 sequence 242 (4774673-4776045)
    LNS: Standby redo logfile selected for thread 1 sequence 243 for destination LOG
    _ARCHIVE_DEST_2
    MESSAGE
    LNS: Beginning to archive log 1 thread 1 sequence 243
    LNS: Completed archiving log 1 thread 1 sequence 243
    ARC5: Beginning to archive thread 1 sequence 243 (4776045-4776508)
    ARC5: Completed archiving thread 1 sequence 243 (4776045-4776508)
    LNS: Standby redo logfile selected for thread 1 sequence 244 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 244
    LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
    LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    MESSAGE
    Error 3135 for archive log file 2 to 'stand'
    LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
    ARC6: Beginning to archive thread 1 sequence 244 (4776508-4778741)
    ARC6: Completed archiving thread 1 sequence 244 (4776508-4778741)
    ARC7: Beginning to archive thread 1 sequence 245 (4778741-4778781)
    ARC7: Completed archiving thread 1 sequence 245 (4778741-4778781)
    ARC8: Beginning to archive thread 1 sequence 246 (4778781-4778787)
    ARC8: Completed archiving thread 1 sequence 246 (4778781-4778787)
    ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LO
    G_ARCHIVE_DEST_2
    MESSAGE
    ARC3: Beginning to archive thread 1 sequence 247 (4778787-4778934)
    LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 247
    ARC3: Completed archiving thread 1 sequence 247 (4778787-4778934)
    LNS: Completed archiving log 1 thread 1 sequence 247
    LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 248
    MESSAGE
    ARC4: Beginning to archive thread 1 sequence 248 (4778934-4781018)
    LNS: Completed archiving log 2 thread 1 sequence 248
    ARC4: Completed archiving thread 1 sequence 248 (4778934-4781018)
    LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 1 thread 1 sequence 249
    LNS: Completed archiving log 1 thread 1 sequence 249
    ARC5: Beginning to archive thread 1 sequence 249 (4781018-4781033)
    ARC5: Completed archiving thread 1 sequence 249 (4781018-4781033)
    LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG
    MESSAGE
    _ARCHIVE_DEST_2
    LNS: Beginning to archive log 2 thread 1 sequence 250
    233 rows selected.
    SQL>Standby
    SQL> select message from v$dataguard_status;
    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
    ARCa: Archival started
    MESSAGE
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    MESSAGE
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARC1: Becoming the 'no FAL' ARCH
    ARC2: Becoming the heartbeat ARCH
    Error 1017 received logging on to the standby
    FAL[client, ARC2]: Error 16191 connecting to RACDB for fetching gap sequence
    MESSAGE
    ARCt: Archival started
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery starting Real Time Apply
    Media Recovery Log /u02/stand/archive/1_119_758280976.arc
    Media Recovery Waiting for thread 2 sequence 183
    RFS[1]: Assigned to RFS process 30110
    RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 25980
    RFS[2]: Assigned to RFS process 30118
    RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 26008
    RFS[3]: Assigned to RFS process 30124
    MESSAGE
    RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 26029
    RFS[4]: Assigned to RFS process 30130
    RFS[4]: Identified database type as 'physical standby': Client is ARCH pid 26021
    ARC4: Beginning to archive thread 1 sequence 244 (4776508-4778741)
    ARC4: Completed archiving thread 1 sequence 244 (0-0)
    RFS[5]: Assigned to RFS process 30144
    RFS[5]: Identified database type as 'physical standby': Client is LGWR ASYNC pid
    26128
    Primary database is in MAXIMUM PERFORMANCE mode
    ARC5: Beginning to archive thread 1 sequence 247 (4778787-4778934)
    MESSAGE
    ARC5: Completed archiving thread 1 sequence 247 (0-0)
    ARC6: Beginning to archive thread 1 sequence 248 (4778934-4781018)
    ARC6: Completed archiving thread 1 sequence 248 (0-0)
    ARC7: Beginning to archive thread 1 sequence 249 (4781018-4781033)
    ARC7: Completed archiving thread 1 sequence 249 (0-0)
    58 rows selected.
    SQL>also find the output for the primary alertlog file.
    Tue Aug 30 10:45:41 2011
    LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
    LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
    Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
    ORA-03135: connection lost contact
    Error 3135 for archive log file 2 to 'stand'
    Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
    ORA-03135: connection lost contact
    LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
    Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
    ORA-03135: connection lost contact
    Tue Aug 30 10:50:25 2011
    Thread 1 advanced to log sequence 245 (LGWR switch)
      Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
      Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
    Tue Aug 30 10:50:25 2011
    Archived Log entry 612 added for thread 1 sequence 244 ID 0x2d0e0689 dest 1:
    Thread 1 cannot allocate new log, sequence 246
    Checkpoint not complete
      Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
      Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
    Thread 1 advanced to log sequence 246 (LGWR switch)
      Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
      Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
    Tue Aug 30 10:50:27 2011
    Archived Log entry 613 added for thread 1 sequence 245 ID 0x2d0e0689 dest 1:
    Thread 1 cannot allocate new log, sequence 247
    Checkpoint not complete
      Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
      Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
    Thread 1 advanced to log sequence 247 (LGWR switch)
      Current log# 1 seq# 247 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
      Current log# 1 seq# 247 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
    Tue Aug 30 10:50:30 2011
    Archived Log entry 614 added for thread 1 sequence 246 ID 0x2d0e0689 dest 1:
    Tue Aug 30 10:51:37 2011
    ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LOG_ARCHIVE_DEST_2
    Tue Aug 30 10:51:39 2011
    Thread 1 advanced to log sequence 248 (LGWR switch)
      Current log# 2 seq# 248 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
      Current log# 2 seq# 248 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
    Tue Aug 30 10:51:39 2011
    Archived Log entry 620 added for thread 1 sequence 247 ID 0x2d0e0689 dest 1:
    Tue Aug 30 10:51:39 2011
    LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG_ARCHIVE_DEST_2
    LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG_ARCHIVE_DEST_2
    Tue Aug 30 11:08:27 2011
    Thread 1 advanced to log sequence 249 (LGWR switch)
      Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
      Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
    Tue Aug 30 11:08:27 2011
    Archived Log entry 622 added for thread 1 sequence 248 ID 0x2d0e0689 dest 1:
    Tue Aug 30 11:08:27 2011
    LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG_ARCHIVE_DEST_2
    Thread 1 cannot allocate new log, sequence 250
    Checkpoint not complete
      Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
      Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
    Thread 1 advanced to log sequence 250 (LGWR switch)
      Current log# 2 seq# 250 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
      Current log# 2 seq# 250 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
    Tue Aug 30 11:08:31 2011
    Archived Log entry 624 added for thread 1 sequence 249 ID 0x2d0e0689 dest 1:
    LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG_ARCHIVE_DEST_2Thanks & Regards,
    Poorna Prasad.S

  • 3 node RAC database need to build standby database

    Respected DBA's
    I have create 3 node rac architecture now i want create a single instance standby database is anyone tell me the steps or any documentation to consult.
    thanks

    See the [ MAA Home page|http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm#Database] for " [MAA 10g Setup Guide: Creating a Single Instance Physical Standby Database for a RAC Primary Database|http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf] "

  • How to connect local database when installing BRStudio as Multi-Instance?

    Hi,
    I have installed BRStudio 7.10 as Multi-Instance mode to plan to administrate several local oracle database in one server.
    Is this installation the correct method? Should I use dedicated instance installation?
    When I trying to create a local database instance in BRStudio, it prompts to input the remote command line to connect to DB.
    Do I have to use putty/ssh .etc to connect even a local Oracle database?
    Please suggest.
    Regards,
    Alex

    Hi Alex,
    Yes you need to connect it seems as using ssh/rsh or putty to access the local server...
    I have got a very good documentation on it... please have a look and it may solve your issue..
    [BRtools Studio Installation and Configuration|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/009af54c-7ce4-2b10-de8e-b062f7cbbcf7?quicklink=index&overridelayout=true]
    all the best !

  • Creating a RAC standby database for a single instance database

    Dear All,
    I have a task of migrating a 500GB single instance database to a two-node RAC database with a little downtime at hand. My migration strategy is to:
    1) Create a RAC physical standby for the Single Instance database
    2) Switchover to RAC standby.
    Primary and Standby OS and DB configurations:
    OS: Windows Server EE 2003 (64-bit)
    DB: Oracle 10g Database Release 2 (10.2.0.4)
    Oracle 10g Clusterware Release 2 (10.2.0.4)
    To create a RAC standby, I will:
    a) Install Clusterware (10.2.0.1)
    b) Install Database (10.2.0.1)
    c) Patch both Clusterware and Database (10.2.0.4)
    d) Create ASM instance for both the nodes (+ASM1 & +ASM2)
    e) create standby controlfile on primary
    f) Move standby controlfile, RMAN backup of primary, pfile, listener.ora, tnsnames.ora, password file to standby host-1
    g) make necessary changes to the pfile on standby host-1 like cluster_database, instance_name, thread, ...
    h) mount standby database and restore backup
    Kindly validate my steps and if there already exists such a document then please do provide me with a link.
    Regards

    Please refer to MAA whitet paper :
    [http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf]
    [MAA website|http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm]

  • Diagnosing an ASM space issue for a primary and a standby database instance with external redundancy.

    I've received an alert from Enterprise manager saying "Disk Group DATA_SID requires rebalance because at least one disk
    is low on space". My colleague who I would go to with this question is unavailable, so this is a learning opportunity
    for me. So far google and Oracle documentation have provided lots of information, but nothing that answers my questions.
    I've run the following query on both the primary and standby databases ASM instances:
    select name, disk_number, sector_size,os_mb, total_mb, free_mb, redundancy from v$asm_disk;
    On the primary I get 4810M Free space and 18431M Total Space
    on the standby I get 1248M Free space and 18431M Total Space -- this is the one that complained via OEM
    When I run the following query in the database instance:
    select sum(bytes)/1024/1024 MB from dba_segments;
    I get 3736.75M as a result.
    My questions are:
    1. Will OEM's suggestion to rebalance the disk actually help in this situation since the instance is set up with external redundancy?
    2. If I've got 18G of space and only 3.7G of data, why is OEM complaining?
    3. How can I reclaim what I presume is allocated but unused space in my problem disk group?
    4. How can I determine what extra data the standby has that the primary doesn't since both have the same total space allocation, but different amounts of free space?

    Thank you for the reply. That link is very good.
    We are an 11.1 version of our database. Linus is OEL 5.6.
    So, looking at the portion of the link that refers to 'Add Standby database and Instances to the OCR' - If we use SRVCTL to give the STANDBY the role of ‘physical_standby’ and the start option of ‘mount’, what effect will that have if the STANDBY becomes our PRIMARY?
    Would these database settings need to be modified manually with SRVCTL each time?
    We understand why the instance is not starting when the node is rebooted, we are looking for a best practice of how this is implemented.
    Thank you.

  • Standby Database for GRID instance

    Hi All,
    I have a requirement from a client to provide a Standby database (Physical or Logical) for the GRID control instance. Baffled by this, I tried to explain that the GRID instance is very small and may not require a standby. The client is adamant.
    So, has anyone had any experience (experimental or otherwise) of configuration of a standby for GRID?. If so, how? and which would be a feasible option, Physical or Logical?
    Any feedback is appreciated.
    Regards,
    Timothy.

    The search function on here isn't great, it took me longer than I care to admit to find you this:
    OMS question on Physical Standby database
    If you need clarification on anything, shout. Like I said, its a pain to do.

  • Standby Database from a RAC instance

    Good Day,
    I have two 10gR2 Enterprise Edition RAC Instances. Is it possible to make two standby database using 10gR2 Standard Edition?
    Thanks in advance
    Alessandro

    You could post your query in the
    Database - General : General Database Discussions
    and/or
    RAC : Real Application Clusters
    forums.

  • Can I mount another instance of standby database

    1. If I have a RAC physical standby database and instance 1 is mounted and is applying redo, can i mount second instance if I wish for example to perform a backup using rman?
    2. If instance 1 is mounted and applying redo can I stop it and start instance 2 and continue to apply redo??
    Thank you.
    Regards.
    Cristina.

    1. If I have a RAC physical standby database and instance 1 is mounted and is applying redo, can i mount second instance if I wish for example to perform a backup using rman?Yes as Emre mentioned, you can mount all of the instances in cluster.
    2. If instance 1 is mounted and applying redo can I stop it and start instance 2 and continue to apply redo??Redo apply will active only on one node, remaining standby instances will be idle
    So you can start recovery any instance where you wish.

  • LGWR: Standby database destination mismatch with other open instances

      Hello ,
    I have the Primary RAC d.b. and standby : single instance .
    When I try to start a second node of RAC d.b. , then I get errors :
    Error 1033 received logging on to the standby
    LGWR: Error 1033 verifying archivelog destination LOG_ARCHIVE_DEST_2
    Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
    LGWR: Continuing...
    LGWR: Standby database destination mismatch with other open instances
    Errors in file /ora01/app/oracle/diag/rdbms/db2/db2/trace/db2_lgwr_28221.trc:
    ORA-16075: standby database destination mismatch
    LGWR (ospid: 28221): terminating the instance due to error 16075
    But the first instance is working , without any errors .
    The d.g. is working in maximum protection mode .
    Thank's

    Spfile is used :
    SQL> show parameter spfile
    NAME                                 TYPE        VALUE
    spfile                               string      +DATA/db/spfiledb.ora                                                 a
    And on both instances , log_archive_dest_2 is the same :
    log_archive_dest_2                   string      SERVICE=dc5 SYNC AFFIR
                                                     M NET_TIMEOUT=30 REOPEN=300 DB
                                                     _UNIQUE_NAME=dc5 VALID
                                                     _FOR=(ALL_LOGFILES,PRIMARY_ROL
                                                     E)
    And :
      1* select inst_id, name,value from gv$parameter where name='log_archive_dest_2
    INST_ID NAME
    VALUE
          1 log_archive_dest_2
    SERVICE=dc5 SYNC AFFIRM NET_TIMEOUT=30 REOPEN=300 DB_UNIQUE_NAME=dc5 VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE)
          2 log_archive_dest_2
    SERVICE=dc5 SYNC AFFIRM NET_TIMEOUT=30 REOPEN=300 DB_UNIQUE_NAME=dc5 VALID_FOR=(ALL_LOGFILES,PRIMARY_ROLE)

  • Standby database instance parameters in OEM repository

    Hello all,
    I am just wondering if someone using mgmt$db_init_params view to get information
    about init parameters for standby databases in OEM (11.1.0.1)
    I had problems for one of standby databases and after creation of SR was told that
    dbconfig metric is not gathering that information for standby databases
    Using Management Repository Views
    However I have ~40 standby databases in OEM and 25 of them got entries in the view - how they got there?
    And if there are any other ways to get init params for standby databases which do not
    have that information in the view
    Thank you,
    Andrey

    How are you monitoring the standby targets with sys account or dbsnmp?

  • Physical Standby Database with slight complication

    Hello Database experts,
    Primary is a multi-node RAC instance , primarily two distinct schemas (for simplicity sake schema A on tablespace A1/A2 and schema B on tablespace B1/B2). There is a proposed physical standby database. Now primary is Enterprise Data warehouse with millions of updates per minute. Is it possible to somehow bypass objects owned by schema A to be propogated on DR instance.
    Any workaround possible?
    Assume that Hot backup of primary database backup has to be done so we can not perform nologging operations on schema A and Logical standby is not a option.
    Kind Regards,
    Sunil

    ***Is it possible to somehow bypass objects owned by schema A to be propogated on DR instance.***
    Yes. but not in physical standby. While bypassing the objects to physical standby the recovery cannot be enabled at the time. So data loss may occur. Try to configure logical standby database. you can get what you expect.
    thanks

  • Issue in configuring Standby Database from Active database in 11g by RMAN

    POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
    Hi All,
    I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
    Version of Database:11g(11.2.0.1.0)
    Operating System:Linux 5
    Error:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Primary Database Entries:
    Tnsentry:
    SONYPRD =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)(UR=A)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listner Entry:
    SID_LIST_SONYPRD =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtproc)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (PROGRAM = extproc)
    (SID_DESC =
    (SID_NAME = SONYPRD)
    (GLOBAL_DBNAME = SONYPRD)
    Auxiliary Details:
    Tns Entry:
    SONYPRD =
    (DESCRIPTION =
    # (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprd.localdomain)
    SONYPRDSTBY =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = sonyprdstby)(UR=A)
    Listener Entry in auxiliary:
    SID_LIST_SONYPRDSTBY =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = SONYPRDSTBY)
    (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
    (SID_NAME = SONYPRDSTBY)
    TNSPING from Primary DB:
    [oracle@oracle11g ~]$ tnsping sonyprdstby
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
    OK (0 msec)
    TNSPING from Auxuliary server
    [oracle@oracle11gstby ~]$ tnsping sonyprd
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
    OK (10 msec)
    Script Used for duplicate:
    run {
    allocate channel prmy1 type disk;
    allocate channel prmy2 type disk;
    allocate channel prmy3 type disk;
    allocate channel prmy4 type disk;
    allocate auxiliary channel stby type disk;
    duplicate target database for standby from active database
    spfile
    parameter_value_convert 'sonyprd','sonyprdstby'
    set db_unique_name='sonyprdstby'
    set db_file_name_convert='/sonyprd/','/sonyprdstby/'
    set log_file_name_convert='/sonyprd/','/sonyprdstby/'
    set control_files='/u01/app/oracle/oradata/control01.ctl'
    set log_archive_max_processes='5'
    set fal_client='sonyprdstby'
    set fal_server='sonyprd'
    set standby_file_management='AUTO'
    set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
    set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
    Tried the script from both Primary and auxiliary but no luck
    [oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: SONYPRD (DBID=3131093559)
    connected to auxiliary database: SONYPRD (not mounted)
    Listener Status from primary:
    [oracle@oracle11g ~]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 20-DEC-2012 17:42:17
    Uptime 1 days 0 hr. 26 min. 41 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
    Services Summary...
    Service "sonyprd.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    Service "sonyprdXDB.localdomain" has 1 instance(s).
    Instance "sonyprd", status READY, has 1 handler(s) for this service...
    The command completed successfully
    Listener Status from Standby when database bring to Nomount state:
    [oracle@oracle11gstby admin]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 21-DEC-2012 16:13:47
    Uptime 0 days 1 hr. 58 min. 6 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
    Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
    Services Summary...
    Service "sonyprdstby" has 1 instance(s).
    Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
    The command completed successfully
    Please provide any work arounds to proceed further in creating the standby database.
    Thanks,
    Ram.
    Edited by: 895188 on Dec 21, 2012 5:50 PM
    Edited by: 895188 on Dec 21, 2012 6:09 PM
    Edited by: 895188 on Dec 21, 2012 6:22 PM

    Hello;
    Script has to be run from auxiliary.
    Great details, but what I don't see is how you connect in RMAN.
    Example
    Start RMAN
    $ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
    Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: RECOVER2 (DBID=3806912436)
    connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
    Generally for active duplication I start the future standby on a pfile NOMOUNT.
    Auxiliary Instance Initialization Parameters Needed :
    DB_NAME
    CONTROL_FILES
    DB_BLOCK_SIZE
    ( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
    Then start RMAN and finally run a single line duplication command.
    $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
    RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
    mseberg

Maybe you are looking for