Cleanup data guard drc SID .log

Hi,
Is it possible to automatically rotate and/or cleanup the data guard log in the bdump destination?
Do I manually have to clean/empty/delete or rename the always growing drc<SID>.log file?
thanks for any suggestions

Hi,
You may schedule a job to delete/rename the log file once every month/quarter.....

Similar Messages

  • RMAN,Data Guard and Archive log deletion

    Our DG environment is running Oracle 11g R2
    we have a 3 node DG environment with
    A being the Primary
    B and C being Active Data Guard Standbys
    Backups are taken off of B and go directly to tape.
    Standby Redo Logs and Fast Recovery Area are being used
    Taking recommendation from "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
    RMAN Setting on Primary ("A")
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
    RMAN Setting on Standby ("B") where Backup is done
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
    RMAN Setting on other Standby ("C")
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
    How can we know what archive logs are eligible to be deleted from "A" and "C" ?
    When does the delete take place?
    How can we tell when the archive logs are being deleted from "A" and "C" ?

    Dear user10260925,
    The documentation that you have read is reliable but insufficient.
    The Oracle can manage the archivelog directory and knows which one is eligible for the deletion. Those stuff you have posted in here has been taken from the online documentation and is supported and can be used when the Oracle knows and manages the archivelogs. That is simply called the flash recovery area. Please read about the FRA in this very moment.
    Under normal circumstances people in the industry uses some scripts to achive the archivelog deletion on the standby system.
    Here is a useful example to you;
    # Remove old archivelogs
    00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
    vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
    export ORACLE_SID=optstby
    export ORACLE_HOME=/oracle/product/10.2.0/db_1
    cd /db/optima/archive/OPTPROD/archivelog
    /oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
    grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
    chmod 755 delete_applied_redo_logs_1.sh
    sh delete_applied_redo_logs_1.sh
    rm delete_applied_redo_logs_1.sh
    rm delete_applied_redo_logs.lst
    vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
    vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
    set echo off
    set heading off
    spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
    select 'rm -f ' || name from v$archived_log where applied = 'YES';
    spool off
    exit
    vals3:/db/optima/archive/OPTPROD/archivelog#Hope That Helps.
    Ogan

  • Data guard - missed archive log

    Hi:
    I am on 10.2.0.3, using physical standby. One of my check-up sqls shows missed (not applied) arch log:
    SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
    where applied='NO'
    THREAD# SEQUENCE# APP
    1 16595 NO
    It's relatively old one, my max is 18211i and the log application is going fine.
    How can I apply this missed one? Do I have to stop managed recovery and do manual recovery for it?
    TIA.

    GregX,
    Please check if this file actually needs to be applied.
    You can find out the when the archived log file was created – FIRST_TIME/NEXT_TIME columns in V$ARCHIVED_LOG.
    If the archived log file was created before you created the stand-by DB, you do not need ( nor you can) to apply that file.
    Please note that the physical standby would stop applying archivelog if you fail to provide the next required archive log file. Since this has not happened (as per your statement) there is a good chance that you archive redo in question is not needed.
    Hope that helps,
    Edited by: IordanIotzov on Jan 30, 2009 1:34 PM

  • Data Guard : Standby Redo Log CONFUSION

    Trying to set up test Standby db on 10.2.0
    I am well confused about below step 3.1.3, how is the normal redo linked with standby redo, should standby not be members of orginal redo groups?
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
    Original redo logs:
    SQL>  select * from v$log;
        GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
             1          1         28   52428800          1 YES INACTIVE                375136 22-NOV-07
             2          1         29   52428800          1 YES INACTIVE                375138 22-NOV-07
             3          1         30   52428800          1 NO  CURRENT                 375143 22-NOV-07I added below from notes:
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
    ('/u01/oracle/oradata/db01/redo01_stb.log') SIZE 50M;
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 11
    ('/u02/oracle/oradata/db01/redo02_stb.log') SIZE 50M;
    ALTER DATABASE ADD STANDBY LOGFILE GROUP 12
    ('/u03/oracle/oradata/db01/redo03_stb.log') SIZE 50M;After few alter system switch logfile; I still have:
        GROUP#    THREAD#  SEQUENCE# ARC STATUS
            10          0          0 YES UNASSIGNED
            11          0          0 YES UNASSIGNED
            12          0          0 YES UNASSIGNEDAll are UNASSIGNED, should one standby group not be ACTIVE like the above link shows.
    Many think for any help

    First things first:
    From the Docs.:
    "Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database."
    You are 1 short!

  • Duplicate vs Standby -- What To Do Without Data Guard

    WHAT WE HAVE
    Three 10.2.0.3.0 databases in production on the same Linux x86 server (Red Hat OS). An identical Linux x86 server (with same OS) is available for housing a corresponding backup instance (either duplicate or physical standby).
    THE ASSIGNMENT
    Develop a plan that, in the event of a loss of our prod server, provides the shortest time before substitute databases are up and running on the backup server. WE CANNOT USE DATA GUARD (due to server licensing issues). It isn't necessarily a high priority to apply archive logs to duplicates or standbys on a regular basis, but I realize the more up-to-date a backup database is, the less recovery time would be needed if and when it's pressed into service. (BTW: We take weekly incremental level 0 and daily incremental level 1 backups of our prod databases with RMAN and keep them for 28 days.)
    QUESTIONS
    1. Does our 'no Data Guard' rule eliminate using standbys - even if I could use OS processes to transfer archive logs between servers and manually apply redo? (I'm not quite sure what exactly constitutes Data Guard.)
    2. If I'm allowed to create standbys, I'll create them using RMAN. Since the scenario being planned for is a loss of the production server, I figure I'm worried about failover and not switchover. Thus, once standbys are created, in addition to manually transferring and applying archives and creating redo files for them, what other action(s) would I need to take before they could be activated, if that's ever needed? Would the redo files I would have to create be of type STANDBY or ONLINE?
    3. Can a standby be opened in read/write mode without being activated?
    4. If I can only use duplicates and if the production server were to go down one day, could the most recent valid RMAN backup(s) for the prod databases be used in recovering the duplicates?
    I'd prefer the backup instances have the SAME SID (db_name) as the corresponding one in prod, if possible.
    Thanks.

    Hi
    1. Does our 'no Data Guard' rule eliminate using standbys - even if I could use OS processes to transfer archive logs between servers and manually apply redo? (I'm not quite sure what exactly constitutes Data Guard.)
    Ans:- yes if you are able to transfer archivelog to standby destination ,you also have to register archivelogs in controlfile manually,then only you can recover standby with archivelogs.
    2. If I'm allowed to create standbys, I'll create them using RMAN. Since the scenario being planned for is a loss of the production server, I figure I'm worried about failover and not switchover. Thus, once standbys are created, in addition to manually transferring and applying archives and creating redo files for them, what other action(s) would I need to take before they could be activated, if that's ever needed? Would the redo files I would have to create be of type STANDBY or ONLINE?
    Ans:- Yes you can use RMAN to create standby database.you need to activate standby only with the case of failover.Standby logfile is needed if you use Real Time redo apply .In your case you are not enabling Data Guard to transport logs ,so it is not possible to Real Time apply.
    3. Can a standby be opened in read/write mode without being activated ?
    Ans:- Yes,If you do switchover/failover to open for read/write.Without switchover/failover you can open only in read only mode.
    4. If I can only use duplicates and if the production server were to go down one day, could the most recent valid RMAN backup(s) for the prod databases be used in recovering the duplicates?
    Ans:- IF you make duplicate database then it will not accept any log from primary database.
    Hope this will help you.
    Regards
    Tinku

  • Oracle 11G Direct SQL Load with Data Guard

    Does SQL Loader in direct mode always bypass the writing of redo logs ?
    If the database has force logging on, will SQL Loader in direct mode bypass the writing of redo logs ?
    Is there a way to run SQL Loader in direct mode that will create redo logs that can be applied by Data Guard to the backup database ?

    846797 wrote:
    Does SQL Loader in direct mode always bypass the writing of redo logs ?
    If the database has force logging on, will SQL Loader in direct mode bypass the writing of redo logs ?
    Is there a way to run SQL Loader in direct mode that will create redo logs that can be applied by Data Guard to the backup database ?In case of data guard setup , redo logs will always be generated.

  • DB link problem between active Data Guard and report application database

    My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
    I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
    SQL> select name, database_role, open_mode from v$database;
    NAME DATABASE_ROLE OPEN_MODE
    ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
    Problem detail is below
    I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
    SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
    Database link created.
    But when I run a query using db link from my report application database I got this below error.
    ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
    ORA-02063: preceding line from DATADB_LINK
    Then I check Active Data Guard database alart log file and get below error
    ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
    But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
    So is it a problem of DB link between active Data Guard and other database?

    Fazlul Kabir Mahfuz wrote:
    My database version in 11.2.0.2.0 and OS is Oracle Solaris 10 9/10.
    I am facing a problem in my Active data guard Database for reporting purpose. Active Data guard information is as below.
    SQL> select name, database_role, open_mode from v$database;
    NAME DATABASE_ROLE OPEN_MODE
    ORCL PHYSICAL STANDBY READ ONLY WITH APPLY
    Problem detail is below
    I have created a db link (Name: DATADB_LINK) between active data guard and report application database for reporting purpose.
    SQL> create database link DATADB_LINK connect to HR identified by hr using 'DRFUNPD';
    Database link created.
    But when I run a query using db link from my report application database I got this below error.
    ORA-01555: snapshot too old: rollback segment number 10 with name "_SYSSMU10_4261549777$" too small
    ORA-02063: preceding line from DATADB_LINK
    Then I check Active Data Guard database alart log file and get below error
    ORA-01555 caused by SQL statement below (SQL ID: 11yj3pucjguc8, Query Duration=1 sec, SCN: 0x0000.07c708c3):SELECT "A2"."BUSINESS_TRANSACTION_REFERENCE","A2"."BUSINESS_TRANSACTION_CODE",MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'feature' THEN "A1"."TRANS_DATA_VALUE" END ),MAX(CASE "A1"."TRANS_DATA_KEY" WHEN 'otherFeature' THEN "A1"."TRANS_DATA_VALUE" END )
    But the interesting point if I run the report query directly in Active Data Guard database, I never got error.
    So is it a problem of DB link between active Data Guard and other database?
    Check this note which is applicable for your environment
    *ORA-01555 on Active Data Guard Standby Database [ID 1273808.1]*
    also
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8908307196113

  • Data Guard data population issue

    Hi ...
    I have data guard config with a scenario that new user schema is created (couple tablespaces and datafiles). The tablespace is setup in NOLOGGING mode. After checking the physical standby server, the datafiles are created.
    My questions:
    1. How to re-sync data from primary to physical standby assuming schema has created and no data has populated?
    2. How to drop the data in physical standby server on the same schema with primary server re. above issue, then start the objective on 1.?
    My environments are in AIX 5L with 9.2.0.4 in Unicode character set.
    Thanks in advance for any information.
    Cheers.
    BAM

    Hi Justin.
    Thanks for your reply.
    I have restored the tablespaces to logging mode again, and redo schema creation and re-import the data to the schema. When I did the db switch over, the primary site successfully changed to standby -- the opposite works well also.
    However, after querying these:
    SELECT NAME, UNRECOVERABLE_CHANGE# FROM V$DATAFILE;
    SELECT UNRECOVERABLE_CHANGE#,
    TO_CHAR(UNRECOVERABLE_TIME, 'mm-dd-yyyy hh:mi:ss')
    FROM V$DATAFILE;
    on my primary site, there was 5591564 bytes of unrecoverable_change# on one of the datafile on 05-06-2004 02:44:48am. Then on 05-05-2004 10:51:34 the unrecoverable_change# was gone (becomes 0) for the same datafile.
    In the doc. the unrecoverable_change# will be shown if somehow datablock error like following:
    ORA-01578: ORACLE data block corrupted (file # 1, block # 2521)
    ORA-01110: data file 1: '/oracle/dbs/stdby/tbs_1.dbf'
    ORA-26040: Data block was loaded using the NOLOGGING option
    happened. I've checked my logs in primary/standby alert logs and the data guard switch-over logs -- no similar error as above.
    Any idea what was happened on above scenario?
    Thanks.
    BAM

  • I have one problem with Data Guard. My archive log files are not applied.

    I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
    I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
    In Enterprise Manager on Primary database it looks ok. I get the following message “Data Guard status Normal”
    But as I wrote above ”the archive log files are not applied”
    After I created the Physical Standby database, I have also done:
    1. I connected to the Physical Standby database instance.
    CONNECT SYS/SYS@luda AS SYSDBA
    2. I started the Oracle instance at the Physical Standby database without mounting the database.
    STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
    3. I mounted the Physical Standby database:
    ALTER DATABASE MOUNT STANDBY DATABASE
    4. I started redo apply on Physical Standby database
    alter database recover managed standby database disconnect from session
    5. I switched the log files on Physical Standby database
    alter system switch logfile
    6. I verified the redo data was received and archived on Physical Standby database
    select sequence#, first_time, next_time from v$archived_log order by sequence#
    SEQUENCE# FIRST_TIME NEXT_TIME
    3 2006-06-27 2006-06-27
    4 2006-06-27 2006-06-27
    5 2006-06-27 2006-06-27
    6 2006-06-27 2006-06-27
    7 2006-06-27 2006-06-27
    8 2006-06-27 2006-06-27
    7. I verified the archived redo log files were applied on Physical Standby database
    select sequence#,applied from v$archived_log;
    SEQUENCE# APP
    4 NO
    3 NO
    5 NO
    6 NO
    7 NO
    8 NO
    8. on Physical Standby database
    select * from v$archive_gap;
    No rows
    9. on Physical Standby database
    SELECT MESSAGE FROM V$DATAGUARD_STATUS;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    MRP0: Background Media Recovery terminated with error 1110
    MRP0: Background Media Recovery process shutdown
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 2148
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2384
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 3188
    RFS[3]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 3168
    RFS[4]: Identified database type as 'physical standby'
    RFS[4]: No standby redo logfiles created
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    10. on Physical Standby database
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 1 9 13664 2
    RFS IDLE 0 0 0 0
    10) on Primary database:
    select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARCm: Becoming the 'no FAL' ARCH
    ARCm: Becoming the 'no SRL' ARCH
    ARCd: Becoming the heartbeat ARCH
    Error 1034 received logging on to the standby
    Error 1034 received logging on to the standby
    LGWR: Error 1034 creating archivelog file 'luda'
    LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
    FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
    11)on primary db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
    Luda 4 NO
    Luda 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
    Luda 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
    Luda 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
    Luda 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
    Luda 8 NO
    12) on standby db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
    13) my init.ora files
    On standby db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_unique_name='luda'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='luda'
    *.fal_server='irina'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
    On primary db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='irina'
    *.fal_server='luda'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
    Please help me!!!!

    Hi,
    After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
    Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
    In another session 'show configuration' results in the following, confirming that the enable succeeded.
    DGMGRL> show configuration
    Configuration
    Name: avhtest
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    avhtest - Primary database
    avhtestls53 - Physical standby database
    Current status for "avhtest":
    Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
    It there anybody that experienced the same problem and/or knows the solution to this?
    With kind regards,
    Martin Schaap

  • Setting up the standby side after a crash (Data Guard)

    Hi,
    I hope this is the right area to publish my problem...
    I can't find something like codetags for the system output - so I'm sorry for the bad looking
    I have a problem. I use Oracle 11.2.0.3.0 with a dataguard environment. My primary database crashed and I activate the standby to be the new primary.
    After the old primary gets repaired I want to define them as the ney standby. This didn't work because we have disabled flashback logging.
    We created the new standby:
    rman target sys/password@prim auxiliary sys/password@stby
    duplicate target database for standby from active database;
    After this we do this on the new standby:
    alter database recover managed standby database disconnect from session;
    It looks the now there is a working physical standby.
    Now I look on the primary dataguard:
    DGMGRL> show database verbose stby;
    Database - stby
      Role:            PHYSICAL STANDBY
      Intended State:  APPLY-ON
      Transport Lag:   (unknown)
      Apply Lag:       (unknown)
      Real Time Query: OFF
      Instance(s):
        dbuc4
      Properties:
        DGConnectIdentifier             = '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                = '900'
        LogArchiveMaxProcesses          = '4'
        LogArchiveMinSucceedDest        = '1'
        DbFileNameConvert               = ''
        LogFileNameConvert              = ''
        FastStartFailoverTarget         = ''
        InconsistentProperties          = '(monitor)'
        InconsistentLogXptProps         = '(monitor)'
        SendQEntries                    = '(monitor)'
        LogXptStatus                    = '(monitor)'
        RecvQEntries                    = '(monitor)'
        SidName                         = 'dbuc4'
        StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=stby)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=stby_DGMGRL.blubb.de)(INSTANCE_NAME=stby)(SERVER=DEDICATED)))'
        StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
        AlternateLocation               = ''
        LogArchiveTrace                 = '0'
        LogArchiveFormat                = '%t_%s_%r.arc'
        TopWaitEvents                   = '(monitor)'
    Database Status:
    ORA-16795: the standby database needs to be re-created
    DGMGRL> show database verbose prim;
    Database - prim
      Role:            PRIMARY
      Intended State:  TRANSPORT-ON
      Instance(s):
        dbuc4
        dbuc4stby
      Properties:
        DGConnectIdentifier             = 'prim'
        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          = '4'
        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 dbuc4stby;
    Database - dbuc4stby
      Role:            PRIMARY
      Intended State:  TRANSPORT-ON
      Instance(s):
        dbuc4
        dbuc4stby
      Properties:
        DGConnectIdentifier             = 'dbuc4stby'
        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          = '4'
        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 configuration
    Configuration - dg
      Protection Mode: MaxPerformance
      Databases:
        prim - Primary database
        stby     - Physical standby database (disabled)
          ORA-16795: the standby database needs to be re-created
    Fast-Start Failover: DISABLED
    Configuration Status:
    SUCCESS
    On the stby side it looks like:
    DGMGRL> show configuration
    ORA-16795: Die Standby-Datenbank muss neu erstellt werden (The standby database needs to be recreated)
    Did I have to create a new dataguard configuration?
    I didn't know how I get this to work.
    Thx fuechsin

    Hi,
    first of all: big thanks for your answer!
    I think, this was a bad idea, too. But there was not enough space, so we decided to turn it off without thinking of consequences. :/
    When the new hardware arrive I will enable flashback and never turn it off
    The dataguard-log on the stby says:
    01/23/2014 11:56:13
    >> Starting Data Guard Broker bootstrap <<
    Broker Configuration File Locations:
          dg_broker_config_file1 = "/Daten/stby/stby_dgbroker1.dat"
          dg_broker_config_file2 = "/Daten/stby/stby_dgbroker2.dat"
    01/23/2014 11:56:17
    Database needs to be reinstated or re-created, Data Guard broker ready
    I want to try to delete the configuration on the prim and stby side and reconfigure it. But I don't know if there are side-effects on the working prim side - it is a productive system.
    Best regards,
    fuechsin

  • Data Guard. My archive log files are not applied.

    I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
    I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
    In Enterprise Manager on Primary database it looks ok. I get the following message “Data Guard status Normal”
    But as I wrote above ”the archive log files are not applied”
    After I created the Physical Standby database, I have also done:
    1. I connected to the Physical Standby database instance.
    CONNECT SYS/SYS@luda AS SYSDBA
    2. I started the Oracle instance at the Physical Standby database without mounting the database.
    STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
    3. I mounted the Physical Standby database:
    ALTER DATABASE MOUNT STANDBY DATABASE
    4. I started redo apply on Physical Standby database
    alter database recover managed standby database disconnect from session
    5. I switched the log files on Physical Standby database
    alter system switch logfile
    6. I verified the redo data was received and archived on Physical Standby database
    select sequence#, first_time, next_time from v$archived_log order by sequence#
    SEQUENCE# FIRST_TIME NEXT_TIME
    3 2006-06-27 2006-06-27
    4 2006-06-27 2006-06-27
    5 2006-06-27 2006-06-27
    6 2006-06-27 2006-06-27
    7 2006-06-27 2006-06-27
    8 2006-06-27 2006-06-27
    7. I verified the archived redo log files were applied on Physical Standby database
    select sequence#,applied from v$archived_log;
    SEQUENCE# APP
    4 NO
    3 NO
    5 NO
    6 NO
    7 NO
    8 NO
    8. on Physical Standby database
    select * from v$archive_gap;
    No rows
    9. on Physical Standby database
    SELECT MESSAGE FROM V$DATAGUARD_STATUS;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    ARC1: Becoming the heartbeat ARCH
    Attempt to start background Managed Standby Recovery process
    MRP0: Background Managed Standby Recovery process started
    Managed Standby Recovery not using Real Time Apply
    MRP0: Background Media Recovery terminated with error 1110
    MRP0: Background Media Recovery process shutdown
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 2148
    RFS[1]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 2384
    RFS[2]: Identified database type as 'physical standby'
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[3]: Assigned to RFS process 3188
    RFS[3]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 3168
    RFS[4]: Identified database type as 'physical standby'
    RFS[4]: No standby redo logfiles created
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[3]: No standby redo logfiles created
    10. on Physical Standby database
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 0 0 0 0
    RFS IDLE 1 9 13664 2
    RFS IDLE 0 0 0 0
    10) on Primary database:
    select message from v$dataguard_status;
    MESSAGE
    ARC0: Archival started
    ARC1: Archival started
    ARC2: Archival started
    ARC3: Archival started
    ARC4: Archival started
    ARC5: Archival started
    ARC6: Archival started
    ARC7: Archival started
    ARC8: Archival started
    ARC9: Archival started
    ARCa: Archival started
    ARCb: Archival started
    ARCc: Archival started
    ARCd: Archival started
    ARCe: Archival started
    ARCf: Archival started
    ARCg: Archival started
    ARCh: Archival started
    ARCi: Archival started
    ARCj: Archival started
    ARCk: Archival started
    ARCl: Archival started
    ARCm: Archival started
    ARCn: Archival started
    ARCo: Archival started
    ARCp: Archival started
    ARCq: Archival started
    ARCr: Archival started
    ARCs: Archival started
    ARCt: Archival started
    ARCm: Becoming the 'no FAL' ARCH
    ARCm: Becoming the 'no SRL' ARCH
    ARCd: Becoming the heartbeat ARCH
    Error 1034 received logging on to the standby
    Error 1034 received logging on to the standby
    LGWR: Error 1034 creating archivelog file 'luda'
    LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
    FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
    11)on primary db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
    Luda 4 NO
    Luda 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
    Luda 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
    Luda 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
    Luda 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
    Luda 8 NO
    12) on standby db
    select name,sequence#,applied from v$archived_log;
    NAME SEQUENCE# APP
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
    C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
    13) my init.ora files
    On standby db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_unique_name='luda'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='luda'
    *.fal_server='irina'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
    On primary db
    irina.__db_cache_size=79691776
    irina.__java_pool_size=4194304
    irina.__large_pool_size=4194304
    irina.__shared_pool_size=75497472
    irina.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='luda','irina'
    *.db_name='irina'
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
    *.fal_client='irina'
    *.fal_server='luda'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(irina,luda)'
    *.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
    *.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=30
    *.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
    *.open_cursors=300
    *.pga_aggregate_target=16777216
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.standby_file_management='AUTO'
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
    Please help me!!!!

    Hi,
    After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
    Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
    In another session 'show configuration' results in the following, confirming that the enable succeeded.
    DGMGRL> show configuration
    Configuration
    Name: avhtest
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    avhtest - Primary database
    avhtestls53 - Physical standby database
    Current status for "avhtest":
    Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
    It there anybody that experienced the same problem and/or knows the solution to this?
    With kind regards,
    Martin Schaap

  • Data Guard Missing Redo Archive Logs

    Hi All Gurus
    I have setup data guard on windows 2008 server sp2 with oracle 10.2.0.4.0 (Both OS & Oracle DB are 64 bits).
    The Network Admin have shutdown Backup server. Now when I checked the Archive status as follows
    1. select * from v$archive_gap;            It shows a gap in archives       e.g. 891 - 920.
    2. SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;                 e.g. 891-920 Not Applied.
    Now I issue following command
    1. SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS;                                e.g. MANAGED REAL TIME APPLY
    2.  DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL; 
    or  ALTER DATABASE RECOVER  managed standby database disconnect from session ;     
                        e.g.      incompatible Media Recovery in Progress
    3. Alert Log says Adjust CONTROL_FILE_RECORD_KEEP_TIME to sufficient limits.
    I have also adjusted CONTROL_FILE_RECORD_KEEP_TIME to 90 days as follows
    4. show parameter control_file          e.g. CONTROL_FILE_RECORD_KEEP_TIME=90
    5. I have checked firewall and tnsping for both Primary and Standby Server e.g. tnsping CVMIS (Primary), CVMISBK (Standby)
         Both are OK. TNSPING is showing 10-30msec delay.
    6. I have checked the web for gap Removal, Mostly are using RMAN method to Backup and then Restore to Standby DB.
          Is there any other way to fill this gap without using RMAN? I mean DG automatically fill it by using some commands
         are settings?
    Kind Regards
    Thunder2777

    Hi CKPT
    Thanks for the scripts which I executed today on 24 Mon 2013. Here are the Results.
    Standby Database Script Output:
    NAME                           DISPLAY_VALUE
    db_file_name_convert
    db_name                            UMIS
    db_unique_name                 UMISBK
    dg_broker_config_file1         C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMISBK.DAT
    dg_broker_config_file2         C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMISBK.DAT
    dg_broker_start                TRUE
    fal_client                          (DESCRIPTION=(ADDRESS_LIST=(AD
                                           DRESS=(PROTOCOL=tcp)(HOST=WIN-
                                           7VSLKL4CGU2)(PORT=1521)))(CONN
                                           ECT_DATA=(SERVICE_NAME=umisbk_
                                           XPT)(INSTANCE_NAME=umisbk)(SER
                                           VER=dedicated)))
    fal_server                         (DESCRIPTION=(ADDRESS_LIST=(AD
                                           DRESS=(PROTOCOL=tcp)(HOST=CV-A
                                           JKDB)(PORT=1521)))(CONNECT_DAT
                                           A=(SERVICE_NAME=umis_XPT)(SERV
                                           ER=dedicated)))
    local_listener
    log_archive_config               DG_CONFIG=(UMIS,UMISBK)
    log_archive_dest_2             SERVICE=UMIS LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=UMIS
    log_archive_dest_state_2           ENABLE
    log_archive_max_processes      10
    log_file_name_convert                E:\oracle\product\10.2.0\flash_recovery_area\UMIS\, D:\ORACLE\FRA\UMISBK
    remote_login_passwordfile         EXCLUSIVE
    standby_archive_dest                D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
    standby_file_management                         AUTO
    NAME       DB_UNIQUE_NAME                 PROTECTION_MODE DATABASE_R OPEN_MODE
    UMIS       UMISBK      MAXIMUM PERFORMANCE PHYSICAL STANDBY MOUNTED
       THREAD# MAX(SEQUENCE#)
             1            890
    PROCESS   STATUS          THREAD#  SEQUENCE#
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CLOSING                   1       1062
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    ARCH      CONNECTED             0          0
    MRP0      WAIT_FOR_GAP          1        891
    RFS       IDLE                  1       1063
    RFS       IDLE                  0          0
    NAME                           VALUE      UNIT                           TIME_COMPUTED
    apply finish time                         day(2) to second(1) interval
    apply lag                                   day(2) to second(0) interval
    estimated startup time                22         second
    standby has been open              N
    transport lag                             day(2) to second(0) interval
       THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
             1           891            948
    NAME                                                            Size MB    Used MB
    D:\ORACLE\FRA                                                      2048          0
    STANDBY Alert Log:
    Mon Jun 24 10:19:55 2013
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[2]: Assigned to RFS process 1868
    RFS[2]: Identified database type as 'physical standby'
    RFS[2]: Successfully opened standby log 5: 'D:\ORACLE\ORADATA\UMISBK\SLOG02.LOG'
    Mon Jun 24 10:22:09 2013
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Jun 24 10:22:09 2013
    Starting ORACLE instance (normal)
    Mon Jun 24 10:22:09 2013
    alter database mount standby database
    ORA-1154 signalled during: alter database mount standby database...
    Mon Jun 24 10:22:09 2013
    alter database recover managed standby database using current logfile disconnect from session
    Mon Jun 24 10:22:40 2013
    ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Jun 24 10:24:40 2013
    Starting ORACLE instance (normal)
    Mon Jun 24 10:24:40 2013
    alter database mount standby database
    ORA-1154 signalled during: alter database mount standby database...
    Mon Jun 24 10:24:40 2013
    alter database recover managed standby database using current logfile disconnect from session
    Mon Jun 24 10:25:11 2013
    ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
    Mon Jun 24 10:26:46 2013
    Adjusting the default value of parameter parallel_max_servers
    from 160 to 135 due to the value of parameter processes (150)
    Mon Jun 24 10:26:46 2013
    Starting ORACLE instance (normal)
    Mon Jun 24 10:28:04 2013
    alter database mount standby database
    Mon Jun 24 10:28:04 2013
    ORA-1154 signalled during: alter database mount standby database...
    PRIMARY Database Script Output:
    NAME                           DISPLAY_VALUE
    db_file_name_convert           UMIS, UMISBK
    db_name                             UMIS
    db_unique_name                  UMIS
    dg_broker_config_file1           E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMIS.DAT
    dg_broker_config_file2           E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMIS.DAT
    dg_broker_start                   TRUE
    fal_client                             UMIS
    fal_server                            UMISBK
    local_listener
    log_archive_config               DG_CONFIG=(UMIS,UMISBK)
    log_archive_dest_2             service="(DESCRIPTION=(ADDRESS
                                             _LIST=(ADDRESS=(PROTOCOL=tcp)(
                                             HOST=WIN-7VSLKL4CGU2)(PORT=152
                                             1)))(CONNECT_DATA=(SERVICE_NAM
                                             E=umisbk_XPT)(INSTANCE_NAME=um
                                             isbk)(SERVER=dedicated)))",
                                             LGWR ASYNC NOAFFIRM delay=0 O
                                             PTIONAL max_failure=0 max_conn
                                             ections=1   reopen=300 db_uniq
                                             ue_name="umisbk" register net_
                                             timeout=180  valid_for=(online
                                             _logfile,primary_role)
    log_archive_dest_state_2          ENABLE
    log_archive_max_processes      2
    log_file_name_convert               E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
    remote_login_passwordfile            EXCLUSIVE
    standby_archive_dest
    standby_file_management             AUTO
    NAME       DB_UNIQUE_NAME                 PROTECTION_MODE      DATABASE_R OPEN_MODE  SWITCHOVER_STATUS
    UMIS       UMIS                   MAXIMUM PERFORMANCE  PRIMARY    READ WRITE SESSIONS ACTIVE
       THREAD# MAX(SEQUENCE#)
             1           1062
        Thread Last Sequence Received Last Sequence Applied Difference
             1                   1062                  1062          0
             1                   1062                  1062          0
    SEVERITY        ERROR_CODE timestamp            MESSAGE
    Error                12514 24-JUN-2013 10:08:02 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
    Error                12514 24-JUN-2013 10:08:04 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
    Error                12514 24-JUN-2013 10:08:07 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Error                12514 24-JUN-2013 10:08:31 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
    Error                12514 24-JUN-2013 10:08:59 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Error                12514 24-JUN-2013 10:14:57 PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
    ID STATUS    DB_MODE         TYPE RECOVERY_MODE        PROTECTION_MODE      SRLs ACTIVE ARCHIVED_SEQ#
      1 VALID     OPEN            ARCH IDLE                 MAXIMUM PERFORMANCE     0      0          1062
      2 VALID     UNKNOWN         LGWR UNKNOWN              MAXIMUM PERFORMANCE     4      3          1054
    NAME                                                            Size MB    Used MB
    E:\oracle\product\10.2.0\flash_recovery_area                       2048          0
    Primary Alert Log:
    System parameters with non-default values:
      processes                      = 150
      __shared_pool_size        = 335544320
      __large_pool_size           = 16777216
      __java_pool_size            = 33554432
      __streams_pool_size      = 0
      sga_target                     = 1258291200
      control_files            = E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL03.CTL
      db_file_name_convert     = UMIS, UMISBK
      log_file_name_convert    = E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
      control_file_record_keep_time= 90
      db_block_size                      = 8192
      __db_cache_size                 = 855638016
      compatible                           = 10.2.0.3.0
      log_archive_config                = DG_CONFIG=(UMIS,UMISBK)
      log_archive_dest_1       = location="E:\oracle\product\10.2.0\flash_recovery_area\UMIS\ARCHIVELOG", valid_for=(ONLINE_LOGFILE,ALL_ROLES)
      log_archive_dest_2       = service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))",    LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)
      log_archive_dest_state_1 = ENABLE
      log_archive_dest_state_2 = ENABLE
      log_archive_max_processes= 2
      log_archive_min_succeed_dest= 1
      standby_archive_dest     =
      log_archive_trace        = 0
      log_archive_format       = ARC_s%S_r%R_t%T.arc
      fal_client               = UMIS
      fal_server               = UMISBK
      archive_lag_target       = 0
      db_file_multiblock_read_count= 16
      db_recovery_file_dest    = E:\oracle\product\10.2.0\flash_recovery_area
      db_recovery_file_dest_size= 2147483648
      standby_file_management  = AUTO
      undo_management          = AUTO
      undo_tablespace          = UNDOTBS1
      remote_login_passwordfile= EXCLUSIVE
      db_domain                =
      dispatchers              = (PROTOCOL=TCP) (SERVICE=UMISXDB)
      job_queue_processes      = 10
      audit_file_dest          = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\ADUMP
      background_dump_dest     = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\BDUMP
      user_dump_dest           = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\UDUMP
      core_dump_dest           = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\CDUMP
      db_name                  = UMIS
      open_cursors             = 300
      pga_aggregate_target     = 417333248
      dg_broker_start          = TRUE
    PSP0 started with pid=3, OS id=2824
    MMAN started with pid=4, OS id=2820
    DBW0 started with pid=5, OS id=2396
    LGWR started with pid=6, OS id=2676
    CKPT started with pid=7, OS id=2692
    SMON started with pid=8, OS id=2096
    RECO started with pid=9, OS id=2924
    CJQ0 started with pid=10, OS id=2832
    MMON started with pid=11, OS id=3052
    Mon Jun 24 10:07:34 2013
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    Mon Jun 24 10:07:34 2013
    starting up 1 shared server(s) ...
    MMNL started with pid=12, OS id=2700
    DMON started with pid=15, OS id=2908
    PMON started with pid=2, OS id=2812
    Mon Jun 24 10:07:35 2013
    alter database mount exclusive
    Mon Jun 24 10:07:40 2013
    Setting recovery target incarnation to 2
    Mon Jun 24 10:07:42 2013
    Successful mount of redo thread 1, with mount id 316954407
    Mon Jun 24 10:07:42 2013
    Database mounted in Exclusive Mode
    Completed: alter database mount exclusive
    Mon Jun 24 10:07:42 2013
    alter database open
    Mon Jun 24 10:07:47 2013
    Starting Data Guard Broker (DMON)
    NSV1 started with pid=16, OS id=3552
    Mon Jun 24 10:07:50 2013
    Beginning crash recovery of 1 threads
    parallel recovery started with 7 processes
    INSV started with pid=24, OS id=3628
    Mon Jun 24 10:07:52 2013
    Started redo scan
    Mon Jun 24 10:07:53 2013
    Completed redo scan
    144 redo blocks read, 60 data blocks need recovery
    Mon Jun 24 10:07:53 2013
    Started redo application at
    Thread 1: logseq 1059, block 8380
    Mon Jun 24 10:07:53 2013
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 1059 Reading mem 0
      Mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
    Mon Jun 24 10:07:53 2013
    Completed redo application
    Mon Jun 24 10:07:53 2013
    Completed crash recovery at
    Thread 1: logseq 1059, block 8524, scn 26461769
    60 data blocks read, 60 data blocks written, 144 redo blocks read
    Mon Jun 24 10:07:57 2013
    LGWR: STARTING ARCH PROCESSES
    ARC0 started with pid=25, OS id=3804
    ARC1 started with pid=26, OS id=3808
    Mon Jun 24 10:07:57 2013
    ARC0: Archival started
    ARC1: Archival started
    LGWR: STARTING ARCH PROCESSES COMPLETE
    RSM0 started with pid=27, OS id=3812
    LNS1 started with pid=28, OS id=3824
    Mon Jun 24 10:08:01 2013
    Thread 1 advanced to log sequence 1060 (thread open)
    Thread 1 opened at log sequence 1060
      Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
    Successful open of redo thread 1
    Mon Jun 24 10:08:02 2013
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Jun 24 10:08:02 2013
    ARC1: STARTING ARCH PROCESSES
    Mon Jun 24 10:08:02 2013
    ARC0: Becoming the 'no FAL' ARCH
    ARC0: Becoming the 'no SRL' ARCH
    Mon Jun 24 10:08:02 2013
    ARC2: Archival started
    Mon Jun 24 10:08:02 2013
    ARC1: STARTING ARCH PROCESSES COMPLETE
    ARC2 started with pid=29, OS id=3544
    ARC1: Becoming the heartbeat ARCH
    Mon Jun 24 10:08:02 2013
    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
    Error 12514 received logging on to the standby
    LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Mon Jun 24 10:08:02 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Mon Jun 24 10:08:02 2013
    SMON: enabling cache recovery
    Mon Jun 24 10:08:03 2013
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Mon Jun 24 10:08:03 2013
    LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
    Mon Jun 24 10:08:03 2013
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Mon Jun 24 10:08:03 2013
    ALTER DATABASE OPEN
    Mon Jun 24 10:08:03 2013
    ORA-1531 signalled during: ALTER DATABASE OPEN...
    Mon Jun 24 10:08:04 2013
    Error 12514 received logging on to the standby
    LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Mon Jun 24 10:08:04 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
    Mon Jun 24 10:08:04 2013
    Successfully onlined Undo Tablespace 1.
    Mon Jun 24 10:08:04 2013
    SMON: enabling tx recovery
    Mon Jun 24 10:08:05 2013
    Database Characterset is WE8MSWIN1252
    Opening with internal Resource Manager plan
    where NUMA PG = 1, CPUs = 8
    Mon Jun 24 10:08:06 2013
    Error 12514 received logging on to the standby
    Mon Jun 24 10:08:06 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Mon Jun 24 10:08:07 2013
    replication_dependency_tracking turned off (no async multimaster replication found)
    Mon Jun 24 10:08:07 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-16055: FAL request rejected
    Mon Jun 24 10:08:07 2013
    ARCH: FAL archive failed. Archiver continuing
    Mon Jun 24 10:08:08 2013
    Starting background process QMNC
    QMNC started with pid=28, OS id=3984
    Mon Jun 24 10:08:15 2013
    db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
    user-specified limit on the amount of space that will be used by this
    database for recovery-related files, and does not reflect the amount of
    space available in the underlying filesystem or ASM diskgroup.
    Mon Jun 24 10:08:15 2013
    Completed: alter database open
    Mon Jun 24 10:08:19 2013
    ALTER SYSTEM SET standby_archive_dest='' SCOPE=BOTH SID='umis';
    Mon Jun 24 10:08:19 2013
    ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='umis';
    Mon Jun 24 10:08:19 2013
    ALTER SYSTEM SET log_archive_format='ARC_s%S_r%R_t%T.arc' SCOPE=SPFILE SID='umis';
    Mon Jun 24 10:08:20 2013
    ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:20 2013
    ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:20 2013
    ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM SET db_file_name_convert='UMIS','UMISBK' SCOPE=SPFILE;
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM SET log_file_name_convert='E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\','D:\ORACLE\FRA\UMISBK\ARCHIVELOG\' SCOPE=SPFILE;
    Mon Jun 24 10:08:21 2013
    ALTER SYSTEM ARCHIVE LOG
    Mon Jun 24 10:08:21 2013
    Thread 1 cannot allocate new log, sequence 1061
    Private strand flush not complete
      Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
    Mon Jun 24 10:08:22 2013
    Shutting down archive processes
    Mon Jun 24 10:08:22 2013
    Thread 1 advanced to log sequence 1061 (LGWR switch)
    Mon Jun 24 10:08:22 2013
      Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
    Mon Jun 24 10:08:27 2013
    ARCH shutting down
    ARC2: Archival stopped
    Mon Jun 24 10:08:27 2013
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Mon Jun 24 10:08:27 2013
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Mon Jun 24 10:08:27 2013
    ALTER SYSTEM ARCHIVE LOG
    Mon Jun 24 10:08:27 2013
    Thread 1 cannot allocate new log, sequence 1062
    Private strand flush not complete
      Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
    LNS1 started with pid=29, OS id=4204
    Mon Jun 24 10:08:31 2013
    Thread 1 advanced to log sequence 1062 (LGWR switch)
      Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
    Mon Jun 24 10:08:31 2013
    Error 12514 received logging on to the standby
    LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    Mon Jun 24 10:08:31 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_4204.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    LNS: Failed to archive log 3 thread 1 sequence 1062 (12514)
    Mon Jun 24 10:08:59 2013
    Error 12514 received logging on to the standby
    Mon Jun 24 10:08:59 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
    FAL[server, ARC1]: FAL archive failed, see trace file.
    Mon Jun 24 10:08:59 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Mon Jun 24 10:14:57 2013
    Error 12514 received logging on to the standby
    Mon Jun 24 10:14:57 2013
    Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
    Mon Jun 24 10:18:46 2013
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    Mon Jun 24 10:19:23 2013
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180  valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Mon Jun 24 10:19:23 2013
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Mon Jun 24 10:19:23 2013
    ALTER SYSTEM ARCHIVE LOG
    Mon Jun 24 10:19:24 2013
    Thread 1 cannot allocate new log, sequence 1063
    Private strand flush not complete
      Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
    LNS1 started with pid=18, OS id=4300
    Mon Jun 24 10:19:28 2013
    Thread 1 advanced to log sequence 1063 (LGWR switch)
      Current log# 1 seq# 1063 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
    Mon Jun 24 10:19:28 2013
    LNS: Standby redo logfile selected for thread 1 sequence 1063 for destination LOG_ARCHIVE_DEST_2
    Mon Jun 24 10:19:58 2013
    ARC1: Standby redo logfile selected for thread 1 sequence 1062 for destination LOG_ARCHIVE_DEST_2
    Well there seems to be some connectivity issue on Primary DB (I Guess!!!).
    But when I issue tnsping from Primary Database, the result is
    SQL> host tnsping umisbk (Standy DB Name)  --->   Status: OK [10-30msec]
    And when I issue tnsping from Standby Database, the result is
    SQL> host tnsping umis (Primary DB Name)    --->   Status: OK [10-30msec]
    So what your Recommendation.
    Kind Regards
    Thuhnder2777

  • View Log in Data Guard

    In dataguard when i check view log(OBJECT-Viewlog) it return
    "Data Guard Remote Process Startup Fail"?
    Regards

    hi there,
    What's your question and you need to provide the version and the type of standby db too?

  • Data Guard - Redo log files

    Hi....
    I have done data guard .......every thing is fine.......archives are bring transferred to standby..........
    Also, during configuration, I had created standby redolog groups 4,5,6 and copied to standby.....
    But in real time apply.......the standby is not using standby redolog groups 4,5,6........when i am query v$log it is showing group 1,2,3.
    Actually, its should use standby redo log for maximum availability.
    Please help....
    Thanks in advance.

    There was a similar question here just a few days ago:
    Data Guard - redo log files

  • Location of log directory with respect to data guard

    I am working with Oracle 10g in Linux platform
    I was during a switchover from primary to standby which failed due to the incorrect settings of log_file_name_covert parameter . To debug this case I was going through Oracle Documentation material for Data Guard ....http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/troubleshooting.htm
    There I came across this para
    When the switchover to change the role from primary to physical standby was
    initiated, a trace file was written in the log directory. This trace file contains the
    SQL statements required to re-create the original primary control file. Locate the
    trace file and extract the SQL statements into a temporary file. Execute the
    temporary file from SQL*Plus. This will revert the new standby database back to
    the primary role.
    I was not able to understand what the trace file and log directory means ? Which is the location of log directory ?
    Can anyone please explain ?

    It was talking about a trace will be placed under your background dump destination. As you would have using
    alter database backup controlfile to trace;Check your background dump destination where your alert log is.

Maybe you are looking for