Results 1 to 8 of 8
  1. #1
    Join Date
    Oct 2005
    Posts
    8

    Unanswered: Please Help "UNEXPECTED CLIENT ERROR"

    when I try to connect....

    db2 connect to <databasename> user<username> using <password>


    I get....

    SQL30082N Security processing failed with reason "36" ("UNEXPECTED CLIENT ERROR"). SQLSTATE=08001




    Please Help

  2. #2
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    The usual questions:
    • Which version of DB2 are you using (server and client)?
    • Which platform(s) are you running on?
    • What do you find in the db2diag output on the client when you try to connect?
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  3. #3
    Join Date
    Oct 2005
    Posts
    8
    1. I am using the 90 day V9 trial version of UDB . Is it client or server. Must I install both
    2. Linux
    3. Nothing in diaglog

  4. #4
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Have you set the DBM CF parameter DIAGLEVEL to 4? You should then have something in the db2diag.log (or output from the "db2diag" tool).
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  5. #5
    Join Date
    Oct 2005
    Posts
    8
    Yes diag leve set to 4

  6. #6
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    So what do you see in the db2diag output? (at the client)
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

  7. #7
    Join Date
    Oct 2005
    Posts
    8
    Password validation for user fsledge failed with rc = -2146500315

  8. #8
    Join Date
    Jan 2007
    Location
    Jena, Germany
    Posts
    2,721
    Then run the following command to figure out what this reason code stands fore:
    [code]
    $ db2diag -rc -2146500315
    [code]
    And since the password validation failed, you may want to check your password settings. Maybe you have some special characters in the password that DB2 does not allow? Have a look at the DB2 manual to check rules for passwords.
    Knut Stolze
    IBM DB2 Analytics Accelerator
    IBM Germany Research & Development

Posting Permissions

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