ORA-24197: JAVA stored procedure throws JAVA exceptions

Cause : The JAVA stored procedure threw some exceptions that could not be catergorized.

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

Use GET_EXCEPTION procedure to see what the exception is about.

update : 27-06-2017

ORA-24197 - JAVA stored procedure throws JAVA exceptions
ORA-24197 - JAVA stored procedure throws JAVA exceptions

  • ora-06817 : TLI Driver: could not read the Novell network address
  • ora-15109 : conflicting protection attributes specified
  • ora-28501 : communication error on heterogeneous database link
  • ora-28134 : object cannot have fine-grained access control policy
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-02717 : osnpfs: incorrect number of bytes written
  • ora-09911 : Incorrect user password.
  • ora-02274 : duplicate referential constraint specifications
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-07226 : rtneco: unable to get terminal mode.
  • ora-37137 : (XSCCOMP12) You cannot CHGDFN workspace object because it is a COMPRESSED COMPOSITE.
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-10936 : trace name context forever
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-39110 : error deleting worker processes
  • ora-31416 : invalid SOURCE_COLMAP value
  • ora-04045 : errors during recompilation/revalidation of string.string
  • ora-30476 : PLAN_TABLE does not exist in the user's schema
  • ora-13291 : conversion error between the specified unit and standard unit
  • ora-08498 : Warning: picture mask 'string' overrides picture mask option 'USAGE IS string' to 'USAGE IS DISPLAY'
  • ora-09940 : ORACLE password file header is corrupt
  • ora-39106 : Worker process string failed during startup. Worker error:
  • ora-10364 : Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
  • ora-12815 : value for INSTANCES must be greater than 0
  • ora-30572 : AUTO segment space management not valid with DICTIONARY extent management
  • ora-10654 : Table is of type temporary or external
  • ora-32640 : FOR LIKE loops are not allowed for multi-byte character types
  • ora-39070 : Unable to open the log file.
  • ora-02060 : select for update specified a join of distributed tables
  • 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.