Fixes are available
PI86830: CWSIS1530E: The data type, 2, was found instead of the expected type, 3,
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11
APAR status
Closed as program error.
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:S IBAdmin=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.PersistentMessageStore Impl) [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.j ava:478) ***************************
Local fix
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: * **************************************************************** 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.performColumnChec ks(Table.java:443) at com.ibm.ws.sib.msgstore.persistence.impl.MEOuterOwnerTable.initi alize(MEOuterOwnerTable.java:85) at com.ibm.ws.sib.msgstore.persistence.impl.TableManager$1.run(Tabl eManager.java:263) at com.ibm.ws.sib.msgstore.persistence.impl.DatasourceController.pe rformFirstAction(DatasourceController.java:231) at com.ibm.ws.sib.msgstore.persistence.impl.TableManager.initialize (TableManager.java:248) at com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreI mpl.start(PersistentMessageStoreImpl.java:198) at com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start(MessageStore Impl.java:1570) at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagin gEngineImpl.java:638) at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.condition alStart(HAManagerMessagingEngineImpl.java:2338) at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate( HAManagerMessagingEngineImpl.java:1334) at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThr ead.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
Temporary fix
Column checks on the message store database may be disabled using the following setting in the sib.properties file: sib.msgstore.jdbcPerformColumnChecks=false
Comments
APAR Information
APAR number
PI86830
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-05
Closed date
2017-11-27
Last modified date
2017-11-28
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
04 May 2022