|
Problem IC75443
|
Status: Closed |
DB2 CLP OPTION -L IS NOT WORKING WITH CALL STATEMENTS WHILE PRINTING THE END TIME IN THE HISTORY FILE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
CLP option -l is not working with call statements while printing
the end time in the history file.
For example:-
Assuming PROC1() is known, and PROC2() is missing stored
procedure. The call.sql script file contains following lines:
connect to sample;
call proc1(?);
call proc2(?);
connect reset;
After executing of the following command on v97:
db2 -tvf call.sql -l l.txt -z z.txt
file l.txt will contain following:
03/24/2011 06:34:24 connect to sample
03/24/2011 06:34:26 DB20000I The SQL command completed
successfully.
03/24/2011 06:34:26 call proc1(?)
03/24/2011 06:34:26 call proc2(?)
03/24/2011 06:34:26 connect reset
03/24/2011 06:34:26 DB20000I The SQL command completed
successfully.
Using the -l option, the completion status of the call
statements are not written to the history file.
Should expect to see the following:
03/24/2011 06:00:05 connect to sample
03/24/2011 06:00:06 DB20000I The SQL command completed
successfully.
03/24/2011 06:00:06 call proc1(?)
03/24/2011 06:00:06 DB20000I The SQL command completed
successfully.
03/24/2011 06:00:06 call proc2(?)
03/24/2011 06:00:06 SQL0440N No authorized routine named
"PROC2" of type "PROCEDURE" having compatible arguments was
found. SQLSTATE=42884
03/24/2011 06:00:06 connect reset
03/24/2011 06:00:06 DB20000I The SQL command completed
successfully |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users running DB2 v9.7 FP4 or earlier. *
****************************************************************
* PROBLEM DESCRIPTION: *
* CLP option -l is not working with call statements while *
* printing *
* the end time in the history file. *
* *
* *
* *
* For example:- *
* *
* Assuming PROC1() is known, and PROC2() is missing stored *
* *
* procedure. The call.sql script file contains following *
* lines: *
* *
* *
* connect to sample; *
* *
* call proc1(?); *
* *
* call proc2(?); *
* *
* connect reset; *
* *
* *
* *
* After executing of the following command on v97: *
* *
* *
* *
* *
* *
* db2 -tvf call.sql -l l.txt -z z.txt *
* *
* *
* *
* file l.txt will contain following: *
* *
* *
* *
* *
* *
* 03/24/2011 06:34:24 connect to sample *
* *
* 03/24/2011 06:34:26 DB20000I The SQL command completed *
* *
* successfully. *
* *
* *
* *
* 03/24/2011 06:34:26 call proc1(?) *
* *
* *
* *
* 03/24/2011 06:34:26 call proc2(?) *
* *
* *
* *
* 03/24/2011 06:34:26 connect reset *
* *
* 03/24/2011 06:34:26 DB20000I The SQL command completed *
* *
* successfully. *
* *
* *
* *
* Using the -l option, the completion status of the call *
* *
* statements are not written to the history file. *
* *
* Should expect to see the following: *
* *
* *
* *
* 03/24/2011 06:00:05 connect to sample *
* *
* 03/24/2011 06:00:06 DB20000I The SQL command completed *
* *
* successfully. *
* *
* *
* *
* 03/24/2011 06:00:06 call proc1(?) *
* *
* 03/24/2011 06:00:06 DB20000I The SQL command completed *
* *
* successfully. *
* *
* *
* *
* 03/24/2011 06:00:06 call proc2(?) *
* *
* 03/24/2011 06:00:06 SQL0440N No authorized routine named *
* *
* "PROC2" of type "PROCEDURE" having compatible arguments was *
* *
* found. SQLSTATE=42884 *
* *
* *
* *
* 03/24/2011 06:00:06 connect reset *
* *
* 03/24/2011 06:00:06 DB20000I The SQL command completed *
* *
* successfully *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FP5. *
**************************************************************** |
| Local Fix: |
Not available |
| available fix packs: |
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
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 31.03.2011
19.12.2011
19.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
