473,574 Members | 2,692 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

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 8126
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.goo gle.com...
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_******@hotma il.com> wrote in message
news:bp******** **@hanover.toro lab.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.goo gle.com...
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.goo gle.com...
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_******@hotma il.com> wrote in message news:<bp******* ***@hanover.tor olab.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
1482
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 table on DBDC. The traffic should be minimal the call to the remote tables is just for user log in. It appears that the db2syscs.exe process grows...
1
1942
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 databases. Database server = DB2/LINUX 7.1.0
4
606
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 tables in TestA database and the reference tables in TestB database. Now i want to select data from TestB database referencing base table in TestA...
2
4843
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 added attached table T1 in offlinedb using Federated Objects. Then i created a procedure P1 in uatdb database with the following contents.
5
3709
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 got this error : ***************************************************** SQL1013N The database alias name or database name "SAMPLE" could not be...
5
3324
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 definition? Thanks Klemens
2
1921
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 different database running under the same instance. I have created a stored procedure in one database that takes data and inserts it into the other...
4
3443
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 possible until federated server is made.Please tell me how to create a federated server.Moreover, is there any thing extra which I need to buy for...
4
4605
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
2696
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 having a 64bit transaction manager and a 32bit database is not valid. I updated my testing database to 64 bit but my 32 bit COBOL applications no...
0
7814
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main...
0
8067
Oralloy
by: Oralloy | last post by:
Hello folks, I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>". The problem is that using the GNU compilers, it seems that the internal comparison operator "<=>" tries to promote arguments from unsigned to signed. This is as boiled down as I can make it. ...
0
8249
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that...
0
8107
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the...
1
5631
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes...
0
5307
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert...
0
3756
by: adsilva | last post by:
A Windows Forms form does not have the event Unload, like VB6. What one acts like?
1
1352
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.
0
1071
bsmnconsultancy
by: bsmnconsultancy | last post by:
In today's digital era, a well-designed website is crucial for businesses looking to succeed. Whether you're a small business owner or a large corporation in Toronto, having a strong online presence can significantly impact your brand's success. BSMN Consultancy, a leader in Website Development in Toronto offers valuable insights into creating...

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.