By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,136 Members | 2,135 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,136 IT Pros & Developers. It's quick & easy.

Federated setup - additional column

P: n/a
Problem:
=========
Unknown column appearing in federated tables.

Description:
============
Local database (L) is an established 'federated' database, extracting
values from multiple remote databases.
Database server = DB2/LINUX 7.1.0

Remote (R) database is a new database. Id like L to pull values from
R.
Database server = DB2/6000 8.1.4

Note the different version numbers.

I can set up the federated configurations on L to R. When building
nicknames additional, and different, columns are appearing in both the
describe and select.

On R
-----
CREATE TABLE application (
Application_id INTEGER NOT NULL,
Application_name VARCHAR(16) NOT NULL
)

On L (having created a nickname)
--------------------------------
describe table r_application
Column Type Type
name schema name Length Scale Nulls
------------------------------ --------- ------------------ --------
APPLICATION_ID SYSIBM INTEGER 4 0 No
APPLICATION_ID0 SYSIBM INTEGER 4 0 No
APPLICATION_NAME SYSIBM VARCHAR 16 0 Yes

Where has the column APPLICATION_ID0 come from?
select * from r_application
Returns back rows with the following columns:
Application_id OK
Application_id1 ???
Application_id11 ???
Application_id111 ???
Application_name OK

What are those addition columns?
select APPLICATION_ID0 from r_application
Works, returning the values found in APPLICATION_ID0 - which isnt in
the APPLICATION table!
select APPLICATION_ID1 from r_application


fails - which is good.
Im perplexed, this is very odd.
Why Im I obtaining additional columns in the describe?
Why Im I obtaining additional columns in the select? Why are these
different form the view?
Any thoughts are welcome.

Thanks

Terry

KEYWORDS: federated, DB2, columns, additional, 7.1, 8.1, describe,
select
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
It appears the issue relates to the fixpak level. I located the
following is IBM documentation.

"DB2 for UNIX and Windows Version 7.2 federated databases

To successfully create nicknames for DB2 for UNIX and Windows Version
8 tables and views, you must apply the DB2 for UNIX and Windows
Version 7.2 Fixpak 8 on your DB2 for UNIX and Windows Version 7.2
federated database. If you do not apply Fixpak 8 on your DB2 for UNIX
and Windows Version 7.2 federated database, an error will occur when
you access the nicknames."
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.