Use this task to diagnose problems that are caused by your data store configuration.
Why and when to perform this task
The following problems depend on the database that you use with your
data store configuration and the
level of that database:
- Examine this section if your messaging engine uses
an Oracle 9i database for its data store and
your messaging engine fails to start. If the messaging engine fails
with the following message, where XXXXXXXX is
the schema for the table, ensure that your Oracle installation is at 9.2.0.4,
or higher:
CWSIS1530E: The data type, 1,111, was found instead
of the expected type, 2,004, for column, LONG_DATA, in table, XXXXXXXX.SIB000.
- Examine this section if your messaging engine uses
a Sybase database for its data store. When you create your Sybase server:
- Ensure that you create the database server with a page
size of at least 4k.
- Ensure that you set the lock scheme property
on your server to the value datarows. This avoids the possibility
of a deadlock on the data store tables.
- Examine this section if your messaging engine uses
an Informix database for its data store and
the messaging engine is unable to
access its data store. When you configure
your messaging engine to use an Informix
database, ensure that you specify the schema name in lower case.
For a full description of the configuring procedure, refer to Configuring a messaging engine to use a data source.