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 : 23-05-2017

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

  • ora-01237 : cannot extend datafile string
  • ora-14188 : sub-partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-29662 : Unable to find a field that matches one or more of the attributes
  • ora-21700 : object does not exist or is marked for delete
  • ora-26055 : Invalid buffer specified for direct path unload
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-13482 : GeoRaster object is not initialized for the image
  • ora-13192 : failed to read number of element rows
  • ora-08330 : Printing not supported
  • ora-25120 : MINIMUM EXTENT option already specified
  • ora-31416 : invalid SOURCE_COLMAP value
  • ora-27034 : maximum length of ORACLE_SID exceeded
  • ora-00268 : specified log file does not exist 'string'
  • ora-00279 : change string generated at string needed for thread string
  • ora-16802 : downgrading redo transport mode from SYNC disallowed
  • ora-06813 : TLI Driver: the configured ethernet address is incorrect
  • ora-31155 : attribute string not in XDB namespace
  • ora-07591 : spdde: $GETJPIW failure
  • ora-13779 : invalid load option
  • ora-24292 : no more tables permitted in this sorted hash cluster
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-40104 : invalid training data for model build
  • ora-25406 : could not generate a connect address
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-09741 : spwat: error waiting for a post.
  • ora-16192 : Primary and standby network integrity mismatch
  • ora-01588 : must use RESETLOGS option for database open
  • ora-25279 : dequeue as select not supported before 8.2
  • ora-23321 : Pipename may not be null
  • 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.