ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

Cause : The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file does not have a CMANAGER_NAME specified.

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

Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error.

update : 20-08-2017

ORA-12212 - TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
ORA-12212 - TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA

  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-28153 : Invalid client initial role specified: 'string'
  • ora-06775 : TLI Driver: error reading break mode
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • ora-27212 : some entrypoints in Media Management Library are missing
  • ora-02453 : duplicate HASH IS specification
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-06534 : Cannot access Serially Reusable package string
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-16203 : Unable to interpret skip procedure return values
  • ora-07627 : smsfre: $CRETVA failure
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-13600 : error encountered in Advisor string
  • ora-16700 : the standby database has diverged from the primary database
  • ora-25157 : Specified block size string is not valid
  • ora-30135 : OCI Thread operation fails
  • ora-10920 : Cannot offline tablespace belonging to default temporary tablespace group
  • ora-32404 : snapshot log uses Change Data Capture which is not enabled for this database
  • ora-02090 : network error: attempted callback+passthru
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-31057 : Display Name of the element being inserted is null
  • ora-24237 : object id argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-32134 : Cannot assign LOBs
  • ora-13699 : Advisor feature is not currently implemented.
  • ora-14625 : subpartition contains rows corresponding to values being dropped
  • ora-12556 : TNS:no caller
  • ora-39950 : invalid parameter for PLSQL warnings flag
  • ora-22980 : must specify a set of attributes for the WITH OBJECT OID clause
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-01925 : maximum of string enabled roles exceeded
  • 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.