suche 36x36
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 IT24218 Status: Closed

CLP CRASHES WITH DB21018E

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Calling stored procedure located on DB2 z/OS from V11.1 Fixpack 
2 client crashes the DB2 CLP. 
Affects only v11.1 FP2. Crash does not occur on v11.1 FP1. No 
diagnostics generated, nothing in db2diag.log and no trap files 
created. 
 
db2 connect to sample user db2inst1 
Enter current password for db2inst1: 
 
   Database Connection Information 
 
Database server        = DB2 z/OS 11.1.5 
SQL authorization ID   = DB2INST1 
Local database alias   = SAMPLE 
 
db2 call SYSPROC.ADMIN_INFO_SSID(?,?,?) 
DB21018E  A system error occurred. The command line processor 
could not continue processing.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in v11.1 M3 FP3. Apply fix to the system where   * 
* DB2 CLP receives the error.                                  * 
****************************************************************
Local Fix:
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First fixed in v11.1 M3 FP3. Apply fix to the system where DB2 
CLP receives the error.
Workaround
See LOCAL fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.02.2018
15.03.2018
15.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)