ORA-00129: listener address validation failed 'string'

Cause : An error was encountered while validating the listener address.

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

Resolve error or contact your ORACLE representative.

update : 23-06-2017
ORA-00129

ORA-00129 - listener address validation failed 'string'
ORA-00129 - listener address validation failed 'string'

  • ora-22891 : cannot have multiple columns in REF constraint
  • ora-01982 : invalid auditing option for tables
  • ora-31494 : could not activate a LogMiner session
  • ora-02155 : invalid DEFAULT tablespace identifier
  • ora-27056 : could not delete file
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-30193 : reserved for future use
  • ora-13149 : failed to generate next sequence number for spatial table string
  • ora-38712 : Corrupt flashback log record header: block string, offset string.
  • ora-31401 : change source string is not an existing change source
  • ora-00318 : log string of thread string, expected file size string doesn't match string
  • ora-30437 : all job queue processes have stopped running
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-39082 : Object type string created with compilation warnings
  • ora-31017 : Error generating unique OID for XML document
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-30153 : An invalid File Object is passed to the OCIFile function
  • ora-09878 : sstascre/sstasat: shmat error, unable to attach tas write page
  • ora-39122 : Unprivileged users may not perform string remappings.
  • ora-16083 : LogMiner session has not been created
  • ora-19902 : incarnation key string not found
  • ora-02306 : cannot create a type that already has valid dependent(s)
  • ora-16096 : ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-16735 : error executing dbms_logstdby.unskip_error procedure
  • ora-03221 : Temporary tablespaces and temporary segments must have standard block size
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-01353 : existing Logminer session
  • 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.