home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91941 Status: Geschlossen

DB2IUPGRADE IS FAILING DUE TO DUPLICATE MATCHING RECORDS IN /ETC/SERVICES

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
db2iupgrade is failing due to duplicate matching  records in 
/etc/services 
 
A  db2iupgrade -d    debug  trace  shows : 
 
33002  |||||||\ 1 iPrepareServicesRecord EXIT Wed Apr 17 
17:07:30 2013 --  , INT = 0 
33003  ||||||| 1 IServiceFile::addService 50 -DATA-  , INT = 
-1879047688 
33004  ||||||| 1 IServiceFile::addService 99 -ERROR-  , STRING = 
Duplicate matching record found 
33005  |||||||/ 1 IServiceFile::setLastEcfError ENTRY Wed Apr 17 
17:07:30 2013 --  , 
33006  |||||||| 1 IServiceFile::setLastEcfError 10 -DATA-  , INT 
= -1879047688 
33007  |||||||\ 1 IServiceFile::setLastEcfError EXIT Wed Apr 17 
17:07:30 2013 --  , INT = 0 
33008  ||||||\ 1 IServiceFile::addService EXIT Wed Apr 17 
17:07:30 2013 --  , INT = 5601 
33009  |||||\ 1 IServiceFile::addService2 EXIT Wed Apr 17 
17:07:30 2013 --  , INT = 5601 
33010  ||||\ 1 ITCP::commitFCM EXIT Wed Apr 17 17:07:30 2013 -- 
, INT = 5601 
33011  |||| 1 Instance::commit 90 -ERROR-  , DATA = 00 00 15 e1 
33012  |||\ 1 Instance::commit EXIT Wed Apr 17 17:07:30 2013 -- 
, INT = 5601 
33013  ||| INFORMATION-1 UREMPPNode::initializeSettings 70 -- 
An error occurred while configuring the instance "db2inst1". 
 
 
Duplicate  records  similar to following could be observed in 
/etc/services 
 
 /etc/services shows  duplicate  ports : 
 
comm_serv1       5616/tcp 
DB2_db2inst1      5617/tcp 
DB2_db2inst1_1    5618/tcp 
DB2_db2inst1_2    5619/tcp 
DB2_inst1_END  5620/tcp 
 
comm_serv2       5616/tcp 
DB2_db2inst2      5617/tcp 
DB2_db2inst2_1    5618/tcp 
DB2_db2inst2_2    5619/tcp 
DB2_db2inst2_END  5620/tcp 
 
/etc/services verification is not new to DB2, but it was changed 
in a significant way in 10.1 .  In 9.5 and 9.7 these checks 
exist for new instance creation (not for upgrades), and are only 
performed if  GUI is used or silent installation method is used. 
Neither command line installation, nor upgrades, would perform 
this environmental validation in 9.5 and 9.7. 
 
In 10.1, due to a number of serious customer issues where 
incorrect service names and/or ports lead to other issues and 
difficult to diagnose problems for different  customers 
production environments, these checks were made to common one 
and now it  affects both instance upgrade and new instance 
creation. 
 
After close review it's decided that shared /etc/services file 
with duplicates is a valid and useful architecture for an LPAR'd 
environment.  So, this defect is created to  fix the issue as 
needed to get  migrations to 10.1 succeed without  failure due 
to duplicate records.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running db2iupgrade                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please see the Error Description to find the details.        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Users can upgrade to DB2 Version 10.1 fix pack 3 or higher   * 
* to avoid this defect                                         * 
****************************************************************
Local-Fix:
Update  the /etc/services to make each record with unique name 
and port number.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First Fixed in DB2 Version 10.1 fix pack 3
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95323 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.04.2013
07.10.2013
07.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList