IBM Support

"db2val -o” returns DBI1334E RC = 2 on validating an installation image after the install is completed

Technical Blog Post


Abstract

"db2val -o” returns DBI1334E RC = 2 on validating an installation image after the install is completed

Body

Problem : 
 

In a couple of instances, we have noted that customers tried to run "db2val -o" on install images after actual install and the db2val failed with DBI1334E RC = 2 in "Task 2” (can be seen in db2val output) 


The db2val log may show the error as follows :

Installation file validation for the DB2 copy installed at "/opt/ibm/db2/V11.1" starts.

Task 1: Validating Installation file sets.
Status 1 : Success

Task 2: Validating installation image inside the install path.
Files are missing from the image "/opt/ibm/db2/V11.1/sd"
Status 2 : Failure


Task 3: Validating embedded runtime path for DB2 executables and libraries.
Status 3 : Success

Task 4: Validating the accessibility to the installation path.
Status 4 : Success

Task 5: Validating the accessibility to the /etc/services file.
Status 5 : Success

DBI1334E Installation file validation failed for the DB2 copy installed at /opt/ibm/db2/V11.1. Reason code = 2.



Reson code = 2 means, the installation image inside the install path has missing files.



Cause : 

1> Consider as example that the installation image is extracted in the default 
install path /opt/ibm/db2/V11.1/sd. 

 

2> There will be a .savedImageChksums file (/opt/ibm/db2/V11.1/sd/cfg/.savedImageChksum) which gets created during install in the install_path/sd directory. This file contains checksums of all the files stored in the install path and during validation (db2val -o) the checksums are compared (actual checksum to the ones recorded in this .savedImageChksum file)  and if they do not match it is reported as DBI1334E RC = 2 in Task 2. 

 

The expected files in install path are only the ones listed below:

drwxr-xr-x 6 bin bin 4096 Jul 11 09:23 db2

-r-xr-xr-x 1 bin bin 5306 Jul 11 09:23 db2ckupgrade

-r-xr-xr-x 1 bin bin 5259 Jul 11 09:22 db2_deinstall

-r-xr-xr-x 1 bin bin 5129 Jul 11 09:23 db2_install

-r-xr-xr-x 1 bin bin 5093 Jul 11 09:22 db2ls

-r-xr-xr-x 1 bin bin 5111 Jul 11 09:22 db2prereqcheck

-r-xr-xr-x 1 bin bin 5111 Jul 11 09:22 db2setup

-r-xr-xr-x 1 bin bin 5147 Jul 11 09:23 installFixPack

 

 3> But in our customer cases, we also had an extra file “db2setup.trc.jtrc” file in there which was the last one checked before the error was reported (we found it out from db2val traces). 

 

4> So it seems the customer had some sort of tracing enabled at some stage during the install and a trace file has been created because of this - db2setup.trc.jtrc. Understandably, that trc file has probably been recreated/appended at some stage since and so when db2val checked it the chksum on it was different than the saved one. And hence the error. 

 

 

Solution : 

The file db2setp.trc.jtrc, is not part of the install image so we can safely remove it and its references from the .savedImageChksum file. 

 

Steps :

1> Go to /opt/ibm/db2/V11.1/sd/cfg/ or /opt/ibm/db2/V11.1/cfg/

2> Edit the file .savedImageChksum (open in edit mode). 

3> Remove/delete the line/s which refer to db2setup.trc.jtrc file and save.

4> Also delete/remove the actual file - db2setup.trc.ctrc. 

Retry the db2val command  and the problem should be fixed now. 

 

 

References : 

DBI1334E Installation file validation failed for the DB2 copy installed at installation-location. Reason code = reason-code.
https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.messages.dbi.doc/doc/mdbi01334e.html 
 

[{"Business Unit":{"code":"BU029","label":"Data and AI"}, "Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm13285951