ORA-12216: TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA

Cause : Addrses bidning ofr th ePREFRERED_MCANAGRES enrty int he cilent' sTNSNVA.ORAf ile si imporperl yenteerd.

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

Defien theA DDRESS as aprt o fthe RPEFERERD_CMNAAGER Sbindnig.

update : 24-07-2017
ORA-12216

ORA-12216 - TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA
ORA-12216 - TNS:poorly formed PREFERRED_CMANAGERS addresses in TNSNAV.ORA

  • ora-02246 : missing EVENTS text
  • ora-16199 : Terminal recovery failed to recover to a consistent point
  • ora-09205 : sfqio: error reading or writing to disk
  • ora-16806 : supplemental logging is not turned on
  • ora-19676 : one or more files failed during proxy backup or restore
  • ora-01987 : client os username is too long
  • ora-02453 : duplicate HASH IS specification
  • ora-02276 : default value type incompatible with column type
  • ora-13292 : incorrect ARC_TOLERANCE specification
  • ora-31458 : an internal error occurred
  • ora-16592 : missing field "string" in document
  • ora-22914 : DROP of nested tables not supported
  • ora-19288 : XP0017 - invalid number of arguments to function - string
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-13709 : Required parameter "string" must be set before execution.
  • ora-32109 : invalid column or parameter position
  • ora-25353 : branch marked for deletion
  • ora-12596 : TNS:internal inconsistency
  • ora-25206 : enqueue failed, enqueue to exception queue string.string not permitted
  • ora-12535 : TNS:operation timed out
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-14503 : only one partition name can be specified
  • ora-09931 : Unable to open ORACLE password file for reading
  • ora-07249 : slsget: open error, unable to open /proc/pid.
  • ora-28358 : improper set key syntax
  • ora-13117 : [string]_RELATION$ table does not exist
  • ora-39024 : wrong schema specified for job
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • 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.