DB2 FOR LUW / DB2FORLUW / A50 - DB2

When db2iupdt command is executed sometimes you may get error as 
follows : 
 
... finished with return code 1. Output: DB2 installation is 
being initialized. 
 
DBI1264E  This program failed. Errors encountered during 
execution were 
      written to the installation log file. Program name: 
      db2iupdt. Log file name: /tmp/db2iupdt.log.*** 
 
 
In db2iupdt.log.*** : 
 
ERROR: An error occurred while configuring the instance 
"<instance name>". 
 
Configuring DB2 instances :.......Failure 
Updating global profile registry :.......Success 
 
Required steps: 
DBI20001E A DB2 instance could not be created as specified. A 
rollback of the instance creation has been 
performed. 
 
 
If we trace it using db2trc utility , in the db2iupdt.trc we can 
see : 
 
119548 ||||||||| 1 InstallProcess::executeLocal 90 -DATA-  , 
STRING = cd /db2/<instancename>;tar -cf sqllib.0000.tar sqllib 
1> /tmp/path 2> /tmp/path 
119568 ||||||| 1 Instance::updateToSD 10 -DATA-  , STRING = tar: 
sqllib/tmp/DB2VEND.STDIN.0.258.1458968357851579 could not be 
archived 
tar: sqllib/tmp/DB2VEND.STDOUT.0.258.1458968357851579 could not 
be archived 
 
DB2 needs to backup sqllib as part of instance update process, 
it failed to do so as the above tar command returned error for 
those sqllib/tmp/DB2VEND* files. 
 
This issue may also be seen when running db2iupgrade.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 10.5 Fix Pack 9 or higher                     * 
****************************************************************

Before updating or upgrading the instance, do the following: 
 
1. Completely stop the instance [do not unlink any files when 
the instance is active and running, that might lead to 
unexpected execution behavior.] 
2. Login as instance owner, then under sqllib/tmp 
 
ls -lu ./DB2VEND* 
ls -lc ./DB2VEND* 
 
file ./DB2VEND.STDIN.0.258.1458968357851579 
file ./DB2VEND.STDOUT.0.258.1458968357851579 
 
3. Run the following on all DB2VEND* files: 
 
 unlink DB2VEND.STDIN.0.258.1458968357851579 
 echo $? 
 unlink DB2VEND.STDOUT.0.258.1458968357851579 
 echo $?

First fixed in Db2 10.5 Fix Pack 9

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

05.05.2016
29.09.2017
29.09.2017

9.0.