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-05-2017

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

  • ora-27056 : could not delete file
  • ora-36274 : (XSCGMDLAGG05) The operator used in this equation needs a weight variable.
  • ora-22062 : invalid input string [string]
  • ora-16612 : string value too long for attribute "string"
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-07201 : slhom: oracle_home variable not set in environment.
  • ora-09273 : szrfc: error verifying role name
  • ora-10265 : Keep random system generated output out of error messages
  • ora-16160 : Cannot change protected standby database configuration
  • ora-12333 : database (link name string) is not mounted
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-06119 : NETTCP: spurious client request
  • ora-09743 : smscre: could not attach shared memory.
  • ora-28237 : seed length too short
  • ora-26565 : Call to _arg made before calling dbms_defer.call
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-23611 : tablespace "string" has more than one data file
  • ora-22613 : buflen does not match the size of the scalar
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-38700 : Limit of string flashback database logs has been exceeded.
  • ora-16412 : ONDEMAND archival requires active SQL apply operation
  • ora-28180 : multiple authentication methods provided by proxy
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-34019 : (MSCGADD03) workspace object is not a LIST PARTITION TEMPLATE.
  • ora-06133 : NETTCP: file not found
  • ora-36908 : (XSAGDNGL46) In AGGMAP workspace object, MODEL workspace object has the repeating dimension with the previous model.
  • ora-30030 : suppress resumable related error message
  • ora-12454 : label string does not exist for policy string
  • ora-30005 : missing or invalid WAIT interval
  • 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.