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

DB2_DEINSTALL LOG SHOWS IRRELEVANT MESSAGES IN THE POST UNINSTALL
RECOMMENDATIONS

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
After removing DB2 via db2_deinstall, the log file may show 
irrelevant messages in the post uninstall recommendation 
section. 
 
e.g. db2_deinstall -a -l /tmp/db2_deinstall.log 
 
Contents of /tmp/db2_deinstall.log: 
 
... 
Post Uninstall Recommendations 
------------------------------- 
... 
Optional steps: 
Some features, such as OS-based authentication, DB2 High 
Availability, and configuring the DB2 Advanced Copy Services 
(ACS) directory are available only in r 
oot installations. Also, reserving service names for TCP/IP 
remote connection or DB2 Text Search is available only in root 
installations. To enable these fea 
tures and abilities in non-root installations, run the db2rfe 
script as the root user with a configuration file. See 
/opt/IBM/db2/V9.7/instance/db2rfe.cfg fo 
r an example of the configuration file. 
 
To start using the DB2 instance "root", you must set up the DB2 
instance environment by sourcing db2profile (for Bourne or Korn 
shell) or db2cshrc (for C she 
ll) in the sqllib directory with the command ". 
$HOME/sqllib/db2profile" or "source   $HOME/sqllib/db2cshrc". 
$HOME represents the home directory of the DB2 
 instance. You can also open a new login window of the DB2 
instance user. 
 
After applying the fix, these irrelevant messages will not be 
displayed in the log file.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* After removing DB2 via db2_deinstall, the log file may show  * 
*                                                              * 
* irrelevant messages in the post uninstall recommendation     * 
*                                                              * 
* section.                                                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* e.g. db2_deinstall -a -l /tmp/db2_deinstall.log              * 
*                                                              * 
*                                                              * 
*                                                              * 
* Contents of /tmp/db2_deinstall.log:                          * 
*                                                              * 
*                                                              * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* Post Uninstall Recommendations                               * 
*                                                              * 
* -------------------------------                              * 
*                                                              * 
* ...                                                          * 
*                                                              * 
* Optional steps:                                              * 
*                                                              * 
* Some features, such as OS-based authentication, DB2 High     * 
*                                                              * 
* Availability, and configuring the DB2 Advanced Copy Services * 
*                                                              * 
* (ACS) directory are available only in r                      * 
*                                                              * 
* oot installations. Also, reserving service names for TCP/IP  * 
*                                                              * 
* remote connection or DB2 Text Search is available only in    * 
* root                                                         * 
* installations. To enable these fea                           * 
*                                                              * 
* tures and abilities in non-root installations, run the       * 
* db2rfe                                                       * 
* script as the root user with a configuration file. See       * 
*                                                              * 
* /opt/IBM/db2/V9.7/instance/db2rfe.cfg fo                     * 
*                                                              * 
* r an example of the configuration file.                      * 
*                                                              * 
*                                                              * 
*                                                              * 
* To start using the DB2 instance "root", you must set up the  * 
* DB2                                                          * 
* instance environment by sourcing db2profile (for Bourne or   * 
* Korn                                                         * 
* shell) or db2cshrc (for C she                                * 
*                                                              * 
* ll) in the sqllib directory with the command ".              * 
*                                                              * 
* $HOME/sqllib/db2profile" or "source  $HOME/sqllib/db2cshrc". * 
*                                                              * 
* $HOME represents the home directory of the DB2               * 
*                                                              * 
* instance. You can also open a new login window of the DB2    * 
*                                                              * 
* instance user.                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply IBM DB2 V9.7 Fix Pack 5.                               * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
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
Apply IBM DB2 V9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.07.2011
07.12.2011
07.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList