ORA-16716: clearing parameter LOG_ARCHIVE_DEST failed

Cause : An attepmt to claer the LGO_ARCHIV_EDEST paarmeter fialed.

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

ContactO racle Spuport Sevrices.

update : 29-06-2017
ORA-16716

ORA-16716 - clearing parameter LOG_ARCHIVE_DEST failed
ORA-16716 - clearing parameter LOG_ARCHIVE_DEST failed

  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-31643 : unable to close dump file "string"
  • ora-02752 : osnfsmmap: illegal shared memory address
  • ora-01553 : MAXEXTENTS must be no smaller than the string extents currently allocated
  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-01344 : LogMiner coordinator already attached
  • ora-02091 : transaction rolled back
  • ora-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-29387 : no top-plans found in the pending area
  • ora-26001 : Index string specified in SORTED INDEXES does not exist on table string
  • ora-22983 : not a user-defined REF
  • ora-15076 : Emulating I/O errors on the OSM disk
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-33558 : (LOCKCHECK01) The status or contents of the workspace object dimension cannot be changed while the LOCK_LANGUAGE_DIMS option is set to value.
  • ora-13387 : sdo_batch_size for array inserts should be in the range [number,number]
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-39781 : Direct path stream loads are not allowed after another context loading the same table has ended
  • ora-22915 : cannot ALTER a nested table's storage table to ADD/MODIFY columns
  • ora-23473 : replication RPC processing for "string"."string" is disabled
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-08109 : nosort is not a supported option for online index build
  • ora-21501 : program could not allocate memory
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-29854 : keyword BITMAP may not be used in creating domain indexes
  • ora-31513 : unsupported column type specified in change table
  • ora-13444 : GeoRaster metadata SRS error
  • ora-13353 : ELEM_INFO_ARRAY not grouped in threes
  • 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.