Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2013
    Posts
    6

    Unanswered: Remote table access using Db2 federated server is not working

    Hi ,

    I am trying to create connection between 2 db2 servers using federated server.But i am getting below error while trying to create a nickname.

    I follow the below steps:
    Source db:

    Created user and table.
    username :sapsr3_v
    Table : test

    Target:
    db2 UPDATE DATABASE MANAGER CONFIGURATION USING FEDERATED YES
    $db2stop
    $db2start
    create wrapper drda;

    db2 catalog tcpip node Y08_FED remote ***** server *****
    db2 catalog database Y08 at node Y08_FED authentication type server


    db2 list db directory

    Database 2 entry:

    Database alias = Y08
    Database name = Y08
    Node name = Y08_FED
    Database release level = 10.00
    Comment =
    Directory entry type = Remote
    Authentication = SERVER
    Catalog database partition number = -1
    Alternate server hostname =
    Alternate server port number =

    create server Y08_FED_SERVER type db2/udb version 10.5 wrapper drda authorization "sapsr3_v" password "*******" options (DBNAME 'Y08')
    create user mapping for Db2y08 server Y08_FED_SERVER options (remote_authid 'sapsr3_v', remote_password '*********');

    But when i am trying to create nickname im getting below error.

    db2 => create nickname test1 for Y08_FED_SERVER.sapsr3_v.test_1
    DB21034E The command was processed as an SQL statement because it was not a
    valid Command Line Processor command. During SQL processing it returned:
    SQL0551N The statement failed because the authorization ID does not have the
    required authorization or privilege to perform the operation. Authorization
    ID: "SAPSR3_V". Operation: "CREATE NICKNAME". Object: "SAPSR3_V.TEST1".
    SQLSTATE=42501


    I am able to access the data using set passthru

    set passthru Y08_FED_SERVER
    db2 => select * from sAPSR3_V.TEST1

    C1 C2
    ----------- -----------
    9 10


    The database manager authentication is "server" in source and "server_encrypt" in target .

    I am not sure if that is causing any issue


    Soruce:db2y08 55> db2 GET DATABASE MANAGER CONFIGURATION |grep authentication
    Database manager authentication (AUTHENTICATION) = SERVER
    Alternate authentication (ALTERNATE_AUTH_ENC) = NOT_SPECIFIED
    Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
    Bypass federated authentication (FED_NOAUTH) = NO

    Target :db2y11 103> db2 GET DATABASE MANAGER CONFIGURATION |grep authentication
    Database manager authentication (AUTHENTICATION) = SERVER_ENCRYPT
    Alternate authentication (ALTERNATE_AUTH_ENC) = NOT_SPECIFIED
    Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
    Bypass federated authentication (FED_NOAUTH) = NO


    Anyone please suggest .

    Thank you
    Padmini

  2. #2
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    do not forget user mapping to indicate the user to logon on remote system if local user x connected
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

Posting Permissions

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