DB/2 – Configuration Assistant – Error – SQL30082N Security processing failed with reason “17” (“UNSUPPORTED FUNCTION”). SQLSTATE=08001

DB/2 – Configuration Assistant

After a long “furlough” from working with the IBM DB/2 Client, returned back to working with it today (Fri June 12th, 2010 — A good day, as World Cup 2010 Started today).

A bit rusty, quite rusty.  But, what is computer life without problems, or shall we say riddles.

One of the many riddles I received from the DB/2 Connectivity layer is this one:

CLI connection failed.
SQL30082N  Security processing failed with reason "17" ("UNSUPPORTED FUNCTION").  SQLSTATE=08001"

After a bit of wrestling, traced the problem back to an oversight of not “enabling encyption” on the DB/2 Client setup:

To fix:

  • Select the specific Client Alias
  • Launch the “Change Database Wizard”
  • Specify the “Security Options”
  • Select “Server Authentication” \ “Enable Encryption”

4 thoughts on “DB/2 – Configuration Assistant – Error – SQL30082N Security processing failed with reason “17” (“UNSUPPORTED FUNCTION”). SQLSTATE=08001

  1. I’m trying to enable WMQ v7.0.1.5 and WMQFTE 7.0.3 Database Logger and I’m using DB2Connect to a remote LUW DB2. I’m getting:
    [mqm@enysvzalb016 bin]$ ./fteStartDatabaseLogger -b 64 -F
    5655-U80, 5724-R10 Copyright IBM Corp. 2008, 2010. ALL RIGHTS RESERVED
    BFGDB0051I: The database logger is running as a 64-bit process.
    BFGDB0049E: The database logger failed to connect to the database due to an authorization error. The error reported by the database is: [jcc][4038][12241][3.62.56] T2LUW exception: SQL30082N Security processing failed with reason “17” (“UNSUPPORTED FUNCTION”). SQLSTATE=08001
    ERRORCODE=-30082, SQLSTATE=08001
    BFGDB0005E: A serious error has occurred, and the database logger will stop. Messages in progress will be rolled back to the queue manager. See the preceding log entry for details.
    BFGDB0018E: An MQ problem occurred while the database logger was closing the connection to MQ (including committing the last transaction). The reported reason code was MQRC_BACKED_OUT and the reported message text (if any) was: MQJE001: Completion Code ‘1’, Reason ‘2003’. You should examine the MQ error log (for example, /var/mqm/qmgrs/COORD_QM/errors/AMQERR01.LOG ) for further information about the problem.

    Whould this possible be my issue?

    • Yes, it could be. Though, I have not tried your specific use-case, your explanation and reasoning seems very plausible. God Luck – Daniel.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s