IBM Support

Database Error Code shown in Guardium reports for failed logins in DB2 is different than output error shown in the DB2 client tool

Troubleshooting


Problem

Your attempt to connect to a DB2 database failed. The error code shown in the Guardium report does not correspond to the error in the output on the DB2 client application.

Symptom

DB2 Error code shown on the DB2 client application such as the DB2 Command Line , is different than error code in the Guardium report. For example, below are 3 scenarios with 3 different errors reported trying to connect to a DB2 database from the DB2 Command Line:


$db2 connect to sample user user1 using xxxxxxxxx
SQL20157N User with authorization ID "user1" failed to attach to a quiesced instance, or connect to a quiesced database or a database in a quiesced instance which is in the following quiesce mode : "QUIESCE DATABASE".
SQLSTATE=08004


$db2 connect to sample user user2 using xxxxxxxxx
SQL1060N User "user2" does not have  the CONNECT privilege. SQLSTATE=08004


$db2 connect to sample user user3 using xxxxxxxx
SQL30082N Security processing failed with reason "24" ("USERNAME AND/OR PASSWORD INVALID").
SQLSTATE=08001

Guardium report shows totally different error codes for each of the above scenarios. Guardium report shows error (-30082, rc 15) for the first two scenarios, and (-30082, rc 2) for the third one. Below is a sample Guardium report (ips have been intentionally digitally obscured or blurred for security).


[{"Product":{"code":"SSMPHH","label":"IBM Security Guardium"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.1;9.0;8.2;8.1;8.0.1","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
16 June 2018

UID

swg21673683

Page Feedback