PM11814: USING A SYNONYM FOR THE SCHEMA NAME IN THE DATA STORE SETTING FAILS TO RESOLVE THE THE ACTUAL NAME

Fixes are available

APAR status

Closed as program error.

Error description

When using an Oracle database, an attempt to use a schema
synonym for the datastore of a messaging engine results in
"IllegalStateException: CWSIS1532E: The table,
<synonym_name>.SIBOWNER, is missing.", and the messaging engine
will not start.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider for *
*                  IBM WebSphere Application Server Version    *
*                  6.1 and Version 7.0                         *
****************************************************************
* PROBLEM DESCRIPTION: When using a synonym as a schema name   *
*                      for a data store, the name is not       *
*                      found causing the messaging engine to   *
*                      fail to start.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The messaging engine datastore code looks for tables that
match the schema and table type provided. If the schema is a
synonym, then the table is not found even if it actually
exists because the datastore code is only looking for table
types 'table' and 'alias'. This results in the messaging
engine failing to start, with the following error message
being output:
"IllegalStateException: CWSIS1532E: The table,
<synonym_name>.SIBOWNER, is missing."

The problem is known to affect Oracle databases using
synonyms, and could affect other databases where synonyms are
configured.

Problem conclusion

The fix for this APAR adds a custom property that allows
the messaging engine code to find the table whether the schema
is real or a synonym.

The messaging engine custom property is as follows:
sib.msgstore.jdbcAllowSynonymUse=true

Details of setting messaging engine custom properties are
available in the "Setting tuning properties of a messaging
engine" section of the information center.

In addition to enabling the above custom property, it might be
necessary to set the following additional two custom
properties:
sib.msgstore.jdbcPerformColumnChecks=false
sib.msgstore.jdbcUseDeleteInsteadOfTruncateAtStartup=true

These properties are required in cases where vendor specific
limitations that prevent the JDBC driver from obtaining column
meta data for, or TRUNCATE, a table that is a synonym.
These limitations are known to apply to Oracle databases,
where the two additional custom properties must be set to
utilize synonyms with a data store.

The fix for this APAR is currently targeted for inclusion in fix
pack 6.1.0.33 and 7.0.0.13. 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
PM11814
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
2010-04-08
Closed date
2010-06-21
Last modified date
2010-08-31

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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM11814: USING A SYNONYM FOR THE SCHEMA NAME IN THE DATA STORE SETTING FAILS TO RESOLVE THE THE ACTUAL NAME

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R300 PSY

Document Information

Share your feedback

Need support?