IBM BPM, V8.0.1, All platforms > Troubleshooting and support > Troubleshooting the z/OS installation and configuration
IBM BPM configuration errors
If you experience a problem with one of the configuration tasks then there will be three main sources of information about the problem.
- The error messages issued by the task
- Error messages in the WebSphere dmgr or application server job logs. If you are federating a node you might also find messages in the node agent job logs
- Log files in the UNIX file system
Wherever possible, the cause and solution to each problem is also documented with the symptoms. The problems described here were experienced when starting the server after completing the installation procedure for IBM BPM. In the examples of error messages, the messages have been made easier to read by changing the places where line breaks occur. Therefore, if you see these errors in your system the messages will have a slightly different layout.
Failure in loading T2 native library db2jcct2zos
This error can occur when using the DB2 Universal Driver connector, and WebSphere Application Server cannot load some external DB2 modules from SDSNLOAD or SDSNLOD2.DataSource has a null RelationalResourceAdapter property
The error shown in the example in this topic is caused by a redundant data source that is left behind after running the augmentation job. You can safely delete this data source by using the WebSphere administrative console. Be careful not to delete the JDBC provider that has a very similar name.SQLCODE = -471
This error can occur when the Universal Driver has not been properly configured in a DB2 system.SQL code -204 and -516
This error can be caused if the currentSchema property does not match the schema name of the tables and indexes created. The error messages show the JCA authentication alias that is being used.Repeated SIB messages about acquiring and losing locks
This error can occur after correcting the DB2 Universal Driver configuration and restarting the server. The error messages are repeated continuously in the adjunct region.bpeconfig.jacl: An error occurred installing TaskContainer
A bpeconfig.jacl error normally occurs if you enter invalid input. The example below is displayed if you make a mistake entering group names and if you use the delete key instead of the backspace key to make a correction. In the example in this topic, the input appears to be MKHTSMG, but the value that was entered contained invalid characters "MKSMG[D[D[D[D[CHTSMG".