Friday, August 23, 2013

ORA-16033: parameter LOG_ARCHIVE_DEST_1 destination cannot be the same as


##########################
## Error
##########################

ORA-16033: parameter LOG_ARCHIVE_DEST_1 destination cannot be the same as

### Full Error

Alter system set log_archive_dest_1="location=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stdby";

*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-16033: parameter LOG_ARCHIVE_DEST_1 destination cannot be the same as
parameter LOG_ARCHIVE_DEST_4 destination

##########################
#  Error Occurred
##########################

Error occured while trying to modify log_archive_dest_1 parameter to resolve archive gaps issue in our standby database

##########################
## Command Executed
##########################

In Sqlplus,

Alter system set log_archive_dest_1="location=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stdby";


##########################
## Issue Description.
##########################

###

Error occurred because, there is already a destination  defined with the same physical location. so we need to define a new value.

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_4                   string      LOCATION=USE_DB_RECOVERY_FILE_
                                                 DEST VALID_FOR=(ALL_LOGFILES,A
                                                 LL_ROLES) DB_UNIQUE_NAME=stdby

##########################
## Solution
##########################

Either change the value for LOG_ARCHIVE_DEST_4 to a different path or reset LOG_ARCHIVE_DEST_1 to a different value.

Alter system set log_archive_dest_4="location=/u01/app/oracle/11upgrade/stdby/rman_standby VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stdby";

5 comments:

Aldar Tsengeljav said...

pls help me , icant log in sqlplus with startup; oracle not available , error msg = ora-16033 , pls

Sri said...


Hi Aldar,

Please post the full output which you got from sqlplus.

If possible attach

1) screenshot of your error
2) database alert log file

and send it across to my email ( stepintooracledba@gmail.com )

Once you sent an email, kindly comment in this post. I will take a look and try to resolve your issue.

Aldar Tsengeljav said...

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup mount ;
ORA-16033: parameter LOG_ARCHIVE_DEST_3 destination cannot be the same as parameter LOG_ARCHIVE_DEST_1 destination
SQL>

Aldar Tsengeljav said...

i can connect with init.ora file to use this command SQL> startup pfile=/u01/app/oracle/admin/uccsdb2/pfile/init.ora.912013185639;
but alter system set log_archive_dest_1='LOCATION=/bkp/aldar' ; after shutdown , it was same , pls help me

Sri said...


Aldar,

Looks like when you give "startup mount" it tries to start the instance from spfile.

Please try the below steps,

1) Create a new pfile

sqlplus / as sysdba

Create pfile='/tmp/initdb.ora' from spfile;

2) Now open the initdb.ora file and check the below parameters,

log_archive_dest_1
log_archive_dest_3

3) Make sure both the values are different, if its same then modify it for different values.

4) Take a backup of spfile before proceeding with below step

5) Create spfile from pfile='/tmp/initdb.ora';

6) now startup the instance

startup

Note : Please take a backup of init and spfile before making any changes and also try this in test environment first.