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

Cause : The PERFERRE_DCMANAEGRS bidning i nthe cilent'sT NSNAVO.RA fiel doesn ot haev an ADDRESS psecifide.

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

Defin ethe ADDRESS sa parto f theP REFERERD_CMAANGERS ibnding.

update : 29-04-2017

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

  • ora-31419 : source table string does not exist
  • ora-07740 : slemop: incorrect handle size (programming error)
  • ora-29307 : datafile string error, string
  • ora-06960 : Failed to access log file
  • ora-06262 : NETNTT: nfconn() failed
  • ora-31070 : Invalid database user ID string
  • ora-12562 : TNS:bad global handle
  • ora-06267 : NETNTT: bad state
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-00721 : changes by release string cannot be used by release string
  • ora-16206 : database already configured as Logical Standby database
  • ora-08102 : index key not found, obj# string, file string, block string (string)
  • ora-19960 : Internal use only
  • ora-08209 : scngrs: SCN not yet initialized
  • ora-31645 : unable to read from dump file "string"
  • ora-12611 : TNS:operation is not portable
  • ora-00257 : archiver error. Connect internal only, until freed.
  • ora-01680 : unable to extend LOB segment by string in tablespace string
  • ora-23406 : insufficient privileges on user "string"
  • ora-25213 : message with specified RELATIVE_MSGID has been dequeued
  • ora-29707 : inconsistent value string for initialization parameter string with other instances
  • ora-23373 : object group "string"."string" does not exist
  • ora-02784 : Invalid shared memory ID specified
  • ora-09940 : ORACLE password file header is corrupt
  • ora-30687 : session terminated by debugger
  • ora-08445 : syntax error in SIGN clause in mask options
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-29381 : plan/consumer_group string referred to by another plan and cannot be deleted
  • ora-14303 : partitions or subpartitions are not in the right order
  • ora-31480 : staging database and source database cannot be the same
  • 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.