When verifying an installation with a DB2® database,
it is important to check the Servant and Adjunct job logs to see whether
there are any error messages that might indicate problems accessing
the data store.
Procedure
- Ask your DB2 system administrator to check
the authorities that have been granted to ensure that you have not
granted more authority than necessary to any user ID. It
can be tempting to grant DB2 SYSADM authority to the J2C
authentication aliases in order to avoid possible problems with DB2 security during the configuration.
- Ask your DB2 system administrator to check
the storage group assignments and buffer pool usage. Incorrect
storage group assignment and buffer pool usage might not show up as
an error message in a log but might cause problems later. It is better
to resolve such problems now rather than when the system has been
handed over to people to use. For example, correcting storage groups
and VCATs is not easy after the tables and indexes have been used.
- Log in to the administrative console. See Starting and stopping the administrative console.
- In the administrative console, check that all the applications
are started, the messaging engines are started, and all the data sources
can be accessed using the Test Connection option. If any application has failed to start, look in the Servant
and Adjunct job logs for SEVERE or WARNING messages that provide detail
about the failure.
- If you see DB2 errors such as SQLCODE -204, in the administrative
console, set the correct schema name or currentSQLID value in the
custom properties section of the data sources. If the schema name
is not the same as the user ID in the J2C authentication aliases,
the SQL requests try to find tables qualified by the user ID in the
J2C authentication alias.
- If you see DB2 deadlock errors such as SQLCODE -913 Reason
Code 00C90088, check the RRULOCK DB2 parameter is set to YES as described in the Tuning checklist section.
What to do next
If all the SIBs have initialized correctly, and you do not
see any other errors related to opening JDBC connections, you can
continue to customize your configuration of
WebSphere® ESB.