Federated database

[Terry]

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

[Aakash Bordia]

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

[Harold Lee]

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

[Aakash Bordia]

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

[Aakash Bordia]

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

[Terry]

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.