IBM Support

Tracing the db2relocatedb or db2inidb utility when you receive an error such as SQL10007N

Troubleshooting


Problem

Sometimes the db2relocatedb or db2inidb utility will not be returning an helpful error message and the db2diag.log will not either.

Symptom

For example, you could be getting:

db2relocatedb -f db2inidb1.cfg
SQL10007N Message "0" could not be retrieved. Reason code: "4".

Cause

db2relocatedb and db2inidb do many things in the background and by default the full steps and messages are not displayed.

Resolving The Problem

If you are encountering an error using those utilities and the error message is not meaningful try generating a specific log file with those utilities by setting the DB2RELOCATEDB_LOGFILE environment variable. Example:

export DB2RELOCATEDB_LOGFILE=/home/db2inst1/relocate.log (Unix)

set DB2RELOCATEDB_LOGFILE=C:\temp\relocate.log (Windows)

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data movement - db2relocatedb","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.8;9.7;9.5;10.1;10.5;11.1","Edition":"Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21991270

Page Feedback