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

CLI RUNNING INSIDE THE ENGINE REPORTS EINVAL (22) "INVALID
ARGUMENT"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The problem only happens on HP UNIX. 
 
When you connect to database and run the evmon_upgrade_tables 
procedure, or query a DRDA nickname, there are error messages 
logged in db2diag.log. The problem only happens at the first 
time. 
 
2011-03-13-12.28.29.131940+480 E1927A443          LEVEL: Error 
(OS) 
PID     : 27926                TID  : 9           PROC : db2sysc 
INSTANCE: db2inst1              NODE : 000         DB   : TEST 
EDUID   : 9                    EDUNAME: db2agent (TEST) 
FUNCTION: DB2 UDB, Client-side (app) latches, sqloxltc_app, 
probe:15 
MESSAGE : ZRC=0x83000016=-2097151978 
CALLED  : OS, -, unspecified_system_function 
OSERR   : EINVAL (22) "Invalid argument" 
 
2011-03-13-12.28.29.140636+480 E2371A443          LEVEL: Error 
(OS) 
PID     : 27926                TID  : 9           PROC : db2sysc 
INSTANCE: db2inst1              NODE : 000         DB   : TEST 
EDUID   : 9                    EDUNAME: db2agent (TEST) 
FUNCTION: DB2 UDB, Client-side (app) latches, sqloxult_app, 
probe:10 
MESSAGE : ZRC=0x83000016=-2097151978 
CALLED  : OS, -, unspecified_system_function 
OSERR   : EINVAL (22) "Invalid argument" 
 
You can ignore the error message, there should not be any side 
effects.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.1                                * 
****************************************************************
Local Fix:


Solution


Please upgrade to DB2 v10.1 FP1


Workaround


not known / see Local fix


Timestamps


Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

22.11.2012
10.10.2017
10.10.2017


Problem solved at the following versions (IBM BugInfos)




Problem solved according to the fixlist(s) of the following version(s)