DataGuard broker WARNING: ORA-16610

Similar Questions

• dgmgrl show configuration - ORA-16610: command "Service Broker implementation" ongoing (impossible to determine status)

  Hello

  
  

  We have an active guard of data with a physical standby database. Using custom scripting zabbix we execute dgmrl 'See the configuration' and grep result of ' State of ' the output Configuration.  If this isn't "SUCCESS", then a notification is sent.

  Today @ 15:12:53 has been following the release of the primary database:
  
  ORA-16610: command "Service Broker implementation" ongoing

  DGM-17017: unable to determine the configuration state

  
  

  I happened to notice the notification immediately, connected and run "show configuration" manually, which was SUCCESSFUL. Also the next result for zabbix has SUCCESS @ 15:15:53.

  On the basis of data pending, the results have been successful all the way (also at 12:15:56).

  
  

  No errors not found in the journal to the DRC, nor in the log of the server logs or alerts. EM's own beautiful graphic. Data has been / are in sync and I couldn't find anything indicating problems.

  However, the exit for 'see the configuration' may not have been drawn from air - it something must have caused. Any ideas on this subject?
  
  

  
  

  Hello;

  It is possible, that a health check is running. OR one of your databases does not use a SPFILE.

  In any case, it is not an error, just a warning, so unless he's going on a high percentage of the time I wouldn't worry on this subject.

  Best regards

  mseberg

• ORA-16610: "ENABLE DATABASE command < DB_NAME > ' current

  Hello

  After the reconstruction of 3 times my configuration, I bounce back with the same problem. I read all the threads on the subject but couldn't find a solution. If someone has an idea:

  I have 2 instances acting as main currently: "ORCL1" (the server ServerS1) and "ORCL2" (on server server2 server) on a "ORCLS" (cluster CCR) database RAC

  I have 2 instances acting as dataguard currently: "ORCL1" (on the ServerP1 server) and 'ORCL2' (on the ServerP2 server) on a data base RAC "ORCL" (cluster RACP)

  (a failover occurred recently, I just rebuilt dataguards, archivelog are normally applied)

  Before you build, I do the following:

  DGMGRL > connect sys@ORCLS

  DGMGRL > disable the configuration

  DGMGRL > remove the configuration

  sqlplus / as sysdba on ORCL1/ServerS1 > ALTER SYSTEM SET DG_BROKER_START = FALSE;

  sqlplus / as sysdba on ORCL1/ServerP1 > ALTER SYSTEM SET DG_BROKER_START = FALSE;

  asmcmd on ServerS1 > rm +DATA/ORCLS/DGCONFIG/dgb_config01.ora

  asmcmd on ServerS1 > rm +RECOVERY/ORCLS/DGCONFIG/dgb_config02.ora

  asmcmd on ServerP1 > rm +DATA/ORCL/DGCONFIG/dgb_config01.ora

  asmcmd on ServerP1 > rm +RECOVERY/ORCL/DGCONFIG/dgb_config02.ora

  Then I try to rebuild my setup:

  sqlplus / as sysdba on ORCL1/ServerS1 > ALTER SYSTEM SET DG_BROKER_START = TRUE;

  sqlplus / as sysdba on ORCL1/ServerS1 > show parameter broker

  NAME

  TYPE

  VALUE

  ------------------------------------ ----------- ------------------------------

  dg_broker_config_file1	string	+Data/ORCLS/dgconfig/dgb_config01.ora
  dg_broker_config_file2	string	+Recovery/ORCLS/dgconfig/dgb_config02.ora
  dg_broker_start	Boolean	TRUE

  sqlplus / as sysdba on ORCL1/ServerP1 > ALTER SYSTEM SET DG_BROKER_START = TRUE;

  sqlplus / as sysdba on ORCL1/ServerP1 > display setting broker

  NAME

  TYPE

  VALUE

  ------------------------------------ ----------- ------------------------------

  dg_broker_config_file1	string	+Data/ORCL/dgconfig/dgb_config01.ora
  dg_broker_config_file2	string	+Recovery/ORCL/dgconfig/dgb_config02.ora
  dg_broker_start	Boolean	TRUE

  DGMGRL > connect sys@ORCLS

  DGMGRL > create primary as database 'DG_ORCL' configuration is "ORCLS" connect identifier is "ORCLS";

  Configuration "DG_ORCL" created with the primary database 'ORCLS '.

  DGMGRL > add "ORCL" data like login name is "ORCL".

  Database "ORCL" added

  DGMGRL > activate the configuration

  Permit.

  DGMGRL > see Configuring

  Configuration - DG_ORCL

  Protection mode: MaxPerformance

  Databases:

  ORCLS - primary

  ORCL - Physical standby database

  Fast-Start Failover: DISABLED

  The configuration status:

  ORA-16610: command-'ACTIVATE the ORCL DATABASE' current

  DGM-17017: unable to determine the configuration state

  Also, when I try to run:

  DGMGRL > see the ORCL database

  Database - ORCL

  Role: STANDBY PHYSICS

  State of destination: apply one <-from there, it goes very slow and then...:

  Transport delay: (unknown)

  Apply the Lag: (unknown)

  Apply the rate: (unknown)

  Real-time query: OFF

  Occurrence (s):

  ORCL1

  ORCL2

  State of the database:

  DGM-17016: unable to retrieve the database state "ORCL".

  ORA-16532: the Data Guard broker Configuration does not exist

  ORA-16625: cannot reach the database "ORCL".

  Details:

  -all databases use pfiles

  -access tnsping databases easily of ServerS1 or server Server2 ORCL

  -It worked correctly before the failover when the databases have opposing roles!

  I am lost, if someone can tell me where to drive my research, it would be very useful.

  Best regards.

  Eric

  I finally found and fix the problem.

  I discovered that dg_broker messages are followed in the footsteps of the dataguard instance directory (same as location of alert file) under the name of DRC.log

  In this file, I found messages like:

  [...]

  INSV: could not open the file of configuration "+ RECOVERY/ORCL/dgconfig/dgb_config02.ora".

  ORA-17503: ksfdopn:2 failed to open the file +RECOVERY/ORCL/dgconfig/dgb_config02.ora

  ORA-15173: entry 'dgb_config02.ora' does not exist in the directory "dgconfig.

  In fact, as I was deleting the files from dgb_config0*.ora through ASMCMD, I did not notice that I was also remove DGCONFIG directory.

  After creating the directory manually, everything is back to normal.

  Thanks for your time and support, in the hope that it will help someone someday...

• addition of relief in dataguard broker database fails

  When adding of Eve in dataguard broker database, I get the following error

  DGMGRL > add database as uat login is uat maintained as physical;

  Error: ORA-16698: parameter LOG_ARCHIVE_DEST_n defined for the object to add

  Failed.

  DGMGRL > output

  I deleted the log_archive_dest_2 parameter in the primary database and null value

  SQL > sho parameter log_archive_dest_1;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  Log_archive_dest_1 string LOCATION = USE_DB_RECOVERY_FILE_

  DEST = VALID_FOR (ALL_LOGFILES, A).

  LL_ROLES) DB_UNIQUE_NAME = prod

  SQL > sho parameter log_archive_dest_2;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  LOG_ARCHIVE_DEST_2 string

  log_archive_dest_20 string

  Can someone help me please

  vmkumar wrote:

  When adding of Eve in dataguard broker database, I get the following error

  DGMGRL > add database as uat login is uat maintained as physical;

  Error: ORA-16698: parameter LOG_ARCHIVE_DEST_n defined for the object to add

  Failed.

  DGMGRL > output

  I deleted the log_archive_dest_2 parameter in the primary database and null value

  SQL > sho parameter log_archive_dest_1;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  Log_archive_dest_1 string LOCATION = USE_DB_RECOVERY_FILE_

  DEST = VALID_FOR (ALL_LOGFILES, A).

  LL_ROLES) DB_UNIQUE_NAME = prod

  SQL > sho parameter log_archive_dest_2;

  VALUE OF TYPE NAME

  ------------------------------------ ----------- ------------------------------

  LOG_ARCHIVE_DEST_2 string

  log_archive_dest_20 string

  Can someone help me please

  What you have shown here is the log_archive_dest_2 of the primary database. You must clear the log_archive_dest_2 of the standby database too.

  The error is speaking on the parameter log_archive_dest_2 of the database pending. 12 c, then the broker configuration, you must clear the log_archive_dest_2 (destinations archive remote) on the primary and standby databases. DG broker would take care of her.

  On autonomy in standby:

  SQL > alter system set log_archive_dest_2 = ";

  And then try to add the standby database to the broker configuration.

  HTH

  -Jonathan Rolland

• DataGuard broker 11 GR 2 - StaticConnectIdentifier

  OK, I read that in 11 GR 2 you do have more to put in a static in your listener.ora with < SID > _DGMGRL file entry if you use the Dataguard Broker: StaticConnectIdentifier. I used this new setting, and it was automatically created to be:
  
  StaticConnectIdentifier = ' (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=DB1) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = prod_sb_DGMGRL) (INSTANCE_NAME = prod_sb)(SERVER=DEDICATED)))'
  
  My question is that there is no entry anywhere that specifies the SERVICE_NAME as prod_sb_DGMGRL. My passage to the work without SERVICE_NAME is not defined any where? Am I missing a step? Thank you people.

  Hello;

  I think that the digital switchover will fail with an ORA-12514. Without the listener.ora entry DGMGRL won't be able to connect to the databases once that they were arrested.

  You must therefore always the _DGMGRL or at least a static entry in the listener.ora. In any State to cause the static entry will not cause a problem.

  * Passage failed with ORA-12521 using Dataguard broker [1380949.1 ID] *.

  For more information, see - 8.3.40 StaticConnectIdentifier in "broker Data Guard 11 g Release 2 (11.2) E17023-04.

  "A connect identifier that refers to a service that is registered statically.

  Best regards

  mseberg

  Published by: mseberg on Sep 20, 2012 04:04

• Implementation of DataGuard broker errors

  Hello
  
  I'm creating Data Guard Broker and get these errors, hope you can help.
  
  My first (orcl) is opened up and watch (orcldg) is to read only State open air.
  
  I ran these on both of my primary node 2 RAC

  dgmgrl
  connect sys
  create configuration dg_tst as primary database is orcl connect identifier is orcl;
  add database orcldg as connect identifier is orcldg maintained as physical;
  exit;

  Then
  

  enable configuration;

  and now get after errors:
  

  DGMGRL> show database orcl;
  
  Database
    Name:            orcl
    Role:            PRIMARY
    Enabled:         YES
    Intended State:  ONLINE
    Instance(s):
      orcl1
  
  Current status for "orcl":
  Error: ORA-16810: multiple errors or warnings detected for the database
  
  
  DGMGRL> show database orcl statusreport;
  STATUS REPORT
         INSTANCE_NAME   SEVERITY ERROR_TEXT
                 orcl1      ERROR ORA-16736: unable to find the destination entry of standby database "orcldg" in V$ARCHIVE_DEST
                 orcl1    WARNING ORA-16714: the value of property ArchiveLagTarget is inconsistent with the database setting
                 orcl1    WARNING ORA-16714: the value of property LogArchiveTrace is inconsistent with the database setting
                 orcl1    WARNING ORA-16714: the value of property LogArchiveFormat is inconsistent with the database setting
                 orcl2      ERROR ORA-16532: Data Guard broker configuration does not exist
  
  DGMGRL> show database orcl LogXptStatus;
  Error: ORA-16777: unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  
  DGMGRL> 

  Hello

  I think that the main issue is due to the location of the configuration files broker is not set to the same common place at the primary level.

  Note: in the case of CCR, you must have broker configuration files on the shared location and definition of the DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 to the same values in all the nodes.

  Reference:

  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14230/configure.htm#i1021661

  Action plan
  =====
  ++ Disable broker on primary and standby
  ++ Configuration files drop existing broker on primary and standby
  ++ The value of DG_BROKER_CONFIG_FILE1 and DG_BROKER_CONFIG_FILE2 properly defined in the primary and standby
  ++ Select broker in the primary and standby
  ++ Create a broker again
  ++ Add Eve in configuration
  ++ Activate configuration

  Concerning
  Nathalie

• DataGuard broker not starting not not instances after passage in the

  I've implemented dataguard broker.
  
  Primary (Server1)
  
  instance name: test
  dbname: sf_test
  
  Standby (Server2)
  
  instance name: test
  DB: test
  
  I want to do the test from server2 as main and server1 sf_test as before.
  
  DGMGRL > switchover to test
  Continue to pass, please wait...
  Operation requires the stop of the instance 'test' on database 'sf_test '.
  Instance closing 'test '...
  ORA-01109: database is not open
  
  The database is dismounted.
  ORACLE instance stops.
  Operation requires the judgment of the instance 'test' on the 'test' database
  Instance closing 'test '...
  ORA-01109: database is not open
  
  The database is dismounted.
  ORACLE instance stops.
  Operation requires the start the instance 'test' on database 'sf_test '.
  Start the instance 'test '...
  Unable to connect to the database
  ORA-12514: TNS:listener is not currently of service requested in connect descriptor
  
  failed. You are no longer connected to ORACLE
  Please log in again.
  Could not start the instance 'test '.
  You must start the instance 'test' manually
  Operation requires the start the instance 'test' on the 'test' database
  You must start the instance 'test' manually
  Successful, the new principal is 'test '.
  DGMGRL > output

  Hello..

  Refer to Metalink Doc ID: Note: 308943.1 -automatic restart of databases over the failure of the transition to digital with ORA-12514 in DGMGRL

  >

  Cause:-the cause of this problem is that without the necessary entry listener.ora, DGMGRL is unable to connect to the databases once they were arrested during the failover operation.

  >

  [http://blogs.oracle.com/AlejandroVargas/gems/DataGuardBrokerandobserverst.pdf]

  Use Data Guard Broker?

  HTH
  Anand

  Published by: Anand... on November 1st, 2008 04:17:-added 2 links

• DataGuard-Dataguard broker

  Hello
  Dataguard automated recovery is dataguard broker is necessary?
  
  I disabled DGbroker but always mrp is underway.
  
  
  SQL > select OPEN_MODE, DATABASE_ROLE, DATAGUARD_BROKER, GUARD_STATUS from v$ database;
  
  OPEN_MODE DATABASE_ROLE DATAGUAR GUARD_S
  ---------- ---------------- -------- -------
  MOUNTED ON STANDBY PHYSICS DISABLED NO
  
  
  SQL > select PROCESS, STATUS, DELAY_MINS from v$ MANAGED_STANDBY;
  
  DELAY_MINS PROCESS STATUS
  --------- ------------ ----------
  CONNECTED ARCH 0
  CONNECTED ARCH 0
  CONNECTED ARCH 0
  CONNECTED ARCH 0
  CONNECTED ARCH 0
  MRP0 WAIT_FOR_LOG 0
  RFS RECEIVING 0
  RFS 0 HOME
  RFS 0 HOME
  RFS RECEIVING 0
  
  Can you please help understand this?
  
  Published by: 873341 on July 21, 2011 16:10

  If the DG broker is not enabled then the switch on doesnot take place.

  You must perform the failover manually.

  Another question.

  IS the DG and DR are the same.
  I have head that DR archives logs doesnot recovery takes place automatically. We must manually push .is this true?

  If it is ENTERPRISE Edition, so no need to copy archives manually, if you have configured properly everything is automated.

  DR - disaster recovery, how do you plan to recover from the loss of data and methods.
  DG - Dataguard (method)

• ORA-19815: WARNING (ORA-00257)

  Hello

  Environment:

  Virtual machine

  OS: Windows Server 2008 R2 64-bit (5 GB RAM) STD

  DB: Database Oracle 12 c (12.1.0.1.0) 64-bit Production

  Home Oracle: C:\

  Location of the archiving log. E:\

  The information in the log.xml:

  Errors in file C:\ORACLE\LINE3\diag\rdbms\line3\line3\trace\line3_arc0_3196.trc: ORA-19815: WARNING:

  db_recovery_file_dest_size 10737418240 bytes is 100.00% used and 0 bytes remaining available.

  is somewhat misleading, because there is enough space on the disk.

  See the recovery of parameter

  NAME

  TYPE

  VALUE

  -------------------------------------------------- ----------- -------------

  db_recovery_file_dest	string	E:\OraArchive
  db_recovery_file_dest_size	large whole 10G
  db_unrecoverable_scn_tracking	Boolean	TRUE
  recovery_parallelism	integer	0

  Select nom_dest, status, destination of V$ ARCHIVE_DEST

  When status = 'INVALID ';

  NOM_DEST

  STATUS

  DESTINATION

  ------------------ --------- -------------------------

  VALID LOG_ARCHIVE_DEST_1

  USE_DB_RECOVERY_FILE_DEST

  Select * from v$ flash_recovery_area_usage;

  TYPE_DE_FICHIER

  PERCENT_SPACE_USED

  PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES

  CON_ID

  ----------------------- ---------------------- ------------------------- ---------------------- ----------------------

  CONTROL FILE	0	0	0	0
  REDO LOG	0	0	0	0
  ARCHIVED JOURNAL	32.99	0	90	0
  BACKUP PIECE	0.17	0	1	0
  COPY OF THE IMAGE	0	0	0	0
  NEWSPAPER FLASHBACK	0	0	0	0
  ARCHIVED FOREIGN JOURNAL	0	0	0	0
  COPY OF DATA 0 AUXILIARY FILE	0	0	0

  8 selected lines

  RMAN retention policy

  CONFIGURE THE RMAN OUTPUT TO KEEP FOR 7 DAYS; # by default

  We have configured our system to remove all logs archived last 7 days to free up disk space. However, the log.xml always shows the same caveat.

  The database was also interrupted because of an ORA-00257.

  We would appreciate any suggestions to avoid the ORA-00257 error.

  Thank you!

  did you remove OS archivelogs, do not use rman, right?  Fox

  RMAN > overlap archivelog all;

  RMAN > delete all. expired archivelog

  RMAN > remove obsolete;

  If you delete your archive of OS, Oracle do not know that this archivelogs have been removed, then you have to overlap.

  Check also:

  The files being removed in the area of flash recovery, log messages in the alert removed Oracle managed file [1369341.1 ID]

• DataGuard Configuration problem / ORA-16047

  So last night I decided to set up a test of physical database paused. I had everything working properly and when I started to play with the Data Guard Broker I started having a few problems. Now I can't get the logs to be shipped from the primary to the day before.
  
  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/Linux

  First of all, I noticed a problem with a gap in the 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           39

  Here are the configuration on the primary information:
  

  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=dgdb1

  Sleep settings
  

  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     dgdb1

  So 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
  database

  The 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 above the DB_UNIQUE_NAME in the parameter LOG_ARCHIVE_DEST_2 to match that of the database pending.
  
  Also DG_BROKER_START is false on the back-end databases and relief.
  
  Finally, I deleted all the files DRC * the directory $ORACLE_HOME/dbs on primary servers and intelligence to make sure that the broker is not configured.
  
  Where am I wrong? How can I get the standby caught up and working properly again?
  
  I apologized if I missed something. I'm relatively new to databases in waiting.

  Centinul;

  I noticed a few things

  1. If you run the query below the sleep mode, you will probably always get the results you've posted

  SELECT sequence #, applied to the order of v$ archived_log by sequence #.

  What to do if run it from primary school and I add the "DEST_ID" column to the query.

  2. you may have more luck finding GAPS using these queries:

  Select max(sequence#) from v$ archived_log in case of application = 'YES ';

  Choose the process, status from v$ managed_standby;

  SELECT * FROM V$ ARCHIVE_GAP;

  3. you mix SQL result with data broker, which can bite you. You don't know where you went wrong, but I would create PFILE file versions before trying to broker data at both ends. You can view each setting and avoid problems before adding the data broker. Data broker will take control and you can even find that it adds entries to your settings file.

  The ORA-16047 is probably related database parameter and that should help at least answer the question. For example you might miss log_archive_config on the standby or soething. In comparing the two PFILE should refine this

  I checked my notes from data broker, but did not find an ORA-16047, ORA-01031, ORA-16675, ORA-12514 and ORA-16608, I managed.

  For me I decided it was a good idea to run Data Guard without data broker at first, until I got the impression using SQL.

  Finally if you have not already consider the purchase of Larry 'Oracle Data Guard 11g Handbook' Carpenter IMHO its worth every penny and more.

  Best regards

  mseberg

• DataGuard broker

  Gurus,
  
  My first CAR is "orcl_prim" n RAC Eve is "orcl_stdby" then
  connection to primary and running the commands below.
  
  for the stop
  DGMGRL > STATE of MODIFICATION of DATABASE ORCL_STDBY SET = offline.
  
  above dg takes command off mode of recovery and shutsdown the relief RAC database or just out of recovery mode takes and then I shall he sleep RAC srvctl stop?
  
  the same with the primary with primary
  DGMGRL > STATE of MODIFICATION of DATABASE ORCL_PRIM SET = offline.
  
  and to start
  
  DB primary CARS start with srvctl or the command, below is the Pb of cars?
  
  
  
  DGMRL > ALTER DATABASE ORCL_PRIM SET STATE = online;
  
  
  the startup (mount) command DG broker configuration ensures in phy below and put it into recovery mode?
  
  DGMGRL > ALTER DATABASE ORCL_STDBY SET STATE = online;
  
  
  
  The above steps are not? His confusion can someone let me know the exact steps to stop the primary and standby with dg broker.
  
  fact below command shutsdown the RAC database?
  
  elementary school:
  DGMGRL > SHUTDOWN
  
  standby:
  DGMGRL > stop
  
  What commands can I use to stop primary and standby in broker configuration gracefully.

  While you can use the broker to start and stop instances but with CARS, it is preferable to use srvctl.

  You don't need to change the sleep state or the primary before stopping, either. Account assignment is blocked on the standby srvctl stop this instance without any damage.

  Larry

• Database broker and dataguard Creaton of Eve

  Hi Experts,
  
  I use Linux with Oracle version 11 GR 2. We have plans to create a database of physical intelligence and also configure dataguard broker for the standby database.
  Also, I read the documents that active dataguard is a feature on 11g. It is not possible on 10g?
  
  Can someone give me please the steps to create the standby database and configure the dataguard broker.

  Hello

  Check this thread DR synchronize with primary

  Also, to check whether or not the managed recovery is underway on the standby database, run the following query:

  SQL > select process, status, sequence # from v$ managed_standby;

  If process columns is a value such as MRP, then the managed recovery is underway on the standby database.

  Hope this is clear.

• DG fails with ora-16532 / ora-16577

  Because my DBs are on a network disconnected, I can't copy and paste large quantities. Everything here is typical. Please be patient.

  Primary DB is EE 11.2.0.3.0 on RHEL 5.1 and running on the file (no - ASM) system.

  DB pending is EE 11.2.0.4.0 OEL 6.4 and running on ASM.

  I perform RMAN DUPLICATE ACTIVE without error. I have run the following SQL queries on the instance of relief:

  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
  
  ALTER SESSION SET nls_date_format='DD-MON-YYYY HH24:MI:SS';
  
  select database_role,protection_mode from v$database;
  DATABASE_ROLE      -     PROTECTION_MODE
  PHYSICAL STANDBY   -     MAXIMUM PERFORMANCE
  
  SELECT sequence#, first_time, next_time, applied
  FROM   v$archived_log ORDER BY sequence#;
  
  
  
  

  I compare v$ archived_log against primary. Everything transferred and applied. Life is good. I am surprised, I did not met all the problems again! Maybe I really became a good DBA now! Now all I do is turn on Data Guard.

  I have set up my caller on hold. Notable entries are below.

  ...

  (SID_DESC =
  (SDU = 32767)
  (GLOBAL_DBNAME = acme2_DGMGRL)
  (ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_home1)
  (ENVS="TNS_ADMIN=/u01/app/oracle/product/11.2.0/grid/network/admin")
  (SERVER = DEDICATED)
  (SID_NAME = acme2)
  )
  (SID_DESC =
  (SDU = 32767)
  (GLOBAL_DBNAME = acme2_DGB)
  (ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_home1)
  (ENVS="TNS_ADMIN=/u01/app/oracle/product/11.2.0/grid/network/admin")
  (SERVER = DEDICATED)
  (SID_NAME = acme2)
  )
  
  DYNAMIC_REGISTRATION_LISTENER_ACME2=OFF
  
  
  
  

  Because dynamic registration is disabled, I have generated statically _DGB above entry. I understand that ENVS is not strictly necessary, however, I have included to exclude errors. I'm sure some additional settings are properly configured.

  Elementary school:

  show parameter log_archive
  log_archive_config:  'dg_config=(acme,acme2)'
  log_archive_dest_1:  LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=acme
  log_archive_dest_2:  SERVICE=acme2 SYNC AFFIRM reopen=15 NET_TIMEOUT=15 DB_UNIQUE_NAME=acme2 VALID_FOR=(online_logfiles,primary_role) 
  
  
  
  

  Standby:

  show parameter log_archive
  log_archive_config:  'dg_config=(acme2,acme)'
  log_archive_dest_1:  LOCATION=USE_DB_RECOVERY_FILE_DEST
  log_archive_dest_2:  SERVICE=acme AFFIRM SYNC VALID_FOR=(online_logfiles,primary_role) DB_UNIQUE_NAME=acme
  
  
  
  

  I check on the primary:

  show parameter dg_broker
  NAME      -  VALUE
  dg_broker_config_file1 - /u02/app/oracle/fra/dr1acme.dat
  dg_broker_config_file2 - /u02/app/oracle/fra/dr2acme.dat
  dg_broker_true         - TRUE
  
  

  I put and check that the sleep settings:

  show parameter dg_broker
  NAME      -  VALUE
  dg_broker_config_file1 - +DATA/acme2/broker/dr1acme.dat
  dg_broker_config_file2 - +FRA/acme2/broker/dr2acme.dat
  dg_broker_true         - TRUE
  
  
  

  I'm going to the ASMCMD from the night before and make the directories above.

  Elementary school:

  dgmgrl
  connect sys/mypassword
  Connected.
  add database acme2 as connect identifier is acme2 maintained as physical;
  
  
  
  

  He adds very well. It is part of the configuration, but disabled. In the listener from sleep log, I see that the primary is a successful connection to the service 'acme2'.

  show database verbose acme2 (I only typed relevant properties...ask for more if need be)
  DGConnectIdentifier = 'acme2'
  LogXptMode = 'SYNC'
  Standbyfilemanagement = 'AUTO'
  DbFileNameConvert = '/u02/app/oracle, +DATA, /u03/app/oracle, +DATA'
  LogFileNameConvert = '/u02/app/oracle, +FRA, /u03/app/oracle, +FRA'
  StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(host=mystandbyhost)(port=1521))(CONNECT_DATA=(SERVICE_NAME=acme2_DGMGRL)(INSTANCE_NAME=acme)(SERVER=DEDICATED)))'
  StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
  
  Database Status:
  DISABLED
  
  
  
  

  Just to double check, I use my DGMGRL Standby to try to connect to the primary DGMGRL with "sys/mypassword". Success! I can view primary DGMGRL configuration of the previous day. I have then copy and paste the "StaticConnectIdentifier" above in my primary tnsnames.ora file and create a temporary entry of TNS. I then try to tnsping this entry temp. All right. I have remove the temporary entry and return to DGMGRL. Everything went perfectly. Finally, I check the file of newspaper DG on the eve. The last line is "Configuration does not exist, Data Guard Broker loan", which is exactly what I expected to see at this stage. Can now do better?

  Elementary school:

  dgmgrl
  connect sys/mypassword
  Connected.
  enable database acme2;
  
  
  
  

  .. and so my long nightmare starts. Custody of intelligence data does not work.

  On logs waiting for DG, I see these errors for a while, but then they disappear:

  drcx: cannot open configuration file "+DATA/acme2/broker/dr1acme.dat"
  
  
  
  

  What makes the sense that they have not been copied yet. After a minute, I check the DATA + and + FRA starts on the eve and two config DG files have transferred and is where they should be. Ok. I check the database of pending log file. Only standard archived journal entries (files are always transferred from the primary school outside of Data Guard). I check ADRCI on intelligence. There are no problems or incidents.

  On the primary level, there is no problem or incident at the ADRCI and errors will only find is in the DG log file. They are:

  Broker Initiated ENABLE of site acme2 has been scheduled
  Data Guard Broker Status Summary:
  Type                 --       Name           --            Severity  --   Status
  Configuration                 DG_ACME_CONFIG       warning       ora-16607
  Primary DB                   acme                           success       ora-00000
  Physical Standby DB        acme2                         error         ora-16532
  
  ENABLE DATABASE acme2
  Metadata Resync failed. Status = ora-16577
  
  Command ENABLE DATABASE acme2 completed
  
  
  
  

  The error is repeated continually as main tent contact the broker ensures DG. I have check the earphone standby log file. I see that primary is connected to the local 'acme2_DGB' about once every minute, right mark. It is to achieve the TNS service, but the TNS service does not meets with the local broker.

  On the Pb of the day before, I run

  SQL> select process,client_process,status from v$managed_standby;
  
  
  
  

  PROCESS of	CLIENT_PROCESS	STATUS
  ARCH	ARCH	CLOSING
  ARCH	ARCH	CLOSING
  ARCH	ARCH	CONNECTED
  ARCH	ARCH	CLOSING
  RFS	ARCH	IDLE
  RFS	UNKNOWN	IDLE
  RFS	LGWR	IDLE

  SELECT THE MESSAGE FROM V$ DATAGUARD_STATUS; shows nothing useful (transfers archive standard only).

  
  I've completely removed the DG configuration on all the boxes, removed the DG config files and completely recreated the configuration several times. In fact, I completely rebuilt the standby database DG twice. In addition, accelerated failover is disabled on the configuration of the DG.

  I tried everything I can think and find online. I would be very happy any idea on this issue that the community has to offer.

  Hello

  I do not use DG with broker but I want to ask something. I couldn't see the values of the parameters compatible on both sides. You know that the values must be the same on all the databases in a dataguard configuration.

  Primary DB is EE 11.2.0.3.0 on RHEL 5.1 and running on the file (no - ASM) system.

  DB pending is EE 11.2.0.4.0 OEL 6.4 and running on ASM.

  Best regards

• Passage of Oracle Dataguard and DNS

  Hi, a few days ago, we planned a passage in a configuration of 10g dataguard (dataguard pasive) between the 2 servers.

  primary: Europe.com APP

  secondary: APP1 in Asia.com

  The two databases was Oracle 10.2.0.3 in Redhat (single instance)

  Everything is going well with databases and the digital switchover but what happened with the web-based applications?

  I have a lot of web PHP applicattion provided with a string of connection with OIC and oracle customer, all have the connection as user/pass@dbname where dbname is defined in the local tnsnames.ora with DNS host names.

  (All have xxx/xxx@APP), and was APP (host:europe.com and SID = APP)

  Europe.com was ip 1.1.1.1

  Asia.com has been ip 2.2.2.2

  My primary instance was APP (name sid) and the standby APP1 (name sid) but what happened when I pass the dataguard?

  Yes, because we have a lot of requests and we don t change the connection string, each of them tries to connect to the new basis of Eve physics APP which is in Europe.com. (and the main news is APP1 in Asia.com)

  Well, first of all, I must change the SID in the database (same as the primary database) waiting for the connection string, for which I have: (thus development are don't want to change the string of connection...)

  (1) immediate stop aid database

  (2) remove the dataguard broker configuration,

  (3) change the instance name in the spfile APP1 to APP.

  (4) change the name of db in the spfile APP1 to APP.

  (5) change the setting fal_client (INSTANCE_NAME = APP1) to (INSTANCE_NAME = APP)

  (6) change the app APP1 orapwd file

  (7) Exchange configuration bash_profile APP and re start the database pending.

  (8) check the listener.ora, so that the new listening service is APP and no APP1

  (8) with respect to the dataguard broker configuration config

  OK, everything works very well and we have the main and the database pending with the same SID.

  But what happened with the dns servers? because the web-based applications will try to connect to APP but APP has been defined as Europe.com and I want to redirect Asia.com as primary database.

  Well, first of all, I changed all my settings and broker dataguard over IP and not dns configuration files, so I made a guide to procedure for the passage to the then when we said that, first we must transition to digital, data bases and then the surface NET must change the DNS for new Europe.com dns point to 2.2.2.2 ip

  After that, everything works great!

  So in conclusion, to forward a permutation with dataguard (which was an excellent feature) check the connection of the chain of applications and take care of them) and if necessary, use the same SID for the two (databases) and emergency

  (In Oracle 12 c, we have a lot of thing to use as a continuation of the app for that)

  Kind regards

  Hernan

  Hi Herman,.

  Maybe I'm mistaken, please correct me if this is the case.

  Assuming you are using oracle customer why not just use the construction in the mechanism for this purpose? DNS has nothing to do with it, but I see people using it yet for this - it is not only suitable for failovers, I do not have my TTL of 60 seconds or less to my recordings of A.

  I had a project for banking HA where after permutation is launched the application (Tomcat) could in a minute to connect automatically to the database of watch on the Internet. First, you must use the database instead of SID service, so you can have the same service on the previous day. What more have a service, you can be sure that it will run the day before until it becomes primary, otherwise you can find yourself in a funny situation. Secondly, why not using built in failover of the connection string parameter, this way you can queue db (s) and in the case where your primary does not that the oracle client will simply try to connect to the waiting (to search for the same service). To ensure that the standby database does not have the service at any time, you can deploy trigger (AFTER startup) to check the role of database, if it is 'primary' it starts just the database service.

  Kind regards

  EVS

• primary DB in the role of Eve with ORA-16816: incorrect database role

  We have two node RAC of Primary (oraqa) as well as two-node RAC Physicalstandby (orasqa) managed by dataguard broker. Start quick active failover.  Version of the database is 11.2.0.3. OS is Redhat 5.3

  There are a few days, our primary oraqa switched to orasqa by fast-start failover, and I couldn't get the passage from some network problem.

  Today, the network number, and I want to the transition to the orasqa to oraqa.

  However, I got this error:

  ORA-16816: incorrect database role

  a check for database_role in v$ database at orasqa shows that it is read only physical role of Eve.

  So now the two oraqa/orasqa are in the physical database role.

  How can I solve this problem?

  Help is very appreciated.

  Note that in his note, where it is a:

  change the database for validation at the grade crossing;

  This is the step where it converts the physics of the day before in a primary. So I would try to convert the database that was recently in primary mode at the elementary level. If this works, you need to do several switches of newspaper and make sure you have Data Guard work system before retrying the switch.

  
  

  I had this happen without a broker and you end up with what amounts to two standbys. "change database validation at the primary crossing" in kind of a way to double back to where you started.

  If this gives you more trouble, I'd get Oracle support help as soon as POSSIBLE.

  Another way to look at

  If you were doing this with SQL the brief summary can be:

  On primary

  1. check switchover_status

  2. commit to failover to standby database

  3 stop of the database and the Mont as new mode standby

  4 reporter the destination of archive remote

  At this point, you have in fact two standbys and zero primary.

  If your switchover_status gives a wrong answer, you need to return the primary.

  So rather than place orders to the other server, you continue on the same server, a double return and you convert to what was again the primary back to a primary.

  Then you trouble shoot the issue and try again.

  If you use a broker I would not use SQL unless Oracle Support told me to mix of SQL and broker is a bad idea.

  Best regards

  mseberg