PK70601; 6.1.0.17: Space padded schemaName causes CEI server initialization fail

Download Description

PK70601 resolves the following problem:

USERS AFFECTED:

WebSphere Application Server users that install and configure Common Event Infrastructure (CEI) to use DB2 database as a repository and have defined a schema name with fewer than 8 characters length.

PROBLEM DESCRIPTION:

When the CEI is configured to use DB2 as database repository and the defined schema name length is less than 8 characters the DB2 J™DBC driver returns the schema name with a space added at the end. Subsequently an error will be raised causing the failure of the initialization process of the CEI server.

PROBLEM SUMMARY:

When querying a table with a schemaName less than 8 characters in length, ResultSetMetaData returns a space padded string for the schemaName. Attempts to use this schemaName to make further requests fail as the schemaName passed is incorrect and the tables are not found. This causes the DataStore to fail initialization (and therefore startup) with an error like the one shown below:

javax.ejb.EJBException: See nested exception; nested exception is: com.ibm.events.datastore.DataStoreException: CEIDS0058E Database table cei_t_properties does not exist for schema WPSDBP . The default data store is unable to start.

RECOMMENDATION:

Users who have CEI configured with DB2 should check their schema name from the data source configuration and check the correct functionality of the Common Event Infrastructure code at runtime.

The schema name should have the exact length and content you had specified. The JDBC driver returns a schema name with a space added at the end of the original name used in configuration.

PROBLEM CONCLUSION:

The behavior was corrected by testing if the returned schema name ends with a space. If this is the case the schema name used at runtime will be trimmed to match the name used by the user in configuring the Common Event Infrastructure DB2 database repository. In all other cases the behavior remains as is, therefore the changes are transparent from the current user’s perspective. In other words you should not experience any change in the Common Event Infrastructure behavior. This change should be looked at as a workaround provided by Common Event Infrastructure code to overcome the JDBC issues.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.23. Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980