Troubleshooting
Problem
DB2 instance upgrade may fail due to the duplicate ports defined in /etc/services file
Symptom
During db2iupgrade course, a general error regarding the instance configuration may be thrown out.
ERROR: An error occurred while configuring the instance "db2inst1".
Configuring DB2 instances :.......Failure
Cause
This is a general error indicating that instance configuration failure. To identify the root cause, a trace for db2iupragde needs to be collected by using the command "db2iupgrade -d <instname> > debug.out". A trace file with the name db2iupgrade.trc.<db2iupgrade PID> is generated.
Diagnosing The Problem
From the trace file, locate the following errors:
81742 ||||||| 1 IServiceFile::addService 50 -DATA- , INT = -1879047688
81743 ||||||| 1 IServiceFile::addService 99 -ERROR- , STRING = Duplicate matching record found
81751 |||| 1 Instance::commit 90 -ERROR- , DATA = 00 00 15 e1
81753 ||| INFORMATION-1 UREMPPNode::initializeSettings 70 -- An error occurred while configuring the instance "db2inst1".
Check the /etc/services file. Here is a sample /etc/services file in which DB2 FCM ports(30001,30002) are duplicate with pago-services1 and pago-services2 ports.
pago-services1 30001/tcp # Pago Services 1
pago-services1 30001/udp # Pago Services 1
pago-services2 30002/tcp # Pago Services 2
pago-services2 30002/udp # Pago Services 2
DB2_db2inst1 30000/tcp
DB2_db2inst1_1 30001/tcp
DB2_db2inst1_2 30002/tcp
DB2_db2inst1_END 30003/tcp
Resolving The Problem
Manually remove the duplicate DB2 ports entries and assign other port numbers or entirely remove them and db2iupgrade can automatically assign the correct port numbers.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21614308