DB2 - Problembeschreibung
Problem IC89707 | Status: Geschlossen |
IN AN EEE MULTI-PARITION ENVIROMENT, THE TEMP FILE "DB2LOOK_DUMP FILE" DOESN'T GET DELETED AFTER EXECUTION OF DB2LOOK COMMAND | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
When DB2LOOK with option '-l' is run in an EEE environment with multiple physical partitions, it will create a temp file "DB2LOOK_DUMPFILE" under <sqllib>/tmp/ directory with "-rw-r-----" permissions. This file is not deleted at the end of the execution and also block other users trying to execute the db2look command with '-l' option. Example: 1. User A executes db2look as below: db2look -d SAMPLE -a -l 2. User B tries to run db2look command and it will fail with the following permission error: db2look -d SAMPLE -a -l -- Generate statistics for all creators -- This CLP file was created using DB2LOOK Version "9.7" -- Timestamp: Thu 20 Sep 2012 02:36:26 PM EDT -- Database Name: SAMPLE -- Database Manager Version: DB2/LINUXX8664 Version 9.7.5 -- Database Codepage: 1208 . . sh: /home/hotel54/sqllib/tmp/db2look_dumpfile: Permission denied | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW version v10.1 fixPack 3 * **************************************************************** | |
Local-Fix: | |
Log in with the same user and remove the "DB2LOOK_DUMPFILE" manually. | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Upgrade to DB2 LUW version v10.1 fixPack 3 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.01.2013 12.11.2013 12.11.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |