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 : 27-04-2017
ORA-12212

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

  • ora-26711 : remote table does not contain a primary key constraint
  • ora-01932 : ADMIN option not granted for role 'string'
  • ora-16172 : archive logs detected beyond Terminal End-Of-Redo
  • ora-26697 : LCR contains extra column 'string'
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-25105 : RECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-38464 : expression set is not empty.
  • ora-27018 : BLKSIZE is not a multiple of the minimum physical block size
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-26077 : direct path column array is not initialized
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-27162 : thread creation failed
  • ora-27039 : create file failed, file size limit reached
  • ora-12003 : materialized view "string"."string" does not exist
  • ora-14004 : missing PARTITION keyword
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-07494 : scgcm: unexpected error.
  • ora-22327 : cannot change a type to NOT INSTANTIABLE if it has dependent tables
  • ora-19243 : XQ0023 - invalid document node content in element constructor
  • ora-13020 : coordinate is NULL
  • ora-01623 : log string is current log for instance string (thread string) - cannot drop
  • ora-06779 : TLI Driver: error reading ccode
  • ora-04080 : trigger 'string' does not exist
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-39219 : directory object name is too long
  • ora-01479 : last character in the buffer is not Null
  • ora-04932 : increment or adjust of sequence number failed
  • ora-13783 : invalid tuning scope
  • ora-16559 : out of memory at string
  • ora-39218 : type check on object type "string"."string" failed
  • 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.