Wednesday, August 5, 2009

LOV criteria bug.

Some times after using search criteria inside an LOV we get a strange exception:

java.sql.SQLException: Attempt to set a parameter name that does not occur in the SQL: vc_temp_2
at oracle.jdbc.driver.SQLStateMapping.newSQLException(
at oracle.jdbc.driver.DatabaseError.newSQLException(
at oracle.jdbc.driver.DatabaseError.throwSqlException(
at oracle.jdbc.driver.DatabaseError.throwSqlException(
at oracle.jdbc.driver.DatabaseError.throwSqlException(
at oracle.jdbc.driver.OraclePreparedStatement.setObjectAtName(
at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObjectAtName(
at oracle.jbo.server.OracleSQLBuilderImpl.bindParamValue(
at oracle.jbo.server.BaseSQLBuilderImpl.bindParametersForStmt(
at oracle.jbo.server.ViewObjectImpl.bindParametersForCollection(
at oracle.jbo.server.QueryCollection.buildResultSet(
at oracle.jbo.server.QueryCollection.executeQuery(
at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(
at oracle.jbo.server.ViewRowSetImpl.execute(
at oracle.jbo.server.ViewRowSetImpl.execute(

It is not easy to reproduce but when it happens you cannot open the LOV again and you cannot set a value to the LOV field, even from diferent row or from diferent session.

I managed to reproduce it in a simple test case of Employees form with simple Department LOV.
The steps to reproduce are:

1.Select an existing department department LOV add a criterion and press search.

3.Close LOV without selecting row and type a non existing value and press Tab. LOV automatically opens and even though it doesnt have values in criteria only the previus results are visible.

4.Press cancel again and type an existing value and press Tab. Then the error apears

It seems that LOVs Love bugs.


  1. Hi,
    Thanks for the info. Is there any work around for this. Cant I use LOV at all with Search criteria ? I would like to change the search region that is opened by LOV. it seems ADF LOV is so rigid

  2. Hello Michael,

    Have you found a workaround for this bug yet?

  3. This is an old bug and hard to reproduce. We are at least 2 versions of jdeveloper ahead now and we dont meet this bug. I will try to reproduce it in and see if still exist