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 IC69125 Status: Geschlossen

SOME DATA NOT COLLECTED BY DB2COS / DB2FODC SCRIPTS ON SOME LINUX
DISTRIBUTIONS DUE TO ARGUMENTS TO SORT

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The collection of some data in the db2cos / db2fodc script may 
not work for all Linux distributions due to different 
requirements in handling arguments to "sort". 
 
The current scripts include a call to sort such as: 
sort +5 -rn 
 
That syntax will work on SUSE Linux; however, some distributions 
(such as Redhat) require the "-k" option to be included so that 
the syntax would instead be: 
sort -k +5 -rn 
 
 
The result of this is that some data may not be collected (such 
as ps output): 
$ cat pself.fullstack 
 11:33:02 up 1 day, 12:09,  6 users,  load average: 128.84, 
126.31, 119.53 
sort: open failed: +5: No such file or directory
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Linux users on Redhat                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The collection of some data in the db2cos / db2fodc script   * 
* may not work for all Linux distributions due to different    * 
* requirements in handling arguments to "sort".                * 
*                                                              * 
* The current scripts include a call to sort such as:          * 
* sort +5 -rn                                                  * 
*                                                              * 
* That syntax will work on SUSE Linux; however, some           * 
* distributions (such as Redhat) require the "-k" option to be * 
* included so that                                             * 
* the syntax would instead be:                                 * 
* sort -k +5 -rn                                               * 
*                                                              * 
*                                                              * 
* The result of this is that some data may not be collected    * 
* (such as ps output):                                         * 
* $ cat pself.fullstack                                        * 
* 11:33:02 up 1 day, 12:09,  6 users,  load average: 128.84,   * 
* 126.31, 119.53                                               * 
* sort: open failed: +5: No such file or directory             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 4 or later or another        * 
* release of DB2 that contains the fix.                        * 
****************************************************************
Local-Fix:
On impacted distributions, manually collect impacted data.
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 Version 9.7 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC69414 IC69415 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.06.2010
29.04.2011
29.04.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP4
Problem behoben lt. FixList in der Version
9.7.0.4 FixList