Some limitations apply to configurations of the event database
using certain database software.
Refer to the following table to see which limitations might apply
to your environment.
Table 1. Event database limitationsDatabase type |
Limitations |
Oracle |
The Oracle 10g JDBC thin driver imposes some size restrictions
for string values if you are using a Unicode character set. This can
result in an Oracle ORA-01461 error when events containing large values
(such as a long message attribute) are stored in the event database.
For more information about this restriction, refer to the Oracle 10g
documentation.
To avoid this problem, use the Oracle 10g OCI
driver or the Oracle 9i thin driver.
- Oracle database software treats a blank string as a NULL value.
If you specify a blank string as an event attribute value, that string
is converted to a NULL when it is stored in an Oracle event database.
|
Informix® |
- The JDBC 3.0 driver (or later) is required. Previous versions
of the JDBC driver do not provide full support for the required XA
transactions.
- The database configuration and removal scripts generated by the configEventServiceInformixDB administrative
command require the dbaccess command in order to run SQL scripts.
This command might be available only on the Informix server. Therefore, if the Informix server is on a different
system from the WebSphere® server,
the database configuration scripts might need to be copied to the Informix server and run locally.
|
SQL Server |
- The SQL Server database must be configured to use mixed authentication
mode. Trusted connections are not supported.
- The XA stored procedures must be installed. These stored procedures
are provided with the JDBC driver from Microsoft® Corporation.
- The sqljdbc.dll file must be available in a directory specified
on the PATH statement. This file is provided with the JDBC driver
from Microsoft Corporation.
- The Distributed Transaction Coordinator (DTC) service must be
started.
|