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 IT21221 Status: Closed

LIST INDOUBT TRANSACTIONS MAY NOT RETURN TO PROPMT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
"l" option in a "db2 list indoubt transactions with prompting" 
command session may not come back to prompt. 
 
Here is a problem reproducible scenario. 
 
1. Create/have 10 or more indoubt transactions on a server. 
2. Run "db2 list indoubt transactions with prompting" 
3. Then follow below at the prompt. 
   3.1)  Type "r 1" then [Enter]  (rollback 1st one) 
   3.2)  Type "y" for confirmation. 
   3.3)  Type "l" (list transactions) and hit [Enter] 
   3.4)  continue "r X", "y" and "l" five times 
   3.5)  5th "l" will not come back to prompt
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 9.                           * 
****************************************************************
Local Fix:
Do not use "l" option in a "db2 list indoubt transactions with 
prompting" command session.
Solution
Problem was first fixed in DB2 UDB Version 10.5 FixPack 9.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.06.2017
27.09.2017
27.09.2017
Problem solved at the following versions (IBM BugInfos)
9.0.
Problem solved according to the fixlist(s) of the following version(s)