DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011, SQLERRMC: null

Technote (FAQ)


Question

Receiving error during TADDM database migration

Cause

Getting the following error during database migration:

su - <taddm_user>

cd /<taddm home>/dist/bin

During the next step- getting the following error:

./db-upgrade.sh ../etc/schema_upgrade/7.1.2/DB210_ModSchema.sql > /home/cmdb1/IGA1-0316.../migrating/Db210_modShcmea.out
Db210_modSchema.out
igalab42# more Db210_modSchema.out
Run ../etc/schema_upgrade/5.1.1.3/DB210_ModSchema.sql for user cmdb1
SQL = INSERT INTO CHANGE_HISTORY_TABLE (ATTRIBUTE_NAME, ID, WHEN_CHANGED, OLD_VALUE_DISPLAY_NAME, NEW_VALUE_DISPLAY_NAME, OBJECT_DISPLAY_NAME, NEW_VALUE, ACTUAL_CHANGE_TYPE, WHA
T_CHANGED, DISCOVERY_RUN_ID, OBJECT_ID, HANDLED_BY_STATE_MANAGER, CMDBSOURCE_X, OLD_VALUE, CLASS_NAME, PARENT_IDS, TYPE_OF_EVENT) SELECT ATTRIBUTE_NAME, ID, WHEN_CHANGED, OLD_VA
LUE_DISPLAY_NAME, NEW_VALUE_DISPLAY_NAME, OBJECT_DISPLAY_NAME, NEW_VALUE, ACTUAL_CHANGE_TYPE, WHAT_CHANGED, DISCOVERY_RUN_ID, OBJECT_ID, HANDLED_BY_STATE_MANAGER, CMDBSOURCE_X,
OLD_VALUE, CLASS_NAME, PARENT_IDS, TYPE_OF_EVENT FROM B_CHANGE_HISTORY_TABLE
DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011, SQLERRMC: null


Answer

This means the transaction log size on the database server side is too small


The size of "LOGPRIMARY" must be increased.

db2 get db cfg for <cmdb> | grep LOGP"

(multiply whatever you get by at least x 3 )

"db2 update db cfg for <cmdb> using LOGPRIMARY <newvalue>"

Re-do the upgrade

Product Alias/Synonym

taddm
5724n5500

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Application Dependency Discovery Manager

Software version:

All Versions

Operating system(s):

AIX

Reference #:

1298630

Modified date:

2011-02-23

Translate my page

Machine Translation

Content navigation