db2iupgrade fails with DBI1205E
Priyanka Joshi 270003HTNX Comment (1) Visits (9192)
While working on a recent customer case, we encountered that db2iupgrade was failing with DBI1205E even if db2ckupgrade completed successfully earlier.
The customer was trying to upgrade from DB2 v10.1 to v10.5 but the error and resolution apply to all version upgrades.
The upgrade.log from db2iupgrade failure shows following error:
Setting default global profile registry variables :.......Success
The DBI1205E with return value "1" is a generic error. It is mostly related to problems with hostname and db catalog entries.
Command to run on OS (linux, Unix) :
Then check the hostname entry in db2nodes.cfg.
Both these hostnames should be identical. If it is not, please change the entry in db2nodes.cfg to the value returned by hostname or uname output.
This was the problem with our customer's case and after fixing db2nodes.cfg entry, the db2iupgrade was run successfully i.e. instance was upgraded.
2> In most cases, it is the db2nodes.cfg entry problem, but if it does not resolve an easy way to get around this upgrade issue is to :
Note : Please always keep a full offline backup before any upgrade trials.