JnextPlan fails with the database message "The transaction log for the database is full."

You receive a message from JnextPlan which includes the following database message (the example is from DB2®, but the Oracle message is very similar):

The transaction log for the database is full.

The JnextPlan message is probably the general database access error message AWSJDB801E.

Cause and solution:

The problem is probably caused by the number of Job Scheduler instances that JnextPlan needs to handle. The default database transaction log files cannot handle more than the transactions generated by a certain number of Job Scheduler instances. In the case of DB2 this number is 180 000; in the case of Oracle it depends on how you configured the database. If JnextPlan is generating this many instances, you need to change the log file creation parameters to ensure more log space is created. You might also need to increase the Java™ heap size on the application server. See "Scalability" in the IBM® Workload Scheduler: Administration Guide for a full description of how to perform these activities.