DB2 - Problem description
| Problem IC89699 | Status: Closed |
CREATE NICKNAME FOR A TABLE ON DB2/Z VERSION 10 FAILED WITH SQL0901N REASON "ERROR SERVER VERSION" | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
Create nicknames that point to some Host tables on SYLDSN. Most
of them works just fine, but receives -901 error on the others:
DB21034E The command was processed as an SQL statement because
it was not a valid Command Line Processor command. During SQL
processing it returned: SQL0901N The SQL statement failed
because of a non-severe system error. Subsequent SQL statements
can be processed. (Reason "Error Server Version".)
SQLSTATE=58004
Here is the error message from db2diag.log:
2012-09-24-18.56.24.142000-300 E162857F1365 LEVEL: Info
PID : 6472 TID : 3728 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : SAMPL
APPHDL : 0-746 APPID: *LOCAL.DB2.120924235525
AUTHID : DB2INST1
EDUID : 3728 EDUNAME: db2agent (SAMPL)
FUNCTION: DB2 UDB, SW- common services, sqlnn_cmpl, probe:650
MESSAGE : ZRC=0x803100AF=-2144272209=SQLNN_E_BADNEWS
"unexpected error but state is OK"
DATA #1 : String, 62 bytes
An unexpected error was detected during statement compilation.
DATA #2 : Boolean, 1 bytes
true
DATA #3 : Boolean, 1 bytes
true
DATA #4 : Boolean, 1 bytes
true
DATA #5 : Boolean, 1 bytes
false
DATA #6 : Hex integer, 4 bytes
0x00000000
DATA #7 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 20
sqlerrmc: Error Server Version
sqlerrp : SQLQG_DR
sqlerrd : (1) 0x8026006D (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 58004
DATA #8 : Hex integer, 4 bytes
0x00000040
DATA #9 : String, 59 bytes
Compiler error stack for rc = -2144272209:
sqlnn_cmpl[565] | |
| Problem Summary: | |
User affected: Users who use DRDA wrapper of InfoSphere Federation Server Problem description and summay: See error description | |
| Local Fix: | |
alter server <your_server> version 9; | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
Problem was fistly fixed in Version 10.1, FixPak 3. This fix should be applied on the federation Server. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2013 22.10.2013 22.10.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.3 |
|
| 10.1.0.3 |
|