Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2002
    Posts
    1

    Question Unanswered: DB2 Federated Server: Unable to access remote tables

    We are having problems in accessing tables from another DB2 database. While creating a nickname for a table on a remote database we get the following error. Any help will be appreciated.

    "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 "TSTODSD1" on node "DB2INST1" could not be accessed
    with the specified authorization id and password."


    We have two instances

    Instance Database
    - - - - - - - - - - - - - - - - - - - - - - -
    db2inst1 TSTODSD1
    db2inst2 TSTSTGD1


    From database TSTSTGD1 we want to access tables from TSTODSD1

    To achieve this we have done the following

    1.
    In db2inst2, we have set dbm parameter FEDERATED = YES

    2.
    In db2inst2/TSTSTGD1, we have created a wrapper DRDA with library libdrda.a using "Create Wrapper ..." command

    3.
    In db2inst2/TSTSTGD1, we have created a server using the following syntax

    create server tstods
    type DB2/6000
    version 7.1.0
    wrapper drda
    authorization "tst"
    password "tst123"
    options
    ( node 'DB2INST1',
    dbname 'TSTODSD1');

    4.
    We tried to create a nickname using the following statement, but it failed.

    db2 "create nickname tb_customer for tstods.ods.tb_customer"

    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 "TSTODSD1" on node "DB2INST1" could not be accessed
    with the specified authorization id and password.

    We recreated the server by issuing the "CREATE SERVER .. " command with different options like fold_id 'U', fold_pw 'U' but still we had the same problems when creating the nickname.

  2. #2
    Join Date
    Aug 2003
    Location
    Florida
    Posts
    2

    Re: DB2 Federated Server: Unable to access remote tables

    You need to create the USER MAPPING with the USER and PASSWORD from where you will access the SOURCE database.
    It fix the problem.
    any questions, let me know....mcelidba@aol.com



    Originally posted by nbhandarkar
    We are having problems in accessing tables from another DB2 database. While creating a nickname for a table on a remote database we get the following error. Any help will be appreciated.

    "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 "TSTODSD1" on node "DB2INST1" could not be accessed
    with the specified authorization id and password."


    We have two instances

    Instance Database
    - - - - - - - - - - - - - - - - - - - - - - -
    db2inst1 TSTODSD1
    db2inst2 TSTSTGD1


    From database TSTSTGD1 we want to access tables from TSTODSD1

    To achieve this we have done the following

    1.
    In db2inst2, we have set dbm parameter FEDERATED = YES

    2.
    In db2inst2/TSTSTGD1, we have created a wrapper DRDA with library libdrda.a using "Create Wrapper ..." command

    3.
    In db2inst2/TSTSTGD1, we have created a server using the following syntax

    create server tstods
    type DB2/6000
    version 7.1.0
    wrapper drda
    authorization "tst"
    password "tst123"
    options
    ( node 'DB2INST1',
    dbname 'TSTODSD1');

    4.
    We tried to create a nickname using the following statement, but it failed.

    db2 "create nickname tb_customer for tstods.ods.tb_customer"

    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 "TSTODSD1" on node "DB2INST1" could not be accessed
    with the specified authorization id and password.

    We recreated the server by issuing the "CREATE SERVER .. " command with different options like fold_id 'U', fold_pw 'U' but still we had the same problems when creating the nickname.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •