[
https://issues.apache.org/jira/browse/SYNCOPE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282383#comment-13282383
]
Denis Signoretto commented on SYNCOPE-59:
-----------------------------------------
Searching on Oracle Metalink, the issues it's related to a know Oracle JDBC and
OCI Bug.
As reported in the Oracle Note 1160014.1:
- Applies to: JDBC - Version: 10.1.0.3.0 and later [Release: and later ] When
executing a SELECT FOR UPDATE through the OCI JDBC driver with the 'Auto
Commit' enabled, following error is reported: java.sql.SQLException: ORA-01002:
fetch out of sequence. The same problem is not seen using Oracle Thin drivers.
- Solution
An internal bug exists for this issue and it has been fixed in JDBC 11g.
There are multiple solutions to this issue:
a) Use the 11g version of JDBC-OCI.
Install an Oracle 11g client. Either 11.1.0.7.0 or above should be fine. Make
sure to install this into a seperate ORACLE_HOME and not in the same home as
the 10g client.
According to the below note:
Note 207303.1 - Client / Server / Interoperability Support Between Different
Oracle Versions
11g clients supported/certified against 10g database if database has a minimum
version of 10.2.0.2.
b) Use Oracle JDBC Thin Driver 10.2.0.1 or above.
c) If you do not wish to upgrade to the 11g drivers or if you do not want to
change to thin drivers, raise a SR with Oracle Software Support and request for
a one-off patch for the version of JDBC OCI driver that you are using.
> ERROR org.syncope.core.init.JobInstanceLoader - While loading NotificationJob
> instance - ORA-01002: fetch out of sequence
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: SYNCOPE-59
> URL: https://issues.apache.org/jira/browse/SYNCOPE-59
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.0-incubating
> Environment: Oracle 10g, Linux x86_64, OCI
> Reporter: Denis Signoretto
> Assignee: fabio martelli
> Labels: oracle
>
> Stracktrace Error on startup:
> 15:51:05.908 ERROR org.syncope.core.init.JobInstanceLoader - While loading
> NotificationJob instance
> org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock:
> ORA-01002: fetch out of sequence
> {prepstmnt 155276228 SELECT * FROM QRTZ_LOCKS WHERE LOCK_NAME = ? FOR UPDATE
> [params=?]} [code=1002, state=72000]
> at
> org.quartz.impl.jdbcjobstore.StdRowLockSemaphore.executeSQL(StdRowLockSemaphore.java:109)
> ~[quartz-1.8.6.jar:na]
> at
> org.quartz.impl.jdbcjobstore.DBSemaphore.obtainLock(DBSemaphore.java:112)
> ~[quartz-1.8.6.jar:na]
> at
> org.quartz.impl.jdbcjobstore.JobStoreCMT.executeInLock(JobStoreCMT.java:235)
> ~[quartz-1.8.6.jar:na]
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInLock(JobStoreSupport.java:3712)
> ~[quartz-1.8.6.jar:na]
> at
> org.quartz.impl.jdbcjobstore.JobStoreSupport.storeJobAndTrigger(JobStoreSupport.java:1059)
> ~[quartz-1.8.6.jar:na]
> at
> org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java:822)
> ~[quartz-1.8.6.jar:na]
> at org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:243)
> ~[quartz-1.8.6.jar:na]
> at
> org.syncope.core.init.JobInstanceLoader.registerJob(JobInstanceLoader.java:134)
> ~[JobInstanceLoader.class:na]
> at
> org.syncope.core.init.JobInstanceLoader.registerJob(JobInstanceLoader.java:162)
> ~[JobInstanceLoader.class:na]
> at
> org.syncope.core.init.JobInstanceLoader.load(JobInstanceLoader.java:210)
> ~[JobInstanceLoader.class:na]
> at
> org.syncope.core.init.JobInstanceLoader$$FastClassByCGLIB$$edd08387.invoke(<generated>)
> [cglib-2.2.2.jar:na]
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> [cglib-2.2.2.jar:na]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
