PI86830: CWSIS1530E: The data type, 2, was found instead of the expected type, 3,

Download Description

PI86830 resolves the following problem:

ERROR DESCRIPTION:
Problem description: CWSIS1530E: The data type, 2, was found instead of the expected type, 3, for column, EMPTY_COLUMN, in table, DBADMIN.SIBOWNERO.


Error Stack from System.out
***************************

[8/30/17 17:47:43:884 HKT] 00000001 ManagerAdmin I TRAS0017I:
The startup trace state is *=info:WAS.j2c=all:RRA=all:Transaction=all:SIBAdmin=all:SIBProcessor=all:SIBMessageStore=all.

and the error:
[8/30/17 18:12:24:527 HKT] 0000007b PersistentMes 1
(com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreImpl) [XXXXXXXXXX] Exception caught starting MessageStore persistence!

java.lang.IllegalStateException: CWSIS1530E: The data type, 2, was found instead of the expected
type, 3, for column, EMPTY_COLUMN, in table, DBADMIN.SIBOWNERO.
at com.ibm.ws.sib.msgstore.persistence.impl.Table.compareColumnInfo(Table.java:478)
***************************

LOCAL FIX:
none

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server users of SIB Java Messaging Service (JMS) communication using an Oracle database backed message store, using ojdbc8.jar.

PROBLEM DESCRIPTION:
CWSIS1530E due to failed message store column checks when using ojdbc8.jar

RECOMMENDATION:
None

Oracle Database columns that were reported to be of type DECIMAL using ojdbc7.jar (or previous) now report to be of type NUMERIC when using ojdbc8.jar . When the SIB message store is configured to use an Oracle database, this difference in reporting causes the existing database column checking code during WebSphere Application Server startup to fail with the following error:
----
java.lang.IllegalStateException: CWSIS1530E: The data type, 2, was found instead of the expected type, 3, for column, EMPTY_COLUMN, in table, CMN201USER.SIBOWNERO.
at com.ibm.ws.sib.msgstore.persistence.impl.Table.compareColumnInfo(Table.java:477)
at com.ibm.ws.sib.msgstore.persistence.impl.Table.performColumnChecks(Table.java:443)
at com.ibm.ws.sib.msgstore.persistence.impl.MEOuterOwnerTable.initialize (MEOuterOwnerTable.java:85)
at com.ibm.ws.sib.msgstore.persistence.impl.TableManager$1.run(TableManager.java:263)
at com.ibm.ws.sib.msgstore.persistence.impl.DatasourceController.performFirstAction (DatasourceController.java:231)
at com.ibm.ws.sib.msgstore.persistence.impl.TableManager.initialize(TableManager.java:248)
at com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreImpl.start (PersistentMessageStoreImpl.java:198)
at com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start(MessageStoreImpl.java:1570)
at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagingEngineImpl.java:638)
at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.conditionalStart (HAManagerMessagingEngineImpl.java:2338)
at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate (HAManagerMessagingEngineImpl.java:1334)
at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThread.java:94)
----
The fix is for the column checking code to accept a column type of either DECIMAL or NUMERIC when checking the message store tables in Oracle databases.

PROBLEM CONCLUSION:
The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.15, 8.5.5.13, and 9.0.0.7.

Please refer to the Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980