Error in Standby

Hi,
RAC Database - 11.2 , Standby - 11.2
There was not much space in the archive destination of the primary database, so moved few archive logs to a diff destination within the same server. Few archivelogs were backed by RMAN after the sequence 37635, since
archivelogs from seq from 37631 to 37634 were in a diff destination. Now the standby is comlplaining abaout the seq 37631.
Standby database is unable to fetch an archivelog from the primary database " Fetching gap sequence in thread 1, gap sequence 37631-37730 ".
So i moved the archivelogs from seq 37631 to 37634 were moved to their original destination. The archivelog - 37631 is present in the archive destination of the primary database.
However, still the standby database is unable to find these archivelogs.
Crosschecked the archivelogs, but its unable to run crosscheck on these 4 archivelogs.
First thought to backup these archivelogs and then to restore it back. But RMAN is unable to find these archivelogs :
RMAN> backup archivelog from logseq 37631 until logseq 37634 thread 1;
Starting backup at 06-04-2012 07:47:00
using channel ORA_DISK_1
using channel ORA_DISK_2
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 06-04-2012 07:47:01
Thanks

There was not much space in the archive destination of the primary database, so moved few archive logs to a diff destination within the same server. Few archivelogs were backed by RMAN after the sequence 37635, since
archivelogs from seq from 37631 to 37634 were in a diff destination. Now the standby is comlplaining abaout the seq 37631.
Standby database is unable to fetch an archivelog from the primary database " Fetching gap sequence in thread 1, gap sequence 37631-37730 ".
So i moved the archivelogs from seq 37631 to 37634 were moved to their original destination. The archivelog - 37631 is present in the archive destination of the primary database.
However, still the standby database is unable to find these archivelogs.
Crosschecked the archivelogs, but its unable to run crosscheck on these 4 archivelogs.Does this RMAN will backup & delete or just backup?
If just backup then fine, Once after you moving archives to the original location.
Still standby is an impression as there is GAP, so better if you bounce MRP.
First thought to backup these archivelogs and then to restore it back. But RMAN is unable to find these archivelogs :First check where physically exist, also check from v$archived_log;
once you move to the original location, this step no need still better you catalog them again.
RMAN> crosscheck archivelog all;
RMAN> delete expired archivelog all;
- now make sure all the archives exist in archive destination, then
RMAN> catalog start with 'archive location';
This command will search for all the archives, if any new archives found then it will register it.
You have less archive gaps, so you are fine with this procedure, or restore archives from backup and SCP to standby and then perform recovery.
Also you can check procedure of incremental roll forward http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
HTH.

Similar Messages

  • Errors in Standby Alert Log

    Dear All,
    We have 10gR2 RAC with Physical Data Guard environment using ASM and both have same disk group names. Lets say the primary database name is prim and stand by database name is stdby. We are getting the following errors in alert log file of standby:
    Clearing online redo logfile 9 +DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo
    Clearing online log 9 of thread 2 sequence number 0
    Errors in file c:\oracle\product\10.2.0\admin\stdby\bdump\stdby1_mrp0_4288.trc:
    ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [9] [2]
    ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [9] [2] [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-17503: Message 17503 not found; No message file for product=RDBMS, facility=ORA; arguments: [2] [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-15173: entry 'prim does not exist in directory '/'
    Errors in file c:\oracle\product\10.2.0\admin\stdby\bdump\stdby1_mrp0_4288.trc:
    ORA-00344: Message 344 not found; No message file for product=RDBMS, facility=ORA; arguments: [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-17502: Message 17502 not found; No message file for product=RDBMS, facility=ORA; arguments: [4] [+DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo]
    ORA-15173: entry 'prim' does not exist in directory '/'The errors show that the standby is trying to find files in directory +DG_DATAFILES_AND_FB/prim/onlinelog which apparently doesn’t exist on standby. Below is the result of query for redo logs on standby:
    SQL> SELECT group#, status, member FROM v$logfile where member like '%prim/%'
        GROUP#   STATUS         MEMEBER
             9                            +DG_DATAFILES_AND_FB/prim/onlinelog/group9_2a.rdo
             1                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo1.rdo
            10                           +DG_DATAFILES_AND_FB/prim/onlinelog/group10_1a.rdo
             2                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo2.rdo
             3                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo3.rdo
             4                            +DG_DATAFILES_AND_FB/prim/standbylogs/sredo4.rdo
            11                           +DG_DATAFILES_AND_FB/prim/onlinelog/group11_1a.rdo
            12                           +DG_DATAFILES_AND_FB/prim/onlinelog/group12_2a.rdo
    8 rows selected.  How we can get rid of this error?
    Best regards,

    Generally when we setup standby, are these directories created automatically (i mean '+DG_DATAFILES_AND_FB/prim and '+DG_DATAFILES_AND_FB/stdby) on standby? My understanding is that by default only '+DG_DATAFILES_AND_FB/stdby is created.
    What if i want to put all logs (that are in stdby and prim) in +DG_DATAFILES_AND_FB/stdby?What is the value of DB_CREATE_FILE_DEST and you also set DB_CREATE_ONLINE_LOG_DEST_<> value?
    Also i don't know whether it is relevant or not, but we performed a roll forward for standby using metalink doc id: 836986.1 (Steps to perform for Rolling forward a standby database using RMAN incremental backup when primary and standby are in ASM filesystem). But i am not sure whether the error started coming after that or not.
    But in the beginning for sure, there were no such errors. Just trying to put as much information as i can.Even though you are using same disk groups, But the sub directory names such as "prim","stby" are different,
    After you changed the values of DB_FILE_NAME_CONVERT/LOG_FILE_NAME_CONVERT have you bounced database ? They are static parameters.
    Bounce it and then start MRP, initally errors are expected even it happens during RMAN duplicate.
    logfile member shows in database but not on physical disk, not match
    if you haven't used RMAN duplicate then drop and create redo logs, this can be done at any time.

  • Ora 00364,ora 00305 ora 00312 errors in standby database

    hii friends i got a problem in my standby database yesterday i performed database restoration activity, restoration is done and database is in MRM modemout stage, archive gap sequence is completed and is in synchronize with primary but suddenly after some time i got in alertlog media recovery waiting for thread one and from there its is showing nothing in alert log after stoping mrm and restarting database i got few errors please check them and suggest me some solution
    alert log file
    RFS[87]: Assigned to RFS process 7912
    RFS[87]: Identified database type as 'physical standby'
    Tue Jan 4 17:12:14 2011
    RFS[87]: Archived Log: '/backup/standby_archivelogs/1_87532_622555682.dbf'
    Tue Jan 4 17:12:17 2011
    Media Recovery Log /backup/standby_archivelogs/1_87532_622555682.dbf
    Media Recovery Waiting for thread 1 sequence 87533
    Tue Jan 4 17:55:35 2011
    alter database recover managed standby database cancel
    Tue Jan 4 17:55:38 2011
    MRP0: Background Media Recovery cancelled with status 16037
    Tue Jan 4 17:55:38 2011
    Errors in file /oracle/app/oracle/admin/****/bdump/*******mrp03017.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Recovery interrupted!
    Tue Jan 4 17:55:39 2011
    Waiting for MRP0 pid 3017 to terminate
    Tue Jan 4 17:55:39 2011
    Errors in file /oracle/app/oracle/admin/****/bdump/****mrp03017.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Tue Jan 4 17:55:39 2011
    MRP0: Background Media Recovery process shutdown (****)
    Tue Jan 4 17:55:40 2011
    Managed Standby Recovery Canceled (****)
    Completed: alter database recover managed standby database cancel
    Tue Jan 4 17:55:56 2011
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    Tue Jan 4 17:55:56 2011
    Attempt to start background Managed Standby Recovery process (****)
    MRP0 started with pid=16, OS id=9300
    Tue Jan 4 17:55:56 2011
    MRP0: Background Managed Standby Recovery process started (****)
    Managed Standby Recovery not using Real Time Apply
    Tue Jan 4 17:56:01 2011
    Errors in file /oracle/app/oracle/admin/****/bdump/****mrp09300.trc:
    ORA-00367: checksum error in log file header
    ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
    ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
    Clearing online redo logfile 2 /dev/vg04/rREDOR21
    Clearing online log 2 of thread 1 sequence number 87533
    Tue Jan 4 17:56:01 2011
    Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
    Clearing online redo logfile 2 complete
    Media Recovery Waiting for thread 1 sequence 87533
    Tue Jan 4 17:56:02 2011
    Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    Tue Jan 4 17:57:56 2011
    alter database recover managed standby database cancel
    Tue Jan 4 17:57:56 2011
    MRP0: Background Media Recovery cancelled with status 16037
    Tue Jan 4 17:57:56 2011
    Errors in file /oracle/app/oracle/admin/APMBDRDB/bdump/apmbdrdb_mrp0_9300.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Recovery interrupted!
    Tue Jan 4 17:57:57 2011
    Waiting for MRP0 pid 9300 to terminate
    Tue Jan 4 17:57:57 2011
    Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
    ORA-16037: user requested cancel of managed recovery operation
    Tue Jan 4 17:57:57 2011
    MRP0: Background Media Recovery process shutdown (*****)
    Tue Jan 4 17:57:58 2011
    Managed Standby Recovery Canceled (*****)
    Completed: alter database recover managed standby database cancel
    Tue Jan 4 17:58:10 2011
    Shutting down instance: further logons disabled
    Tue Jan 4 17:58:10 2011
    Stopping background process CJQ0
    Tue Jan 4 17:58:10 2011
    Stopping background process MMNL
    Tue Jan 4 17:58:11 2011
    Stopping background process MMON
    Tue Jan 4 17:58:12 2011
    Shutting down instance (immediate)
    License high water mark = 3
    Tue Jan 4 17:58:12 2011
    Stopping Job queue slave processes
    Tue Jan 4 17:58:12 2011
    Job queue slave processes stopped
    Tue Jan 4 17:58:12 2011
    ALTER DATABASE CLOSE NORMAL
    ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
    Tue Jan 4 17:58:12 2011
    ALTER DATABASE DISMOUNT
    Completed: ALTER DATABASE DISMOUNT
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Tue Jan 4 17:58:17 2011
    ARCH shutting down
    ARC1: Archival stopped
    Tue Jan 4 17:58:22 2011
    ARCH shutting down
    ARC0: Archival stopped
    Tue Jan 4 17:58:24 2011
    ARCH: Archival disabled due to shutdown: 1089
    Shutting down archive processes
    Archiving is disabled
    Archive process shutdown avoided: 0 active
    Tue Jan 4 17:58:33 2011
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =242
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.1.0.
    System parameters with non-default values:
    processes = 2000
    sga_max_size = 3221225472
    __shared_pool_size = 1006632960
    shared_pool_size = 637534208
    __large_pool_size = 503316480
    large_pool_size = 503316480
    __java_pool_size = 16777216
    __streams_pool_size = 0
    sga_target = 3221225472
    control_files = /dev/vg01/rCTRLR1, /dev/vg01/rCTRLR2, /dev/vg01/rCTRLR3
    db_block_size = 8192
    __db_cache_size = 1677721600
    db_cache_size = 637534208
    compatible = 10.2.0.1.0
    log_archive_config = DG_CONFIG=(APMBPROD,APMBDRDB)
    log_archive_dest_1 = LOCATION=/archive/archivelogs/ valid_for=(ONLINE_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=APMBDRDB
    log_archive_dest_2 =
    log_archive_dest_4 = service=APMBPROD LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=APMBPROD
    log_archive_max_processes= 2
    standby_archive_dest = /backup/standby_archivelogs
    fal_client = APMBDRDB
    fal_server = APMBPROD
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    job_queue_processes = 10
    background_dump_dest = /oracle/app/oracle/admin/APMBDRDB/bdump
    user_dump_dest = /oracle/app/oracle/admin/APMBDRDB/udump
    core_dump_dest = /oracle/app/oracle/admin/APMBDRDB/cdump
    audit_file_dest = /oracle/app/oracle/admin/APMBDRDB/adump
    db_name = APMBPROD
    db_unique_name = APMBDRDB
    open_cursors = 300
    pga_aggregate_target = 1703936000
    PMON started with pid=2, OS id=9371
    PSP0 started with pid=3, OS id=9373
    MMAN started with pid=4, OS id=9375
    DBW0 started with pid=5, OS id=9377
    LGWR started with pid=6, OS id=9380
    CKPT started with pid=7, OS id=9382
    SMON started with pid=8, OS id=9384
    RECO started with pid=9, OS id=9386
    CJQ0 started with pid=10, OS id=9388
    MMON started with pid=11, OS id=9390
    MMNL started with pid=12, OS id=9392
    Tue Jan 4 17:58:35 2011
    ALTER DATABASE MOUNT
    Tue Jan 4 17:58:39 2011
    Setting recovery target incarnation to 2
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=14, OS id=9395
    Tue Jan 4 17:58:39 2011
    ARC0: Archival started
    ARC1: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Tue Jan 4 17:58:39 2011
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC0: Thread not mounted
    ARC1 started with pid=15, OS id=9397
    ARC1: Becoming the heartbeat ARCH
    ARC1: Thread not mounted
    Tue Jan 4 17:58:39 2011
    Successful mount of redo thread 1, with mount id 3471861451
    Tue Jan 4 17:58:39 2011
    Physical Standby Database mounted.
    Completed: ALTER DATABASE MOUNT
    Tue Jan 4 17:58:51 2011
    ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    Tue Jan 4 17:58:51 2011
    Attempt to start background Managed Standby Recovery process ()
    MRP0 started with pid=16, OS id=9400
    Tue Jan 4 17:58:51 2011
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    Tue Jan 4 17:58:57 2011
    Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
    ORA-00367: checksum error in log file header
    ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
    ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
    Clearing online redo logfile 2 /dev/vg04/rREDOR21
    Clearing online log 2 of thread 1 sequence number 87533
    Tue Jan 4 17:58:57 2011
    Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
    Clearing online redo logfile 2 complete
    Media Recovery Waiting for thread 1 sequence 87533
    Tue Jan 4 17:58:57 2011
    Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
    Tue Jan 4 19:37:24 2011
    alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
    Tue Jan 4 19:37:24 2011
    There are 1 logfiles specified.
    ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
    Completed: alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
    Tue Jan 4 19:37:27 2011
    Media Recovery Log /backup/standby_archivelogs/1_87533_622555682.dbf
    Tue Jan 4 19:37:43 2011
    Media Recovery Waiting for thread 1 sequence 87534
    from here it is showing no errors or nothing in my alert log file from yesterday evening

    No version number, no definition of what you mean by "standby database" and not a clue as to what you mean by "restore" or why you did it.
    No help is possible at this time.
    PS: We do not guess at what someone means by "MRM modemout stage" ... you need to define your terms.

  • Error in Standby alert log continuously

    After I setup the Physical Standby and Logical Standby database, I found lots of errors showing in alert log of Standby database.
    LOGMINER: Error 308 encountered, failed to read missing logfile /u01/oradata/arch2/primary/1_1_111111111.dbf
    According to the doc, I set the values LOG_ARCHIVE_DEST_3 in case of role transition:
    (for primary)
    LOCATION=/u01/oradata/arch2/primary/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=primary(for standby)
    LOCATION=/u01/oradata/arch2/standby/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=standbyWhen I run this command, the error keeps showing in the alert log continuously! Why does it look for the path "primary", but not "standby" ?
    ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
    Help! Does anyone know the problem? All new data can't be found in the logical standby now.
    Thank you!

    When I enable the LOG_ARCHIVE_DEST_STATE_3, the errors show in alert log again!
    LOGMINER: Error 308 encountered, failed to read missing logfile /u01/oradata/arch2/primary/1_1_111111111.dbf
    SELECT TYPE,STATUS FROM V$LOGSTDBY;
    COORDINATOR
    ORA-01291: missing logfile
    here are my parameters:
    Primary:
    LOG_ARCHIVE_DEST_1='LOCATION=/u01/oradata/arch/ MANDATORY VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary'
    LOG_ARCHIVE_DEST_2='SERVICE=ORCL_SB LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=standby'
    LOG_ARCHIVE_DEST_3='LOCATION=/u01/oradata/arch2/primary/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=primary'
    Standby:
    LOG_ARCHIVE_DEST_1='LOCATION=/u01/oradata/arch/ MANDATORY VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=standby'
    LOG_ARCHIVE_DEST_2='SERVICE=ORCL_PRI LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary'
    LOG_ARCHIVE_DEST_3='LOCATION=/u01/oradata/arch2/standby/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=standby'
    Why does the path in primary parameter file show in standby alert log??

  • Error in standby db while applying logs

    Hi,
    we have a manual standby db of version 9.2.0.6 on sun solaris
    in alert log file i found error in one og the log i.e Errors with log /arch/log/1_1817.dbf
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Wed Oct 22 18:33:03 2008
    Media Recovery Log /arch/log/2_1616.dbf
    Wed Oct 22 18:35:47 2008
    ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Wed Oct 22 18:35:47 2008
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Wed Oct 22 18:35:47 2008
    Media Recovery Log /arch/log/2_1617.dbf
    Wed Oct 22 18:36:50 2008
    ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Wed Oct 22 18:36:50 2008
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Wed Oct 22 18:36:50 2008
    Media Recovery Log /arch/log/1_1817.dbf
    Errors with log /arch/log/1_1817.dbf
    ORA-308 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ...
    Wed Oct 22 18:36:50 2008
    ALTER DATABASE RECOVER CANCEL
    Wed Oct 22 18:36:50 2008
    Media Recovery Cancelled
    Completed: ALTER DATABASE RECOVER CANCEL
    Wed Oct 22 18:37:38 2008
    alter database open read only
    Wed Oct 22 18:37:38 2008
    SMON: enabling cache recovery
    Wed Oct 22 18:37:38 2008
    Database Characterset is WE8ISO8859P1
    replication_dependency_tracking turned off (no async multimaster replication fo
    nd)
    Completed: alter database open read only
    Wed Oct 22 18:39:33 2008
    Errors in file /arch/dump/udump/icai_ora_25288.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [1823949223], [0], [197
    003713], [4194306], [], []
    Wed Oct 22 18:39:45 2008
    Errors in file /arch/dump/udump/icai_ora_25288.trc:
    ORA-00600: internal error code, arguments: [2662], [0], [1823949225], [0], [197
    003713], [4194306], [], []
    ORA-00600: internal error code, arguments: [2662], [0], [1823949223], [0], [197
    003713], [4194306], [], []
    003713], [4194306], [], []i want to konw the whether the system had applied the 1_1817.dbf logs or not if db server generates an error on one of the logs...
    looking for your reply...

    SQL> select * from v$log_history;
         RECID      STAMP    THREAD#  SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
          3421  668092912          2       1613    1821523608 08-OCT-08   1822019922
          3422  668092971          1       1809    1821576072 08-OCT-08   1821777080
          3423  668093151          1       1810    1821777080 10-OCT-08   1822019918
          3424  668093340          1       1811    1822019918 11-OCT-08   1822282436
          3425  668284338          2       1614    1822019922 11-OCT-08   1822677394
          3426  668284525          1       1812    1822282436 13-OCT-08   1822526199
          3427  668284721          1       1813    1822526199 14-OCT-08   1822781536
          3428  668801898          2       1615    1822677394 15-OCT-08   1823381495
          3429  668801993          1       1814    1822781536 15-OCT-08   1823106551
          3430  668802398          1       1815    1823106551 17-OCT-08   1823381490
          3431  668802577          1       1816    1823381490 18-OCT-08   1823923486
         RECID      STAMP    THREAD#  SEQUENCE# FIRST_CHANGE# FIRST_TIM NEXT_CHANGE#
          3432  668802783          2       1616    1823381495 18-OCT-08   1823814529
          3433  668802947          2       1617    1823814529 20-OCT-08   1824079514
    453 rows selected.
    SQL>so here we can see that there is not recid for 1817 sequence that has been corrupted ,so now does it mean that archived have not been applied to the stanby database.....
    SQL> SELECT MAX(R.SEQUENCE#) LAST_SEQ_RECD, MAX(L.SEQUENCE#) LAST_SEQ_SENT FROM
      2  V$ARCHIVED_LOG R, V$LOG L WHERE
      3  R.DEST_ID=1 AND L.ARCHIVED='YES';
    LAST_SEQ_RECD LAST_SEQ_SENT
    ------------- -------------Edited by: user00726 on Oct 23, 2008 3:21 AM

  • Error in standby database

    Hi, I've Two database one for primary(GISC) and one for standby (GISCST) when i start open standby database i appeare erro :
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'D:\ORACLE\ORADATA\ORCLSB\SYSTEM01.DBF'
    I take the copy the datafiles from primary database and Pase them to the Standby database
    and the Enviroment of two database is :
    SPfile for primary(GISC) IS:
    *.compatible='10.2.0.3'
    *.control_files='C:\oracle\product\10.2.0\oradata\gisc\CONTROL01.CTL','C:\oracle\product\10.2.0\oradata\gisc\CONTROL02.CTL','C:\oracle\product\10.2.0\oradata\gisc\CONTROL03.CTL'
    *.db_block_size=8192
    *.db_cache_size=30M#DEMO
    *.db_file_multiblock_read_count=16
    *.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\oradata\gisc','C:\oracle\product\10.2.0\oradata\giscst'
    *.db_name='GISC'
    *.fal_client='gisc'
    *.fal_server='giscst'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG= (GISC, GISCST)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\flash_recovery_area\ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=GISC'
    *.LOG_ARCHIVE_DEST_2='SERVICE=GISCST VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=GISCST'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\oradata\gisc','C:\oracle\product\10.2.0\oradata\giscst'
    *.optimizer_mode='choose'
    *.parallel_threads_per_cpu=4#SMALL
    *.pga_aggregate_target=30M#DEMO
    *.query_rewrite_enabled='true'
    *.query_rewrite_integrity='trusted'
    *.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
    *.shared_pool_size=50M#DEMO
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.star_transformation_enabled='true'
    *db_unique_name='gisc'
    *.service_name='gisc'
    *.instance_name='gisc'
    *.LOG_ARCHIVE_FORMAT='log%t_%s_%r.arc'
    listener.ora for primary(GISC):
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.2)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = c:\oracle\product\10.2.0)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = gisc)
    (ORACLE_HOME = C:\oracle\product\10.2.0)
    (SID_NAME = GISC)
    (SID_DESC =
    (GLOBAL_DBNAME = GISC_DGMGRL)
    (ORACLE_HOME = C:\oracle\product\10.2.0)
    (SID_NAME = GISC)
    TNSNAME For (GISC):
    GISC =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.2)(PORT = 1521))
    (CONNECT_DATA =
    (SID = GISC_DGMGRL)
    GISCST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.3)(PORT = 1521))
    (CONNECT_DATA =
    (SID = GISCST_DGMGRL)
    SPfile for Standby database (GISCST):
    *.compatible='10.2.0.3'
    *.control_files='C:\oracle\product\10.2.0\oradata\giscst\CONTROL01.CTL','C:\oracle\product\10.2.0\oradata\giscst\CONTROL02.CTL','C:\oracle\product\10.2.0\oradata\giscst\CONTROL03.CTL'
    *.db_block_size=8192
    *.db_cache_size=30M#DEMO
    *.db_file_multiblock_read_count=16
    *.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\oradata\gisc','C:\oracle\product\10.2.0\oradata\giscst'
    *.db_name='GISC'
    *.fal_client='giscst'
    *.fal_server='gisc'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG= (GISC, GISCST)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\flash_recovery_area\ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=GISCST'
    *.LOG_ARCHIVE_DEST_2='SERVICE=GISC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=GISC'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\oradata\gisc','C:\oracle\product\10.2.0\oradata\giscst'
    *.optimizer_mode='choose'
    *.parallel_threads_per_cpu=4#SMALL
    *.pga_aggregate_target=30M#DEMO
    *.query_rewrite_enabled='true'
    *.query_rewrite_integrity='trusted'
    *.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
    *.shared_pool_size=50M#DEMO
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.star_transformation_enabled='true'
    *db_unique_name='giscst'
    *.service_name='giscst'
    *.instance_name='giscst'
    *.LOG_ARCHIVE_FORMAT='log%t_%s_%r.arc'
    listener.ora for standby (GISCST):
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.3)(PORT = 1521))
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = c:\oracle\product\10.2.0)
    (PROGRAM = extproc)
    (SID_DESC =
    (GLOBAL_DBNAME = giscst)
    (ORACLE_HOME = C:\oracle\product\10.2.0)
    (SID_NAME = GISCST)
    (SID_DESC =
    (GLOBAL_DBNAME = GISCST_DGMGRL)
    (ORACLE_HOME = C:\oracle\product\10.2.0)
    (SID_NAME = GISCST)
    TNSNAME for standby (GISCST):
    GISCST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.3)(PORT = 1521))
    (CONNECT_DATA =
    (SID = GISCST_DGMGRL)
    GISC =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.2)(PORT = 1521))
    (CONNECT_DATA =
    (SID = GISC_DGMGRL)
    then i do ping to service :
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\Administrator>tnsping gisc
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.3.0 - Production on 12-FEB-2
    012 09:49:17
    Copyright (c) 1997, 2006, Oracle. All rights reserved.
    Used parameter files:
    C:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = 192.168.0.2)(PORT = 1521))) (CONNECT_DATA = (SID = GISC_DGMGRL)))
    OK (0 msec)
    C:\Users\Administrator>tnsping giscst
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.3.0 - Production on 12-FEB-2
    012 09:49:40
    Copyright (c) 1997, 2006, Oracle. All rights reserved.
    Used parameter files:
    C:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = 192.168.0.3)(PORT = 1521))) (CONNECT_DATA = (SID = GISCST_DGMGRL)))
    OK (10 msec)
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\gis>tnsping gisc
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.3.0 - Production on 12-FEB-2
    012 09:52:22
    Copyright (c) 1997, 2006, Oracle. All rights reserved.
    Used parameter files:
    C:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = 192.168.0.2)(PORT = 1521))) (CONNECT_DATA = (SID = GISC_DGMGRL)))
    OK (10 msec)
    C:\Users\gis>tnsping giscst
    TNS Ping Utility for 32-bit Windows: Version 10.2.0.3.0 - Production on 12-FEB-2
    012 09:52:30
    Copyright (c) 1997, 2006, Oracle. All rights reserved.
    Used parameter files:
    C:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = 192.168.0.3)(PORT = 1521))) (CONNECT_DATA = (SID = GISCST_DGMGRL)))
    OK (0 msec)

    CKPT wrote:
    Hello,
    Do as follows.
    From standby:-
    SQL> alter database recover managed standby database disconnect from session;Later post the content from alert log file.
    Now, Post below Commands from primary & check for any errors in Alert log file of primary
    set lines 100
    set numwidth 15
    column ID format 99
    column "SRLs" format 99
    column active format 99
    col type format a4
    select     ds.dest_id id
    ,     ad.status
    ,     ds.database_mode db_mode
    ,     ad.archiver type
    ,     ds.recovery_mode
    ,     ds.protection_mode
    ,     ds.standby_logfile_count "SRLs"
    ,     ds.standby_logfile_active active
    ,     ds.archived_seq#
    from     v$archive_dest_status     ds
    ,     v$archive_dest          ad
    where     ds.dest_id = ad.dest_id
    and     ad.status != 'INACTIVE'
    order by
         ds.dest_idID STATUS DB_MODE TYPE RECOVERY_MODE PROTECTION_MODE SRLs ACTIVE
    ARCHIVED_SEQ#
    1 VALID MOUNTED-STANDBY ARCH MANAGED MAXIMUM PERFORMANCE 0 0
    0
    2 VALID MOUNTED-STANDBY ARCH MANAGED MAXIMUM PERFORMANCE 0 0
    0
    11 VALID MOUNTED-STANDBY ARCH MANAGED MAXIMUM PERFORMANCE 0 0
    0
    >
    SQL> select error_code,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') ,message,facility from v$dataguard_status;ERROR_CODE TO_CHAR(TIMESTAMP,'D
    MESSAGE
    FACILITY
    0 15-FEB-2012 13:05:02
    ARC0: Archival started
    Log Transport Services
    0 15-FEB-2012 13:05:02
    ARC1: Archival started
    Log Transport Services
    ERROR_CODE TO_CHAR(TIMESTAMP,'D
    MESSAGE
    FACILITY
    0 15-FEB-2012 13:05:02
    ARC1: Becoming the 'no FAL' ARCH
    Log Transport Services
    0 15-FEB-2012 13:05:02
    ARC1: Becoming the 'no SRL' ARCH
    ERROR_CODE TO_CHAR(TIMESTAMP,'D
    MESSAGE
    FACILITY
    Log Transport Services
    0 15-FEB-2012 13:05:02
    ARC0: Becoming the heartbeat ARCH
    Log Transport Services
    0 15-FEB-2012 13:09:57
    ERROR_CODE TO_CHAR(TIMESTAMP,'D
    MESSAGE
    FACILITY
    Attempt to start background Managed Standby Recovery process
    Log Apply Services
    0 15-FEB-2012 13:09:57
    MRP0: Background Managed Standby Recovery process started
    Log Apply Services
    ERROR_CODE TO_CHAR(TIMESTAMP,'D
    MESSAGE
    FACILITY
    0 15-FEB-2012 13:10:03
    Managed Standby Recovery not using Real Time Apply
    Log Apply Services
    0 15-FEB-2012 13:10:03
    Media Recovery Waiting for thread 1 sequence 7
    Log Apply Services
    ERROR_CODE TO_CHAR(TIMESTAMP,'D
    MESSAGE
    FACILITY
    9 rows selected.

  • ORA-01157: cannot identify/lock data file error in standby database.

    Hi,
    i have a primary database and standby database (11.2.0.1.0) running in ASM with different diskgroup names. I applied an incremental backup on standby database to resolve archive log gap and generated a controlfile for standby in primary database and restored the controlfile in standby database.But when i started the MRP process its not starting and thows error in alert log ORA-01157: cannot identify/lock data file. When i queried the standby database file it shows the location on primary database datafiles names not the standby database.
    PRIMARY DATABASE
    SQL> select name from v$datafile;
    NAME
    +DATA/oradb/datafile/system.256.788911005
    +DATA/oradb/datafile/sysaux.257.788911005
    +DATA/oradb/datafile/undotbs1.258.788911005
    +DATA/oradb/datafile/users.259.788911005
    STANDBY DATABASE
    SQL> select name from v$datafile;
    NAME
    +STDBY/oradb/datafile/system.256.788911005
    +STDBY/oradb/datafile/sysaux.257.788911005
    +STDBY/oradb/datafile/undotbs1.258.788911005
    +STDBY/oradb/datafile/users.259.788911005
    The Actual physical location of standby database files in ASM in standby server is shown below
    ASMCMD> pwd
    +STDBY/11gdb/DATAFILE
    ASMCMD>
    ASMCMD> ls
    SYSAUX.259.805921967
    SYSTEM.258.805921881
    UNDOTBS1.260.805922023
    USERS.261.805922029
    ASMCMD>
    ASMCMD> pwd
    +STDBY/11gdb/DATAFILE
    i even tried to rename the datafiles in standby database but it throws error
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01275: Operation RENAME is not allowed if standby file management is
    automatic.
    Regards,
    007

    Hi saurabh,
    I tried to rename the datafiles in standby database after restoring it throws the below error
    ERROR at line 1:
    ORA-01511: error in renaming log/data files
    ORA-01275: Operation RENAME is not allowed if standby file management is
    automatic.
    Also in my pfile i have mentioned the below parameters
    *.db_create_file_dest='+STDBY'
    *.db_domain=''
    *.db_file_name_convert='+DATA','+STDBY'
    *.db_name='ORADB'
    *.db_unique_name='11GDB'
    Regards,
    007

  • Error in standby server

    The standby server not receiving archivelogs continuesly . Scenario : in 10 files transmission,database transmitting only 7 or 8 files. remaining files i am copying maunally & then resolving the gap sequence .when i see alert log file in standby server I am geting an error like follows.what should i do?
    FAL[client]: Failed to request gap sequence
    GAP - thread 1 sequence 152366-152366
    DBID 3500755944 branch 694072247
    FAL[client]: All defined FAL servers have been attempted.
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    -------------------------------------------------------------

    Post Operating System (OS) name & version for DB server system.
    Post results of
    SELECT * from v$version
    What clues exist in alert_SID.log file on Primary?

  • Error in standby alertlog

    Hi,
    in10g R2 Unix
    In stand by alertlog I have :
    ALTER DATABASE RECOVER    CONTINUE DEFAULT
    Mon Jun  6 11:02:46 2011
    Media Recovery Log /data01/oracle/MYDB/arch01/arcMYDB1_23448_620900925.arc
    Errors with log /data01/oracle/MYDB/arch01/arcMYDB1_23448_620900925.arc
    ORA-308 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT  ..But on primary archived log of 23448 sequence is generated at 11h30 :
    -rw-r-----  1 oracle dba 47700480 jun  6 10:26 arcMYDB1_23446_620900925.arc
    -rw-r-----  1 oracle dba 47694848 jun  6 10:30 arcMYDB1_23447_620900925.arc
    -rw-r-----  1 oracle dba 47700480 jun  6 11:33 arcMYDB1_23448_620900925.arcCan anyone explain me why and how Standby looks for 23448 at 11h02 ; before that is being generated ??
    Thank you.

    Thank Forstmann,
    DATABASE_ROLE
    PRIMARY
    SQL> show parameter log_archive_dest
    show parameter log_archive_config
    NAME                                 TYPE        VALUE
    log_archive_dest                     string
    log_archive_dest_1                   string      location=/c00_ora_MYDB/arc
                                                     hor1/ VALID_FOR=(ALL_LOGFILES,
                                                     ALL_ROLES) DB_UNIQUE_NAME= log_archive_dest_10                  string
    log_archive_dest_2                   string      SERVICE=MYDBLIX  VALID_FOR
                                                     =(ONLINE_LOGFILES,PRIMARY_ROLE
                                                     ) DB_UNIQUE_NAME=MYDBLIX
    log_archive_dest_3                   string      SERVICE=MYDBLMW  VALID_FOR
                                                     =(ONLINE_LOGFILES,PRIMARY_ROLE
    NAME                                 TYPE        VALUE
                                                     ) DB_UNIQUE_NAME=MYDBLMW
    log_archive_dest_4                   string
    log_archive_dest_5                   string
    log_archive_dest_6                   string
    log_archive_dest_7                   string
    log_archive_dest_8                   string
    log_archive_dest_9                   string
    log_archive_dest_state_1             string      enable
    log_archive_dest_state_10            string      enable
    log_archive_dest_state_2             string      enable
    log_archive_dest_state_3             string      enable
    NAME                                 TYPE        VALUE
    log_archive_dest_state_4             string      enable
    log_archive_dest_state_5             string      enable
    log_archive_dest_state_6             string      enable
    log_archive_dest_state_7             string      enable
    log_archive_dest_state_8             string      enable
    log_archive_dest_state_9             string      enable
    SQL>
    NAME                                 TYPE        VALUE
    log_archive_config                   string      DG_CONFIG=(MYDB,MYDBLI
                                                     X,MYDBLXX)Tnarsh,
    how to see protection mode of your Primary Database?
    Thanks to all.

  • RMAN-20999: internal error on standby....help

    Hey guys,
    A little background of events of what happened:
    1) data guard got broken
    2) rebuild data guard
    in the rebuild process I took the /backup mount point from primary database NFS mounted it to the alternate database.(The reason I did that was because it was going to take too much time to transfer over the backups from the primary to the alternate).
    During this process while /backup1 was NFS mounted, i had to add "alter system set event='10298 trace name context forever, level 32'scope= spfile ; " to my spfile.
    3) finished the data guard rebuild
    4) NFS unmounted /backup from primary (take out alter system set event='10298 trace name context forever, level 32'scope= spfile ; from spfile)
    5)bounce database and re sync data guard
    5) data guard is in sync and everything is fine
    Now comes the trouble..
    went to the standby side and went to run rman.
    here it is:
    RMAN> @connect.rman
    RMAN> connect target *
    connected to target database: AFCD1D1 (DBID=3242165457, not open)
    RMAN> connect catalog *
    connected to recovery catalog database
    RMAN> **end-of-file**
    RMAN> resync catalog;
    starting partial resync of recovery catalog
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of resync command on default channel at 12/08/2011 15:05:16
    RMAN-20999: internal error
    RMAN>
    so I thought maybe the primary database needs to do a full re sync.
    I did that still no help
    I also search on oracle support, couldn't find anything useful.
    Just to play with it
    -I went to the primary db-recreated the standby controlfile
    -went to the standby , shut db down. copied the standby controlfile over to the standby server
    -restarted the dataguard
    Data Guard is in sync
    went to rman and same issue.
    Any help would be appreciated!!
    PS. The rman backups were working before data guard was broken.
    Edited by: 867954 on Dec 8, 2011 12:45 PM

    RMAN-20999: internal errorInternal errors require help from Oracle support. They have the tools to trace the problem.
    Werner

  • Hitting with ORA-16664 error in standby Database.

    DGMGRL> show database kohldbpa_m2_stby
    Database - kohldbpa_m2_stby
      Role:            PHYSICAL STANDBY
      Intended State:  APPLY-ON
      Transport Lag:   (unknown)
      Apply Lag:       (unknown)
      Real Time Query: OFF
      Instance(s):
        kohldbpa1 (apply instance)
        kohldbpa2
        kohldbpa3
        kohldbpa4
    Database Status:
    DGM-17016: failed to retrieve status for database "kohldbpa_m2_stby"
    ORA-16664: unable to receive the result from a database
    all the archives getting transported and apllying on the DR side...But we are hitting the error in dgmgrl

    DGMGRL> show database verbose kohldbpa_m2;
    Database - kohldbpa_m2
      Role:            PRIMARY
      Intended State:  TRANSPORT-ON
      Instance(s):
        kohldbpa1
        kohldbpa2
        kohldbpa3
        kohldbpa4
      Properties:
        DGConnectIdentifier             = 'kohldbpa_m2'
        ObserverConnectIdentifier       = ''
        LogXptMode                      = 'ASYNC'
        DelayMins                       = '0'
        Binding                         = 'optional'
        MaxFailure                      = '0'
        MaxConnections                  = '1'
        ReopenSecs                      = '300'
        NetTimeout                      = '30'
        RedoCompression                 = 'DISABLE'
        LogShipping                     = 'ON'
        PreferredApplyInstance          = ''
        ApplyInstanceTimeout            = '0'
        ApplyParallel                   = 'AUTO'
        StandbyFileManagement           = 'MANUAL'
        ArchiveLagTarget                = '0'
        LogArchiveMaxProcesses          = '10'
        LogArchiveMinSucceedDest        = '1'
        DbFileNameConvert               = ''
        LogFileNameConvert              = ''
        FastStartFailoverTarget         = ''
        InconsistentProperties          = '(monitor)'
        InconsistentLogXptProps         = '(monitor)'
        SendQEntries                    = '(monitor)'
        LogXptStatus                    = '(monitor)'
        RecvQEntries                    = '(monitor)'
        SidName(*)
        StaticConnectIdentifier(*)
        StandbyArchiveLocation(*)
        AlternateLocation(*)
        LogArchiveTrace(*)
        LogArchiveFormat(*)
        TopWaitEvents(*)
        (*) - Please check specific instance for the property value
    Database Status:
    SUCCESS
    DGMGRL> show database verbose kohldbpa_m2_stby;
    Database - kohldbpa_m2_stby
      Role:            PHYSICAL STANDBY
      Intended State:  APPLY-ON
      Transport Lag:   (unknown)
      Apply Lag:       (unknown)
      Real Time Query: OFF
      Instance(s):
        kohldbpa1 (apply instance)
        kohldbpa2
        kohldbpa3
        kohldbpa4
      Properties:
        DGConnectIdentifier             = 'kohldbpa_m2_stby'
        ObserverConnectIdentifier       = ''
        LogXptMode                      = 'ASYNC'
        DelayMins                       = '0'
        Binding                         = 'optional'
        MaxFailure                      = '0'
        MaxConnections                  = '1'
        ReopenSecs                      = '300'
        NetTimeout                      = '30'
        RedoCompression                 = 'DISABLE'
        LogShipping                     = 'ON'
        PreferredApplyInstance          = ''
        ApplyInstanceTimeout            = '0'
        ApplyParallel                   = 'AUTO'
        StandbyFileManagement           = 'Auto'
        ArchiveLagTarget                = '0'
        LogArchiveMaxProcesses          = '10'
        LogArchiveMinSucceedDest        = '1'
        DbFileNameConvert               = '+DATA/kohldbpa_m2, +DATA/kohldbpa_m2_STBY'
        LogFileNameConvert              = '+DATA/kohldbpa_m2, +DATA/kohldbpa_m2_STBY, +FRA/kohldbpa_m2, +FRA/kohldbpa_m2_STBY'
        FastStartFailoverTarget         = ''
        InconsistentProperties          = '(monitor)'
        InconsistentLogXptProps         = '(monitor)'
        SendQEntries                    = '(monitor)'
        LogXptStatus                    = '(monitor)'
        RecvQEntries                    = '(monitor)'
        SidName(*)
        StaticConnectIdentifier(*)
        StandbyArchiveLocation(*)
        AlternateLocation(*)
        LogArchiveTrace(*)
        LogArchiveFormat(*)
        TopWaitEvents(*)
        (*) - Please check specific instance for the property value
    Database Status:
    DGM-17016: failed to retrieve status for database "kohldbpa_m2_stby"
    ORA-16664: unable to receive the result from a database
    DGMGRL>
    SQL> col severity for a15
    col message for a70
    col timestamp for a20
    select severity,error_code,to_char(timestamp,'DD-MON-YYYY HH24:MI:SS') "timestamp" , message from v$dataguard_status where dest_id=2;SQL> SQL> SQL> SQL> SQL> SQL>
    no rows selected
    SQL>
    They are in sync...but still i get that error

  • Getting db_unique_name error on standby...

    HP-UX vscdsh01 B.11.23 U ia64
    10.2.0 oracle
    I have a primary/standby set up that just "stopped" receiving the archive files for some reason. There was no error in the alert log, so I received no notification.
    I had to rebuild everything due to archive log retention issues....the configuration was calling for an archive log much older than what was available.
    I did a new hot backup, created the new standby control file...transferred everything, brought it back on line doing recover standby database and alter database mount standby database...
    everything worked fine.
    I then issued an alter system switch logfile on the primary, while watching the alert logs...it showed the switch, but I don't see any activity for sending the log file from the primary to the secondary...
    I then issue show parameter on both systems to see what is showing as the destinations. Looks fine.
    So I decide to restart the process.
    On the primary, I issued the following command...
    alter system set log_archive_dest_state_2 = DEFER' --to shut off the shipping of log files.
    it came back as system altered.
    Then I issued the following, resulting in error...
    SQL> alter system set log_archive_dest_2 = "MANDATORY service=SWESC reopen=30";
    alter system set log_archive_dest_2 = "MANDATORY service=SWESC reopen=30"
    ERROR at line 1:
    ORA-02097: parameter cannot be modified because specified value is invalid
    ORA-16052: DB_UNIQUE_NAME attribute is required
    Below are the init file for the primary....
    ## Original Init parameters
    peregrine.__db_cache_size=2332033024
    peregrine.__java_pool_size=16777216
    peregrine.__large_pool_size=184549376
    peregrine.__shared_pool_size=2533359616
    peregrine.__streams_pool_size=0
    *.audit_file_dest='/opt/oracle/admin/peregrine/adump'
    *.background_dump_dest='/opt/oracle/admin/peregrine/bdump'
    *.compatible='10.2.0.2.0'
    *.control_files='/ora1/oradata/peregrine/control01.ctl','/ora2/oradata/peregrine/cont
    rol02.ctl','/ora3/oradata/peregrine/control03.ctl'
    *.core_dump_dest='/opt/oracle/admin/peregrine/cdump'
    *.db_block_size=8192
    *.db_domain='vscdsh01.northgrum.com'
    *.db_file_multiblock_read_count=16
    *.db_name='peregrin'
    *.db_recovery_file_dest='/ora10/oradata/peregrine'
    *.db_recovery_file_dest_size=2147483648
    *.db_unique_name='peregrine'
    *.dispatchers='(protocol=TCP)'
    *.job_queue_processes=10
    *.log_archive_dest_1='LOCATION=/oraarch/peregrine'
    *.log_archive_format='peregrine_%t_%s_%r.arc'
    *.nls_date_format='SYYYY-MM-DD HH24:MI:SS'
    *.open_cursors=300
    *.pga_aggregate_target=1692401664
    *.processes=350
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sessions=390
    *.sga_target=5079302144
    *.shared_servers=30
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='/opt/oracle/admin/peregrine/udump'
    ## End original parameters
    log_archive_dest_1='LOCATION=/oraarch/peregrine'
    log_archive_dest_2='SERVICE=swesc reopen=60'
    log_archive_dest_state_1=enable
    log_archive_dsst_state_2=enable
    log_archive_format=%t_%s.dbf
    log_archive_start=true
    remote_archive_enable=true
    log_archive_config DG_CONFIG=(peregrine,swesc)
    fal_client peregrine
    fal_server swesc
    And here is the init file for the standby
    peregrine.__db_cache_size=4647288832
    peregrine.__java_pool_size=16777216
    peregrine.__large_pool_size=184549376
    peregrine.__shared_pool_size=218103808
    peregrine.__streams_pool_size=0
    *.audit_file_dest='/opt/oracle/admin/peregrine/adump'
    *.background_dump_dest='/opt/oracle/admin/peregrine/bdump'
    *.compatible='10.2.0.2.0'
    *.control_file_record_keep_time=14
    *.CONTROL_FILES='/ora1/oradata/peregrine/control01.ctl'
    *.core_dump_dest='/opt/oracle/admin/peregrine/cdump'
    *.db_block_size=8192
    *.db_domain='vscdsh01.northgrum.com'
    *.db_file_multiblock_read_count=16
    *.DB_NAME='peregrin'
    *.db_recovery_file_dest='/ora10/oradata/peregrine'
    *.db_recovery_file_dest_size=2147483648
    *.DB_UNIQUE_NAME='swesc'
    *.dispatchers='(protocol=TCP)'
    *.FAL_CLIENT='swesc'
    *.FAL_SERVER='peregrine'
    *.job_queue_processes=10
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(peregrine,swesc)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=/oraarch/swesc/
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=swesc'
    *.LOG_ARCHIVE_DEST_2='SERVICE=peregrine LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=peregrine'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    *.nls_date_format='SYYYY-MM-DD HH24:MI:SS'
    *.open_cursors=300
    *.pga_aggregate_target=1692401664
    *.processes=350
    *.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
    *.sessions=390
    *.sga_target=5079302144
    *.shared_servers=30
    *.STANDBY_FILE_MANAGEMENT='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='/opt/oracle/admin/peregrine/udump'
    Did I configure something WRONG here? Seems like I did it right...
    Some checks I ran...(primary)
    SQL> select * from V$DATAGUARD_CONFIG
    2 ;
    DB_UNIQUE_NAME
    peregrine
    swesc
    SQL> show parameter db_unique
    NAME TYPE VALUE
    db_unique_name string peregrine
    Thanks.

    I'm at a loss at what to do at this point then. When I run the following on the primary database, I get the following error.
    SQL> connect /as sysdba
    Connected.
    SQL> alter system set log_archive_dest_2 = "MANDATORY service=SWESC reopen=30"
    2 ;
    alter system set log_archive_dest_2 = "MANDATORY service=SWESC reopen=30"
    ERROR at line 1:
    ORA-02097: parameter cannot be modified because specified value is invalid
    ORA-16052: DB_UNIQUE_NAME attribute is required

  • Standby Gives Error

    Hi
    I m facing an error on standby database(Physically) when i trying to open it in read only mode it gives error
    SQL> ALTER DATABASE OPEN READ ONLY;
    ALTER DATABASE OPEN READ ONLY
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    And in alert log
    Wed Mar 19 18:26:20 2008
    File 201 not verified due to error ORA-01157
    Wed Mar 19 18:26:20 2008
    SMON: enabling cache recovery
    Wed Mar 19 18:26:21 2008
    Errors in file e:\orant\admin\apr1b\udump\apr1b_ora_524.trc:
    ORA-01578: ORACLE data block corrupted (file # 1, block # 14851)
    ORA-01110: data file 1: 'E:\ORANT\ORADATA\APR1B\SYSTEM01.DBF'
    ORA-26040: Data block was loaded using the NOLOGGING option
    Wed Mar 19 18:26:21 2008
    Error 1578 happened during db open, shutting down database
    USER: terminating instance due to error 1578
    Instance terminated by USER, pid = 524
    ORA-1092 signalled during: ALTER DATABASE OPEN READ ONLY...
    Please suggest me how can i open it in read only mode.

    Just enable force logging on production: ALTER DATABASE FORCE LOGGING;
    And then recreate standby database.
    However, enabling "force logging" will cause nologging operations to be logged which may cause performance problems. If you need nologging operations, then i suggest:
    * Move all tables on which you do nologging operations to a tablespace A
    * Set force logging on tablespace level on all tablespaces except tablespace A
    * Recreate standby
    You may open standby if you set tablespace A offline. However tablespace A will not be a part of disaster recovery (as it seems now)

  • Standby logfile missing error

    Hello all,
    I am getting this following error in standby alertlog file.
    ORA-00313: open failed for members of log group 8 of thread 2
    ORA-00312: online log 8 thread 2: '+DG_FLASH/hsstl/onlinelog/group_8.273.779638759'
    ORA-17503: ksfdopn:2 Failed to open file +DG_FLASH/hsstl/onlinelog/group_8.273.779638759
    ORA-15012: ASM file '+DG_FLASH/hsipstl/onlinelog/group_8.273.779638759' does not exist
    ORA-00312: online log 8 thread 2: '+DG_DATA/hsstl/onlinelog/group_8.1766.779638759'
    ORA-17503: ksfdopn:2 Failed to open file +DG_DATA/hsstl/onlinelog/group_8.1766.779638759
    ORA-15012: ASM file '+DG_DATA/hsipstl/onlinelog/group_8.1766.779638759' does not exist
    When i manually check the diskgroup '+DG_FLASH, +DG_DATA, i can see the group_8 file with some other numbers.
    Kindly let me know how to proceed for that. oracle 11g database, standalone standby database in aix box
    My guess is control file is still thinking that the group 8 file is present and looks for it when starting the standby, but actually that file is not there in the diskgroup. instead some other filename is there for the same group.
    Either i want to update the control file about the new log group 8, or drop the log 8 group, delete the log 8 group files from the disgroups +DG_FLASH, +DG_DATA and create a new log 8 group
    Kindly suggest
    Regards,

    Test
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1327 52428800
      6 1 0 52428800
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 7 '/u01/app/oracle/oradata//redo07.log' SIZE 50M;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1327 52428800
      6 1 0 52428800
      7 0 0 52428800 
    ALTER DATABASE CLEAR LOGFILE GROUP 7; 
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> ALTER DATABASE CLEAR LOGFILE GROUP 7;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1327 52428800
      6 1 0 52428800
      7 0 0 52428800
    SQL> /
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 1330 52428800
      5 1 0 52428800
      6 1 0 52428800
      7 0 0 52428800
    What I noticed is no matter how many switches I do the Standby only uses group 4 and 5. If I recreate with a Thread number it seems to work.
    SQL> alter database recover managed standby database cancel;
    Database altered.
    SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;
    Database altered.
    SQL> !rm /u01/app/oracle/oradata//redo07.log
    SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 7 '/u01/app/oracle/oradata//redo07.log' SIZE 50M;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
      GROUP# THREAD# SEQUENCE# BYTES
      4 1 0 52428800
      5 1 1343 52428800
      6 1 0 52428800
      7 1 0 52428800
    SQL>
    Check
    SQL> select GROUP#,BYTES/1024/1024/1024 , STATUS, FIRST_TIME,NEXT_TIME from v$standby_log;
      GROUP# BYTES/1024/1024/1024 STATUS FIRST_TIM NEXT_TIME
      4 .048828125 UNASSIGNED
      5 .048828125 ACTIVE 29-NOV-13
      6 .048828125 UNASSIGNED
      7 .048828125 UNASSIGNED
    SQL>

  • Error when starting Weblogic server with Coherence

    We want to use Coherence 3.6 with Weblogic Server 10.3. During server startup, we get the following error. My understanding is the cluster should be started automatically based on the configuration listed below the error. Appreciate any pointers.
    <Dec 15, 2011 3:20:11 PM PST> <Error> <Coherence> <BEA-000000> <2011-12-15 15:20:11.920/67.311 Oracle Coherence SE 3.6.0.4 <Error> (thread=Cluster, member=n/a): This member could not join the cluster because of a configuration mismatch between this member and the configuration being used by the rest of the cluster. This member specified a cluster name of "EPCIS" which did not match the name of the running cluster. This indicates that there are multiple clusters on this network attempting to use overlapping network configurations. Rejected by Member(Id=9, Timestamp=2011-11-16 13:58:42.941, Address=10.229.189.30:8088, MachineId=21022, Location=site:us.oracle.com,machine:adc2101177,process:30667, Role=WeblogicServer).>
    <Dec 15, 2011 3:20:11 PM PST> <Error> <oracle.apps.pas.epc.framework.db.Cache> <BEA-000000> <java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)>
    <Dec 15, 2011 3:20:11 PM PST> <Error> <Coherence> <BEA-000000> <2011-12-15 15:20:11.957/67.349 Oracle Coherence SE 3.6.0.4 <Error> (thread=[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)', member=n/a): Error while starting cluster: java.lang.RuntimeException: Failed to start Service "Cluster" (ServiceState=SERVICE_STOPPED, STATE_JOINING)
    CONFIGURATION:
    We have the following descriptor (epcis-coherence-cache-config.xml) in $DOMAIN_HOME/epc-config:
    <?xml version="1.0"?>
    <!DOCTYPE cache-config SYSTEM "cache-config.dtd">
    <cache-config>
    <caching-scheme-mapping>
    <cache-mapping>
    <cache-name>*</cache-name>
    <scheme-name>distributed</scheme-name>
    </cache-mapping>
    </caching-scheme-mapping>
    <caching-schemes>
    <distributed-scheme>
    <scheme-name>distributed</scheme-name>
    <service-name>DistributedCache</service-name>
    <backing-map-scheme>
    <local-scheme></local-scheme>
    </backing-map-scheme>
    <autostart>true</autostart>
    </distributed-scheme>
    </caching-schemes>
    </cache-config>
    We also have tangosol-coherence-override.xml in the same dir:
    <coherence>
    <cluster-config>
    <member-identity>
    <cluster-name system-property="tangosol.coherence.clustername">EPCIS</cluster-name>
    </member-identity>
    </cluster-config>
    <configurable-cache-factory-config>
    <class-name>com.tangosol.net.DefaultConfigurableCacheFactory</class-name>
    <init-params>
    <init-param>
    <param-type>java.lang.String</param-type>
    <param-value>epcis-coherence-cache-config.xml</param-value>
    </init-param>
    </init-params>
    </configurable-cache-factory-config>
    <license-config>
    <edition-name system-property="tangosol.coherence.edition">SE</edition-name>
    <license-mode system-property="tangosol.coherence.mode">dev</license-mode>
    </license-config>
    </coherence>
    We have modified startWebLogic.sh by adding:
    PRE_CLASSPATH="/slot/xyz/oracle/mwhome/oracle_common/modules/oracle.coherence_3.6/coherence.jar:${DOMAIN_HOME}/epc-config/:${PRE_CLASSPATH}"

    As the error message says, your WebLogic server is trying to join a cluster that has a different cluster name.
    This bit in your tangosol-coherence-override.xml file or the tangosol.coherence.clustername system property must be the same in all members of the cluster
    <cluster-name system-property="tangosol.coherence.clustername">EPCIS</cluster-name>JK

Maybe you are looking for

  • ORA-20001 error when creating Tabular Form or Form and Report

    Whenever I try and add a Tabular Form or Form and Report to my application i am getting the following error at the end of the Wizard. ORA-20001: Unable to create updateable report. ORA-20001: Error creating shortcut id="" ORA-00001: unique constraint

  • To delete Cost Element that already has posting.

    Hi, I need to delete Cost element that already has posting. I used KO04 error msg. KS133 Deletion is not possible (depend records exist in table COEP). Cummulative balance already zerorise. Thank you. Moderator: Please, search SDN

  • Report Output In DOC or RTF

    Hello All, Is it possible to generate a report in Doc / (RTF)(Document) format, if so can you please help me. Regards Melvin

  • JMS Adapter: Unable to parse the scema error in step 7

    Hi I get unable to parse the schema error in step 7 of JMS Adapter partner link definition (in Type Chooser window). I am using RosettaNet 3b2 Schema converted from DTD by Tibco tools. Any help greatly appreciated.

  • HELP ME! Embedding Graphics in Reports.

    I am trying to embed an Oracle Graph (from Graphics) in a report, but when I try to run the report I get a REP-0075 error followed by an OG-01603 "Unable to create PL/SQL Development Environment Context" Error. Then when I click OK, I get another err