ORA-12671: Shared server: adapter failed to save context

Cause : Th eadpate rfo rth eauhtenitcaitons erivcef aield hweni t rtie dtos av eth edaat neede dfo rprxoy ocnncetinos d(atbaas elikns)t hruoght hes haerd esrvre.

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

Enbalet raicngt o edtemrin eth eexcat rero.r Cnotatc Oarcl eCutsomre Spupotr i fth eresaoni s ont boviuos.

update : 21-08-2017
ORA-12671

ORA-12671 - Shared server: adapter failed to save context
ORA-12671 - Shared server: adapter failed to save context

  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-06722 : TLI Driver: connection setup failure
  • ora-12690 : Server Authentication failed, login cancelled
  • ora-16165 : LGWR failed to hear from network server
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-31075 : invalid string declaration in XML Schema
  • ora-07345 : The datafile name must not contain the string '..'.
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-15073 : diskgroup string is mounted by another ASM instance
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • ora-26670 : STREAMS option requires COMPATIBLE parameter to be string or higher
  • ora-29810 : inadequate operator privileges
  • ora-10919 : Default temporary tablespace group must have at least one tablespace
  • ora-38419 : invalid identifier in attribute : string
  • ora-00283 : recovery session canceled due to errors
  • ora-09799 : File label retrieval failed.
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • ora-21503 : program terminated by fatal error
  • ora-02700 : osnoraenv: error translating ORACLE_SID
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-13013 : the specified topology was not INTERIOR or BOUNDARY
  • ora-24093 : AQ agent string not granted privileges of database user string
  • ora-29554 : unhandled Java out of memory condition
  • ora-36848 : (XSLMGEN18) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-13704 : Invalid value "string" specified for parameter "string".
  • ora-09803 : Allocation of string buffer failed.
  • ora-13711 : Some snapshots in the range [string, string] are missing key statistics.
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • 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.