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

Similar Messages

  • 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

  • Resizing redo log files on a 3 node RAC with single node standby database

    Hi
    On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
    SQL> select group#,thread#,members,status from v$log;
    GROUP# THREAD# MEMBERS STATUS
    1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
    2 1 3 CURRENT & resized, switch logfile can change logfile group
    3 1 3 INACTIVE
    4 2 3 INACTIVE
    5 2 3 INACTIVE
    6 2 3 CURRENT
    7 3 3 INACTIVE
    8 3 3 INACTIVE
    9 3 3 CURRENT
    9 rows selected.
    SQL> alter database drop logfile group 1;
    Database altered.
    SQL> ALTER DATABASE ADD LOGFILE THREAD 1
    GROUP 1 (
    '/PROD/redo1/redo01a.log',
    '/PROD/redo2/redo01b.log',
    '/PROD/redo3/redo01c.log'
    ) SIZE 100M reuse; 2 3 4 5 6
    Database altered.
    However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
    SQL> select group#,member from v$logfile where type='STANDBY';
    GROUP#
    MEMBER
    10
    /PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
    11
    /PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
    12
    /PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
    Please let me know.
    Thanks
    Sumathy

    Hello;
    For Redo and Standby redo this won't help :
    standby_file_management is set to auto
    On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
    Then start recovery again.
    Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
    alter database add standby logfile group 4
    ('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
    ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
    Notes worth reviewing :
    Online Redo Logs on Physical Standby [ID 740675.1]
    Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
    Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
    Best Regards
    mseberg

  • 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

  • Using RMAN to create single instance standby from 2 node rac

    Any advice on the RMAN command to take a non catalog full rman backup from a two node 11gr2 rac node and use it to create the STANDBY single instance.
    The RAC two node instance is in ASM (Linux)
    The Physical Standby is Normal File System (Linux)
    The command that I get from Metalink suggests:
    rman target sys/passwd@primary catalog RMAN/RMAN@RMAN auxiliary sys/passwd
    RMAN> run {
    allocate auxiliary channel C1 device type disk;
    duplicate target database for standby;
    When I took the rman backup I did not use catalog. Please suggest how to accomplish the same task without catalog. Thanks

    Listener.ora
    SID_LIST_STANDBY_LSNR =
    (SID_LIST =
    (SID_DESC =
    (GLOBAL_DBNAME = KEMETRAC.respecti.com)
    (SID_NAME = STANDBY)
    (ORACLE_HOME = /u02/standby/11.2.0.3/STANDBY)
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /u02/standby/11.2.0.3/STANDBY)
    (PROGRAM = extproc)
    ADR_BASE_STANDBY = /u02/standby/11.2.0.3
    TRACE_LEVEL_STANDBY = OFF
    STANDBY_LSNR =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby.respecti.com)(PORT = 2012))
    LOGGING_STANDBY = OFF
    ...... Tnsnames.ora
    STANDBY.RESPECTI.COM,STANDBY =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = standby.respecti.com)(PORT = 2012))
    (CONNECT_DATA =
    (SERVICE_NAME = STANDBY.respecti.com)
    KEMETRAC1.respecti.com, KEMETRAC1 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.respecti.com)(PORT = 2012))
    (CONNECT_DATA =
    (SERVICE_NAME = kemetrac1.respecti.com)
    KEMETRAC2.respecti.com, KEMETRAC2 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.respecti.com)(PORT = 2012))
    (CONNECT_DATA =
    (SERVICE_NAME = kemetrac2.respecti.com)
    # TAF 2 Node RAC
    KEMETRAC.respecti.com, KEMETRAC =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (FAILOVER = ON)
    (LOAD_BALANCE = ON)
    (ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.respecti.com)(PORT = 2012))
    (ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.respecti.com)(PORT = 2012))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = kemetrac.respecti.com)
    (FAILOVER_MODE =
    (TYPE = SELECT)
    (METHOD = BASIC)
    (RETRIES = 180)
    (DELAY = 5)
    The Standby has been started up with nomount.
    standby> rman target sys/[email protected] auxiliary sys/pw
    Recovery Manager: Release 11.2.0.3.0 - Production on Wed Jan 18 18:16:46 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
    connected to target database: KEMETRAC (DBID=1448030790)
    connected to auxiliary database: KEMETRAC (not mounted)
    RMAN>
    RMAN> run {
    2> duplicate target database for standby from active database dorecover nofilenamecheck;}
    Starting Duplicate Db at 18-JAN-12
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 01/18/2012 18:23:06
    RMAN-05501: aborting duplication of target database
    RMAN-06217: not connected to auxiliary database with a net service name
    RMAN>

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

  • Single-instance manual standby for a three-node RAC database

    Hi all,
    I am wondering how it is possible to create a manual standby database for a rac primary database.
    Oracle versione is standard edition 11.1.
    I have experience creating and managing manual standby for single-instance database; I am wondering if and how I can instruct the single-instance standby database to discover and apply the three redo threads that I will copy from the primary site to the standby site.
    Should I use rman to catalog all the archived log on the standby site ?
    Should I configure many LOG_ARCHIVE_DEST_n parameters to point to many different path, one for each primary instance (i.e. one for each redo thread), and let rman automagically discover all the archived logs ?
    Should I configure only LOG_ARCHIVE_DEST_1 , put archivelogs from all threads in the same folder, and let rman automagically discover all the archived logs ?
    Thanks for every answer!
    Andrea

    Hi,
    indeed i catalog all transfered archive logs in front of the recover process.
    During the tests i believe (iirc) i was unable to recover from transfered archivelogs without catalog them first. But this statement is out of my mind, i am not 100% sure for this, sorry.
    Some more details.
    Because it is a standard edition, i have to use on the RAC side ASM. So our normal scripts to transfer archivelogs from primary to standby are obsolete.
    So i decided to put the whole standby thing into the database. Now the primary database uses external scheduler jobs to do the work. The standby side is not using ASM, so there is no need to handle the logs in any special way.
    The steps are:
    1. Get SCN from primary and standby
    2. Transfer the logs for the gap from ASM to "normal" filesystem.
    3. Transfer (and compress, if not in LAN) to standby archive dest
    4. Catalog on standby side
    5. Recover on standby side
    6. Delete on normal filesystem (on both sides, but on standby with a delay of 2 days just to be sure)
    The steps on the standby side are both using the primary scn from step 1 as a parameter to avoid error messages during the catalog or recover call.
    Hth
    Joerg

  • Primary database is RAC and Physical standby is single instance

    Hello All,
    I am using Oracle RAC 11.2.0.3 as primary database, we are going to start using Oracle data guard.
    So I am designing my infrastructure and planing to use Oracle 11.2.0.3 Single instance as my physical stand by database.
    My question is it feasible to have my standby database as single instance while the primary is RAC?
    is it feasible to build my Oracle single instance standby database from the RMAN backup of the RAC primary database?
    Is there any restrictions (or any points to be taken into consideration) since my primary database is RAC while the physical standby is Oracle single instance?
    in the below link
    [http://docs.oracle.com/cd/B28359_01/server.111/b28294/concepts.htm#i1039416]
    it was mentioned that primary can be RAC or single and same for standby, but my question is it feasible to have primary as RAC while standby as single instance? or it should be like each others?
    The primary database can be either a single-instance Oracle database or an Oracle Real Application Clusters (RAC) database.
    Similar to a primary database, a standby database can be either a single-instance Oracle database or an Oracle RAC database.Regards,

    My question is it feasible to have my standby database as single instance while the primary is RAC?Yes...quite a common setup.
    is it feasible to build my Oracle single instance standby database from the RMAN backup of the RAC primary database?Yes.
    Is there any restrictions (or any points to be taken into consideration) since my primary database is RAC while the physical standby is Oracle single instance?No show stoppers.

  • Datagurad setup from 2 Node RAC to single instance (DR site)

    Dear Expert,
    I have request from management to setup the DR site from current production RAC database using active dataguard. I have two node rac database 11.2.0.3 running on sun solaris machine. I need proper step or good document can refer to setup between production RAC database to DR site single instance standby database. I only experience setup single instance to single instance .Apreciate expert can provide me some link
    Regard
    liang

    Hello;
    This will provide a good start and overview :
    Creating a Single Instance Physical Standby for a RAC Primary : ( please note parameter changes for Oracle 11 )
    http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimarysingleinstance-131970.pdf
    As will this :
    http://oracleinstance.blogspot.com/2012/01/create-single-instance-standby-database.html
    Oracle 11
    Rapid Oracle RAC Standby Deployment: Oracle Database 11g Release 2
    http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-rac-standby-133152.pdf
    Best Regards
    mseberg

  • Migrate from single instance to RAC manually

    Hi,
    I have a 10g database running in single instance.I have installed grid 11.2.0.2 in two nodes including the node where current instance is running,I have installed 10g again in a seperate mount point in both the nodes .It has the same patches as single instance 10g home.Now how to migrate from single instance to RAC manually.
    Thanks,
    Sekar

    -restore this database into 11g ASM if its not already on ASM.
    -upgrade this database to 11g from 10g on single instance.
    -Now Converting Single Instance on a Cluster to Oracle RAC ,here you have different option to perform this once its 11g database after upgrade.
    using rconfig
    using dbca or manually.
    see detail here
    http://docs.oracle.com/cd/E11882_01/install.112/e24660/cvrt2rac.htm#autoId9

  • Configuring multiple services in a single instance database

    Dear All,
    I would like to create multiple service names for a single instance oracle database (10.2.0.3 on IBM - AIX 6.1). I tried searching on the net, reading documentation, and also on the metalink but couldn't find anything relevant to single instance database.
    Say I have two users, userA and userB, for which I would like to use two services (ServA and ServB) to connect to the same single instance database.
    Any help in this direction is appreciated.
    Regards

    Oracle Lover3 wrote:
    Thanks for your quick solution.
    By the time you answered I was able to locate it in the documentation. I have tested it and its working perfectly. Here's the documenation link.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams188.htm#i1133481
    It is very hard to believe you didn't find this in the documentation, and my suspicion is you didn't search for it at all.It is very hard to believe that you don't trust others and end up in suspicion. I wish you were sitting next to me while I was searching for the link/document.It is because the vast majority of doc questions are asked by people who don't read the docs at all.
    Now, I'm curious about your requirement. While it can be done, it is pretty unusual. That always leads me to want to step back from the technical question and ask What business problem is this solving?

  • Do we require HBA card for single instance database.

    Hi All,
    I have doubt that we are going to implement a single instance with ASM.
    Db version will 11gR2 as it is asm. My concern HBA is required for single instance oracle database.
    Please suggest.
    Thanks and Regards,

    The question is : do you want your user to be able ti use their application offline ?
    If yes, then you may provide them a local database and use a JDBC type4 driver. (The application is fetch directly from the server when first connected and then is able to lauch the applicaiton off-line) Such a network listen is allowed by the JNLP security model without any application sign !
    If no, then why not having a single database and some user debedant table that store the user specific data (as usual), and using a login dialog-bon (or an auto-logon mechanism) to restric identify and access your database thru some business logic via RMI or any ligh-webservice technology.
    Anyway you have plenty of solutions ..... it only depends of what are the exact needs.
    Regards,
    Jean-Baptiste Bugeaud
    WWW.UP2GO.NET - The JNLP Applications Repository

  • Converting to Oracle Real Application Clusters from Single-Instance Oracle

    Is there any notes at metalink for
    Converting to Oracle Real Application Clusters from Single-Instance Oracle Databases
    We should have 10g DB on ASM to make it RAC?

    With Oracle Database 10g Release 2, $ORACLE_HOME/bin/rconfig tool can be used to convert Single instance database to RAC. This tool takes in a xml input file and convert the Single Instance database whose information is provided in the xml. You can run this tool in "verify only" mode prior to performing actual conversion. This is documented in the RAC admin book and a sample xml can be found $ORACLE_HOME/assistants/rconfig/sampleXMLs/ConvertToRAC.xml. Grid Control 10g Release 2 provides a easy to use wizard to perform this function.

  • Protect single instance linux Oracle 11Gr2 with Clusterware 11Gr2 non-RAC

    Hi All,
    I saw this link, but it mentions RAC as a solution:
    Using Oracle Clusterware to Protect A Single Instance Oracle Database 11g
    I have seen various articles about protecting single instance with cold failover using clusterware, but they mention scripts and older versions of Clusterware. I am trying to figure out if possible to incorporate virtual ip's / scan listeners or if this is even a supported configuration...
    I have set up clusterware 11gr2 using OCFS2. I basically just want to do a cold failover from one node to the other, and I do not wish to purchase a RAC license...
    thanks much
    Edited by: vcovco on Sep 30, 2010 1:52 PM

    Below are the steps which i followd. Can you pls take a look & reply if the below are correct.
    Step1 rg1
    crsctl add resource rg1 -type cluster_resource \
    -attr "ACTION_SCRIPT=$CRS_HOME/crs/public/act_resgroup.pl, \
    CHECK_INTERVAL=600"
    ./crsctl start resource rg1
    Step2 rg1.vip
    As root
    $CRS_HOME/bin/appvipcfg create -network=1 -ip=xx.xx.xx.xx -vipname=rg1.vip -user=root -group=root
    ./crsctl setperm resource rg1.vip -u user:oracle:r-x
    ./crsctl start resource rg1.vip
    Step3 rg1.listener
    export CRS_HOME=/optware/grid/11.2.0.2
    export ORACLE_HOME=/optware/oracle/11.2.0.2/db
    export USRORA_LANG=$ORACLE_HOME
    export USRORA_SRV=LISTENER_rg1
    export ORACLE_SID=rg1
    $CRS_HOME/crs/public/act_listener.pl start
    Listener.ora
    =========
    LISTENER_rg1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=lxwkbc-app)(PORT=1320))))
    Tnsnames.ora
    =========
    LISTENERS_rg1 =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = lxwkbc-app)(PORT = 1320)))
    ./crsctl add resource rg1.listener -type cluster_resource \
    -attr "ACTION_SCRIPT=$CRS_HOME/crs/public/act_listener.pl, \
    CHECK_INTERVAL=20,RESTART_ATTEMPTS=5, \
    START_DEPENDENCIES=hard(rg1.vip) pullup(rg1.vip),STOP_DEPENDENCIES=hard(rg1.vip)"
    ./crsctl start resource rg1.listener
    Step4 rg1.db_rg1
    export CRS_HOME=/optware/grid/11.2.0.2
    export ORACLE_HOME=/optware/oracle/11.2.0.2/db
    export USRORA_LANG=$ORACLE_HOME
    export USRORA_SRV=rg1
    export ORACLE_SID=rg1
    export USRORA_FLAGS=1
    $CRS_HOME/crs/public/act_db.pl stop
    ./crsctl add resource rg1.db_rg1 -type cluster_resource \
    -attr "ACTION_SCRIPT=$CRS_HOME/crs/public/act_db.pl, CHECK_INTERVAL=20,RESTART_ATTEMPTS=5, \
    START_DEPENDENCIES=hard(rg1.listener) pullup(rg1),STOP_DEPENDENCIES=hard(rg1.listener)"
    ./crsctl start resource rg1.db_rg1
    Step5 rg1.head
    ./crsctl add resource rg1.head -type cluster_resource \
    -attr "ACTION_SCRIPT=$CRS_HOME/crs/public/act_resgroup.pl, CHECK_INTERVAL=600,RESTART_ATTEMPTS=2, \
    START_DEPENDENCIES=hard(rg1.listener,rg1.db_rg1,rg1)"
    ./crsctl start resource rg1.head

  • How to convert from single instance to RAC?

    Hi, I have one environment it is version is 10.2.0.4 in linux SUSE.
    I decided to move this environment to 10.2.0.4 Real applicaiton cluster has two nodes in linux red-hat.
    Firstly,
    I install 10.2.0.1 rac on two new machine in linux red hat.
    Then I upgrade my rac to 10.2.0.4 from 10.2.0.
    Now I want to move the single instance to RAC,
    Is there an anathoer way that different from export , import?

    Besides the obvious Export-Import which do not want to consider (although it would be the neatest method !), look the 4th conversion scenario under paragraph D.3.2 "Single-Instance to RAC Conversion Scenarios" at
    http://download.oracle.com/docs/cd/B19306_01/install.102/b14203/cvrt2rac.htm#BABFCAHF
    The 4th conversion scenario is "Converting a single-instance Oracle Database 10g Release 2 (10.2) to an 10g Release 2 (10.2) RAC database, running out of a different Oracle home, and where the host where the single-instance database is running is not one of the nodes of the RAC database".
    Reference section D of the "Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide 10g Release 2 (10.2) for Linux"
    http://download.oracle.com/docs/cd/B19306_01/install.102/b14203/toc.htm

Maybe you are looking for