ORA-16030: session specific change requires a LOG_ARCHIVE_DEST_n destination

Cause : The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION command.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1...10) parameters.

update : 26-04-2017

ORA-16030 - session specific change requires a LOG_ARCHIVE_DEST_n destination
ORA-16030 - session specific change requires a LOG_ARCHIVE_DEST_n destination

  • ora-04069 : cannot drop or replace a library with table dependents
  • ora-01039 : insufficient privileges on underlying objects of the view
  • ora-01116 : error in opening database file string
  • ora-02850 : File is closed
  • ora-29830 : operator does not exist
  • ora-30359 : Query rewrite is not supported on SYS materialized views
  • ora-13423 : invalid cell coordinate parameter
  • ora-28010 : cannot expire external or global accounts
  • ora-03261 : the tablespace string has only one file
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-00033 : current session has empty migration password
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-16204 : DDL successfully applied
  • ora-10371 : disable TQ hint
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-19602 : cannot backup or copy active file in NOARCHIVELOG mode
  • ora-13016 : specified topology [string] is invalid
  • ora-00264 : no recovery required
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-06021 : NETASY: connect failed
  • ora-28528 : Heterogeneous Services datatype conversion error
  • ora-12439 : invalid combination of policy options
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • ora-37073 : (XSMCSESS01) Applied relation workspace object must be dimensioned by dimension workspace object.
  • ora-24374 : define not done before fetch or execute and fetch
  • ora-23533 : object "string"."string" can not be cached
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-02095 : specified initialization parameter cannot be modified
  • ora-08413 : invalid compiler type in FORMAT parameter at string
  • ora-13900 : missing or invalid parameter string
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.