Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC96283 Status: Geschlossen

SYSPROC.NNSTAT PROCEDURE CAN FAIL IF USING METHOD 2 WITH SQL0206N ERROR.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem First Fixed in DB2 v10.1 Fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.09.2013
21.10.2013
21.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList