|
Problem IC96434
|
Status: Closed |
SQL0901N ERROR WHEN CREATING NICKNAME ON NICKNAME |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Create Nickname statement can't accept a nickname as the remote
object if the remote nickname's STATS_TIME attribute is invalid.
The root cause of this issue is that the remote nickname's
STATS_TIME attribute gets invalid when its remote table's CARD
attribute is -1.
For example, if there is a remote nickname "RNICK" with
STATS_TIME attribute as below:
db2 => select stats_time from syscat.tables where tabname =
'RNICK'
STATS_TIME
--------------------------
0000-00-00-00.00.00.000000
1 record(s) selected.
Then, we can't create a nickname on this nickname:
db2 => create nickname LNICK for rserver.schema.rnick
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 "cannot
convert stats
timestamp value ".) SQLSTATE=58004
The previous APAR JR35191 actually doesn't fix this issue
completely. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* The user creates nicknames on nicknames. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) or higher. *
**************************************************************** |
| Local Fix: |
Run NNSTAT with method 2 to collect statistic data for the
remote nickname, so STATS_TIME will be set to correct value. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.09.2013
15.09.2014
14.10.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
