ORA-12222: TNS:no support is available for the protocol indicated

Cause : The protocol requested in the ADDRESS portion of the connect descriptor identified through the net service name is not available. If the supplied ADDRESS is typographically correct then support for that protocol is not installed.

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

Install support for the protocol or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the net service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA) or in the directory server.

update : 26-04-2017
ORA-12222

ORA-12222 - TNS:no support is available for the protocol indicated
ORA-12222 - TNS:no support is available for the protocol indicated

  • ora-07534 : scginq: $getlki unexpected return on lockid string
  • ora-24393 : invalid mode for creating connection pool
  • ora-19377 : no "SQL Tuning Set" with name like "string" exists for owner like "string"
  • ora-32742 : Hang analysis initialize failed
  • ora-09342 : Detached process terminated by Oracle during shutdown abort
  • ora-22334 : cannot reset type "string"."string". Dependent tables must be upgraded to latest version
  • ora-40306 : wide data not supported for decision tree model create
  • ora-27062 : could not find pending async I/Os
  • ora-31019 : Recursive deletion snapshot too old for string/string
  • ora-00068 : invalid value string for parameter string, must be between string and string
  • ora-31622 : ORACLE server does not have string access to the specified file
  • ora-24143 : invalid evaluation context name
  • ora-27145 : insufficient resources for requested number of processes
  • ora-33265 : (DBERRBSZ) Analytic workspace string cannot be opened. Tablespace blocksize number does not match database cache size number.
  • ora-24050 : subscribers are not supported for exception queue string
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-06735 : TLI Driver: client failed to close error conn
  • ora-36684 : (XSDPART22) You cannot rename values of DIMENSION workspace object because it is the partition dimension of RANGE PARTITION TEMPLATE workspace object
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-29900 : operator binding does not exist
  • ora-06776 : TLI Driver: error sending parms
  • ora-13230 : failed to create temporary table [string] during R-tree creation
  • ora-08112 : a composite partition may not be coalesced as a whole
  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-28263 : Insufficient memory in global context pool
  • ora-38951 : Target platform string not cross platform compliant
  • ora-28113 : policy predicate has error
  • ora-27072 : File I/O error
  • ora-27473 : argument string does not exist
  • ora-02064 : distributed operation 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.