Data guard difference in primary and standby OS.

Dear All,
We are planning to setup a data guard in our landscape. But my question what are the prerequisites should be consider before getting in to that.
Like my environment -
1. The primary database is running with Red hat Linux 5 - IBM 64 bit and the standby database is Redhat Linux 2.1 IBM 32 bit system.
2. The primary database is running with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 and the standby database is
   Linux  2.1 IBM 32 bit system with oracle 10g.
Is the above thing is possible? or we should maintain the same OS / DB combination in the data guard setup.
I am following the below link.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/standby.htm#i72053
If anyone have thoughts on this please do advice me.
Regards
Vijay

Please explain to us what exactly you want to do with the standby database?
According to note 105047 - Support for Oracle functions in the SAP environment
12. Data Guard
You can use "Physical Standby", but Oracle provides support (not SAP).
You cannot use "Logical Standby"
So in short, no a data guard configuration with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 to Linux 2.1 IBM 32 bit system with oracle 10g is NOT possible.
Regards, Michael

Similar Messages

  • Oracle data guard configuration for primary and standby db_name

    I am working on configuring an active data guard for one primary DB and one standby DB. I have a few questions:
    1. Can I use different db_name, db_unique_name and instance_name for primary and standby. For example: primary(db_name, db_unique_name and instance_name)=chicago. When I create standby DB with Rman backup and copy of pfile and control file from primary DB or use Grid control to create standby database. Oracle document or Grid control all keep standby db_name=chicago. Only make standby db_unique_name and instance_name=boston. Due to my application system condition, I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?
    2. In primary datafiles, application system generate datafile name like this: hr_chicago_01.dbf, fn_chicago_01.dbf. When I move datafiles to standby server, if I plan to use db_name=boston for standby DB, can I rename datafiles as
    hr_boston_01.dbf, fn_boston_01.dbf? In this way, datafile name match up with db_name. but I will create standby log group and members on primary and standby identically. If in future switching over, DB will not have problems.
    3. If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standby. Then "alter database backup controlfile to trace" from promary and also " create pfile='/xxx/initSTANDBY.ora' from primary. Then modify init.ora and controlfile. Then run control.sql to bring standby DB up. After that, configure redo log shipping and apply with data guard or SQL. Is this a acceptable way to create physical standby DB?
    Please advise your comments. Thanks in advance.

    I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?NO. DB_NAME must be the same ("chicago") at both sites. The Standby will be using a different DB_UNIQUE_NAME (e.g. "boston") and can be using a different Instance name / SID (e.g. "boston").
    can I rename datafiles Yes. The database file names can be changed.
    If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standbyWhat is the difference between the first sentence (a backup of the primary) and the second sentence (a copy of the primary) ? A Copy is a backup.
    Are you intending to differentiate between an RMAN Backup and a User-Managed (aka "scripted") backup ?
    Normally, for DataGuard, tou can use non-RMAN methods to copy the database but there's no value add in this.
    You'd still have to setup DataGuard ! (and I wonder if you'd have complications setting up Active DataGuard).
    But remember that you MUST create the Standby controlfile from the Primary and copy it over to your Standby -- particularly as you are planning to use DataGuard. This is not created by 'alter database backup controlfile to trace' , but by 'ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename''
    Hemant K Chitale

  • Steps for Data Guard with one primary and 2 standby

    Hi,
    Database :10.2.0.4, 11.2.0.1
    Os: Windows , Unix
    A ----------------> Primary database
    B ----------------> Standby Database 1
    C ----------------> Standby Database 2
    I want to configure *2 standby* databases for single primary database.
    Lets take, A ,B and C are my machines.My data guard configuration will be like,*archive logs will be moving* from A to B and A to C.
    If i do any switchover in between A and B , now B is primary and remaining A and C are standby databases.At this stage also , archive logs should move from B to A and B to C. Also, same should happen from C to A and C to B,If i do switchover in between B and C.If everything is fine , then i will do switchback to main Primary database(A).
    How do i have to mention PFILE in all machines ,the parameters like
    LOG_ARCHIVE_DEST_1=LOCATION=<PATH> -- LOCAL ARCHIVE PATH
    LOG_ARCHIVE_DEST_2=SERVICE=
    LOG_ARCHIVE_DEST_3=SERVICE=
    FAL_SERVER=
    FAL_CLIENT=
    STANDBY_FILE_MANAGEMENT=
    In my tnsnames.ora , primary,standby1 and standby2 are my service entries and these are same in all of my machines.
    Please suggest me , how do i can configure my pfiles in all machines ?.
    Thanks,
    Sunand

    Not yet, but now you have me interested.
    Please consider Flashback.
    I still have to test but here's my take:
    PRIMARY SETTINGS
    *.FAL_SERVER=STANDBY
    *.FAL_CLIENT=PRIMARY
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.DB_UNIQUE_NAME=PRIMARY
    *.LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
    *.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
    *.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
    *.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_3=ENABLE
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    STANDBY 1 SETTINGS
    *.FAL_SERVER=PRIMARY
    *.FAL_CLIENT=STANDBY
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.DB_UNIQUE_NAME=STANDBY
    *.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY'
    *.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
    *.log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
    *.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=DEFER
    *.LOG_ARCHIVE_DEST_STATE_3=DEFER
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    STANDBY2 SETTINGS
    *.FAL_SERVER=PRIMARY
    *.FAL_CLIENT=STANDBY2
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.DB_UNIQUE_NAME=STANDBY2
    *.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY2'
    *.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY2'
    *.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
    *.log_archive_dest_3='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=DEFER
    *.LOG_ARCHIVE_DEST_STATE_3=DEFER
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    Edited by: mseberg on Nov 29, 2010 9:39 AM
    The first test slapped me. Looking at 409013.1 Cascaded Standby Databases
    Edited by: mseberg on Nov 29, 2010 12:49 PM

  • SCN number difference in primary and standby databases

    Hi All,
    Is it possible that primary database SCN is 20 and standby database SCN is 22 ? If yes , how it works ?
    Thankyou !

    I agree that it is possible depending on your setup. However, I read your posting and BLOG entry but it does not address out the Standby database has a GREATER SCN than the Primary.
    The answer will depend on the type of standby database you have configured (LOGICAL vs PHYSICIAL) and perhaps if it is a SNAPSHOT Standby that has been used and not rolledback.
    In what I would consider "Normal" situations the SCN of the standby database would always either be at the same SCN or be lagging.
    I have not tested it but I could see where if you had a standby database that you converted to a SNAPSHOT Standby (11g ability), made changes to the standby and had not converted it back to a normal Standby then your SCN can be ahead in the standby because the changes had not been discarded yet.
    Regards.
    Tim

  • Time zone difference between primary and physical standby

    Dear Team,
    We have Primary database server (with EST Time zone) and physical standby (with PST time zone), in case of switch over/fail over to physical standby
    what are the major impacts.
    Is it mandatory to be in time sync?
    Thanks in advance
    Aj

    CURRENT_TIMESTAMP
    04-FEB-10 10.22.20.444692 AM +05:30
    ( above is same on primary and standby)
    SQL> select systimestamp from dual;
    SYSTIMESTAMP
    03-FEB-10 08.52.46.934125 PM -08:00
    (above is 3hr diff from primary and standby)It is 13hrs difference
    One is around Indian subcontinent and other should be in US western region ?
    Systimestamp is the timestamp of the OS of the server and hence the difference and the sysdate value will be from systimestamp and if the applications uses SYSDATE then there can be an issue...

  • Data Guard Failover after primary site network failure or disconnect.

    Hello Experts:
    I'll try to be clear and specific with my issue:
    Environment:
    Two nodes with NO shared storage (I don't have an Observer running).
    Veritas Cluser Server (VCS) with Data Guar Agent. (I don't use the Broker. Data Guard agent "takes care" of the switchover and failover).
    Two single instance databases, one per node. NO RAC.
    What I'm being able to perform with no issues:
    Manual switch(over) of the primary database by running VCS command "hagrp -switch oraDG_group -to standby_node"
    Automatic fail(over) when primary node is rebooted with "reboot" or "init"
    Automatic fail(over) when primary node is shut down with "shutdown".
    What I'm NOT being able to perform:
    If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
    Same situation happens if I manually disconnect the server from the power.
    This is the alert logs I have:
    This is the portion of the alert log at Standby site when Real Time Replication is working fine:
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
      Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
    At this moment, node1 (Primary) is completely disconnected from the network. SEE at the end when the database (standby which should be converted to PRIMARY) is not getting all the archived logs from the Primary due to the abnormal disconnect from the network:
    Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
    Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
    Media Recovery Complete (primary_db)
    Terminal Recovery: successful completion
    Forcing ARSCN to IRSCN for TR 0:15922544
    Mon Dec 23 17:13:22 2013
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
    ORA-16014: log 4 sequence# 7 not archived, no available destinations
    ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
    Resetting standby activation ID 2071848820 (0x7b7de774)
    Completed:  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
    Mon Dec 23 17:13:33 2013
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
    Terminal Recovery: applying standby redo logs.
    Terminal Recovery: thread 1 seq# 7 redo required
    Terminal Recovery:
    Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
      Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
    Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
    Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
    Media Recovery Complete (primary_db)
    Terminal Recovery: successful completion
    Forcing ARSCN to IRSCN for TR 0:15922544
    Mon Dec 23 17:13:22 2013
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
    ORA-16014: log 4 sequence# 7 not archived, no available destinations
    ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
    Resetting standby activation ID 2071848820 (0x7b7de774)
    Completed:  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
    Mon Dec 23 17:13:33 2013
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
    Attempt to do a Terminal Recovery (primary_db)
    Media Recovery Start: Managed Standby Recovery (primary_db)
    started logmerger process
    Mon Dec 23 17:13:33 2013
    Managed Standby Recovery not using Real Time Apply
    Media Recovery failed with error 16157
    Recovery Slave PR00 previously exited with exception 283
    ORA-283 signalled during:  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH...
    Mon Dec 23 17:13:34 2013
    Shutting down instance (immediate)
    Shutting down instance: further logons disabled
    Stopping background process MMNL
    Stopping background process MMON
    License high water mark = 38
    All dispatchers and shared servers shutdown
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    ALTER DATABASE DISMOUNT
    Shutting down archive processes
    Archiving is disabled
    Mon Dec 23 17:13:38 2013
    Mon Dec 23 17:13:38 2013
    Mon Dec 23 17:13:38 2013
    ARCH shutting downARCH shutting down
    ARCH shutting down
    ARC0: Relinquishing active heartbeat ARCH role
    ARC2: Archival stopped
    ARC0: Archival stopped
    ARC1: Archival stopped
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Mon Dec 23 17:13:40 2013
    Stopping background process VKTM
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Mon Dec 23 17:13:43 2013
    Instance shutdown complete
    Mon Dec 23 17:13:44 2013
    Adjusting the default value of parameter parallel_max_servers
    from 1280 to 470 due to the value of parameter processes (500)
    Starting ORACLE instance (normal)
    ************************ Large Pages Information *******************
    Per process system memlock (soft) limit = 64 KB
    Total Shared Global Region in Large Pages = 0 KB (0%)
    Large Pages used by this instance: 0 (0 KB)
    Large Pages unused system wide = 0 (0 KB)
    Large Pages configured system wide = 0 (0 KB)
    Large Page size = 2048 KB
    RECOMMENDATION:
      Total System Global Area size is 3762 MB. For optimal performance,
      prior to the next instance restart:
      1. Increase the number of unused large pages by
    at least 1881 (page size 2048 KB, total size 3762 MB) system wide to
      get 100% of the System Global Area allocated with large pages
      2. Large pages are automatically locked into physical memory.
    Increase the per process memlock (soft) limit to at least 3770 MB to lock
    100% System Global Area's large pages into physical memory
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Initial number of CPU is 32
    Number of processor cores in the system is 16
    Number of processor sockets in the system is 2
    CELL communication is configured to use 0 interface(s):
    CELL IP affinity details:
        NUMA status: NUMA system w/ 2 process groups
        cellaffinity.ora status: cannot find affinity map at '/etc/oracle/cell/network-config/cellaffinity.ora' (see trace file for details)
    CELL communication will use 1 IP group(s):
        Grp 0:
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =88
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    NUMA system with 2 nodes detected
    Starting up:
    Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options.
    ORACLE_HOME = /u01/oracle/product/11.2.0.4
    System name:    Linux
    Node name:      node2.localdomain
    Release:        2.6.32-131.0.15.el6.x86_64
    Version:        #1 SMP Tue May 10 15:42:40 EDT 2011
    Machine:        x86_64
    Using parameter settings in server-side spfile /u01/oracle/product/11.2.0.4/dbs/spfileprimary_db.ora
    System parameters with non-default values:
      processes                = 500
      sga_target               = 3760M
      control_files            = "/u02/oracle/orafiles/primary_db/control01.ctl"
      control_files            = "/u01/oracle/fast_recovery_area/primary_db/control02.ctl"
      db_file_name_convert     = "standby_db"
      db_file_name_convert     = "primary_db"
      log_file_name_convert    = "standby_db"
      log_file_name_convert    = "primary_db"
      control_file_record_keep_time= 40
      db_block_size            = 8192
      compatible               = "11.2.0.4.0"
      log_archive_dest_1       = "location=/u02/oracle/archivelogs/primary_db"
      log_archive_dest_2       = "SERVICE=primary_db ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary_db"
      log_archive_dest_state_2 = "ENABLE"
      log_archive_min_succeed_dest= 1
      fal_server               = "primary_db"
      log_archive_trace        = 0
      log_archive_config       = "DG_CONFIG=(primary_db,standby_db)"
      log_archive_format       = "%t_%s_%r.dbf"
      log_archive_max_processes= 3
      db_recovery_file_dest    = "/u02/oracle/fast_recovery_area"
      db_recovery_file_dest_size= 30G
      standby_file_management  = "AUTO"
      db_flashback_retention_target= 1440
      undo_tablespace          = "UNDOTBS1"
      remote_login_passwordfile= "EXCLUSIVE"
      db_domain                = ""
      dispatchers              = "(PROTOCOL=TCP) (SERVICE=primary_dbXDB)"
      job_queue_processes      = 0
      audit_file_dest          = "/u01/oracle/admin/primary_db/adump"
      audit_trail              = "DB"
      db_name                  = "primary_db"
      db_unique_name           = "standby_db"
      open_cursors             = 300
      pga_aggregate_target     = 1250M
      dg_broker_start          = FALSE
      diagnostic_dest          = "/u01/oracle"
    Mon Dec 23 17:13:45 2013
    PMON started with pid=2, OS id=29108
    Mon Dec 23 17:13:45 2013
    PSP0 started with pid=3, OS id=29110
    Mon Dec 23 17:13:46 2013
    VKTM started with pid=4, OS id=29125 at elevated priority
    VKTM running at (1)millisec precision with DBRM quantum (100)ms
    Mon Dec 23 17:13:46 2013
    GEN0 started with pid=5, OS id=29129
    Mon Dec 23 17:13:46 2013
    DIAG started with pid=6, OS id=29131
    Mon Dec 23 17:13:46 2013
    DBRM started with pid=7, OS id=29133
    Mon Dec 23 17:13:46 2013
    DIA0 started with pid=8, OS id=29135
    Mon Dec 23 17:13:46 2013
    MMAN started with pid=9, OS id=29137
    Mon Dec 23 17:13:46 2013
    DBW0 started with pid=10, OS id=29139
    Mon Dec 23 17:13:46 2013
    DBW1 started with pid=11, OS id=29141
    Mon Dec 23 17:13:46 2013
    DBW2 started with pid=12, OS id=29143
    Mon Dec 23 17:13:46 2013
    DBW3 started with pid=13, OS id=29145
    Mon Dec 23 17:13:46 2013
    LGWR started with pid=14, OS id=29147
    Mon Dec 23 17:13:46 2013
    CKPT started with pid=15, OS id=29149
    Mon Dec 23 17:13:46 2013
    SMON started with pid=16, OS id=29151
    Mon Dec 23 17:13:46 2013
    RECO started with pid=17, OS id=29153
    Mon Dec 23 17:13:46 2013
    MMON started with pid=18, OS id=29155
    Mon Dec 23 17:13:46 2013
    MMNL started with pid=19, OS id=29157
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    starting up 1 shared server(s) ...
    ORACLE_BASE from environment = /u01/oracle
    Mon Dec 23 17:13:46 2013
    ALTER DATABASE   MOUNT
    ARCH: STARTING ARCH PROCESSES
    Mon Dec 23 17:13:50 2013
    ARC0 started with pid=23, OS id=29210
    ARC0: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    ARC0: STARTING ARCH PROCESSES
    Successful mount of redo thread 1, with mount id 2071851082
    Mon Dec 23 17:13:51 2013
    ARC1 started with pid=24, OS id=29212
    Allocated 15937344 bytes in shared pool for flashback generation buffer
    Mon Dec 23 17:13:51 2013
    ARC2 started with pid=25, OS id=29214
    Starting background process RVWR
    ARC1: Archival started
    ARC1: Becoming the 'no FAL' ARCH
    ARC1: Becoming the 'no SRL' ARCH
    Mon Dec 23 17:13:51 2013
    RVWR started with pid=26, OS id=29216
    Physical Standby Database mounted.
    Lost write protection disabled
    Completed: ALTER DATABASE   MOUNT
    Mon Dec 23 17:13:51 2013
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
             USING CURRENT LOGFILE DISCONNECT FROM SESSION
    Attempt to start background Managed Standby Recovery process (primary_db)
    Mon Dec 23 17:13:51 2013
    MRP0 started with pid=27, OS id=29219
    MRP0: Background Managed Standby Recovery process started (primary_db)
    ARC2: Archival started
    ARC0: STARTING ARCH PROCESSES COMPLETE
    ARC2: Becoming the heartbeat ARCH
    ARC2: Becoming the active heartbeat ARCH
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance primary_db - Archival Error
    ORA-16014: log 4 sequence# 7 not archived, no available destinations
    ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
    At this moment, I've lost service and I have to wait until the prmiary server goes up again to receive the missing log.
    This is the rest of the log:
    Fatal NI connect error 12543, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 23-DEC-2013 17:13:52
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12543
    TNS-12543: TNS:destination host unreachable
        ns secondary err code: 12560
        nt main err code: 513
    TNS-00513: Destination host unreachable
        nt secondary err code: 113
        nt OS err code: 0
    Fatal NI connect error 12543, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 23-DEC-2013 17:13:55
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12543
    TNS-12543: TNS:destination host unreachable
        ns secondary err code: 12560
        nt main err code: 513
    TNS-00513: Destination host unreachable
        nt secondary err code: 113
        nt OS err code: 0
    started logmerger process
    Mon Dec 23 17:13:56 2013
    Managed Standby Recovery starting Real Time Apply
    MRP0: Background Media Recovery terminated with error 16157
    Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_29230.trc:
    ORA-16157: media recovery not allowed following successful FINISH recovery
    Managed Standby Recovery not using Real Time Apply
    Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
             USING CURRENT LOGFILE DISCONNECT FROM SESSION
    Recovery Slave PR00 previously exited with exception 16157
    MRP0: Background Media Recovery process shutdown (primary_db)
    Fatal NI connect error 12543, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 23-DEC-2013 17:13:58
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12543
    TNS-12543: TNS:destination host unreachable
        ns secondary err code: 12560
        nt main err code: 513
    TNS-00513: Destination host unreachable
        nt secondary err code: 113
        nt OS err code: 0
    Mon Dec 23 17:14:01 2013
    Fatal NI connect error 12543, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 23-DEC-2013 17:14:01
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12543
    TNS-12543: TNS:destination host unreachable
        ns secondary err code: 12560
        nt main err code: 513
    TNS-00513: Destination host unreachable
        nt secondary err code: 113
        nt OS err code: 0
    Error 12543 received logging on to the standby
    FAL[client, ARC0]: Error 12543 connecting to primary_db for fetching gap sequence
    Archiver process freed from errors. No longer stopped
    Mon Dec 23 17:15:07 2013
    Using STANDBY_ARCHIVE_DEST parameter default value as /u02/oracle/archivelogs/primary_db
    Mon Dec 23 17:19:51 2013
    ARCH: Archival stopped, error occurred. Will continue retrying
    ORACLE Instance primary_db - Archival Error
    ORA-16014: log 4 sequence# 7 not archived, no available destinations
    ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
    Mon Dec 23 17:26:18 2013
    RFS[1]: Assigned to RFS process 31456
    RFS[1]: No connections allowed during/after terminal recovery.
    Mon Dec 23 17:26:47 2013
    flashback database to scn 15921680
    ORA-16157 signalled during: flashback database to scn 15921680...
    Mon Dec 23 17:27:05 2013
    alter database recover managed standby database using current logfile disconnect
    Attempt to start background Managed Standby Recovery process (primary_db)
    Mon Dec 23 17:27:05 2013
    MRP0 started with pid=28, OS id=31481
    MRP0: Background Managed Standby Recovery process started (primary_db)
    started logmerger process
    Mon Dec 23 17:27:10 2013
    Managed Standby Recovery starting Real Time Apply
    MRP0: Background Media Recovery terminated with error 16157
    Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_31486.trc:
    ORA-16157: media recovery not allowed following successful FINISH recovery
    Managed Standby Recovery not using Real Time Apply
    Completed: alter database recover managed standby database using current logfile disconnect
    Recovery Slave PR00 previously exited with exception 16157
    MRP0: Background Media Recovery process shutdown (primary_db)
    Mon Dec 23 17:27:18 2013
    RFS[2]: Assigned to RFS process 31492
    RFS[2]: No connections allowed during/after terminal recovery.
    Mon Dec 23 17:28:18 2013
    RFS[3]: Assigned to RFS process 31614
    RFS[3]: No connections allowed during/after terminal recovery.
    Do you have any advice?
    Thanks!
    Alex.

    Hello;
    What's not clear to me in your question at this point:
    What I'm NOT being able to perform:
    If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
    Same situation happens if I manually disconnect the server from the power.
    This is the alert logs I have:"
    Are you trying a failover to the Standby?
    Please advise.
    Is it possible your "valid_for clause" is set incorrectly?
    Would also review this:
    ORA-16014 and ORA-00312 Messages in Alert.log of Physical Standby
    Best Regards
    mseberg

  • Require 9i Primary and Standby redo logs files same size?

    Hi,
    We have 9.2.0.6 Oracle RAC (2 node) and configured data guard (physical standby).
    I want to increase redo log files size, but i can't this do same time primary and standby side.
    Is there a rule, primary and standby database instances have same size redo log files?
    If I increase only primary redo log files, is there any side effect? However I try this issue on test system. I increased all primary redo log files(if status='INACTIVE' drop redo log group and add redo log group, switch logfile,...)
    , but i couldn't changed standby side. So the system is work well. Is this correct solution or not? How can i increase both sides redo log files?
    Thank you for helps..

    Thank you for your helps.. I found this issue answer:
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010448
    Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
    If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
    If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
    Add or drop an online redo log file:
    To add an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
    To drop an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
    Repeat the statement you used in Step 3 on each standby database.
    Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
    bye..

  • Data Guard with Oracle 9i and 10g -- have you done it?

    We have an ERP system (JDEdwards, db size approx 600 GB) and we'd like to copy the data in this system to a database on another computer. We'd use the remote database for reporting, so we need it to be available. We are looking at using Data Guard running in Logical Standby mode.
    The ERP database is Oracle 9i, and we are considering having the Logical Standby database be 10g. Have you done this and if so, what was your experience?
    Here's why we want to do this. There are many tables in the ERP database that contain descending indexes. We can't change this, and it is not supported with Data Guard under Oracle 9.2. Tables with descending indexes do not copy to the logical standby database.
    We were told that this is corrected in a newer release of Oracle, and we were wondering if a 10g database would properly copy tables with descending indexes.
    Thanks in advance for any experiences you can share.
    Best Regards,
    Mike

    What you are trying to do might not be possible. Because when you create logical standby you have to create a physical standby first and convert it. Primary and standby have to be same version.
    In furture it might be possible because 10G will support rolling upgrade of logical standby.
    However even it's possible you have to go through a lot of pain to setup and maintain it because Oracle don't support the setup.
    What you could try are Stream and Replication, I will say Stream is very interesting one. Because Oracle say : "Oracle Streams and Oracle Data Guard (including Data Guard SQL Apply) are independent features based on some common underlying infrastructure and technology. "
    http://www.oracle.com/technology/deploy/availability/htdocs/DataGuardStreams.html

  • How to configure Enterprise Manager Database Control (EMDC) to make it work on 2 servers working (primary and standby) under DG rules

    Hello everybody i use Oracle Database EE 11.2.0.4 with DG.
    In those cases i need to get Enterprise Manager Database Control running against DB with no RAC and no DG i perform the following steps:
    I Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:
    DECLARE
    CURSOR c1 IS
    SELECT owner, synonym_name name
    FROM dba_synonyms
    WHERE table_owner = 'SYSMAN';
    BEGIN
    FOR r1 IN c1 LOOP
    IF r1.owner = 'PUBLIC' THEN
    EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;
    ELSE
    EXECUTE IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name;
    END IF;
    END LOOP;
    END;
    DROP USER mgmt_view CASCADE;
    DROP ROLE mgmt_user;
    DROP USER sysman CASCADE;
    After that i run
    emca -config dbcontrol db -repos recreate
    But what should i do in cases i have 2 servers working (primary and standby) under DG rules?

    Hi ,
    It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control.  This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
    If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
    Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality).  In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
    Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
    Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
    You can use EM 12c cloud control to monitor and manager Standby DB effectively
    Ref to below link for details
    Set Up and Manage Oracle Data Guard using Oracle Enterprise Manager Cloud Control 12c
    Regards,
    Rahul

  • Can I have primary and standby in same OS but different releases.

    All,
    Can I have primary and standby DBs in same OS but in different releases?
    i.e. primary is in RHEL 5 and standby is in RHEL 4, is it ok to setup or do we see any issues?
    Thanks,
    Mahi

    In 10g, dataguard started to support different binaries on primary and standby database servers with the same OS family. For example Microsoft Windows 64-bit on primary and Microsoft Windows 32-bit or Microsoft Windows 64-bit for AMD on standby database server. However with 11g, dataguard also supports different OS on primary and standby servers
    Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries [ID 414043.1]
    Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]

  • DNS / BIND  - Can I configure primary and standby forwarders?

    Hi all,
    I have on Solaris 10 (x86) a DNS server (BIND 9.3.6-P1) that relies exclusively on two “forwarders”: 155.28.144.13and 154.23.134.32.
    The configuration is as follow:
    # cat /etc/named.conf
    acl "CSClan" { 192.168.4.0/24; 192.168.7.0/24; }; //CSC internal LAN ip address range
    options {
            directory "/var/named";
            forward only;
            forwarders {
                    155.28.144.13;
                    154.23.134.32;
                 allow-query { "localnets"; };
    # cat /etc/resolv.conf
    nameserver 127.0.0.1
    When I check with snoop, I can see requests sometimes to one forwarder, sometimes to the other.
    Is it possible to configure DNS to use primarily one forwarder?
    Thanks in advance for your support.
    Best Regards,
    Rui Vilão

    In 10g, dataguard started to support different binaries on primary and standby database servers with the same OS family. For example Microsoft Windows 64-bit on primary and Microsoft Windows 32-bit or Microsoft Windows 64-bit for AMD on standby database server. However with 11g, dataguard also supports different OS on primary and standby servers
    Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries [ID 414043.1]
    Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]

  • V$dataguard_stats showing 8 hrs delay between Primary and standby

    Hello All,
    My Primary and standby database are in sync but v$dataguard_stats on standby server showing 8 hrs delay between Primary and standby.
    DB Version:11.2.0.1.0
    Server :AIX
    Primary:
    SQL> select /*+ FULL(c) PARALLEL(c, 35) */ distinct SEQUENCE# "Last Sequence Generated" FROM V$ARCHIVED_LOG c WHERE (THREAD#,FIRST_TIME ) IN (select /*+ FULL(c) PARALLEL(c, 35) */ THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG c GROUP BY THREAD#);
    Last Sequence Generated
                       4521
    Standby:
    SQL> SELECT  APPL.SEQUENCE# "Last Sequence Applied"
    FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
      2    3  (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
      4  WHERE ARCH.THREAD# = APPL.THREAD#;
    Last Sequence Applied
                     4521
    SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
      2  FROM (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
      3  (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
    WHERE ARCH.THREAD# = APPL.THREAD#;
      4
        Thread Last Sequence Received Last Sequence Applied Difference
             1                   4521                  4521          0
    SQL> select name, 'Hours', to_number(substr(value,5,2)) from v$dataguard_stats where name = 'apply lag' ;
    NAME                             'HOUR TO_NUMBER(SUBSTR(VALUE,5,2))
    apply lag                        Hours                            8------------------------------------------------------------------>>>Problem area

    SQL> SELECT status, error
    FROM V$ARCHIVE_DEST_STATUS
    WHERE STATUS <> 'DEFERRED' AND STATUS <> 'INACTIVE';  2    3
    STATUS    ERROR
    VALID
    VALID
    Standby--Generally in Night it happens that primary and standby 'apply lag' is 8/10/4 hrs .When manually checked database are in sync but  v$dataguard_stats showing difference in hrs
    NAME                             'AL
    SUBSTR(VALUE,1,12)
    apply lag                        ALL
    +00 04:11:03
    SQL> SQL>   2
    NAME                             'SECOND TO_NUMBER(SUBSTR(VALUE,11,2))
    apply lag                        Seconds                             3
    SQL> SQL>   2
    NAME                             'MINUTE TO_NUMBER(SUBSTR(VALUE,8,2))
    apply lag                        Minutes                           11
    SQL> SQL>   2
    NAME                             'HOUR TO_NUMBER(SUBSTR(VALUE,5,2))
    apply lag                        Hours                            4
    SQL> SQL>   2
    NAME                             'DAY TO_NUMBER(SUBSTR(VALUE,2,2))
    apply lag                        Days                            0

  • DG primary and standby

    Hi all,
    11.2.0.1
    Aix 6.1
    I want to monitor the applied logs both on my primary and standby
    using > select client_process, process, sequence#, status from v$managed_standby;
    I want to issue the command on my client laptop so I want compare the output easily, whether logs are synch.
    How can I connect to a standby database s which is not open using client?
    Thanks a lot,
    zxy

    hi,
    Just wanted to share
    On Primary
    SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
    FROM V$ARCHIVED_LOG
    WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
    ORDER BY 1;
    On Standby
    SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied",
    (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
    FROM
    (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN
    (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
    (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN
    (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
    WHERE ARCH.THREAD# = APPL.THREAD# ORDER BY 1;
    SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;
    Reference : http://www.oraclemasters.in/?p=1255
    -- List archivelogs not applied on standby
    SELECT DISTINCT SEQUENCE# FROM V$ARCHIVED_LOG where APPLIED='NO' and sequence# > 100 MINUS (SELECT SEQUENCE# FROM V$ARCHIVED_LOG where APPLIED='YES' AND SEQUENCE# IN (SELECT DISTINCT SEQUENCE# FROM V$ARCHIVED_LOG where APPLIED='NO'));
    -- Give the count of archvielogs not applied on standby
    select thread#,count(sequence#) "COUNT_ARCS_PENDING" from (SELECT DISTINCT THREAD# ,SEQUENCE#  FROM V$ARCHIVED_LOG where APPLIED='NO' and sequence# > 100 MINUS (SELECT THREAD#,SEQUENCE# FROM V$ARCHIVED_LOG  where APPLIED='YES' AND SEQUENCE# IN (SELECT DISTINCT SEQUENCE# FROM V$ARCHIVED_LOG where APPLIED='NO' and sequence# > 100))) group by thread#;

  • Purging archivelogs on Primary and Standby

    Hi all,
    11.2.0.1
    Aix 6.1
    I am monitoring space usage in our FRA for both DG primary and standby. I want to purge all archivelogs once they have been applied to standby. What is the use of it anyway?
    I checked google and I found this procedure,  kindly correct if this is wrong?
    At Primary:
    =========
    RMAN
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    At Standby:
    ========
    RMAN
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    Where do I issue the command DELETE NOPROMPT OBSOLETE ARCHIVELOGS?
    Thanks a lot,
    zxy

    Which tool in oracle dear maintains the FRA/achivelogs? is it RMAN or Dataguard. If it maintains
    them  auto, why is that I still have lots of archivelog at PRIMARY and STANDBY?
    primary:oracle[/backup/flash_recovery_area/PROD/archivelog] ls -lt
    total 200
    drwxr-x---    2 oracle   oinstall       4096 Sep 25 15:59 2013_09_25
    drwxr-x---    2 oracle   oinstall       4096 Sep 24 22:51 2013_09_24
    drwxr-x---    2 oracle   oinstall       4096 Sep 23 22:03 2013_09_23
    drwxr-x---    2 oracle   oinstall       4096 Sep 22 23:02 2013_09_22
    drwxr-x---    2 oracle   oinstall       4096 Sep 21 21:25 2013_09_21
    drwxr-x---    2 oracle   oinstall       4096 Sep 20 22:05 2013_09_20
    drwxr-x---    2 oracle   oinstall       4096 Sep 19 23:00 2013_09_19
    drwxr-x---    2 oracle   oinstall       4096 Sep 18 22:03 2013_09_18
    drwxr-x---    2 oracle   oinstall       4096 Sep 17 22:53 2013_09_17
    drwxr-x---    2 oracle   oinstall       4096 Sep 16 23:00 2013_09_16
    drwxr-x---    2 oracle   oinstall       4096 Sep 15 23:01 2013_09_15
    drwxr-x---    2 oracle   oinstall       4096 Sep 15 02:45 2013_09_01
    drwxr-x---    2 oracle   oinstall       4096 Sep 14 20:32 2013_09_14
    drwxr-x---    2 oracle   oinstall       4096 Sep 13 23:29 2013_09_13
    drwxr-x---    2 oracle   oinstall       4096 Sep 12 22:02 2013_09_12
    drwxr-x---    2 oracle   oinstall       4096 Sep 11 23:43 2013_09_11
    drwxr-x---    2 oracle   oinstall       4096 Sep 10 22:27 2013_09_10
    drwxr-x---    2 oracle   oinstall       4096 Sep 09 23:10 2013_09_09
    drwxr-x---    2 oracle   oinstall       4096 Sep 08 23:00 2013_09_08
    drwxr-x---    2 oracle   oinstall       4096 Sep 07 23:30 2013_09_07
    drwxr-x---    2 oracle   oinstall       4096 Sep 06 23:11 2013_09_06
    drwxr-x---    2 oracle   oinstall       4096 Sep 05 22:02 2013_09_05
    drwxr-x---    2 oracle   oinstall       4096 Sep 04 23:45 2013_09_04
    drwxr-x---    2 oracle   oinstall       4096 Sep 03 22:09 2013_09_03
    drwxr-x---    2 oracle   oinstall       4096 Sep 02 22:33 2013_09_02
    standby:oracle[/backup/flash_recovery_area/PRODDR/archivelog] ls -lt
    total 296
    drwxr-x---    2 oracle   oinstall       4096 Sep 25 15:59 2013_09_25
    drwxr-x---    2 oracle   oinstall       4096 Sep 24 23:24 2013_09_24
    drwxr-x---    2 oracle   oinstall       4096 Sep 23 22:13 2013_09_23
    drwxr-x---    2 oracle   oinstall       4096 Sep 22 23:02 2013_09_22
    drwxr-x---    2 oracle   oinstall       4096 Sep 21 21:39 2013_09_21
    drwxr-x---    2 oracle   oinstall       4096 Sep 20 22:08 2013_09_20
    drwxr-x---    2 oracle   oinstall       4096 Sep 19 23:01 2013_09_19
    drwxr-x---    2 oracle   oinstall       4096 Sep 18 22:23 2013_09_18
    drwxr-x---    2 oracle   oinstall       4096 Sep 17 22:53 2013_09_17
    drwxr-x---    2 oracle   oinstall       8192 Sep 16 23:01 2013_09_16
    drwxr-x---    2 oracle   oinstall       8192 Sep 16 00:46 2013_09_15
    drwxr-x---    2 oracle   oinstall       4096 Sep 15 01:34 2013_09_14
    drwxr-x---    2 oracle   oinstall       4096 Sep 14 01:03 2013_09_13
    drwxr-x---    2 oracle   oinstall       4096 Sep 13 01:48 2013_09_12
    drwxr-x---    2 oracle   oinstall       4096 Sep 12 03:29 2013_09_11
    drwxr-x---    2 oracle   oinstall       4096 Sep 11 01:19 2013_09_10
    drwxr-x---    2 oracle   oinstall       4096 Sep 10 01:54 2013_09_09
    drwxr-x---    2 oracle   oinstall       4096 Sep 09 01:44 2013_09_08
    drwxr-x---    2 oracle   oinstall       4096 Sep 08 01:59 2013_09_07
    drwxr-x---    2 oracle   oinstall       4096 Sep 07 03:30 2013_09_06
    drwxr-x---    2 oracle   oinstall       4096 Sep 06 02:05 2013_09_05
    drwxr-x---    2 oracle   oinstall       4096 Sep 05 03:40 2013_09_04
    drwxr-x---    2 oracle   oinstall       4096 Sep 04 01:48 2013_09_03
    drwxr-x---    2 oracle   oinstall       4096 Sep 03 01:22 2013_09_02
    drwxr-x---    2 oracle   oinstall       4096 Sep 02 02:31 2013_09_01
    drwxr-x---    2 oracle   oinstall       4096 Sep 01 00:08 2013_08_31
    drwxr-x---    2 oracle   oinstall       4096 Aug 31 03:18 2013_08_30
    drwxr-x---    2 oracle   oinstall       4096 Aug 30 00:28 2013_08_29
    drwxr-x---    2 oracle   oinstall       4096 Aug 29 03:51 2013_08_28
    drwxr-x---    2 oracle   oinstall       4096 Aug 28 02:34 2013_08_27
    drwxr-x---    2 oracle   oinstall        256 Aug 26 00:24 2013_08_26
    drwxr-x---    2 oracle   oinstall        256 Aug 25 00:24 2013_08_25
    drwxr-x---    2 oracle   oinstall        256 Aug 24 00:24 2013_08_24
    drwxr-x---    2 oracle   oinstall        256 Aug 23 00:21 2013_08_23
    drwxr-x---    2 oracle   oinstall        256 Aug 22 00:00 2013_08_22
    drwxr-x---    2 oracle   oinstall        256 Aug 21 00:20 2013_08_21
    drwxr-x---    2 oracle   oinstall        256 Aug 20 00:17 2013_08_20
    drwxr-x---    2 oracle   oinstall        256 Aug 19 00:16 2013_08_19
    drwxr-x---    2 oracle   oinstall        256 Aug 18 00:17 2013_08_18
    drwxr-x---    2 oracle   oinstall        256 Aug 17 00:14 2013_08_17
    drwxr-x---    2 oracle   oinstall        256 Aug 16 00:13 2013_08_16
    drwxr-x---    2 oracle   oinstall        256 Aug 15 00:12 2013_08_15
    drwxr-x---    2 oracle   oinstall       4096 Aug 14 10:53 2013_08_14
    drwxr-x---    2 oracle   oinstall       4096 Aug 13 23:34 2013_08_13
    drwxr-x---    2 oracle   oinstall       4096 Aug 12 23:10 2013_08_12
    drwxr-x---    2 oracle   oinstall       4096 Aug 11 21:25 2013_08_11
    drwxr-x---    2 oracle   oinstall       4096 Aug 10 22:44 2013_08_10
    All of the above dates have been applied already. Thanks.

  • Taking RMAN backup of primary and standby databases.

    Hi,
    I am going to setup a Standby for Primary two node RAC to single node standby.
    My doubt is, in standby both primary and standby will have the same db_name. So how can i take the RMAN backup of both primary and standby by using a single catalog.
    That is, we can register the primary DB with catalog using it's db_name. But how can we register the standby with catalog using same db_name as it is already registered.
    Thanks,
    Mahi

    Are you using a physical or logical standby?
    If its a physical standby why do you need to back up both databases? backup the standby and you are done, the backup from the standby can be recovered to either the live serever or the standby if needed, andt hen the archivelogs used to bring it up to date.
    If its a logical standby then change the database name for the standby and you can back both up to the same catalog, or alternativly cretae a new catalog for the standby, either as a new database or a new schema in your existing catalog.

Maybe you are looking for