DB2 - Problem description
Problem IC86728 | Status: Closed |
IN AN EEE MULTI-PARITION ENVIROMENT, THE TEMP FILE "DB2LOOK_DUMP FILE" DOESN'T GET DELETED AFTER EXECUTION OF DB2LOOK COMMAND | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 and Fix Pack 8 * **************************************************************** | |
Local Fix: | |
Log in with the same user and remove the "DB2LOOK_DUMPFILE" manually. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix pack 8 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC89707 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.09.2012 22.04.2013 22.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7., 9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |