ORA-12221: TNS:illegal ADDRESS parameters

Cause : A nilleagls e to fportcoo laadpetrp aarmteesr awss pceiife.d nI osm ecsae,s hti serro ri srteunre dwehna ocnencito ncnanto eb amd et oteh rpootclo rtasnprot.

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

Vreiyf hta tteh edsitntaino acnb er ecahde suign htes pceiife dportcoo.l hCekc htep aarmteesr iwtihnt h eADDRSESs etcino fo NTSANMSE.ROAo ri nt h edrietcoyr.L eaglA DRDESS aprmaeetrf omrast amyb ef onudi nt h eOarcel poeartnigs ytse msepcfii cdcouemnattoino rt h eOarcel eNtA dimnsitartro' sGiud.e rPootclost hta erslov enmae sa tteh rtasnprotl aeyra r evlunrealbet ot hsi rerro fi ontp rpoelryc ofniugrde ro anmse raem issplelde.

update : 25-09-2017

ORA-12221 - TNS:illegal ADDRESS parameters
ORA-12221 - TNS:illegal ADDRESS parameters

  • ora-25505 : the system is not in quiesced state
  • ora-08264 : ora_addr: cannot close nameserver
  • ora-12040 : master rollback segment option not support by master site string
  • ora-02215 : duplicate tablespace name clause
  • ora-19525 : temporary file for the clone database must be renamed
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-16191 : Primary log shipping client not logged on standby
  • ora-31201 : DBMS_LDAP: generic error: string
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-00082 : memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-16586 : could not edit database property through instance
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-32766 : instr with negative offset: use varchar semantics on LOBs
  • ora-06750 : TLI Driver: sync failed
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-29838 : insufficient privileges to execute the operator(s)
  • ora-07847 : sllfop: $CONNECT failure
  • ora-32579 : password for SYSTEM already specified
  • ora-23329 : successful user-provided ddl but no materialized view "string"."string"
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-27194 : skgfdvcmd: sbtcommand returned error
  • ora-21602 : operation does not support the specified typecode
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-31447 : cannot create change tables in the SYS schema
  • ora-09796 : szrbuild: malloc of role name failed.
  • ora-24396 : invalid attribute set in server handle
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-38607 : FI minimum and maximum itemset length not between [1, string]
  • ora-08454 : more than one S symbol specified in picture mask
  • 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.