ORA-20000: %s

Cause : The stored procedure 'raise_application_error' was called which causes this error to be generated.

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

Correct the problem as described in the error message or contact the application administrator or DBA for more information.

update : 27-06-2017
ORA-20000

ORA-20000 - %s
ORA-20000 - %s

  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-12643 : Client received internal error from server
  • ora-16791 : unable to check the existence of the standby redo logs
  • ora-31493 : could not prepare session for LogMiner session
  • ora-24065 : propagation for QUEUE string and DESTINATION string already disabled
  • ora-16731 : error executing dbms_logstdby.unskip_txn procedure
  • ora-04096 : trigger 'string' has a WHEN clause which is too large, limit 2K
  • ora-27376 : event condition cannot be NULL
  • ora-02791 : Unable to open file for use with asynchronous I/O
  • ora-39150 : bad flashback time
  • ora-02788 : Unable to find kernel process pointer in async process array
  • ora-13462 : invalid blocking specification
  • ora-19011 : Character string buffer too small
  • ora-30455 : summary contains VARIANCE without corresponding SUM & COUNT
  • ora-13620 : The task or object string is read-only and cannot be deleted or modified.
  • ora-13282 : failure on initialization of coordinate transformation
  • ora-13260 : layer table string does not exist
  • ora-24769 : cannot forget an active transaction
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-39111 : Dependent object type string skipped, base object type string already exists
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-22958 : This operation is not allowed in check constraints or triggers
  • ora-14504 : syntax not supported for analyze
  • ora-22371 : Table contains data of type string.string, version string, which does not exist
  • ora-06303 : IPA: Message send error
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-15075 : disk(s) are not visible cluster-wide
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-36843 : (XSLMGEN13) Dimension string.string!string hierarchy string is missing a PHYSICALNAME property value
  • 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.