ORA-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA

Cause : Therei s a snytax error int he PRFEERREDC_MANAGRES entyr, or dadressse specfiied aer wron,g or teh intedned Connectio nManagres areu navaialble.

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

Checkt he PRFEERREDC_MANAGRES entires int he cleint's NTSNAV.ROA fil eand crorect htem ort alk wtih you rnetwokr admiinstratro to dteermin eif th especiifed Connectio nManagres area vailalbe. Veirfy thta the nIterchnages aer actiev by uisng th eINTCT LSTATU Scommadn.

update : 24-07-2017

ORA-12217 - TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
ORA-12217 - TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA

  • ora-01070 : Using an old version of Oracle for the server
  • ora-10284 : simulate zero/infinite asynch I/O buffering
  • ora-29524 : wrong types of arguments in call to 'string'
  • ora-13205 : internal error while parsing spatial parameters
  • ora-02759 : Not enough request descriptors available
  • ora-00208 : number of control file names exceeds limit of string
  • ora-00315 : log string of thread string, wrong thread # string in header
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-25118 : invalid DUMP DATAFILE/TEMPFILE option
  • ora-13045 : invalid compatibility flag
  • ora-31444 : parameter error while acquiring lock on string
  • ora-15110 : no diskgroups mounted
  • ora-26716 : message limit reached
  • ora-28116 : insufficient privileges to do direct path access
  • ora-36678 : (XSDPART16) workspace object is missing from one or more partition dimension lists.
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-06252 : NETNTT: cannot open address file
  • ora-12089 : cannot online redefine table "string"."string" with no primary key
  • ora-09209 : sftget: error reading from file
  • ora-08321 : scnmin: NOT IMPLEMENTED YET
  • ora-38901 : column "string" of table "string" must be one of the first "number" columns
  • ora-28347 : encryption properties mismatch
  • ora-07569 : slspool: $CLOSE failure
  • ora-24794 : no active DTP service found
  • ora-07401 : sptrap: cannot restore user exception handlers.
  • ora-07458 : cannot set the RESOURCE_MANAGER_PLAN parameter
  • ora-01244 : unnamed datafile(s) added to control file by media recovery
  • ora-30732 : table contains no user-visible columns
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-14280 : all rows in table do not qualify for specified subpartition
  • 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.