|
Problem IC95447
|
Status: Closed |
DB2IUPGRADE/DB2IUPDT MAY CAUSE OPERATION TO FAIL WITH "DBI1250E APPLICATIONS ARE STILL USING THE INSTANCE" |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Running db2iupgrade/db2iupdt to complete a upgrade, fixpak or
special build
installation may return
DBI1250E Applications are still using instance <instance name>
despite the fact that the instance was shutdown and it's
proven that there are no db2 processes active anymore.
This issue may be caused by a too low timeout value (10 seconds)
currently used in function "chk_instance_stopped" in the
db2iutil script which is called by db2iupdt. It's likely to be
seen when updating a large DPF instance (large = number of
partitions in db2nodes.cfg).
If this issue applies in your environemnt run the db2gcf utility
standalone:
$ timex <DB2INSTALLPATH>/bin/db2gcf -i <instance> -s -t 10 -L
and check if the command returns:
db2gcf Error : GCF Module function failed.
and needs more than 10 seconds to complete.
Then you are affected by this APAR. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to 10.5.0.3 *
**************************************************************** |
| Local Fix: |
Can edit the <DB2 Installation>/instance/db2iutil and remove the
-t 10 from the call to db2gcf command checks. |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem Fixed In 10.5.0.3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
04.03.2014
04.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
|
|
