Results 1 to 6 of 6
  1. #1
    Join Date
    Mar 2010
    Posts
    32

    Unanswered: Authentication issue whiel creating nicknames in federation

    I have been setting up federation on RHEL 5 servers and i see the authorization issue .everything looks correct to me .


    Below are the commands I am issuing for fed on the federated database . :-

    Code:
    > db2 "create server sample_db type db2/udb version 9.7 wrapper drda authorization "db2inst1" password "temp" options (ADD NODE 'TCPFED' ,DBNAME 'sample',FOLD_PW 'L')"
    DB20000I  The SQL command completed successfully.
    > db2 "create user mapping for db2inst1  server sample_db options (remote_authid 'db2inst1', remote_password 'temp')"
    DB20000I  The SQL command completed successfully.
    > db2 "create nickname nt1 for  sample_db.db2inst1.t1"
    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 "sample" on node "TCPFED" could not be accessed with
    the specified authorization id and password.  SQLSTATE=08004

    I am able to connec to the catalog database with the same user name and password .

    Code:
    > db2 connect to sample user db2inst1
    Enter current password for db2inst1:
    
       Database Connection Information
    
     Database server        = DB2/LINUXX8664 9.7.4
     SQL authorization ID   = DB2INST1
     Local database alias   = SAMPLE
    
    > db2 "select * from db2inst1.t1"
    
    NO
    -----------
              1
    
      1 record(s) selected.
    Catalog details :-
    Database 3 entry:

    Database alias = SAMPLE
    Database name = SAMPLE
    Node name = TCPFED
    Database release level = d.00
    Comment =
    Directory entry type = Remote
    Catalog database partition number = -1
    Alternate server hostname =
    Alternate server port number =
    Can someone please tell me why it's not working ?

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Which of the suggestions indicated in the error description in the Messages manual did you try, and what were the results?
    ---
    "It does not work" is not a valid problem statement.

  3. #3
    Join Date
    Mar 2010
    Posts
    32
    I have gone through all the below statements but f
    Federated system users: This error can also occur when any of the
    following is true:
    Code:
    *  There is no user mapping and the remote authorization ID or remote
       password does not match the authorization ID and password that were
       specified when connecting to the DB2 federated database.
    
    From the above commands you can see the user mapping created successfully.
    
    *  The user mapping does not specify the REMOTE_PASSWORD option, and no
       password was specified when connecting to the DB2 federated database.
    
    I have issued the remote_password in my commands. 
    
    *  The user mapping does not specify the REMOTE_PASSWORD option, and the    remote password does not match the password specified when connecting    to the DB2 federated database.
    
    it doesn' t show me any password failures or any error messages in db2diag stating that it's an invalid password. 
    
    *  The user mapping does not specify the REMOTE_AUTHID option, and the
       remote authorization ID does not match the authorization ID specified
       when connecting to the DB2 federated database.
    
    I have specified the remote_authid in the command 
    
    *  The remote authorization ID or remote password do not match those
       specified on the user mapping.
    
    No errors shown again in the diag file.
    Can you help me how to figure out what's the issue is

  4. #4
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    in the doc is stated
    the remote-authorization-name should be enclosed by double quotation marks.
    executing this in command line removes this
    put the statement in a file :
    create server .... authorization "db2inst1" .....
    execute this with db2 -tvf .....
    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

  5. #5
    Join Date
    Mar 2010
    Posts
    32
    WOW! it worked when i executed the same commands via script .

    Interesting to see it fails again if i run them manually.
    Thank you for making it to work .

  6. #6
    Join Date
    Nov 2004
    Posts
    67
    Quote Originally Posted by przytula_guy View Post
    in the doc is stated
    the remote-authorization-name should be enclosed by double quotation marks.
    executing this in command line removes this
    put the statement in a file :
    create server .... authorization "db2inst1" .....
    execute this with db2 -tvf .....
    Thank you, Guy.

    I had the same problem and could solve it running the commands as SQL file after reading your advice.
    Last month I made a similar federation in the same environment with a script and it worked. I don't know where the difference is.

Posting Permissions

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