Problem in setting archive destination for standby database

[ranvijai]

Database version:10.2.0.1.0

I am getting problem when i am trying to set log archive destination for standby database which is in the same system.

The following parameter is set in parameter file:

log_archive_config='dg_config=(primary,phstandby)'
log_archive_dest_1='LOCATION=f:\oracle\primaryarch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=primary'
log_archive_dest_2='LOCATION=f:\oracle\standbyarch VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=phstandby'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
FAL_SERVER=primary
FAL_CLIENT=phstandby
DB_FILE_NAME_CONVERT='f:\oracle\oradata\PRIMARY','f:\oracle\oradata\STANDBY'
LOG_FILE_NAME_CONVERT='f:\oracle\primaryarch,'f:\oracle\standbyarch'
STANDBY_FILE_MANAGEMENT=AUTO

The archive list command shows online single archive location:

SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination f:\oracle\primaryarch
Oldest online log sequence 27
Next log sequence to archive 29
Current log sequence 29

Output from v$archive_dest_status:
SQL> select dest_id,dest_name,status,error,type,database_mode from v$archive_dest_status;

DEST_ID DEST_NAME STATUS ERROR TYPE DATABASE_MODE
---------- ---------- --------- ---------- -------------- ---------------
1 LOG_ARCHIV VALID LOCAL OPEN
E_DEST_1

2 LOG_ARCHIV BAD PARAM ORA-16053: LOCAL OPEN
E_DEST_2 DB_UNIQUE_
NAME is
not in the
Data Guard
Configurat
ion
Please help me due to this problem i am not able to start standby database.Thanks in advance.

[LKBrwn_DBA]

Oracle Error :: ORA-16053
DB_UNIQUE_NAME string is not in the Data Guard Configuration

Cause
The specified DB_UNIQUE_NAME is not in the Data Guard Configuration.

Action
If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter is enabled, you must specify a valid DB_UNIQUE_NAME. The list of valid DB_UNIQUE_NAMEs can be seen with the V$DATAGUARD_CONFIG view. This problem can also occur when specifying a non-standby destination with an DB_UNIQUE_NAME attribute that does not match the DB_UNIQUE_NAME initialization parameter for the current instance.