If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Attempt to establish connection failed with security reason "15"

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-30-08, 16:04
smith43017 smith43017 is offline
Registered User
 
Join Date: Sep 2006
Posts: 92
Attempt to establish connection failed with security reason "15"

C:\>db2 connect to JCDuser XXXXX
Enter current password for XXXXX:
SQL30082N Attempt to establish connection failed with security reason "15"
("PROCESSING FAILURE"). SQLSTATE=08001

cataloging info accurate.

Actually Strange this is

if I try to connect from server with user name option . It is working fine

EX:

db2 connect to JCD

Database Connection Information

Database server = DB2/AIX64 9.1.6
SQL authorization ID = XXXXX
Local database alias = JCD

but when I pass user name and password it is failing. This is instance owner id.


db2 connect to JCD user XXXXX
Enter current password for XXXXX:
SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE").
SQLSTATE=08001

db2set value, dbm cfg all seems to be fine.
Reply With Quote
  #2 (permalink)  
Old 12-31-08, 02:35
przytula_guy przytula_guy is offline
Registered User
 
Join Date: Apr 2006
Location: Belgium
Posts: 1,159
anyhow there is something wrong with this uid
try using this uid to logon to windows or where the db is located
what is the dbm setting for authentication ?
__________________
Best Regards, Guy Przytula
Database Software Consultant
DB2 UDB LUW Certified V7-V8-V9-V9.7 DB Admin - Dprop..
Information Server Datastage Certified
http://www.infocura.be
Reply With Quote
  #3 (permalink)  
Old 12-31-08, 08:49
smith43017 smith43017 is offline
Registered User
 
Join Date: Sep 2006
Posts: 92
Database manager authentication (AUTHENTICATION) = SERVER


I am having issue on both Unix (when specify the user name) and windows. On UNIX if I don't specify the user name it works fine.
Reply With Quote
  #4 (permalink)  
Old 12-31-08, 08:51
smith43017 smith43017 is offline
Registered User
 
Join Date: Sep 2006
Posts: 92
Server Connection Authentication (SRVCON_AUTH) = NOT_SPECIFIED
Reply With Quote
  #5 (permalink)  
Old 12-31-08, 09:08
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
What's in db2diag.log? Set diaglevel to 4 to get more information.

Also, try changing the password to something that only contains alphanumeric characters and is not longer than 8 characters.
Reply With Quote
  #6 (permalink)  
Old 12-31-08, 09:15
smith43017 smith43017 is offline
Registered User
 
Join Date: Sep 2006
Posts: 92
/db2home/XXXXXX$ passwd XXXXX
Changing password for "XXXXX"
udbinst3's Old password:
udbinst3's New password:
Enter the new password again:

XXXXXX@ s0hers6p3:

/db2home/XXXX$ db2 connect to JCD user XXXXX
Enter current password for udbinst3:
SQL30082N Security processing failed with reason "15" ("PROCESSING FAILURE").
SQLSTATE=08001

XXXXXX@ s0hers6p3:

/db2home/XXXXX$ db2 connect to JCD

Database Connection Information

Database server = DB2/AIX64 9.1.6
SQL authorization ID = XXXXX
Local database alias = JCD




FIXPACK level 9.1 FP6

Last edited by smith43017; 12-31-08 at 09:22.
Reply With Quote
  #7 (permalink)  
Old 12-31-08, 09:20
smith43017 smith43017 is offline
Registered User
 
Join Date: Sep 2006
Posts: 92
2008-12-31-09.18.57.002805-300 I2963A296 LEVEL: Info
PID : 294982 TID : 1
FUNCTION: DB2 Common, Security, Users and Groups, secLoadGroupPlugin, probe:10
DATA #1 : String, 88 bytes
Loaded plugin library /db2home/XXXXX/sqllib/security64/plugin/IBM/group/IBMOSgroups.a

2008-12-31-09.18.57.002887-300 I3260A235 LEVEL: Info
PID : 294982 TID : 1
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 32 bytes
db2secGroupPluginInit successful

2008-12-31-09.18.57.003088-300 I3496A306 LEVEL: Info
PID : 294982 TID : 1
FUNCTION: DB2 Common, Security, Users and Groups, secLoadServerAuthPlugin, probe:10
DATA #1 : String, 93 bytes
Loaded plugin library /db2home/XXXXX/sqllib/security64/plugin/IBM/server/IBMOSauthserver.a

2008-12-31-09.18.57.003116-300 I3803A240 LEVEL: Info
PID : 294982 TID : 1
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 37 bytes
db2secServerAuthPluginInit successful

2008-12-31-09.18.57.003265-300 I4044A273 LEVEL: Warning
PID : 294982 TID : 1
FUNCTION: DB2 Common, Security, Users and Groups, secLogMessage, probe:20
DATA #1 : String, 67 bytes
Password validation for user XXXXX failed with rc = -2146500315


2008-12-31-09.18.57.003395-300 I4318A1071 LEVEL: Info (OS)
PID : 331816 TID : 1 PROC : db2bp
INSTANCE: XXXXX NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemP, probe:3
MESSAGE : ZRC=0x83000024=-2097151964
CALLED : OS, -, semop
OSERR : EIDRM (36) "An identifier does not exist."
DATA #1 : unsigned integer, 4 bytes
38797319
DATA #2 : unsigned integer, 4 bytes
1
CALLSTCK:
[0] 0x0900000006415010 .sqlccrecv_fdprpro_clone_113 + 0x70
[1] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF
[2] 0x0000000000000000 ?unknown + 0x0
[3] 0x090000000642BDCC sqljcReceive__FP10sqljCmnMgr + 0xBC
[4] 0x090000000643BD44 sqljrDrdaArAuthenticate__FP14db2UCinterfacelPUi + 0x394
[5] 0x09000000063E6D68 sqlexAppAuthenticate__FP14db2UCinterface + 0x1C
[6] 0x09000000063E757C sqljrDrdaArConnect__FP14db2UCinterface + 0xAC
[7] 0x09000000063E7780 sqleUCdrdaARinit__FP11UCconHandle + 0xC4
[8] 0x09000000063FDCAC sqleUCappConnect + 0x8B4
[9] 0x09000000063E9944 sqlakConnect__FPP9sqlak_rcbPP15sql_static_dataUs + 0x684

2008-12-31-09.18.57.003832-300 I5390A670 LEVEL: Info
PID : 331816 TID : 1 PROC : db2bp
INSTANCE: XXXXX NODE : 000
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -30082 sqlerrml: 22
sqlerrmc: 15 PROCESSING FAILURE
sqlerrp : SQLEXSMC
sqlerrd : (1) 0x8037012D (2) 0x0000012D (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 08001
Reply With Quote
  #8 (permalink)  
Old 12-31-08, 11:20
smith43017 smith43017 is offline
Registered User
 
Join Date: Sep 2006
Posts: 92
dropped databases (because it's test databases). And dropped instances , dropped dasusr and uninstalled software and reinstall software and recreated
all and now every thing working fine.


Recently I upgraded on this dba test box I ran into issues. We ran into couple of issues we fixed. But we ran into this issue.

Thanks for all you help.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On