Use this task to solve problems with the process choreographer database and data source.
Why and when to perform this task
The business process container needs a database. Without the database, process choreographer and enterprise applications containing business processes will not work.2004-06-25-15.53.42.078000 Instance:DB2 Node:000 PID:2352(db2syscs.exe) TID:4360 Appid:*LOCAL.DB2.027785142343 data management sqldEscalateLocks Probe:4 Database:BPEDB ADM5503E The escalation of "10" locks on table "GRAALFS .ACTIVITY_INSTANCE_T" to lock intent "X" has failed. The SQLCODE is "-911"Increase the LOCKLIST value. For example to set the value to 500, enter the following DB2 command:
db2 UPDATE DB CFG FOR BPEDB USING LOCKLIST 500This can improve performance significantly.
ERROR XJ040: Failed to start database 'C:\WebSphere\AppServer\ProcessChoreographer\BPEDB', see the next exception for details. ERROR XSDB6: Another instance of Cloudscape may have already booted the database C:\WebSphere\AppServer\ProcessChoreographer\BPEDB.you must stop your WebSphere application server before using these tools because only one application can access the Cloudscape database at a time.
The 'ALTER TABLE' command is not allowed within a multi-statement transaction in the 'databaseName' databaseThis can happen after you have installed a new PTF level that requires the database to be migrated. Start the Sybase isql command program, enter the following commands:
use master go sp_dboption databaseName, "ddl in tran", true gowhere databaseName is the name of your database.