Troubleshooting
Problem
An error occurs when you use WebSphere Adapter for JDBC 7.5.0.1_IF01 to insert data into an Ingres database: javax.resource.ResourceException: OTHER does not support named sequence.
Symptom
You see the following error in trace.log:
[9/11/12 11:49:45:189 EDT] 0000003b JDBCRA001 3
com.ibm.j2ca.jdbc.commands.JDBCBaseCommand setSequenceValues UID Type is
SEQUENCE for attribute id in business objectOmnidbaSa_shift_activity
[9/11/12 11:49:45:189 EDT] 0000003b JDBCRA001 2
com.ibm.j2ca.jdbc.JDBCDBOperationHandler getNextSequenceValue Entering
method.
[9/11/12 11:49:45:189 EDT] 0000003b JDBCRA001 3
com.ibm.j2ca.jdbc.JDBCDBOperationHandler getNextSequenceValue Sequence
name is: SA_SHIFT_ACTIVITY_SEQ
[9/11/12 11:49:45:215 EDT] 0000003b FfdcProvider W
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident
emitted on
D:\IBM\WebSphere\AppServer\profiles\qesb\logs\ffdc\server1_2ae92ae9_12.0
9.11_11.49.45.2006515563853741256246.txt
com.ibm.j2ca.jdbc.commands.JDBCCreateCommand execute
[9/11/12 11:49:45:217 EDT] 0000003b JDBCRA001 2
com.ibm.j2ca.jdbc.JDBCASIRetriever retrieve Entering method.
[9/11/12 11:49:45:218 EDT] 0000003b JDBCRA001 1
com.ibm.j2ca.jdbc.JDBCASIRetriever retrieve Retrieving ASI for type :
OmnidbaSa_shift_activity
[9/11/12 11:49:45:218 EDT] 0000003b JDBCRA001 1
com.ibm.j2ca.jdbc.JDBCASIRetriever retrieve Type information found in
the cache.
[9/11/12 11:49:45:221 EDT] 0000003b FfdcProvider W
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident
emitted on
D:\IBM\WebSphere\AppServer\profiles\qesb\logs\ffdc\server1_2ae92ae9_12.0
9.11_11.49.45.2181255836241776263377.txt
com.ibm.j2ca.jdbc.JDBCInteraction execute
[9/11/12 11:49:45:251 EDT] 0000003b JDBCRA001 E JDBCInteraction
execute CWYBC1201E: The execute call to the interaction could not be
completed. Explanation=The adapter could not perform the Execute
operation on the interaction. The exception message logged gives the
reason for the failure. UserAction=Check the exception and perform
corrective action.
[9/11/12 11:49:45:252 EDT] 0000003b JDBCRA001 3
com.ibm.j2ca.jdbc.JDBCUtils getSQLException The Exception not cause by
SQLException, Returning null.
[9/11/12 11:49:45:252 EDT] 0000003b JDBCRA001 I JDBCInteraction
execute Roll Back the transaction.
[9/11/12 11:49:45:252 EDT] 0000003b JDBCRA001 2
com.ibm.j2ca.jdbc.commands.JDBCBaseCommand rollback Entering method.
[9/11/12 11:49:45:269 EDT] 0000003b DMAdapter I
com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis
Engine using data base:
D:\IBM\WebSphere\AppServer\profiles\qesb\properties\logbr\ffdc\adv\ffdcd
b.xml
[9/11/12 11:49:45:284 EDT] 0000003b FfdcProvider W
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident
emitted on
D:\IBM\WebSphere\AppServer\profiles\qesb\logs\ffdc\server1_2ae92ae9_12.0
9.11_11.49.45.2636224996615091827152.txt
com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.rollback 1860
[9/11/12 11:49:45:289 EDT] 0000003b FfdcProvider W
com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident
emitted on
D:\IBM\WebSphere\AppServer\profiles\qesb\logs\ffdc\server1_2ae92ae9_12.0
9.11_11.49.45.2876134076308947782503.txt
com.ibm.j2ca.jdbc.commands.JDBCCreateCommand rollback
[9/11/12 11:49:45:291 EDT] 0000003b JDBCRA001 E
com.ibm.j2ca.jdbc.commands.JDBCBaseCommand rollback CWYDB0502E: The
Rollback operation on the transaction could not be completed. Reason
Invalid transaction state for requested operation. Explanation=The
adapter could not roll back the changes made in the database.
UserAction=Check the logs and verify that the database is operational.
[9/11/12 11:49:45:292 EDT] 0000003b JDBCRA001 2
com.ibm.j2ca.extension.monitoring.interceptors.impl.MonitoringFactory
fireAllConfiguredInterceptors() Entering method.
[9/11/12 11:49:45:293 EDT] 0000003b JDBCRA001 2
com.ibm.j2ca.extension.monitoring.interceptors.impl.CEIInterceptor
invoke(Message) Entering method.
In FFDC file, you may see the following:
9/11/12 11:49:45:205 EDT] FFDC
Exception:javax.resource.ResourceException
SourceId:com.ibm.j2ca.jdbc.commands.JDBCCreateCommand ProbeId:execute
Reporter:com.ibm.j2ca.jdbc.commands.JDBCCreateCommand@19a419a4
javax.resource.ResourceException: OTHER dose not support named sequence
at
com.ibm.j2ca.jdbc.JDBCDBOperationHandler.getNextSequenceValue(JDBCDBOper
ationHandler.java:273)
at
com.ibm.j2ca.jdbc.commands.JDBCBaseCommand.setSequenceValues(JDBCBaseCom
mand.java:730)
at
com.ibm.j2ca.jdbc.commands.JDBCCreateCommand.executeWithOwnership(JDBCCr
eateCommand.java:341)
at
com.ibm.j2ca.jdbc.commands.JDBCCreateCommand.doExecute(JDBCCreateCommand
.java:202)
at
com.ibm.j2ca.jdbc.commands.JDBCBaseCommand.execute(JDBCBaseCommand.java:
785)
at
com.ibm.j2ca.extension.commandpattern.CommandForCursor.execute(CommandFo
rCursor.java:76)
at
com.ibm.j2ca.extension.commandpattern.Interpreter.executeWithChildren(In
terpreter.java:125)
at
com.ibm.j2ca.extension.commandpattern.Interpreter.execute(Interpreter.ja
va:84)
at
com.ibm.j2ca.jdbc.JDBCInteraction.executeInternal(JDBCInteraction.java:4
50)
at
com.ibm.j2ca.jdbc.JDBCInteraction.doExecute(JDBCInteraction.java:126)
at com.ibm.j2ca.base.WBIInteraction.execute(WBIInteraction.java:522)
at com.ibm.ws.sca.bindi
Cause
This is a limitation in WebSphere Adapter for JDBC V7.5. This has been documented in the latest user guide for V7.5.0.2. The JDBC Adapter will only take sequence value for DB2 and Oracle database.
Resolving The Problem
The following workarounds are suggested:
a) You can use sequence on the database side (using trigger to
update value). This way the database automatically takes care of any sequence
value insertion.
b)You can use a stored procedure to get the next sequence value, and insert that value when the other parameters of the insertion are passed to the stored procedure.
Both of these cases require regeneration of artifacts for Adapter.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21611233