473,320 Members | 2,111 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

Federated database

Hi All,

Im having problems setting up the federated database. The commands Im
using are as follows:

CATALOG TCPIP NODE 'FSYS1' REMOTE <ip> SERVER <port>

CREATE SERVER svr_docket TYPE DB2/LINUX VERSION 7.1.0 WRAPPER DRDA
AUTHORIZATION usr1 PASSWORD "usr1pwd" OPTIONS (NODE 'feddb1', DBNAME
'docket' )

CREATE USER MAPPING FOR USER SERVER svr_docket OPTIONS
(REMOTE_AUTHID 'usr1', REMOTE_PASSWORD ' usr1pwd ')

CREATE NICKNAME docket_test FOR svr_docket.test_table

The error message is generated by the last command, CREATE NICKNAME,
is

db2 => Create nickname docket_test for svr_docket.test_table
DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1101N Remote database "docket" on node "feddb1" could not be
accessed with
the specified authorization id and password.

I believe the username and password in the 'CREATE SERVER' are
correct, If I user the incorrect apsswords the command fails. So Im
assuming its the username and password in the CREATE USER MAPPING
command thats causing the issue. The username and password in the two
commands is identical, and they both exist on the same database
instance.

Does anyone have any suggestions to the cause of this problem?

thanks
terry
Nov 12 '05 #1
5 8098
Trying to get a solution for you from some experts, in the meanwhile try a
hack:
use quotes around the usr1 as well in create server
Thanks
Aakash

"Terry" <te************@yahoo.com> wrote in message
news:e8**************************@posting.google.c om...
Hi All,

Im having problems setting up the federated database. The commands Im
using are as follows:

CATALOG TCPIP NODE 'FSYS1' REMOTE <ip> SERVER <port>

CREATE SERVER svr_docket TYPE DB2/LINUX VERSION 7.1.0 WRAPPER DRDA
AUTHORIZATION usr1 PASSWORD "usr1pwd" OPTIONS (NODE 'feddb1', DBNAME
'docket' )

CREATE USER MAPPING FOR USER SERVER svr_docket OPTIONS
(REMOTE_AUTHID 'usr1', REMOTE_PASSWORD ' usr1pwd ')

CREATE NICKNAME docket_test FOR svr_docket.test_table

The error message is generated by the last command, CREATE NICKNAME,
is

db2 => Create nickname docket_test for svr_docket.test_table
DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1101N Remote database "docket" on node "feddb1" could not be
accessed with
the specified authorization id and password.

I believe the username and password in the 'CREATE SERVER' are
correct, If I user the incorrect apsswords the command fails. So Im
assuming its the username and password in the CREATE USER MAPPING
command thats causing the issue. The username and password in the two
commands is identical, and they both exist on the same database
instance.

Does anyone have any suggestions to the cause of this problem?

thanks
terry

Nov 12 '05 #2
Terry,

The userid would be folded to upper case in the CREATE SERVER statement
because there are no double-quotes around the userid. But in the CREATE
USER MAPPING statement, the single quotes preseve the lower case of the
userid string. Check your Linux box's /etc/passwd to see if the id is
really USR1. If so, change the CREATE USER MAPPING statement to specify
the userid as 'USR1'.

Hope this helps,

Harold

Terry wrote:
Hi All,

Im having problems setting up the federated database. The commands Im
using are as follows:

CATALOG TCPIP NODE 'FSYS1' REMOTE <ip> SERVER <port>

CREATE SERVER svr_docket TYPE DB2/LINUX VERSION 7.1.0 WRAPPER DRDA
AUTHORIZATION usr1 PASSWORD "usr1pwd" OPTIONS (NODE 'feddb1', DBNAME
'docket' )

CREATE USER MAPPING FOR USER SERVER svr_docket OPTIONS
(REMOTE_AUTHID 'usr1', REMOTE_PASSWORD ' usr1pwd ')

CREATE NICKNAME docket_test FOR svr_docket.test_table

The error message is generated by the last command, CREATE NICKNAME,
is

db2 => Create nickname docket_test for svr_docket.test_table
DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1101N Remote database "docket" on node "feddb1" could not be
accessed with
the specified authorization id and password.

I believe the username and password in the 'CREATE SERVER' are
correct, If I user the incorrect apsswords the command fails. So Im
assuming its the username and password in the CREATE USER MAPPING
command thats causing the issue. The username and password in the two
commands is identical, and they both exist on the same database
instance.

Does anyone have any suggestions to the cause of this problem?

thanks
terry


Nov 12 '05 #3
Hi, Aakash,

I don't know whether the customer has a typo or not. In the catalog node and
create server don't use the same node.

Regards,

Lan Huang

"Aakash Bordia" <a_******@hotmail.com> wrote in message
news:bp**********@hanover.torolab.ibm.com...
Trying to get a solution for you from some experts, in the meanwhile try a
hack:
use quotes around the usr1 as well in create server
Thanks
Aakash

"Terry" <te************@yahoo.com> wrote in message
news:e8**************************@posting.google.c om...
Hi All,

Im having problems setting up the federated database. The commands Im
using are as follows:

CATALOG TCPIP NODE 'FSYS1' REMOTE <ip> SERVER <port>

CREATE SERVER svr_docket TYPE DB2/LINUX VERSION 7.1.0 WRAPPER DRDA
AUTHORIZATION usr1 PASSWORD "usr1pwd" OPTIONS (NODE 'feddb1', DBNAME
'docket' )

CREATE USER MAPPING FOR USER SERVER svr_docket OPTIONS
(REMOTE_AUTHID 'usr1', REMOTE_PASSWORD ' usr1pwd ')

CREATE NICKNAME docket_test FOR svr_docket.test_table

The error message is generated by the last command, CREATE NICKNAME,
is

db2 => Create nickname docket_test for svr_docket.test_table
DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1101N Remote database "docket" on node "feddb1" could not be
accessed with
the specified authorization id and password.

I believe the username and password in the 'CREATE SERVER' are
correct, If I user the incorrect apsswords the command fails. So Im
assuming its the username and password in the CREATE USER MAPPING
command thats causing the issue. The username and password in the two
commands is identical, and they both exist on the same database
instance.

Does anyone have any suggestions to the cause of this problem?

thanks
terry


Nov 12 '05 #4
here are some more suggestions:
Are the user ID and password in upper or lower case? On the CREATE SERVER
statement, the user ID is not in quotes so it will get folded to upper case.
On the CREATE USER MAPPING statement, the user ID and password are
case-sensitive. They are not folded unless the server definition specifies
the FOLD_ID and/or FOLD_PW options. (Those options could be specified on the
CREATE SERVER or ALTER SERVER statement.) In V7 during the CREATE SERVER,
the DRDA wrapper tried all 9 combinations of user ID and password in upper
case/lower case/unchanged. V8 no longer does that.

The USER keyword on the CREATE USER MAPPING statement specifies the auth ID
of the person issuing the CREATE USER MAPPING statement. (In other words,
that's the local auth ID that gets mapped to the remote auth ID.) It should
match the local auth ID of the person issuing the CREATE NICKNAME statement.

"Terry" <te************@yahoo.com> wrote in message
news:e8**************************@posting.google.c om...
Hi All,

Im having problems setting up the federated database. The commands Im
using are as follows:

CATALOG TCPIP NODE 'FSYS1' REMOTE <ip> SERVER <port>

CREATE SERVER svr_docket TYPE DB2/LINUX VERSION 7.1.0 WRAPPER DRDA
AUTHORIZATION usr1 PASSWORD "usr1pwd" OPTIONS (NODE 'feddb1', DBNAME
'docket' )

CREATE USER MAPPING FOR USER SERVER svr_docket OPTIONS
(REMOTE_AUTHID 'usr1', REMOTE_PASSWORD ' usr1pwd ')

CREATE NICKNAME docket_test FOR svr_docket.test_table

The error message is generated by the last command, CREATE NICKNAME,
is

db2 => Create nickname docket_test for svr_docket.test_table
DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1101N Remote database "docket" on node "feddb1" could not be
accessed with
the specified authorization id and password.

I believe the username and password in the 'CREATE SERVER' are
correct, If I user the incorrect apsswords the command fails. So Im
assuming its the username and password in the CREATE USER MAPPING
command thats causing the issue. The username and password in the two
commands is identical, and they both exist on the same database
instance.

Does anyone have any suggestions to the cause of this problem?

thanks
terry

Nov 12 '05 #5
Hi All,

thanks for your replies.
+ Ive put the password in quotes, and its not making a difference.
+ The name of the federated database was different in the CATALOG and
CREATE SERVER commands, these were due to a cut and paste error when I
copied the info to the message.

Ive added some more information to see if anyone can spot anything. Is
the fact that they both reside on the same instance an issue?

thanks again.

Terry

Im having problems setting up the federated database, and referring to
a database that resides on the same instance.

Server:
linux1

Db2 port from /etc/services:
50000

db2 instance:
usr1

username/password:
usr1/ usr1pwd
CATALOG TCPIP NODE 'feddb1' REMOTE <ip> SERVER <port>

CREATE SERVER svr_docket TYPE DB2/LINUX VERSION 7.1.0 WRAPPER DRDA
AUTHORIZATION "usr1" PASSWORD "usr1pwd" OPTIONS (NODE 'feddb1', DBNAME
'docket' )

CREATE USER MAPPING FOR USER SERVER svr_docket OPTIONS (REMOTE_AUTHID
'usr1', REMOTE_PASSWORD 'usr1pwd')

CREATE NICKNAME docket_test FOR svr_docket.test_table

The error message is generated by the last command, CREATE NICKNAME,
is

db2 => Create nickname docket_test for svr_docket.test_table
DB21034E The command was processed as an SQL statement because it was
not a
valid Command Line Processor command. During SQL processing it
returned:
SQL1101N Remote database "docket" on node "feddb1" could not be
accessed with
the specified authorization id and password.

I believe the username and password in the 'CREATE SERVER' are
correct, If I user the incorrect passwords the command fails.

Does anyone have any suggestions to the cause of this problem?


"Aakash Bordia" <a_******@hotmail.com> wrote in message news:<bp**********@hanover.torolab.ibm.com>...
here are some more suggestions:
Are the user ID and password in upper or lower case? On the CREATE SERVER
statement, the user ID is not in quotes so it will get folded to upper case.
On the CREATE USER MAPPING statement, the user ID and password are
case-sensitive. They are not folded unless the server definition specifies
the FOLD_ID and/or FOLD_PW options. (Those options could be specified on the
CREATE SERVER or ALTER SERVER statement.) In V7 during the CREATE SERVER,
the DRDA wrapper tried all 9 combinations of user ID and password in upper
case/lower case/unchanged. V8 no longer does that.

The USER keyword on the CREATE USER MAPPING statement specifies the auth ID
of the person issuing the CREATE USER MAPPING statement. (In other words,
that's the local auth ID that gets mapped to the remote auth ID.) It should
match the local auth ID of the person issuing the CREATE NICKNAME statement.

Nov 12 '05 #6

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: stevenkblack | last post by:
I have a server W2k running DB2 8.1.6. We have two databases one DBDC that holds our user base and QUALITY with all our application data. I have about 8 tables federated on QUALITY looking at the...
1
by: Terry | last post by:
Problem: ========= Unknown column appearing in federated tables. Description: ============ Local database (L) is an established 'federated' database, extracting values from multiple remote...
4
by: uthuras | last post by:
Greetings all, Is it possible to have federated db feature implemented among DB2 family? I intend to create federated within DB2 databases. I have 2 databases TestA and TestB. I have some base...
2
by: vrbala | last post by:
Hi All, I have a issue in federated database. I will explain the scenario I have a table T1 in database called offlinedb. It has one column F1 I have an another table T2 in database uatdb. I...
5
by: Alias | last post by:
Hi Guys , I am trying to create a federated database link between 2 UDB 8.1 databases running on AIX on the same box but under different instances. When i tried this thru the control centre , I...
5
by: Klemens | last post by:
I get SQL30090 reason 18 by trying to do an insert in a federated table and an update in a local table in one transaction Do I have to change some settings to get done or ist this not possible by...
2
by: mas5 | last post by:
Hello, Sorry if my question is elementary. I've searched google, but can't seem to find exactly what I'm looking for. My client is using db2 8.2. They have 2 companies and each company has a...
4
by: Praveen_db2 | last post by:
Hi All DB2 8.1.3,Windows I have 2 databases in a single instance, say DB_1 and DB_2.I need to query a table from DB_1 in DB_2.I am try to use a nickname for it.But nickname creation is not...
4
by: esmith2112 | last post by:
I have a query running on a federated database that takes the form select col1, col2 from nickname1 where <conditions exist> union all select col1,col2 from nickname2
1
by: TheAndroid | last post by:
All, I'm having a difficult time trying to implement two-phase commits across federated database members in UDB 8.3. I've tried using MQ (v 6.0) as the transaction manager and UDB tells me that...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.