Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When using a JDBC driver that makes use of the new Java 6 JDBC SQL type ROWID, the following exception is seen and an FFDC produced when a messaging engine is starting: CWSIS1530E: The data type, -8, was found instead of the expected type, [Ljava.lang.Integer;@39da39da, for column, LONG_DATA_ID, in table, <SCHEMA_NAME>.SIB000. at com.ibm.ws.sib.msgstore.persistence.impl.Table.compareColumnInfo (Table.java:442) at com.ibm.ws.sib.msgstore.persistence.impl.ItemTable.initialize(It emTable.java:279) at com.ibm.ws.sib.msgstore.persistence.impl.TableManager$2.run(Tabl eManager.java:358) at com.ibm.ws.sib.msgstore.persistence.impl.DatasourceController.pe rformAction(DatasourceController.java:348) at com.ibm.ws.sib.msgstore.persistence.impl.TableManager.initialize (TableManager.java:286) at com.ibm.ws.sib.msgstore.persistence.impl.PersistentMessageStoreI mpl.start(PersistentMessageStoreImpl.java:197) at com.ibm.ws.sib.msgstore.impl.MessageStoreImpl.start(MessageStore Impl.java:1518) at com.ibm.ws.sib.admin.impl.JsMessagingEngineImpl.start(JsMessagin gEngineImpl.java:609) at com.ibm.ws.sib.admin.impl.HAManagerMessagingEngineImpl.activate( HAManagerMessagingEngineImpl.java:995) at com.ibm.ws.sib.admin.impl.JsActivationThread.run(JsActivationThr ead.java:92) This APAR also adds support for DB2v10 on z/OS to the sibDDLGenerator. Note that the DDL produced by the generator for DB2_91 is the same as that produced for the new DB2_101 so this APAR is not required to create DDL for DB2 v10. This APAR is only required to get support for the new SQL type ROWID.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: When starting a messaging engine a * * CWSIS1530E message is produced and * * the messaging engine fails to start. * **************************************************************** * RECOMMENDATION: * **************************************************************** ROWID is a new JDBC SQL type and support for this new type was not present prior to this APAR. Also, customers trying to use the sibDDLGenerator to create DDL for DB2v10 on z/OS could not specify this option.
Problem conclusion
This APAR adds support for the new SQL type ROWID, which resolves the CWSIS1530E message and the messaging engine is able to start. DB2_101 is now a new supported database type in the sibDDLGenerator, although the output for this new type is the same as the output for the existing DB2_91 type. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.19. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM36111
Reported component name
PLAT MSG COM
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-04-01
Closed date
2011-06-30
Last modified date
2011-06-30
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
PLAT MSG COM
Fixed component ID
620800101
Applicable component levels
R300 PSY
UP
Document Information
Modified date:
27 October 2021