DB2 - Problem description
| Problem IC95402 | Status: Closed |
SYSPROC.NNSTAT PROCEDURE CAN FAIL IF USING METHOD 2 WITH SQL0206N ERROR. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
With federated object and running SYSPROC.NNSTAT with the Method
2 option, we can fail with SQL0206N.
eg.
$db2 "set passthru MS1"
DB20000I The SQL command completed successfully.
$db2 "drop table dbo.DATA_TMP"
DB20000I The SQL command completed successfully.
$db2 "CREATE TABLE dbo.DATA_TMP ( INJECTEDSECURITYID int
NOT NULL, FIELDID int NOT NULL, VALDATE
datetime NULL, NUMVALUE varchar(255) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL, REFVALUEID int
NULL, VALIDFROM datetime NULL, VALIDTO
datetime NULL, SECURITYID int NOT NULL,
CONSTRAINT PK_data_TMP PRIMARY KEY CLUSTERED
(INJECTEDSECURITYID,FIELDID,SECURITYID) WITH ( FILLFACTOR = 90 )
)"
DB20000I The SQL command completed successfully.
$db2 "set passthru reset"
DB20000I The SQL command completed successfully.
$db2 "drop nickname nt2"
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0204N "IIDEV4.NT2" is an undefined name. SQLSTATE=42704
$db2 'CREATE NICKNAME "NICK_COMMON"."DATA_TMP" FOR
"MS1"."dbo"."DATA_TMP"'
DB20000I The SQL command completed successfully.
$db2 "CALL
SYSPROC.NNSTAT('MS1','NICK_COMMON','DATA_TMP','FIELDID',NULL,2,N
ULL,?)"
SQL0206N "NICK_COMMON" is not valid in the context where it is
used. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Platforms * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v10.5 Fixpack 3 or Higher * **************************************************************** | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
| Solution | |
First Fixed in DB2 v10.5 Fixpack 3 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 27.02.2014 27.02.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 |
|