Ora-16004(Data guard)

At the time checking with transcation in primary DB,
it is not getting updated even after number of logswitch.
second thing, i tried opening the standby to view the update,
after giving startup i got the following error...
SQL> startup force
ORACLE instance started.
Total System Global Area  289406976 bytes
Fixed Size                  1248576 bytes
Variable Size              92275392 bytes
Database Buffers          188743680 bytes
Redo Buffers                7139328 bytes
Database mounted.
ORA-16004: backup database requires recovery
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST1\SYSTEM01.DBF'

why did you use
startup force ?you can't open the DG using this method.
as you DG database will be in autorecovery mode, your system tablespace is asking for recovery. this is the expected behaviour.
you can open the dataguard in read only mode but not read/write mode. even if you want to open it in the read/write mode using failiover method this is not the way.
you can use following method to open your standby in failover method
+1. Identify and resolve any gaps in the archived redo log files.+
SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;
If any file is listed then copy it from primary and register it to the standby.
ALTER DATABASE REGISTER PHYSICAL LOGFILE 'filespec1';
+2. Copy any other missing archived redo log files and register it to standby database.+
SELECT UNIQUE THREAD# AS THREAD, MAX(SEQUENCE#) OVER (PARTITION BY thread#) AS LAST from V$ARCHIVED_LOG;
ALTER DATABASE REGISTER PHYSICAL LOGFILE 'filespec1';
+3. Initiate a failover on the target physical standby database.+
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH FORCE;
+4.Convert the physical standby database to the primary role.+
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
+5. If the standby database has never been opened before in readonly mode then open the database:+
Alter database open;
Or else:
Shutdown immediate;
Startup;
Hope that helps you.
Anil Malkai
Edited by: Anil Malkai on Mar 18, 2010 3:01 AM

Similar Messages

  • Error: ORA-16532: Data Guard broker configuration does not exist

    Hi there folks. Hope everyone is having a nice weekend.
    Anyways, we have a 10.2.0.4 rac primary and a 10.2.0.4 standby physical standby. We recently did a switchover and the dgbroker files automatically got created in the Oracle_home/dbs location of the primary. Now need to move these files to the common ASM DG. For this, I followd the steps from this doc:
    How To Move Dataguard Broker Configuration File On ASM Filesystem (Doc ID 839794.1)
    The only exception to this case is that I have to do this on a Primary and not a standby so I am disabling and enabling the Primary(and not standby as mentioned in below steps)
    To rename the broker configuration files in STANDBY to FRA/MYSTD/broker1.dat and FRA/MYSTD/broker2.dat, Follow the below steps
    1. Disable the standby database from within the broker configuration
    DGMGRL> disable database MYSTD;
    2. Stop the broker on the standby
    SQL> alter system set dg_broker_start = FALSE;
    3. Set the dg_broker_config_file1 & 2 parameters on the standby to the appropriate location required.
    SQL> alter system set dg_broker_config_file1 = '+FRA/MYSTD/broker1.dat';
    SQL> alter system set dg_broker_config_file2 = '+FRA/MYSTD/broker2.dat'
    4. Restart the broker on the standby
    SQL> alter system set dg_broker_start = TRUE
    5. From the primary, enable the standby
    DGMGRL> enable database MYSTD;
    6. Broker configuration files will be created in the new ASM location.
    I did so but when I try to enable the Primary back I get this:
    Error: ORA-16532: Data Guard broker configuration does not exist
    Configuration details cannot be determined by DGMGRL
    Form this link,(Errors setting up DataGuard Broker it would seem that I would need to recreate the configuration....Is that correct ? If yes then how come Metalink is missing this info of recreating the configuration... OR is it that that scenario wouldnt be applicable in my case ?
    Thanks for your help.

    Yes I can confirm from the gv$spparameter view that the changes are effective for all 3 instances. From the alert log the alter system didnt throw u pany errros. I didnt restart the instances though since I dont have the approvals yet. But I dont think thats required.

  • Question on db_unique_name in init.ora for Data Guard

    I need to set up only one physical standby on a different box (at a different location) for the primary db in production.
    OS: Sun Sparc Solaris 10
    Oracle: 10.2.0.3
    Can I use the same db_unique_name in init.ora for both primary and standby DBs?
    What are the minimal parameters required by Data Guard I have to specify in the init.ora in my case?
    Could anyone please post an example of init.ora for both primary and standby DBs?
    Thanks very much in advance.

    http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i63561

  • Error: ORA-16525: the Data Guard broker is not yet available

    Hi ,
    After upgrading from 11201 to 11203 ON AIX GI/RDBMS on standby but have not upgraded the primary db yet.I had set dg_broker_start=false and disable configuration before i started the upgrade .
    once the GI for oracle restart was upgraded i upgraded the rdbms binaries and brought up the standby on mount ,while trying to enable configuration its throwing the below error.I had already started the broker process.
    SQL> show parameter dg_
    NAME TYPE VALUE
    dg_broker_config_file1 string /u01/app/omvmxp1/product/11.2.
    0/dbhome_2/dbs/dr1mvmxs2.dat
    dg_broker_config_file2 string /u01/app/omvmxp1/product/11.2.
    0/dbhome_2/dbs/dr2mvmxs2.dat
    dg_broker_start boolean TRUE
    DGMGRL> show configuration;
    Configuration - Matrxrep_brkr
    Protection Mode: MaxAvailability
    Databases:
    mvmxp2 - Primary database
    mvmxs2 - Physical standby database
    Error: ORA-16525: the Data Guard broker is not yet available
    Fast-Start Failover: DISABLED
    Configuration Status:
    ERROR
    from drcmvmxs2.log
    Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
    dg_broker_config_file1 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
    dg_broker_config_file2 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
    12/19/2012 16:05:33
    Data Guard Broker shutting down
    DMON Process Shutdown <<12/19/2012 16:10:20
    Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
    dg_broker_config_file1 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
    dg_broker_config_file2 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
    ~
    Regards
    Edited by: Monto on Dec 19, 2012 1:23 PM

    Hi,
    I removed the configuration and removed the broker files from RAC primary(mvmxp2) and single instance standby(mvmxs2) and re-created back.i tried it many times but getting error "ORA-16532" .I needed to have this standby backup before i start upgrading the primary.
    SQL> alter system set dg_broker_start=true scope=both;
    System altered.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Automatic Storage Management, OLAP, Data Mining
    and Real Application Testing options
    palmer60:/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs>dgmgrl
    DGMGRL for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - 64bit Production
    Copyright (c) 2000, 2009, Oracle. All rights reserved.
    Welcome to DGMGRL, type "help" for information.
    DGMGRL> connect sys@mvmxp2
    Password:
    Connected.
    DGMGRL> CREATE CONFIGURATION 'Matrxrep'
    AS
    PRIMARY DATABASE IS 'mvmxp2'
    CONNECT IDENTIFIER IS 'mvmxp2';> > >
    Configuration "Matrxrep" created with primary database "mvmxp2"
    DGMGRL> ADD DATABASE 'mvmxs2'
    AS
    CONNECT IDENTIFIER IS 'mvmxs2'
    ;Database "mvmxs2" added
    DGMGRL> SHOW CONFIGURATION;
    Configuration - Matrxrep
    Protection Mode: MaxPerformance
    Databases:
    mvmxp2 - Primary database
    mvmxs2 - Physical standby database
    Fast-Start Failover: DISABLED
    Configuration Status:
    DISABLED
    DGMGRL> ENABLE CONFIGURATION;
    Enabled.
    DGMGRL> SHOW DATABASE MVMXS2;
    Database - mvmxs2
    Role: PHYSICAL STANDBY
    Intended State: APPLY-ON
    Transport Lag: (unknown)
    Apply Lag: (unknown)
    Real Time Query: OFF
    Instance(s):
    mvmxs2
    Database Status:
    DGM-17016: failed to retrieve status for database "mvmxs2"
    ORA-16532: Data Guard broker configuration does not exist
    ORA-16625: cannot reach database "mvmxs2"
    DGMGRL>
    tailed the drcmvmxs2.log during stop and start of the broker
    palmer60:/u01/app/omvmxp1/diag/rdbms/mvmxs2/mvmxs2/trace>tail -f drcmvmxs2.log
    12/19/2012 20:32:20
    drcx: cannot open configuration file "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    12/19/2012 20:32:55
    drcx: cannot open configuration file "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
    ORA-27037: unable to obtain file status
    IBM AIX RISC System/6000 Error: 2: No such file or directory
    Additional information: 3
    12/19/2012 20:59:10
    Data Guard Broker shutting down
    DMON Process Shutdown <<12/19/2012 20:59:35
    Starting Data Guard Broker bootstrap <<Broker Configuration File Locations:
    dg_broker_config_file1 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr1mvmxs2.dat"
    dg_broker_config_file2 = "/u01/app/omvmxp1/product/11.2.0/dbhome_2/dbs/dr2mvmxs2.dat"
    Not sure how to fix this one.
    Regards

  • Data Guard Broker fails with ORA-16635 and ORA-03135

    Hi All,
    I configured Oracle RAC with Dataguard 11.2 on Windows 2003.
    I've already configured Standby without Data Guard Broker and everything is working fine, but when I try to use Data Guard Broker, he can not synchronize the files from the Data Guard Broker.
    I've tried everything including MOS, but not found anything.
    I'm getting this error.
    From Primary
    DG 2011-02-11-09:15:41        0 2 0 NSV1: (MIV = 57) Start sending metadata file: "+DG_DATA/orcl/dgbroker/dg_config_file1.dat"
    DG 2011-02-11-09:15:41        0 2 0 NSV1: Sending block #1 (containing MIV = 57), 67 blocks
    DG 2011-02-11-09:15:42        0 2 0 NSV1: Error sending block #1, size 67 blocks. Error is ORA-16635.
    DG 2011-02-11-09:15:42        0 2 0 NSV1: Current network link for metadata resync is broken.
    DG 2011-02-11-09:15:42        0 2 0 NSV1: (MIV = 57) End metadata file transmission: opcode CTL_ENABLE (1.1.1825138532)
    DG 2011-02-11-09:15:42        0 2 0 NSV1: Can't send CLOSE message to DRCX. Network error is: ORA-16635.
    DG 2011-02-11-09:15:42        0 2 0 NSV1: Error is ORA-03135 connection lost contact
    DG 2011-02-11-09:15:42        0 2 0 NSV1: Current network link for metadata resync is broken.From Standby
    DG 2011-02-11-08:35:39  3001000 3 1825138419       for opcode = CTL_ENABLE, phase = RESYNCH, req_id = 1.1.1825138419
    DG 2011-02-11-08:35:39        0 2 0 NSV2: Error sending block #1, size 67 blocks. Error is ORA-16635.
    DG 2011-02-11-08:35:39        0 2 0 NSV2: Current network link for metadata resync is broken.
    DG 2011-02-11-08:35:39        0 2 0 NSV2: (MIV = 11) End metadata file transmission: opcode CTL_ENABLE (1.1.1825138419)
    DG 2011-02-11-08:35:39        0 2 0 NSV2: Can't send CLOSE message to DRCX. Network error is: ORA-16635.
    DG 2011-02-11-08:35:39        0 2 0 NSV2: Current network link for metadata resync is broken.
    DG 2011-02-11-08:35:39        0 2 0 NSV2: Metadata Resync failed. Status = ORA-16635
    DG 2011-02-11-08:35:39  3001000 3 1825138419 DMON: Database ORCLSTBY returned ORA-16635

    Hi,
    Are you using firewall between Hosts?
    If yes check if firewall is blocking yours connections.
    Set the following parameter in the sqlnet.ora file that would be referenced by each database, primary and standby.
    SQLNET.EXPIRE_TIME=n
    Where n is some number of minutes. Preferably below 10. When this parameter is enabled, a small 10 byte probe packet will be sent from node to node at specific intervals.
    Regards,
    Levi Pereira

  • Data Guard Broker: errors ORA-16816 and ORA-16817 with Fast Start Failover

    Hi,
    my environment is:
    OS: Windows XP Professional Edition SP2
    DB: Oracle EE 10.2.0.3
    Primary db: orcl
    Standby db: stby
    both databases are running on the same server.
    I have configured Data Guard as described in the DG Administration Guide.
    In the Data Guard Broker I switch to 'stby' succesfully and 'stby' is the primary db and 'orcl' is the standby db.
    I switched back to 'orcl' as primary db and I get some errors:
    DGMGRL> show database 'orcl' statusreport;
    STATUS REPORT
    INSTANCE_NAME SEVERITY ERROR_TEXT
    * WARNING ORA-16817: configuration for Fast Start of Failover is not synchronized.
    DGMGRL> show database 'stby' statusreport;
    STATUS REPORT
    INSTANCE_NAME SEVERITY ERROR_TEXT
    * ERROR ORA-16816: wrong databaserole
    * WARNING ORA-16817: configuration for Fast Start of Failover is not synchronized.
    DGMGRL> show configuration;
    Configuration
    Name: DG1
    Enabled: YES
    Protection Mode: MaxAvailability
    Fast-Start Failover: ENABLED
    Databases:
    orcl - Physical standby database
    - Fast-Start Failover target
    stby - Primary database
    Current status for DG1:
    Warning: ORA-16607: one or more databases failed.
    I have searched for solutions on Metalink and google, but with no success.
    Has anyone got this kind of problem?
    Any suggestions on how to resolve it?
    Thanks

    Hi DigerDBA
    I did your advice , the error disappear, and thanks for your advice , but do I need to keep standby_file_management='AUTO' or 'MANUAL' in primary and standby init files?
    Am asking this because when I use the observer the failover failed and I get the following error
    SQL Execution error=604, sql=[ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN]. See error stack below.
      ORA-00604: error occurred at recursive SQL level 1
      ORA-01275: Operation ADD LOGFILE is not allowed if standby file management is automatic.
    Complete Failover operation failed in the step when attempting to convert the database to be the new primary.
    Database Resource SetState Error (16771)
    01/07/2014 09:14:43
    Command FAILOVER TO epprod2 completed with error ORA-16771
    if possible can you advice me please?

  • ORA-16525: the Data Guard broker is not yet available while conneting ...

    Hi,
    I am trying to connect oracle database instance in dgmgrl prompt.
    Following error message appear ...
    DGMGRL>
    DGMGRL> connect sys/<password>@<oracle_service_name>
    Connected.
    Error:
    ORA-16525: the Data Guard broker is not yet available
    ORA-06512: at "SYS.DBMS_DRS", line 124
    ORA-06512: at line 1
    DGMGRL> exit
    $ e
    We are using oracle enterprise manager ...
    SSM

    DG broker is the way to go. There are only minor points you can't control - like when you have standby redo logs and no redo application delay, dg broker will always start real-time apply.
    Also, DG broker is the only way if you want fast-start failover (10gR2 feature).
    What is the latency of your nework, especially under load? Add this latency to each commit - will the commit time be acceptable? If not, you cannot use sync.
    What version do you use? In 10gR1, there are issues with async - there is only about 50MB buffer, and if you get such backlog, even with async commit will wait for standby. (In 10gR2 this is solved, async will read from disk redo logs.)
    NET_TIMEOUT - set it low for sync (so commits won't hang long), higher for async. Default is 180 seconds, Oracle recommends minimum value to 10 seconds. I would start with 10 sec for sync, 180 for sync. The main question is, how reliable your network is, and how long brownouts you want to survive without affecting data protection (with the expense of performance).
    Regarding the proper setting of all bells and whistles of archive_log_dest_n - I had best experience with leaving it to dg broker. Just set LogXptMode property to sync/async/arch, and let dg broker set everything else (service, valid_for, affirm, retries...).
    The authoritative source: http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm#Publications
    If you are on 10.2.0.1 - 10.2.0.3, please see metalink bug 5578157, 5587231 - if sqlnet.outbound_connection_timeout is not set, the lgwr can hang even if net_timeout is set. (Yes, real-world experience:-)

  • Data Guard Broker teasing error ORA-12514: TNS:listener

    Hello,
    I have spent many hours but don't understand what little thing I am missing or confusing me.. Please help to fix the issue.
    Physical Standb db created successfully, but now facing following issue: Though it should be and must be fixed but really making me mad
    DGMGRL> SHOW CONFIGURATION;
    Configuration - DATA GUARD
      Protection Mode: MaxPerformance
      Databases:
        dg - Primary database
    Fast-Start Failover: DISABLED
    Configuration Status:
    DISABLED
    DGMGRL> ADD DATABASE DG_DB2
    > AS CONNECT IDENTIFIER IS DG_DB2
    > MAINTAINED AS PHYSICAL;
    Error: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Failed.
    PRIM:
    db_name: DG
    db_unique_name: dg
    service_names:  dg
    STBY:
    db_name: DG
    db_unique_name: dg_db2
    service_names:  dg_db2
    # TNSNAMES same entries on both Primary and Standby: HOSTNAMES are different.
    DG =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = db01.domain)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = dg)
    DG_DB2 =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = TCP)(HOST = db02.domain)(PORT = 1521))
        (CONNECT_DATA =
          (SERVER = DEDICATED)
          (SERVICE_NAME = dg_db2)
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
          (ADDRESS = (PROTOCOL = TCP)(HOST = db01.domain)(PORT = 1521))   db02.domain for Standby on standby machine.
    # Listener.ora on PRIMARY:
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
          (ADDRESS = (PROTOCOL = TCP)(HOST = db01.domain)(PORT = 1521))
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = dg_DGMGRL.domain)
          (ORACLE_HOME = /oracle/app/11g/db)
           (SID_NAME = dg)
           (SERVICE_NAME = dg.domain)
    # Listener.ora on Standby:
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = dg_db2_DGMGRL.domain)
          (ORACLE_HOME = /oracle/app/11g/db)
           (SID_NAME = dg_db2)
           (SERVICE_NAME = dg_db2.domain)
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = db02.domain)(PORT = 1521))
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    I created Stby DB with the minimum parameters required, so that I configure BROKER and see it magic, but badly stuck in this situation here. I have read many docs related to this..but can not fix it unfortunately.
    Please guide me from your own experience as note ids, blogs are not helping me here...
    Bundle of thanks.
    Best Regards

    Hi,
    Your listener.ora file has SERVICE_NAME = dg_db2.domain whereas tnsnames.ora file has SERVICE_NAME = dg_db2.
    Check in your database for exact service name and reflect the same in both the files.
    SQL> sho parameter service_names
    Restart the listener and try connecting.
    Thank you!!

  • How to remove data guard broker configuration when  ORA-16625?

    I setup data guard broker for a standby database. However, we recreate the database and re-setup the standby database. But find the earlier broker configuration still exists. But I cannot remove or disable the configuration or any database within the configuration. When I try to do so I got the error, although all network settings are correct:
    Error: ORA-16625: cannot reach the database
    How to remove the configuration at this stage?
    Thanks for help,

    Hi, I saw same issue when doing switchover testing in my lab environment.prerequisite is primary role and standby role switched and og can be applied without data guard broker.
    Here is the step I resolved the issue
    1)on both primary and standby database
    SQL> alter system set dg_borker_start=false;
    on primary DB:
    SQL>alter system set dg_broker_config_file1='?/dbs/dr1afterswichoverpry.dat';
    SQL>alter system set dg_broker_config_file1='?/dbs/dr2afterswichoverpry.dat';
    on standby DB:
    SQL>alter system set dg_broker_config_file1='?/dbs/dr1afterswichoverstby.dat';
    SQL>alter system set dg_broker_config_file1='?/dbs/dr2afterswichoverstby.dat';
    2) enable dg_borker_start on both primay and sandbby db
    SQL> alter system set dg_borker_start=true;
    3)on primary database to create configuration
    Hope this can help you!
    email: [email protected]

  • Data Guard:  net_timeout parameter causing ORA-16163

    Hello all,
    I seem to be having a problem setting up our "TEST" data guard environment.
    First, this is 10.2.0.4 on AIX 5.3.
    My primary and standby databases are set up (with what I thought I had it set before when it was working).
    Now, however, after rebuilding the whole environment again, I seem to be having a problem with the net_timeout parameter used in my "log_archive_dest_2" string.
    When I start my databases as primary/standby, I am getting errors in my primary alert log as:
    Mon Dec 14 10:48:41 2009
    LGWR: Error 16163 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=csctestprd2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=MERCYSTB_XPT)(INSTANCE_NAME=MERCYSTB)(SERVER=dedicated)))'
    Mon Dec 14 10:48:41 2009
    Errors in file /oracle/product/10.2.0/admin/MERCY/bdump/mercy_lgwr_434430.trc:
    ORA-16163: LGWR network server host attach error
    LGWR: Failed to archive log 3 thread 1 sequence 771 (16163)
    From what I've been able to tell, the ORA-16163 is being thrown by the setting of the log_archive_dest_2 "net_timeout" value.
    Even though I have it set to 180, it keeps coming up with a setting of '1' when I show my log_archive_dest_2 parameter.
    What could be causing this to reset itself from 180 to 1 automatically.
    I checked the DG Broker settings, and they seem correct, however, after stopping and restarting the database (and dgmgr), I'm now getting an error when I show database...
    Current status for "MERCY":
    Error: ORA-16797: database is not using a server parameter file

    But, in dgmgrl, it shows it is 180. See below...
    DGMGRL> show database verbose 'MERCY';
    Database
    Name: MERCY
    Role: PRIMARY
    Enabled: YES
    Intended State: ONLINE
    Instance(s):
    MERCY
    Properties:
    InitialConnectIdentifier = 'MERCY'
    ObserverConnectIdentifier = ''
    LogXptMode = 'SYNC'
    Dependency = ''
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '1'
    ReopenSecs = '300'
    NetTimeout = '180'
    LogShipping = 'ON'
    PreferredApplyInstance = ''
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '4'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = ''
    LogFileNameConvert = ''
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName = 'csctestprd1'
    SidName = 'MERCY'
    LocalListenerAddress = '(ADDRESS=(PROTOCOL=tcp)(HOST=csctestprd1)(PORT=1521))'
    StandbyArchiveLocation = 'dgsby_MERCY'
    AlternateLocation = ''
    LogArchiveTrace = '0'
    LogArchiveFormat = '%t_%s_%r.arc'
    LatestLog = '(monitor)'
    TopWaitEvents = '(monitor)'
    Current status for "MERCY":
    Error: ORA-16778: redo transport error for one or more databases

  • Data Guard Configuration Issue / ORA-16047

    So last night I decided to setup a test Physical Standby database. I had everything working correctly and when I started playing around with the Data Guard Broker I started having some problems. Now I can't get the logs to ship from the primary to the standby.
    Version: Primary and Standby
    BANNER
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE    11.2.0.1.0    Production
    TNS for Linux: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production
    OS: Primary and Standby
    [oracle@dgdb0 trace]$ uname -a
    Linux dgdb0.localdomain 2.6.32-100.28.5.el6.x86_64 #1 SMP Wed Feb 2 18:40:23 EST 2011 x86_64 x86_64 x86_64 GNU/LinuxI first noticed a problem with a large gap in sequence numbers.
    Standby
    SQL> SELECT sequence#, applied from v$archived_log order by sequence#;
    SEQUENCE# APPLIED
         8 YES
         9 YES
        10 YES
        11 YES
        12 YES
        13 YES
        14 YES
    7 rows selected.
    Primary
    SQL> archive log list;
    Database log mode           Archive Mode
    Automatic archival           Enabled
    Archive destination           USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence     37
    Next log sequence to archive   39
    Current log sequence           39Here is some of the configuration information on the primary:
    SQL> show parameter db_name
    NAME                     TYPE     VALUE
    db_name                  string     dgdb0
    SQL> show parameter db_unique_name
    NAME                     TYPE     VALUE
    db_unique_name                 string     dgdb0
    SQL> show parameter log_archive_config
    NAME                     TYPE     VALUE
    log_archive_config             string     dg_config=(dgdb0,dgdb1)
    SQL> show parameter log_archive_dest_2
    NAME                     TYPE     VALUE
    log_archive_dest_2             string     service=dgdb1 async valid_for=
                             (online_logfile,primary_role)
                             db_unique_name=dgdb1Standby parameters
    SQL> show parameter db_name
    NAME                     TYPE     VALUE
    db_name                  string     dgdb0
    SQL> show parameter db_unique_name
    NAME                     TYPE     VALUE
    db_unique_name                 string     dgdb1So I proceeded to run this query:
    SQL> SELECT error from v$archive_dest WHERE dest_name='LOG_ARCHIVE_DEST_2';
    ERROR
    ORA-16047: DGID mismatch between destination setting and target
    databaseThe error description is:
    Cause:       The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination.
    Action:     Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination.As you can see from above the DB_UNIQUE_NAME in the LOG_ARCHIVE_DEST_2 parameter matches that of the standby database.
    Also DG_BROKER_START is set to false on both the primary and standby databases.
    Finally, I've removed all the drc* files from the $ORACLE_HOME/dbs directories on both the primary and standby servers to ensure the broker is not configured.
    Where did I go wrong? How can I get the standby caught up and working correctly again?
    I apologized if I missed anything. I'm relatively new to standby databases.

    Centinul;
    I have noticed a couple things
    1. If you are running the query below from the standby you will probably always get the results you posted
    SELECT sequence#, applied from v$archived_log order by sequence#;
    What I do if run this from the primary and I add the "DEST_ID" column to the query.
    2. You might have better luck finding GAPS using these queries:
    select max(sequence#) from v$archived_log where applied='YES';
    select process,status from v$managed_standby;
    SELECT * FROM V$ARCHIVE_GAP;
    3. You are mixing SQL results with Data Broker, that can bite you. Not sure where you went wrong but I would create PFILE versions at both ends before trying to Data Broker. The you can review each setting and avoid issues before adding Data Broker. Data Broker will take control and you may even find it adds entries to your parameter file.
    The ORA-16047 is probably database parameter related and this should at least help answer the question. For example you might be missing log_archive_config on the Standby or soething. Comparing the two PFILE's should narrow this down
    I checked my Data Broker notes but did not find an ORA-16047, I managed ORA-01031, ORA-16675, ORA-12514, and ORA-16608.
    For me I decided it was a good idea to run Data Guard without Data Broker at first until I got the feel of it using SQL.
    Last of all if you have not already consider buying Larry Carpenter's "Oracle Data Guard 11g Handbook" In my humble opinion its worth every penny and more.
    Best Regards
    mseberg

  • Init SID .ora during configuration of Data Guard - advice required

    Hi All,
    I am looking to implement data guard across 2 RAC clusters. One cluster will be primary and the other is for Disaster Recovery.
    I have already set up the two 11g R 2 RAC clusters on RHEL 5 and now need some pointers to good docs for data guard install.
    Can some one direct me to good step by step info for configuring data guard between to RAC clusters - detailed explanations of each step would be useful too, in particular around the init.ora file configuration changes between the primary and DR sites
    Much appreciated
    Steve

    Hi Steve,
    look at the MAA Whitepapers:
    http://www.oracle.com/technetwork/database/features/availability/oracle-database-maa-best-practices-155386.html
    There are very good ressources in setting up RAC DG environments like:
    Data Guard 11g Installation and Configuration Best Practices on Oracle RAC
    Rapid Oracle RAC Standby Deployment: Oracle Database 11g Release 2
    Setup Guide: Creating a RAC Logical Standby Database for a RAC Primary Database
    Client Failover in Data Guard Configurations for Highly Available Oracle Databases
    a.s.o.
    Sebastian

  • 11.2 DB & Data Guard : ORA-16014 how to archive a sequence?

    Hi,
    I've installed 11.2 Oracle Database in my laptop with Oracle Enterprise Linux 5.3 and I have created two standby databases, orcl (primary) and orclstby (physical standby). I performed a switchover to orclstby and consequently, orclstby was the new primary and orcl the physical standby, I checked those values with SQLPlus executing the select database_role from v$database statement, so, there were no problems during the switchover.I also shutteddown and started both primary and stanby databases to check all was fine.
    Today, I've tried to start the environment again and I've encountered the following problem during the startup of the primary database:
    [oracle@mredon-es ~]$ sqlplus / as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 21 17:34:21 2009
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 839282688 bytes
    Fixed Size 2217992 bytes
    Variable Size 507512824 bytes
    Database Buffers 322961408 bytes
    Redo Buffers 6590464 bytes
    Database mounted.
    ORA-03113: end-of-file on communication channel
    Process ID: 5562
    Session ID: 9 Serial number: 3
    I've checked the newest log created and this is its content:
    Dump file /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/log/orclstby_ora_5382.trc
    *** 2009-10-21 17:34:30.467
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
    System name: Linux
    Node name: mredon-es.us.oracle.com
    Release: 2.6.18-128.el5
    Version: #1 SMP Wed Jan 21 08:45:05 EST 2009
    Machine: x86_64
    Instance name: orclstby
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 0
    Unix process pid: 5382, image: [email protected]
    *** 2009-10-21 17:34:30.526
    2009-10-21 17:34:30.457: [ default]utgdv:2:ocr loc file /etc/oracle/olr.loc cann
    ot be opened. errno 2
    2009-10-21 17:34:30.527: [ default]utgdv:2:ocr loc file /etc/oracle/ocr.loc cann
    ot be opened. errno 2
    I've searched in Metalink information about ocr.loc and olr.loc and they seem to be part of an Oracle RAC installation, I don't know why the database needs these files to start if I am using single instance...
    Any idea would be kindly appreciated because I'm a bit confused and I don't really know what steps I am suppposed to take in order to solve this problem.
    Thanks in advance.
    Edited by: mredon on Oct 26, 2009 5:22 AM
    Reason: title of the post changed

    sorry for the delay, here is the alert log:
    <msg time='2009-10-21T23:03:09.576+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module='[email protected] (TNS V1-V3)'
    pid='6582'>
    <txt>Data Guard: version check completed
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:09.642+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module=''
    pid='6486'>
    <txt>LGWR: STARTING ARCH PROCESSES
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:09.709+02:00' org_id='oracle' comp_id='rdbms'
    msg_id='ksbrdp:3833:3697353022' type='NOTIFICATION' group='process start'
    level='16' host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130'
    pid='6588'>
    <txt>RSM0 started with pid=23, OS id=6588
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:09.831+02:00' org_id='oracle' comp_id='rdbms'
    msg_id='ksbrdp:3833:3697353022' type='NOTIFICATION' group='process start'
    level='16' host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130'
    pid='6590'>
    <txt>ARC0 started with pid=24, OS id=6590
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:10.832+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module=''
    pid='6486'>
    <txt>ARC0: Archival started
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:10.832+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module=''
    pid='6486'>
    <txt>LGWR: STARTING ARCH PROCESSES COMPLETE
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:10.833+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module=''
    pid='6590'>
    <txt>ARC0: STARTING ARCH PROCESSES
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:11.180+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module='[email protected] (TNS V1-V3)'
    pid='6582'>
    <txt>ARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_2 after log switch
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:11.183+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module='[email protected] (TNS V1-V3)'
    pid='6582'>
    <txt>ARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_1 after log switch
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:11.258+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module='[email protected] (TNS V1-V3)'
    pid='6582'>
    <txt>Errors in file /u01/app/oracle/product/diag/rdbms/orclstby/orclstby/trace/orclstby_ora_6582.trc:
    ORA-16014: log 1 sequence# 27 not archived, no available destinationsORA-00312: online log 1 thread 1: &apos;/u01/app/oracle/product/oradata/orclstby/redo01.log&apos;
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:11.263+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module='[email protected] (TNS V1-V3)'
    pid='6582'>
    <txt>USER (ospid: 6582): terminating the instance due to error 16014 </txt>
    </msg>
    <msg time='2009-10-21T23:03:11.429+02:00' org_id='oracle' comp_id='rdbms'
    msg_id='ksbrdp:3833:3697353022' type='NOTIFICATION' group='process start'
    level='16' host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130'
    pid='6592'>
    <txt>ARC1 started with pid=25, OS id=6592
    </txt>
    </msg>
    <msg time='2009-10-21T23:03:12.728+02:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='mredon-es.us.oracle.com' host_addr='192.168.237.130' module='[email protected] (TNS V1-V3)'
    pid='6582'>
    <txt>Instance terminated by USER, pid = 6582
    </txt>
    </msg>
    I've marked in bold the errors which may be causing the problem, ¿what do you think?

  • Active Data Guard and Undo and ora-01555

    Hi
    We have an 11.1.0.7 two-node RAC primary with a single instance Active Data Guard physical standby. When running a datapump export from the standby, we get an ORA-01555 although the undo_retention is set way beyond the run time for the export.
    I'm looking to better understand undo within the context of Active Data Guard. Is there any dependency for undo between the primary(s) and standby? Are the undo settings (undo_retention, undo tablespace size..) on the primary and standby independent of each other?
    Thanks.

    The standby is a Physical Standby. An exact copy of the Primary. The undo at the standby is controlled by the redo coming from the Primary. When the undo gets overwritten at the Primary it gets overwritten at the standby regardless of what is running there. You can't have undo kept around longer at the standby, it is an EXACT copy of the Primary.
    Increasing the undo tablespace and the undo_retention at the Primary will allow more undo to be kept at both the Primary and the Standby but the standby is still controlled by the Primary's management of the undo. Of course you should change the parameter at the standby too so that everything behaves the same when you make the standby a Primary database.
    Hope this helps.
    Larry

  • Data Guard ora-00314 and ora-00312

    Good afternoon. Please, I have configured a data guard on the same server and am sure the files are well configured as
    *.db_file_name_convert='C:\Oracle\product\10.2.0\oradata\test2','C:\Oracle\product\10.2.0\oradata\test1'
    log_file_name_convert='C:\Oracle\product\10.2.0\oradata\test2','C:\Oracle\product\10.2.0\oradata\test1'
    Thanks

    The Primary database was OK before I start the Standby database. I've tried many times but failed to open the Primary database after I successfuly created and opened the Standby database. Did the Standby database crash the redo log of Primary? Why?
    Error shown when I want to open the Primary database:
    ORA-00314: log 2 of thread 1, expected sequence# 11 doesn't match 0
    ORA-00312: online log 2 thread 1: '/u01/oradata/DB01/redo_log02.dbf'Part of my initDB01.ora
    DB_NAME=DB01
    DB_UNIQUE_NAME=DB01
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB01,DB02)'
    LOG_ARCHIVE_DEST_1=
    'LOCATION=/u01/oradata/DB01/arc/ MANDATORY
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=DB01'
    LOG_ARCHIVE_DEST_2=
    'SERVICE=DB02
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=DB02'
    LOG_ARCHIVE_DEST_STATE_1=ENABLE
    LOG_ARCHIVE_DEST_STATE_2=ENABLE
    LOG_ARCHIVE_MAX_PROCESSES=30
    FAL_SERVER=DB02
    FAL_CLIENT=DB01
    DB_FILE_NAME_CONVERT='/u01/oradata/DB02/','/u01/oradata/DB01/'
    LOG_FILE_NAME_CONVERT='/u01/oradata/DB02/arc/','/u01/oradata/DB01/arc/'
    STANDBY_FILE_MANAGEMENT=AUTO
    Part of my initDB02.ora
    CONTROL_FILES='/opt/oracle/oradata/DB02/control_primary.ctl'
    DB_NAME=DB01
    DB_UNIQUE_NAME=DB02
    LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB01,DB02)'
    LOG_ARCHIVE_DEST_1=
    'LOCATION=/u01/oradata/DB02/arc/ MANDATORY
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=DB02'
    LOG_ARCHIVE_DEST_2=
    'SERVICE=DB01
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=DB01'
    LOG_ARCHIVE_DEST_STATE_1=ENABLE
    LOG_ARCHIVE_DEST_STATE_2=ENABLE
    STANDBY_FILE_MANAGEMENT=AUTO
    FAL_SERVER=DB01
    FAL_CLIENT=DB02
    DB_FILE_NAME_CONVERT='/u01/oradata/DB01/','/u01/oradata/DB02/'
    LOG_FILE_NAME_CONVERT='/u01/oradata/DB01/arc/','/u01/oradata/DB02/arc/'

Maybe you are looking for