Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC93931 Status: Closed

IN SOME CASES CALLING 'USER-SPECIFIED PROFILE' FROM DB2SUPPORT M
AY CAUSE SCRIPT TIME-OUT REGARDLESS OF THE SETTING OF 'TIMEOUT'.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Here you have an example of such behave. 
 
When one directly executes SQL statement in CLP: 
 
?db2 -v "select routineschema, routinename, specificname, 
fenced, owner, implementation, create_time, alter_time from 
syscat.routines order by routinename asc? 
 
time-out issue doesn't occur and statement returns some results, 
which is expected, but calling above command via user-specified 
profile(example below) won't return any results, and time-out 
appear. 
 
<COLLECTION> 
<NAME>USER SCRIPT: SQL TO RUN</NAME> 
<CMD>db2 -v "select routineschema, routinename, specificname, 
fenced, owner, implementation, create_time, alter_time from 
syscat.routines order by routinename asc" </CMD> 
<OUTFILE>outputFile</OUTFILE> 
<TIMEOUT>200</TIMEOUT> 
</COLLECTION> 
 
The issue is related to size of the output produces by CMD 
command.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Please See Error Description                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please See Error Description                                 * 
****************************************************************
Local Fix:
N/A
available fix packs:
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

Solution
Workaround
N/A
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC94545 IC94546 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.07.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList