PI55465: MESSAGING ENGINE FAILS TO START WHEN THE SCHEMA NAME CONTAINS SPECIAL CHARACTERS

8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
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
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• "Messaging engine fails to start in a SQL server setup when the
  schema name contains special characters"
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using Service Integration bus      *
  *                      with SQL server as datastore, the       *
  *                      messaging engine fails to start if      *
  *                      the schema name contains special        *
  *                      characters even when adhering to the    *
  *                      syntax specified by SQLServer.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  SQLServer when supporting special characters in the schema
  name mandates it to be enclosed within square brackets (eg:
  [MSSQL-USER]). In a WebSphere Application Server when using
  Service Integration bus with SQL server as datastore, the
  messaging engine fails to start if the schema name contains
  special characters even when adhering to the syntax specified
  by SQLServer. Messaging Engine starts using database by first
  checking if the schema exists and there after checks for
  tables. The creation of schema and tables can be done manually
  by running a script generated by SIBDDLGenerator script or by
  selecting create tables option when creating the messaging
  engine. We observe exceptions in both scenarios during
  messaging engine startup -
  a) Exception observed when tables are created manually using a
  script -
  java.lang.IllegalStateException: CWSIS1532E: The
  table,[MSSQL-USER].SIBOWNERO, is missing.
  at
  com.ibm.ws.sib.msgstore.persistence.impl.Table.initialize(Table.
  java:287)
  at
  com.ibm.ws.sib.msgstore.persistence.impl.MEOuterOwnerTable.initi
  alize(MEOuterOwnerTable.java:80)
  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)
  ...
  In this scenario even though the tables exists in the
  database, the api used to fetch the tables do not return
  expected results.
  b) Exception observed when 'create tables' option is enabled
  while creating the messaging engine
  com.microsoft.sqlserver.jdbc.SQLServerException: There is
  already an object named 'MSSQL-USER' in the database.
  at
  com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabase
  Error(SQLServerException.java:216)
  at
  com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQ
  LServerStatement.java:1515)
  at
  com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStateme
  nt(SQLServerStatement.java:792)
  at
  com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doEx
  ecute(SQLServerStatement.java:689)
  ...
  at
  com.ibm.ws.sib.msgstore.persistence.impl.Table.createSchema(Tabl
  e.java:640)
  at
  com.ibm.ws.sib.msgstore.persistence.impl.Table.initialize(Table.
  java:297)
  ...
  In the above scenario, schema is created but when the check is
  made to see if the schema exists, it returns false, so an
  attempt is made to create the schema again which results in
  the above exception
  

Problem conclusion

• To solve the problem, code has been internally fixed to
  handle the schema names enclosed in [] appropriately so that
  both the query on schema existence and the query on tables in
  the schema of interest work as expected.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.9.  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 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

• R850 PSY

     UP