Data Guard Configuration Issue / ORA-16047

Question

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.

Answer 1

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