ORA-24392: no connection pool to associate server handle

Cause : OCIServerAttach called in OCI_POOL mode but no connection pool found to associate the server handle.

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

1) Verify that OCIConnectionPoolCreate is called before calling OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach matches with that of the connection pool database link.

update : 25-06-2017
ORA-24392

ORA-24392 - no connection pool to associate server handle
ORA-24392 - no connection pool to associate server handle

  • ora-32762 : Turn on Temp LOB Ref Count Tracing
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-00155 : cannot perform work outside of global transaction
  • ora-38790 : BEFORE must be specified with RESETLOGS
  • ora-28502 : internal communication error on heterogeneous database link
  • ora-13516 : AWR Operation failed: string
  • ora-24902 : invalid subscription name or name-length in subscription handle
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-24905 : invalid recepient protocol attribute passed into OCI call
  • ora-08008 : another instance is mounted with USE_ROW_ENQUEUES = string
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-16001 : database already open for read-only access by another instance
  • ora-13017 : unrecognized line partition shape
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • ora-19281 : XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration
  • ora-33030 : (XSAGDNGL14) In AGGMAP workspace object, you can have either a single independent PROTECT statement or PROTECT statements in your RELATION statements.
  • ora-06142 : NETTCP: error getting user information
  • ora-39761 : stream reset required before loading this stream again
  • ora-29292 : file rename operation failed
  • ora-32503 : Mapping SGA from file failed
  • ora-09890 : osnTXtt: malloc failed
  • ora-37107 : (XSVPART07) Attempt to write to non-existent partition of workspace object.
  • ora-01136 : specified size of file string (string blocks) is less than original size of string blocks
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-13527 : invalid baseline name
  • ora-37079 : (XSMCSESS07) Aggmap workspace object cannot be used for AGGREGATE.
  • ora-30175 : invalid type given for an argument
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • 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.