Installing > Installing a Development Environment > Installing prerequisite products > Installing a DBMS > IBM DB2 database

Configuring for circular transaction logging

When you use a database with circular transaction logging enabled, certain transactions can exceed the available log file space and fail. To avoid this issue, either use archive logging or set the available log size and quantity appropriately until it meets the needs of the transaction.

About this task

A common point for this failure is when the prepare.application.data Ant target is running, as this target publishes all the CER rule sets on the system. This Ant target is typically run after a clean database build. If the log is too small, it can result in an SQLCODE -964 error.

You can use the following example to help you to increase the DB2 log file size and quantity. The exact amount of log file storage that is required varies from system to system. For more information about increasing the number and size of the log files available, see the specific documentation for your database.

Tasks

1. Open a command prompt and enter db2cmd.

2. Enter the following command:

   db2 connect to db_name user db_user_name using db_password
   

   Where db_name, db_user_name, db_password are the credentials of the database.

3. Enter the following commands:

   db2 update db cfg for db_name using logfilsiz log_file_size 
   

   db2 update db cfg for db_name using logprimary primary_log_files 
   

   db2 update db cfg for db_name using logsecond secondary_log_files
   

   Where the temporary values are as follows:
   • The log file size. Set log_file_size to 1024.
   • The number of primary log files. Set primary_log_files to 50.
   • The number of secondary log files. Set secondary_log_files to 100.

4. Restart the database by entering the following commands:

   db2stop
   db2start
   

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.