DB2 - Problem description
Problem IC94546 | 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 / A50 - 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 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V105FP4. * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
From V105FP4, db2support -pf with large output will output the results in the output file. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.08.2013 03.03.2014 03.03.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 | |
10.5.0.4 |