SQLJ runtime exception in 9.2.0.4

Question

Hi,
I work on a software using oracle, java and SQLJ technology. Since we pass from oracle 8.1.6 to Oracle 9.2.0.4 we have some sqlj runtime exception. These exceptions are randoms, amazing as the same request with SQL*plus is working, and occurrs randomly in time so it works all the same ...
examples (in bold the oracle exception text) :
1/ Unable to define propagation alert iterator (this exception is an SQL one and catched within the program) : Invalid column name
the sqlj command corresponding => #sql ppgAlertIter = { SELECT USER_LOGIN FROM ALERT WHERE SAFETY_EVENT_ID = :incId AND OCCURRENCE_ID = :occId AND USER_LOGIN IN ( SELECT USER_LOGIN FROM USERS WHERE ROLE_NAME <> :roleName) };
all the column names are rights !!!!
2/java.lang.NullPointerException at sqlj.runtime.ExecutionContext$OracleContext.oracleExecuteQuery(ExecutionContext.java:1585) at asmtdb.DBUser.getComponentUpdateTime(DBUser.java:882)
here is a runtime exception (not catched) (this exception correpsonds to the SQLJ commqnd in example 3/)
3/exception when getting component's update time : Unable to retrieve component's update time : expected 1 columns in select list but found 11
the SQLJ command corresponding => #sql { SELECT TO_CHAR(UPDATE_TIME, 'DD/MM/YYYY HH24:MI:SS') INTO :updateTime FROM COMPONENT WHERE COMPONENT_NAME = :componentName };
with SQL*plus no problems to have a result, more is that we have only 3 distinct columns, so why 11 ????
Is anyone had already these kinds of troubleshootings ???
Here is my environment :
- HP-UX B.11.00 U 9000/785 (64 bits)
- Oracle SQLJ Release 9.2.0.3.0 Production
Copyright © 1997, 2003, Oracle Corporation. All Rights Reserved.
Build version: 2.3.0.0 - Built on Feb 15, 2002
IDE interface version: 9.2.0.3.0/2.3.0.0
JDBC version: Oracle JDBC driver version 9.2 (9.2.0.3.0)
SQLJ runtime: Oracle 9.2.0 for JDBC 8.1.7 or later/JDK 1.2.x - Built on Jul 21, 2003
Java version: 1.4 (1.4.2.00)
Chris

Answer 1

Chris,
The error messages are misleading. I'm only guessing, but from what you have posted, it looks like the problem is in the values you are supplying for your bind variables. It could be that the SQL parser thinks that a bind variable is a column name -- and, of-course, there is no such column name, hence the "Invalid column name" error. Do you know about P6Spy ? It captures the SQL with the bind variable values, so you see the exact SQL that is getting sent to Oracle.
Good Luck,
Avi.