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

DB2ICRT SHOULD REFUSE TO CREATE AN INSTANCE UNDER DB2DIR DURING FIXPAK
INSTALLATION.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
This problem occurs during fixpak installation where the 
install fails due to an error... 
Stopping DB2 Fault Monitor :.......Success 
ERROR: The DB2 installer detects that one or more DB2 instances 
"db2inst1" are still active. Stop the active instances and rerun 
the 
command again. 
 
Preparing the system :.......Failure 
This fix will avoid db2icrt to create an instance under 
DB2DIR.
Problem Summary:
Users Affected : All 
Problem Description : 
Install fixpak fails with an error indicating one or more 
instances are still active even if its not. 
Problem Summary : 
The problem occurs during fixpak installation where the install 
fails due to an error... 
Stopping DB2 Fault Monitor :.......Success 
ERROR: The DB2 installer detects that one or more DB2 instances 
"db2inst1" are still active. Stop the active instances and rerun 
the 
command again. 
 
Preparing the system :.......Failure
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in V9.5 FP6 (s100805)
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC68103 IC68104 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.03.2010
13.09.2010
13.09.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)