DB2常见问题解决

 

栏位 同步 永久链接 引用 跳转

DB2常见问题解决

 

1. DB2 SQL error code -964 while migrating data

• SQL0964C The transaction log for the database is full.

1.1Get SQLCODE: -964, SQLSTATE: 57011

You get this error message when migrating IBM TotalStorage Productivity Center data.
Problem
When migrating IBM TotalStorage Productivity Center data, you get this error message in the database installation log:

Instruction SQL : insert into t_stat_file_temp
SQLSTATE: 57011, Vendor error code: -964
DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011,
SQLERRMC: null
Explanation:

All space in the transaction log is being used.

If a circular log with secondary log files is being used, an
attempt has been made to allocate and use them. When the file
system has no more space, secondary logs cannot be used.

If an archive log is used, then the file system has not provided
space to contain a new log file.

The statement cannot be processed.
This indicates that the transaction log file is not large enough to handle the migration.

Action
To configure the size of the transaction log, modify the following parameters:

Log file size (4KB) (LOGFILSIZ) = 1024
Number of primary log files (LOGPRIMARY) = 3
Number of secondary log files (LOGSECOND) = 2

When connected to the database, under the DB2 command line processor, you can update the parameters using the following command:

update db cfg using <parameter> <value>

For example, to modify the LOGFILSIZ parameter, run this command:

update db cfg using logfilsiz 1024

解决方案：
To check the current configuration settings, run the following the command from a DB2 Command prompt:

1. db2 get db cfg

This error message is a result of running out of space in the transaction log. The transaction log configuration is set as:

db2 update db cfg for $DBNAME using logprimary 8
db2 update db cfg for $DBNAME using logsecond 16