Occasionally a stored procedure does not behave as expected. One possible cause can be improper resolution of the Java class. For example, a custom jar in the CLASSPATH may include a class using the same name as our stored procedures generate.
The class resolution can be traced using these procedures:
(DH_JVM_OPTION_STRINGS may contain a variety of Java options, for example, you may be increasing the default Java heap size with -Xmx, etc. Simply add the verbose options to the string.)
Here is the expected load of procedure in err.log:
[Loaded admin_p_sp_getfddversion_SP from __JVM_DefineClass__]
Here is an unexpected version being loaded from a .class file sitting in the CLASSPATH:
[Loaded admin_p_sp_getfddversion_SP from file:/Q:/ctreesrc/ipv6/ctreeAPI/bin.sql/data/]