|
Problem IC72923
|
Status: Geschlossen |
DB2IUPGRADE FAILS WITH DBI1281E BECAUSE AWK FAILS TO PARSE A ROW IN THE GLOBAL REGISTRY |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
If the global registry contains unprintable characters,
db2iupgrade may fail with DBI1281E.
e.g. After running db2iupgrade
DBI1281E The database manager configuration file could not be
initialized.
Viewing the debug output will show the following:
+ /opt/IBM/db2/V9.7/instance/db2iexec db2inst1
/opt/IBM/db2/V9.7/instance/db2idbm db2inst1 /home/db2inst1
db2iadm1 1 SERVER /tmp/db2icrt.tmp1.970980
awk: 0602-562 Field $(V,XXX,YYYYY,<unprintable
characters>,ZZZZZZ,) is not correct.
The input line is XX.
The source line is 1.
/opt/IBM/db2/V9.7/instance/db2idbm: test: 0402-017 Specify a
parameter with this command.
After applying the fix, db2iupgrade will complete without any
errors from db2idbm. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* UNIX *
****************************************************************
* PROBLEM DESCRIPTION: *
* If the global registry contains unprintable characters, *
* *
* db2iupgrade may fail with DBI1281E. *
* *
* *
* *
* e.g. After running db2iupgrade *
* *
* *
* *
* DBI1281E The database manager configuration file could not *
* be *
* initialized. *
* *
* *
* *
* Viewing the debug output will show the following: *
* *
* *
* *
* + /opt/IBM/db2/V9.7/instance/db2iexec db2inst1 *
* *
* /opt/IBM/db2/V9.7/instance/db2idbm db2inst1 /home/db2inst1 *
* *
* db2iadm1 1 SERVER /tmp/db2icrt.tmp1.970980 *
* *
* awk: 0602-562 Field $(V,XXX,YYYYY,<unprintable *
* *
* characters>,ZZZZZZ,) is not correct. *
* *
* The input line is XX. *
* *
* The source line is 1. *
* *
* /opt/IBM/db2/V9.7/instance/db2idbm: test: 0402-017 Specify a *
* *
* parameter with this command. *
* *
* *
* *
* After applying the fix, db2iupgrade will complete without *
* any *
* errors from db2idbm. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fix pack 4. *
**************************************************************** |
| Local-Fix: |
Modify db2idbm as below:
NUMINST=`${DB2DIR?}/bin/db2greg -dump | /usr/bin/grep -v ^V \ |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 4 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 30.11.2010
05.05.2011
05.05.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP4
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.4
|
 |
