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 : 17-08-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-10854 : Sets poll count used for AQ listen code under RAC
  • ora-16558 : the database specified for switchover is not a standby database
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-02771 : Illegal request time out value
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-16717 : clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-02703 : osnpopipe: pipe creation failed
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-25443 : duplicate column value for table alias: string, column number: string
  • ora-03247 : Invalid block number specified
  • ora-24056 : internal inconsistency for QUEUE string and destination string
  • ora-31600 : invalid input value string for parameter string in function string
  • ora-13371 : invalid position of measure dimension
  • ora-31526 : could not find source table string.string for CDC change table string.string
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-12453 : label string already exists
  • ora-29513 : referenced class name too long
  • ora-16105 : Logical Standby is already running in background
  • ora-23397 : global name "string" does not match database link name "string"
  • ora-13151 : failed to remove exception record
  • ora-30942 : XML Schema Evolution error for schema 'string' table string column 'string'
  • ora-26053 : Row was not loaded due to conversion error.
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-01084 : invalid argument in OCI call
  • ora-02221 : invalid MAXEXTENTS storage option value
  • ora-25438 : invalid variable name: string
  • ora-08443 : syntax error in BLANK WHEN ZERO clause in mask options
  • 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.