IBM Support

Database table changes for WebSphere Batch in WebSphere V8.5.x

Question & Answer


Question

What is the runtime update that requires new tables JOBCLASSREC, JOBLOGREC in WebSphere V8.5.0.0, V8.5.5.0, V8.5.5.1, V8.5.5.2 & V8.5.5.3?

Answer

When installing WebSphere V8.5.0.0 or migrating from V8.5.5.0 toWAS V8.5.5.1, V8.5.5.2 or V8.5.5.3, there is a runtime update that requires new tables JOBCLASSREC, JOBLOGREC. The JobScheduler server(s) and Endpoint server(s) depended on the update tables.

The following DDLs/SPUFIs are provided to assist with the table changes for the various databases that are supported with WebSphere Batch in V8.5.x. These files can be found in the WAS_HOME/util/Batch directory. Attempting to run WebSphere Batch without the necessary table changes will result in failures on the Job Scheduler during job processing and management.

Please note that if you upgrade to WebSphere V8.5.5.1, install the fix 8.5.5.1-WS-WAS-DistOnly-IFPI07496.zip (capacity leak detection/recovery) and it will create the following scripts under WAS_HOME/util/Batch/updateSchedulerDBForJobClassRecoveryDB2.ddl (there's also a Derby and Oracle version of the script provided). When you run the ddl that comes with the ifix a new table called CAPACITYDETECTION is created and add a column.


DB2 ULW ()
updateSchedulerDBForJobClassRecoveryDB2.ddl
UpdateLocalJobStatusConstraintDB2.ddl
AddLRSCHEDTablesDB2.ddl

Oracle
updateSchedulerDBForJobClassRecoveryOracle.ddl
UpdateLocalJobStatusConstraintOracle.ddl
AddLRSCHEDTablesOracle.ddl

Derby

updateSchedulerDBForJobClassRecoveryDerby.ddl
AddLRSCHEDTablesDerby.ddl

There is no script to update the local job status constraint for Derby. User can drop their existing Derby database and recreate it using the CreateLRSCHEDTableDerby.ddl to take advantage of the constraints update or create their own script.

All database updates must be done after the Compute Grid code is updated to the latest fix pack level, but before any application server that uses Compute Grid is started.

The following command can be issued from DB2 command line processor to run script to update DB2 database.

db2 -tf <file_name>.ddl

The following command can be used to update Derby database. Process this script in the ij command line processor.

java -Djava.ext.dirs=was_install_root/derby/lib -Dij.protocol=jdbc:derby:
org.apache.derby.tools.ij file_name.ddl

SQL*Plus can be used to run the script update for Oracle database.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Batch applications","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"8.5.5.3;8.5.5.2;8.5.5.1;8.5.5;8.5.0.2;8.5.0.1;8.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21661880