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?

Similar Messages

  • 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

  • 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:-)

  • Monitoring failover - Data Guard Broker

    Hi,
    I work on a Oracle 10.2.0.4 database on Solaris 10. It is a 2 node RAC database with a physical standby configured.
    I want to monitor (send a mail) to myself when failover occurs (which will be triggered by data guard broker ) , I think so I can monitor the failover using alert log (which normally does log the command when we initiate a failover) but I am not sure whether data guard broker also does the same( writes appropriate commands when a failover is triggered)
    Is there any other way we can come to know when a failover occurs (we can query database_role from v$dataguard status) but I am looking for some trigger that will be fired instantaneously when a failover is initiated ?
    Also is it possible to monitor the observer, whether it is up or not ?

    Hi,
    you have several possiblities to do that. Easiest is to use predefined Grid Control Events for it. Or you may put a trigger on the event "after DB_ROLE_CHANGE on database".
    Monitoring the observer can be done with dgmgrl like
    connect sys/<pw>@<cd>;
    show configuration verbose;That show you the presence and location of the observer.
    I give you an example for the usage of the trigger that starts a service depending on the role of the database. You may customize it to send you an email.
    begin
      dbms_service.create_service('safe','safe');
    end;
    create trigger rollenwechsel after DB_ROLE_CHANGE on database
    declare
      vrole varchar(30);
    begin
      select database_role into vrole from v$database;
      if vrole = 'PRIMARY' then
        DBMS_SERVICE.START_SERVICE('safe');
      else
        DBMS_SERVICE.STOP_SERVICE('safe');
      end if;
    end;
    /

  • Protection Modes and Fast-Start Failover

    Oracle Maximum Availability Architecture allows you to set fast-start failover (FSF)to automatically failover to the standby in the event of losing the primary database.
    One condition of FSF is that it will only initiate if there is a guarantee of no data loss. This is where i start getting confused. Maximum Availability mode allows for data loss as the primary will still process transactions if the connection to the standby is lost. This means then in the event of the standby being out of sync with the primary database (i.e. network glitches) and then losing the primary database to hardware issues for example. FSF will not be able to initiate as data will be lossed and a complete loss of service will happen!
    Can FSF be used in Maximum Protection mode as this will always mean FSF will be able to occur? Also what is the overhead towards the databases with regards to running them in this mode?
    Thanks,
    Chris

    Hi,
    Can FSF be used in Maximum Protection mode as this will always mean FSF will be able to occur? Yes, Maximum Protection Mode can be used with Fast-Start Failover, please review the next link.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14230/cli.htm#BABEIIHD
    Also what is the overhead towards the databases with regards to running them in this mode?
    Yes, the overhead is on major scale that other modes.
    Regards.

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

  • 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 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 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/'

  • Getting ORA-17629 and ORA-17627 during setting up of data guard

    Hi All,
    I am working on data guard setup, and getting ORA-17629 and ORA-17627. The orapwd file was copied to DR server, but still getting the same error when doing a duplicate database command.
    RMAN> run{
    2> allocate channel c1 type disk;
    3> allocate channel c2 type disk;
    4> allocate auxiliary channel a1 type disk;
    5> allocate auxiliary channel a2 type disk;
    6> duplicate target database for standby from active database
    7> spfile
    8> set db_unique_name='DRTELPRD'
    9> set standby_file_management='AUTO'
    10> set FAL_CLIENT='DRTELPRD'
    11> set FAL_SERVER='TELRPD'
    12> nofilenamecheck;
    13> }
    allocated channel: c1
    channel c1: SID=950 device type=DISK
    allocated channel: c2
    channel c2: SID=942 device type=DISK
    allocated channel: a1
    channel a1: SID=97 device type=DISK
    allocated channel: a2
    channel a2: SID=96 device type=DISK
    Starting Duplicate Db at 26-AUG-11
    contents of Memory Script:
    backup as copy reuse
    file 'e:\app\product\11.1.0\db_1\DATABASE\PWDtelprd.ORA' auxiliary format
    'e:\app\product\11.1.0\db_1\DATABASE\PWDdrtelprd.ORA' file
    'E:\APP\PRODUCT\11.1.0\DB_1\DATABASE\SPFILETELPRD.ORA' auxiliary format
    'E:\APP\PRODUCT\11.1.0\DB_1\DATABASE\SPFILEDRTELPRD.ORA' ;
    sql clone "alter system set spfile= ''E:\APP\PRODUCT\11.1.0\DB_1\DATABASE\SPF
    ILEDRTELPRD.ORA''";
    executing Memory Script
    Starting backup at 26-AUG-11
    RMAN-03009: failure of backup command on c1 channel at 08/26/2011 14:44:17
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-01031: insufficient privileges
    ORA-17629: Cannot connect to the remote database server
    continuing other job steps, job failed will not be re-run
    released channel: c1
    released channel: c2
    released channel: a1
    released channel: a2
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 08/26/2011 14:44:17
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of backup command on c2 channel at 08/26/2011 14:44:17
    ORA-17629: Cannot connect to the remote database server
    ORA-17627: ORA-01031: insufficient privileges
    ORA-17629: Cannot connect to the remote database server
    RMAN>

    Thanks for your instructions. It worked very good. But, I am getting errors for redo01.log files. The redo log files are not created.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'E:\ORACLE\ORADATA\TELPRD\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    Errors in file e:\app\diag\rdbms\drtelprd\drtelprd\trace\drtelprd_mrp0_352.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'E:\ORACLE\ORADATA\TELPRD\REDO01.LOG'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    Clearing online redo logfile 1 E:\ORACLE\ORADATA\TELPRD\REDO01.LOG
    Clearing online log 1 of thread 1 sequence number 3418
    Errors in file e:\app\diag\rdbms\drtelprd\drtelprd\trace\drtelprd_mrp0_352.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: 'E:\ORACLE\ORADATA\TELPRD\REDO01.LOG'

  • ORA-00001 and ORA-06512 error on  DBMS_WM.ResolveConflicts

    We are getting unique constraint error in Production Database. We are able to merge most of the workspaces with no issues. One workspace is givign errors on merge.
    Here is the code
    begin
    dbms_wm.gotoworkspace('denialletterspoc_onmzpulp');
    dbms_wm.setdiffversions('denialletterspoc_onmzpulp','LIVE');
    dbms_wm.SetConflictWorkspace('denialletterspoc_onmzpulp');
    commit;
    DBMS_WM.BeginResolve('denialletterspoc_onmzpulp');
    DBMS_WM.ResolveConflicts(
    workspace => 'denialletterspoc_onmzpulp',
    table_name => 'MCM_MESSAGE',
    where_clause => ' id in (8403026,10134822,8259485,8259488,8426289,8426287,10186643,8426288) ',
    keep => 'CHILD'
    exception when others then
    DBMS_WM.RollbackResolve('denialletterspoc_onmzpulp');
    raise;
    end;
    ORA-00001: unique constraint (T2.MCM_MESSAGE_PK) violated
    ORA-06512: at line 16
    I looked at the date in XXX_lt tables and it does not look suspecious. Please help us understand
    ORA-00001 and ORA-06512 error.
    Amit Gangwar

    Hi, Ben
    Our OWM_VERSION is 10.2.0.4.3.
    I tried disable and enable constraint MCM_MESSAGE_PK. But didn't fix our issue.
    Split where clause from " id in (...) " syntax to " id = ... " syntax will reduce performance heavily. And I did some test that " id in (...) " syntax works well in our dev env.
    I opened our trace file and get below plsql block. When I perform it get same error with our original codes. Please notice the part of "forall wm_indx in WM_rowids.first .. WM_rowids.last execute immediate 'begin insert into T2.MCM_MESSAGE_lt ... ...", error occurred here. But if I change the "forall" syntax to normal " for ... loop" syntax then no error here. Can you give me some advice or suggestion?
    DECLARE
    WM_rowids wmsys.lt_ctx_pkg.rowidTabType;
    WM_rowids_vt wmsys.lt_ctx_pkg.rowidTabType;
    WM_curver wmsys.lt_ctx_pkg.int_tab;
    WM_vtRow wmsys.lt_ctx_pkg.int_tab;
    WM_nextver wmsys.lt_ctx_pkg.nextver_tab;
    WM_found integer := 0;
    BEGIN
    dbms_wm.gotoworkspace('denialletterspoc_onmzpulp');
    dbms_wm.setdiffversions('denialletterspoc_onmzpulp','LIVE');
    dbms_wm.SetConflictWorkspace('denialletterspoc_onmzpulp');
    /* update the auxilliary table of snapshots */
    /* These are rows in the current version that have already been resolved once */
    update T2.MCM_MESSAGE_aux st
    set (snapShotChild, snapShotParent, versionParent) =
    (select p.WM_childds, p.WM_parentds, p.WM_parentver
    from T2.MCM_MESSAGE_pkc p
    where p.ID = st.ID),
    value = '0',
    wm_opcode = 'CC'
    where st.versionChild = 614
    and (ID) in (select ID
    from T2.MCM_MESSAGE_pkc p
    where (id in (8403026,
    10134822,
    8259485,
    8259488,
    8426289,
    8426287,
    10186643,
    8426288)));
    select distinct WM_ridchild bulk collect
    into WM_rowids
    from T2.MCM_MESSAGE_pkc
    where (id in (8403026,
    10134822,
    8259485,
    8259488,
    8426289,
    8426287,
    10186643,
    8426288))
    and WM_childver != 614;
    if (WM_rowids.first is not null) then
    WM_found := 1;
    forall wm_indx in WM_rowids.first .. WM_rowids.last
    update T2.MCM_MESSAGE_lt
    set retireTime = wmsys.owm_9ip_pkg.activeTimeForDML,
    nextver = wmsys.lt_ctx_pkg.getNextVer(nextver,
    614,
    version,
    'denialletterspoc_onmzpulp',
    'CRS_LEAF',
    22)
    where rowid = WM_rowids(wm_indx)
    returning wmsys.lt_ctx_pkg.getCurNextVer bulk collect into WM_nextver;
    /* These are the rows that have not yet been resolved after the latest BeginResolve */
    forall wm_indx in WM_rowids.first .. WM_rowids.last execute immediate
    'begin insert into T2.MCM_MESSAGE_lt(ID,DPS_APPLICATION_ID,TYPE_ID,NAME,PRIVILEGED,CAMPAIGN_ID,TEXT,FILE_NAME,GRAPHIC_WIDTH,GRAPHIC_HEIGHT,DESCRIPTION,ACTIVE,INCLUDE_IN_LIBRARY,MESSAGE_FILTER_ID,OP_USER_ID,OP_WORKSPACE,OP_TIME,version,createtime,retiretime,nextver,delstatus,ltlock)
    (select t1.ID,t1.DPS_APPLICATION_ID,t1.TYPE_ID,t1.NAME,t1.PRIVILEGED,t1.CAMPAIGN_ID,t1.TEXT,t1.FILE_NAME,t1.GRAPHIC_WIDTH,t1.GRAPHIC_HEIGHT,t1.DESCRIPTION,t1.ACTIVE,t1.INCLUDE_IN_LIBRARY,t1.MESSAGE_FILTER_ID,t1.OP_USER_ID,t1.OP_WORKSPACE,t1.OP_TIME,614, wmsys.owm_9ip_pkg.activeTimeForDML, null,:1, sign(delstatus)*(abs(delstatus)+1),
    wmsys.lt_ctx_pkg.checkngetlock(''C'', t1.ltlock, t1.nextver, ''denialletterspoc_onmzpulp'', 0,
    ''MODIFY'', t1.version, t1.delstatus, 0, 1)
    from T2.MCM_MESSAGE_lt t1
    where t1.rowid = :2); end;'
    using WM_nextver(wm_indx),
    WM_rowids(wm_indx)
    end if;
    if (WM_found = 1) then
    wmsys.lt_ctx_pkg.update_modified_tables('T2',
    'MCM_MESSAGE',
    614,
    'denialletterspoc_onmzpulp',
    22);
    end if;
    if (WM_found = 1) then
    forall wm_indx in WM_rowids.first .. WM_rowids.last
    delete from T2.MCM_MESSAGE_aux
    where (ID) in (select ID
    from T2.MCM_MESSAGE_lt
    where rowid = WM_rowids(wm_indx))
    and childState = 'denialletterspoc_onmzpulp';
    end if;
    /* now insert new syncing information about these rows */
    execute immediate 'insert into T2.MCM_MESSAGE_aux (
    select ID,
    p.WM_childstate, p.WM_parentstate,
    p.WM_childds, 614, p.WM_parentds, p.WM_parentver, ''0'',''CC''
    from T2.MCM_MESSAGE_pkc p
    where ( id in (8403026,10134822,8259485,8259488,8426289,8426287,10186643,8426288) ) )';
    END;
    Thanks
    Amos

  • Data Guard Broker and Cold Failover clusters

    Hi,
    I wanted to use Data Guard Broker to control primary/standby systems on AIX clusters but found that without Oracle clusterware it is not supported on failover of a database to another node (unless you drop and recreate the configuration which in my opinion is not support at all!).
    The 11g documentation states that DG Broker offers support for single instance databases configured for HA using Oracle Clusterware and "cold failover clusters".
    Does anyone know whether this support for cold failover clusters in 11g means "proper support" i.e the configuration detects that the hostname has changed and automatically renames it so it continues to work?, or is the support in 11g the same as that in 10g?.
    Thanks,
    Andy

    Hi Jan,
    We already use virtual hostnames.
    When I set up the configuration the hostname for the databases default to the server name. The only way I know of changing this is to disable the configuration, then use the "edit database...set property" command but when I enable the configuration again it reverts back to its previous value.
    regards,
    Andy

  • Ora 600 and ora 7445 error in oracle 10g r2

    hi all,
    we are using Oracle 10g r2.
    os is windows 2003 server,
    ram is 4 gb.
    front end is java .
    we got a below mentioned errors.
    i got the RA-00600: internal error code, arguments: [qerghFetch:inc], [], [], [], [], [], [], [],
    and ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61F04AC9] [ADDR:0xC] [UNABLE_TO_READ] []
    and Error 0 in kwqmnpartition(), aborting txn errors.
    for aug 3 11.42.47 we got a ora 600 error after that through front end (java) users can't able to connect the database.the not able to executed the query session disconnected error.
    what is reason for theis error . how it will rectifiy.?
    pls advice.Below i attached the alret log message .
    Sun Aug 02 04:04:24 2009
    Error 0 in kwqmnpartition(), aborting txn
    Sun Aug 02 05:48:10 2009
    Error 0 in kwqmnpartition(), aborting txn
    Sun Aug 02 05:49:10 2009
    Error 0 in kwqmnpartition(), aborting txn
    Sun Aug 02 07:38:49 2009
    Thread 1 advanced to log sequence 1732
    Current log# 3 seq# 1732 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
    Sun Aug 02 07:44:14 2009
    Error 0 in kwqmnpartition(), aborting txn
    Sun Aug 02 07:45:14 2009
    Error 0 in kwqmnpartition(), aborting txn
    Sun Aug 02 22:00:26 2009
    Thread 1 advanced to log sequence 1733
    Current log# 1 seq# 1733 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
    Mon Aug 03 07:08:15 2009
    Thread 1 advanced to log sequence 1734
    Current log# 2 seq# 1734 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
    Mon Aug 03 09:28:23 2009
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 09:30:27 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 11:42:47 2009
    Errors in file e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6012.trc:
    ORA-00600: internal error code, arguments: [qerghFetch:inc], [], [], [], [], [], [], []
    Mon Aug 03 13:20:00 2009
    Thread 1 advanced to log sequence 1735
    Current log# 3 seq# 1735 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
    Mon Aug 03 16:07:07 2009
    Errors in file e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_4756.trc:
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61F04AC9] [ADDR:0xC] [UNABLE_TO_READ] []
    Mon Aug 03 16:07:11 2009
    Process m000 died, see its trace file
    Mon Aug 03 16:07:11 2009
    ksvcreate: Process(m000) creation failed
    Mon Aug 03 16:08:37 2009
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 16:10:40 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 17:25:05 2009
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 17:27:11 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 17:32:19 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 17:33:24 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 18:52:08 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 18:54:09 2009
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 19:05:33 2009
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Mon Aug 03 19:09:02 2009
    Errors in file e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_5132.trc:
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C34126B] [ADDR:0x0] [UNABLE_TO_WRITE] []
    Mon Aug 03 19:10:27 2009
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn
    Error 0 in kwqmnpartition(), aborting txn

    Hi reshumakur
    As this is your PRODUCTION system THEN_ The best help to offer in case of ORA-600, and ORA-7445 is to open SR with metalink. Submit with the SR the following
    1- Alert log
    2- Trace files (in ur case e:\oracle\product\10.2.0\admin\orcl\udump\orcl_ora_6012.trc: and e:\oracle\product\10.2.0\em_2\rdbms\trace\orcl_ora_4756.trc:)
    3- Describe what was happening when you had these errors.
    Try to avoid free help when you have ORA-600 and ORA-07445. This errors could be becuase of BUGS. Oracle Support will know this from the call stack in the trace file.
    Then Do your best to patch 10.2.0.4 and the latest CPU patch.
    Good Luck

  • ORA-01180 and ORA-01110 error when restoring database by RMAN in 11.1.0.6.0

    I have a new installed database running in ARCIHVELOG mode on SUSE 10SP3. Catalog is not used. When I try to restore the database from a level 0 backup based on SCN, ORA-01180 and ORA-01110 were raised out today. Please help me through this. Thx. The senario follows:
    1. I got the current SCN by "select dbms_flashback.get_system_change_number from dual". Say it's 12345;
    2. I did a level 0 hot backup with current control file, archived logs and parameter files. Everything went well;
    3. Some other DMLs are applied to the database;
    4. I want to do a SCN-based incomplete recovery for this database to SCN 12345. Then I
    1) shutdown immediate;
    2) startup nomount;
    3) restore the control file from backupset;
    5) startup mount;
    6) catalog start with "[backupset path]";
    7) restore database until scn 12345.
    Just at step 4.7, ORA-01180 and ORA-01110 were raised out, saying cannot create data file 1. Note: Backup files are existing and file permissions are all OK.
    Then I issues "list incarnation of database". There is just one record with incarnation id 1.
    So I queried v$log_history, found serveral record there. The most recent one has NEXT_SCN later than 12345, say 12400. Then I tried to restore database until this SCN. It WORKED! The restore and recovery succeeded.
    My questions are:
    1. Why cannot I restore the database to a previous SCN, say 12345, but 12400 is OK?.
    2. If the database was RESETLOG prior to my recovery, should I reset database to the incarnation where I took my backup? What can I do if there is no that incarnation information in my control file?
    Waiting for your suggestion.

    Hi guys. There is one update.
    This issue is caused by the incorrect SCN vs. backup set. I got this SCN before the backup started. According to Oracle docs, it's not allowed for an SCN based recovery.
    Now, I changed the sequence of my operations, so that SCN is got once backup is done, which is exact the "most recent sequence# and least SCN" mentioned by some thread in this forum. It works now.
    Anyone could explain why the SCN got prior to the level 0 backup is not recognized by restore/recovery phase? Thanks.

Maybe you are looking for