Sqlj fails with call to raise_application_error

Question

I get an error
Invoking loadjava on connection 'dbm1_twebn1' with arguments:
-order -resolve -thin -verbose
creating : class SystemDaemon/testcase
loading : class SystemDaemon/testcase
resolving: class SystemDaemon/testcase
errors : class SystemDaemon/testcase
ORA-29521: referenced name sqlj/runtime/ExecutionContext$OracleContext could not be found
The following operations failed
class SystemDaemon/testcase: resolution
when I load this sqlj file
in an 8.1.7 database
package SystemDaemon;
import sqlj.runtime.*;
import sqlj.runtime.ref.*;
import java.sql.*;
import oracle.sqlj.runtime.*;
public class testcase
static public void testcase1()
String s = new String("this is a test");
try
#sql {CALL RAISE_APPLICATION_ERROR(-20020, :s)};
catch (SQLException e)
// putLine("error in raise_application_error" + e.getMessage());
This works fine in a 9i database
I get other errors when i load the source code into the database but I get thoses in both 8i and 9i.
any sugestions on how to fix this?
Daniel Smith
[email protected]

Answer 1

It appears that you are translating SQLJ using the 9i version of the SQLJ
translator and loading that into an 8i database. The SQLJ code that
is generated by default requires a 9i (or later) version of the SQLJ runtime
and JDBC driver as well. The 8i database only has the 8i SQLJ runtime available to it.
You can turn on backwords compatibility for your SQLJ code with the option:
-codegen=iso
This generates standard SQLJ code (including .ser files that contain the code
of your SQLJ statements) that can be used in 8i as well as in 9i - just make
sure you load both, .ser and .class files into the database (or use the
-ser2class option to convert .ser into .class files). Or, just load the source
directly into the database.
Please note an additional caveat when generating code with SQLJ. If you
translate code with the 9.0.1 JDBC driver in the CLASSPATH, then this
code will run under 9.0.1 and later (such as 9.2) JDBC drivers. However,
the converse is not true: if you use a 9.2 JDBC driver during translation,
the generated code will utilize 9.2-specific JDBC APIs and may not run
under 9.0.1 JDBC. Thus to get compatibility: either use the -codegen=iso
option, or make sure that when your code is run you use the same or
a later JDBC driver than what you used when the code was translated.
Hope this helps.
-- Ekkehard