home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC95264 Status: Closed

SQL1096N WHEN WE TRY TO STOP/START THE DB2 INSTANCE VIA THE DB2SYSTRAY
ICON.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If you have several DB2 instances and one of them is a DB2 
client instance ( db2icrt DB2_01 -client ), you may receive the 
following error if you try to stop/start one of DB2 instance by 
using its db2systray icon while the system environment variable 
DB2INSTANCE is set to the DB2 client instance  ( Control Panel - 
System -Advanced system settings - Environment variables - 
System variable ) : 
SQL1096N the command is not valid for this node type.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW on Windows                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP4 or above                             * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
The problem was first fixed in DB2 10.1 FP4
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95536 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
28.07.2014
28.07.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList