|
Problem IT34670
|
Status: Closed |
ACCESSING HIDDEN COLUMNS WITH FEDERATION RECEIVES SQL0206N
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
Hidden columns can be accessed on the source database. For
example,
$ db2 create table tx1 "(c1 int, ROW_CHG_TS TIMESTAMP NOT NULL
IMPLICITLY HIDDEN GENERATED BY DEFAULT FOR EACH ROW ON UPDATE AS
ROW CHANGE TIMESTAMP)"
$ db2 "select c1, ROW_CHG_TS from tx1"
However, accessing the column in the federated target database
receives error SQL0206N.
$ db2 "select ROW_CHG_TS from dbx1.db2inst1.tx1"
SQL0206N "ROW_CHG_TS" is not valid in the context where it is
used. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.6 or later *
**************************************************************** |
| Local Fix: |
Create a view that includes the hidden columns in source
database and use the view in the target instead |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.6 or later *
**************************************************************** |
| Comment |
Upgrade to 11.5.6 or later |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2020
21.06.2021
21.06.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
