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 : 23-04-2017
ORA-24197

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

  • ora-32615 : incorrect use of MODEL IS ANY predicate
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • ora-08110 : Oracle event to test SMON cleanup for online index build
  • ora-10918 : TABLESPACE GROUP name cannot be the same as tablespace name
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-07455 : estimated execution time (string secs), exceeds limit (string secs)
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-38410 : schema extension not allowed for the table name
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-30135 : OCI Thread operation fails
  • ora-03291 : Invalid truncate option - missing STORAGE keyword
  • ora-01928 : GRANT option not granted for all privileges
  • ora-24808 : streaming of lob data is not allowed when using lob buffering
  • ora-38503 : index already defined using the parameters
  • ora-19955 : only one open thread is allowed to change the DBID
  • ora-00826 : cannot set sga_target for an ASM instance
  • ora-00602 : internal programming exception
  • ora-23415 : materialized view log for "string"."string" does not record the primary key
  • ora-24185 : transformation string.string does not exist
  • ora-40302 : invalid classname string in cost matrix specification
  • ora-19210 : column 'string', specified to be a key or update column for DBMS_XMLSTORE, does not not exist in table 'string'
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-12492 : DBLOW cannot be changed
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-39061 : import mode string conflicts with export mode string
  • ora-01939 : only the ADMIN OPTION can be specified
  • ora-09988 : error while detaching SGA
  • ora-29365 : parameters string and string cannot both be set
  • ora-28551 : pass-through SQL: SQL parse error
  • ora-34145 : (MXCGPUT03) You cannot use the APPEND keyword with SURROGATE workspace object.
  • 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.