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 : 20-08-2017
ORA-12213

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

  • ora-13910 : Parameter string cannot be NULL.
  • ora-07746 : slemrd: invalid error message file handle
  • ora-26650 : %s background process string might not be started successfully
  • ora-15163 : cluster not in rolling downgrade
  • ora-08460 : invalid environment clause in environment parameter
  • ora-00123 : idle public server terminating
  • ora-14172 : invalid ALTER TABLE EXCHANGE SUBPARTITION option
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-24180 : invalid transformation expression, the transformation expression does not evaluate to the target type/attribute
  • ora-13021 : element not continuous
  • ora-26709 : Streams RFS restart
  • ora-26680 : object type not supported
  • ora-12434 : invalid audit type: string
  • ora-13626 : The specified object string is not valid for task string.
  • ora-06710 : TLI Driver: send interrupt break message failed
  • ora-16648 : a new observer registered with identifier string
  • ora-36718 : (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
  • ora-13606 : the specified task parameter element string is out of range for parameter string.
  • ora-28101 : policy already exists
  • ora-28005 : invalid logon flags
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-13633 : The task string was interrupted and needs to be resumed.
  • ora-38744 : file string is not the same file seen at start of flashback
  • ora-02241 : must of form EXTENTS (FILE BLOCK SIZE , ...)
  • ora-30452 : cannot compute AVG(X), VARIANCE(X) or STDDEV(X), without COUNT(X) or SUM(X)
  • ora-36834 : (XSLMGEN04) Column tag is greater than 30 bytes
  • ora-14266 : data type or length of an index subpartitioning column may not be changed
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-19577 : file string is MISSING
  • 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.