Java.sql.SQLException: ORA-02014

Question

Hello.
We are running an application on BEA WLS 8.1 SP1 on Fedora Core1 and HP-UX, connected to an Oracle 9.2.0.4 with the appropriate driver.
In jdbc.log we keep receiving the exception below when deploying or starting our WLS:
SQLException: SQLState(42000) vendor code(2014)
java.sql.SQLException: ORA-02014: cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:573)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:572)
at weblogic.jdbc.wrapper.Statement.executeQuery(Statement.java:316)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.verifySelectForUpdateSupported(RDBMSPersistenceManager.java:964)
at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:202)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:217)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:184)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:164)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1004)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1322)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3012)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2076)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2057)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2005)
at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3136)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1688)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:407)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
at weblogic.Server.main(Server.java:32)
It seems that the BEA deployer is trying to update a locked row in a table. Is there any experience on ORA side on how to deal with this issue? On BEA side there obviously isn't as we have not received satisfactory hints ...
Thanks,
Alex

Answer 1

I had the same problem using INSTEAD OF in combination with VPD. When i remember correctly, for views without VPD, the FOR UPDATE NOWAIT works.
You can overwrite the lock() method in your EntityImpl and lock the tables manually like this:try {
  getDBTransaction(  ).executeCommand( "declare v_my_table_id integer; begin "
                         + "SELECT my_table_id INTO v_my_table_id FROM mytable "
                         + "WHERE my_table_id = "
                         + getMyTableId(  )
                         + " FOR UPDATE NOWAIT; END;" );
  setLocked( true );
} catch( RuntimeException exception ) {
    throw exception;
}Sadly there is no SAVEPOINT support in BC4J, so if you have more than one table, better create a DB Package function that issues a savepoint, try to lock each of the tables and do a ROLLBACK TO savepoint if one of the SELECT FOR UPDATE fails.
hth, Markus