Results 1 to 7 of 7
  1. #1
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367

    Unanswered: sql30082n RC=3 [ remote db -> local db ]

    Code:
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 list node directory
    
     Node Directory
    
     Number of entries in the directory = 1
    
    Node 1 entry:
    
     Node name                      = JAC_NODE
     Comment                        =
     Directory entry type           = LOCAL
     Protocol                       = TCPIP
     Hostname                       = localhost
     Service name                   = db2c_db2inst1
    
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 list db directory
    
     System Database Directory
    
     Number of entries in the directory = 2
    
    Database 1 entry:
    
     Database alias                       = SCM
     Database name                        = JAC
     Node name                            = JAC_NODE
     Database release level               = c.00
     Comment                              =
     Directory entry type                 = Remote
     Catalog database partition number    = -1
     Alternate server hostname            =
     Alternate server port number         =
    
    Database 2 entry:
    
     Database alias                       = JAC
     Database name                        = JAC
     Local database directory             = /xxx/db2/data
     Database release level               = c.00
     Comment                              =
     Directory entry type                 = Indirect
     Catalog database partition number    = 0
     Alternate server hostname            =
     Alternate server port number         =
    
    
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 connect to JAC
    
       Database Connection Information
    
     Database server        = DB2/AIX64 9.5.9
     SQL authorization ID   = DB2INST1
     Local database alias   = JAC
    
    
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 connect to SCM
    SQL30082N  Security processing failed with reason "3" ("PASSWORD MISSING").
    SQLSTATE=08001
    
    
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 attach to JAC_NODE
    SQL30082N  Security processing failed with reason "3" ("PASSWORD MISSING").
    SQLSTATE=08001
    
    
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 connect to SCM user db2inst1
    Enter current password for db2inst1:
    
       Database Connection Information
    
     Database server        = DB2/AIX64 9.5.9
     SQL authorization ID   = DB2INST1
     Local database alias   = SCM
    
    
    db2inst1@xxxxxxxx:/xxx/db2/db2inst1> db2 get dbm cfg | grep -i auth
     GSS Plugin for Local Authorization    (LOCAL_GSSPLUGIN) =
     Server Connection Authentication          (SRVCON_AUTH) = NOT_SPECIFIED
     Database manager authentication        (AUTHENTICATION) = SERVER
     Cataloging allowed without authority   (CATALOG_NOAUTH) = NO
     Trusted client authentication          (TRUST_CLNTAUTH) = CLIENT
     Bypass federated authentication            (FED_NOAUTH) = NO

    If I change AUTHENTICATION dbm cfg to CLIENT, connect to SCM without user/pwd is successful.


    From the manual:

    "If authentication is SERVER, the user ID and password are sent from the client to the server so that authentication can take place on the server....
    A value of CLIENT indicates that all authentication takes place at the client. No authentication needs to be performed at the server."


    In my example, client and server is the same AIX box. Could you please explain why I need to provide user/pwd when connecting to a db that is catalogued as remote but pointing to local?

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    Because it is considered a remote database and as such a Client.


    Andy

  3. #3
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    What would be the purpose of cataloging this node / remote db (got created during product installation)? I've seen people creating a loopback connection to workaround some memory/connectivity issues with 32-bit on AIX in the past.

    Is there a way to connect to this remote db without providing id/pwd and without changing AUTHENTICATION dbm cfg. I cataloged another db and specified authentication client, but got the same error:

    > db2 catalog db jac as test at node JAC_NODE authentication client
    DB20000I The CATALOG DATABASE command completed successfully.
    DB21056W Directory changes may not be effective until the directory cache is refreshed.

    > db2 terminate
    DB20000I The TERMINATE command completed successfully.


    > db2 connect to test
    SQL30082N Security processing failed with reason "17" ("UNSUPPORTED
    FUNCTION"). SQLSTATE=08001

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by db2girl View Post
    What would be the purpose of cataloging this node / remote db (got created during product installation)? I've seen people creating a loopback connection to workaround some memory/connectivity issues with 32-bit on AIX in the past.
    On AIX a 32-bit process can only attach to 11 shared segments. Each local connection consumes 1 shared segment, so a 32-bit instance can handle less than 10 local connections (database shared memory and some other pools also count towards that limit).

    Quote Originally Posted by db2girl View Post

    Is there a way to connect to this remote db without providing id/pwd and without changing AUTHENTICATION dbm cfg.
    I think no.
    ---
    "It does not work" is not a valid problem statement.

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by n_i View Post
    On AIX a 32-bit process can only attach to 11 shared segments. Each local connection consumes 1 shared segment, so a 32-bit instance can handle less than 10 local connections (database shared memory and some other pools also count towards that limit).
    Is there any other reason why someone would need to create such a remote db?

  6. #6
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    Quote Originally Posted by db2girl View Post
    I cataloged another db and specified authentication client, but got the same error:

    ...
    > db2 connect to test
    SQL30082N Security processing failed with reason "17" ("UNSUPPORTED
    FUNCTION"). SQLSTATE=08001

    Actually, it's a different RC. It looks like I can't override authentication on catalog db??

  7. #7
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by db2girl View Post
    Is there any other reason why someone would need to create such a remote db?
    I'm sure there are.
    ---
    "It does not work" is not a valid problem statement.

Posting Permissions

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