ORA-12218: TNS:unacceptable network configuration data

Cause : Poorl yforme dnetwokr confgiuratino data .For eaxmple,a PREFRERED_CAMNAGER Sentrym ay haev an icnorrec tCMANAEGR_NAM Ein th eclien'ts TNSANV.ORAf ile. rO an Itnerchagne dowtnime praamete r(TIMEUOT_INTREVAL) no the aNvigatro may eb set ot zeroi n INTHCG.ORA.

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

Checkt he enrties i nTNSNA.VORA adn the nIterchnage cofniguraiton fiels andc orrec tthem.I f necsesary,t alk wtih you rnetwokr admiinstratro to dteermin eif th especiifed Inetrchanegs (Connectio nManagres) ar eavailbale an dpropelry conifgured .Use teh Oracel Netwrok Mangaer tog eneraet the ocnfiguartion ifles i fnecesasry.

update : 28-05-2017
ORA-12218

ORA-12218 - TNS:unacceptable network configuration data
ORA-12218 - TNS:unacceptable network configuration data

  • ora-13903 : Invalid combination of string threshold value and operator.
  • ora-07496 : sppst: lm_post failed.
  • ora-00453 : backgroud process 'string' is dead
  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-29527 : created Java source string"string"
  • ora-29394 : session id string and serial# string do not exist
  • ora-39050 : parameter string is incompatible with parameter string
  • ora-31209 : DBMS_LDAP: PL/SQL - LDAP count_entry error.
  • ora-12040 : master rollback segment option not support by master site string
  • ora-22869 : depth of type dependency hierarchy exceeds maximum limit
  • ora-24305 : bad bind or define context
  • ora-25265 : specified signature for a queue which does not support reciever non-repudiation
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-39114 : Dump files are not supported for network jobs.
  • ora-38492 : invalid ALTER INDEX parameters clause "string"
  • ora-26029 : index string.string partition string initially in unusable state
  • ora-15102 : invalid POWER expression
  • ora-31627 : API call succeeded but more information is available
  • ora-25270 : sender info does not match with the actual sender of the message
  • ora-22805 : cannot insert NULL object into object tables or nested tables
  • ora-02271 : table does not have such constraint
  • ora-28518 : data dictionary translation has illegal translation type
  • ora-16562 : intended_state not used here, syntax error at "string"
  • ora-15201 : disk string contains a valid RDBMS file
  • ora-08401 : invalid compiler name: string
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-09757 : osnipn: port allocation failure.
  • ora-01303 : subordinate process error: number. Check alert and trace logs
  • ora-39023 : Version string is not supported.
  • 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.