DB2 6.1 UDB - Badly need help please

Darsh · #1 (**permalink**) 01-21-04, 13:06

Dear Friends

Here is the problem :

While I try to connect database through control center I get this error message. In this DB2 I only know how to use control center becuase it is quite similliar to SQL SERVER Enterprise manager. I don't know how to use other tools.

Error : SQL1402N Unable to authenticate user due to unexpected system error. SQLSTATE = 08004

I'm using id = db2admin and password = db2admin

db2admin is a domain account, and I'm very sure password has not been changed. Becuase I'm using the same account to login to different DB2 server which has no problem.

If any one is in USA, please give me your contact number bcoz i badly need some one's help today it self.

Your small help is also highly appericiable.

With regards
darshna shah

Marcus_A · #2 (**permalink**) 01-21-04, 13:18

I don't have the Messages and Codes manual for version 6, but here is a description from version 8.

SQL1402N Unable to authenticate user due to unexpected system error.

Explanation: Call your system administrator. On unix-based systems, the file db2ckpw may not have the correct permission bits set, or the system may have run out of swap/paging space. On Windows NT, the DB2 security service may not have been started or the account may be locked. The command can not be processed.

Federated system users: this situation can also be detected by the data source.

User Response: On unix-based systems, have the system administrator ensure the correct access permissions are set for db2ckpw, and that there is enough swap/paging space allocated. On Windows NT, have the system administrator verify that the DB2 security service is installed and started. If the service is running then ensure that the account is not locked.

sathyaram_s · #3 (**permalink**) 01-21-04, 13:19

Darshana

See if this helps

H:\>db2 ? sql1402n

SQL1402N Unable to authenticate user due to unexpected system
error.

Explanation: Call your system administrator. On unix-based
systems, the file db2ckpw may not have the correct permission
bits set, or the system may have run out of swap/paging space.
On Windows NT, the DB2 security service may not have been
started.

The command can not be processed.

Federated system users: this situation can also be detected by
the data source.

User Response: On unix-based systems, have the system
administrator ensure the correct access permissions are set for
db2ckpw, and that there is enough swap/paging space allocated.
On Windows NT, have the system administrator verify that the DB2
security service is installed and started.

To view details on an error message,

db2 ? <message code>

HTH

Sathyaram

sathyaram_s · #4 (**permalink**) 01-21-04, 13:21

Another occasion I have seen this error is when the account is locked (eg, you have typed in a wrong password a couple of times ) as per the system policy

HTH

Sathyaram

Darsh · #5 (**permalink**) 01-21-04, 14:09

All

(1) This DB2 6.1 is on Windows Nt 4.0

(2) All Db2 services are running - i did double check and i also restarted all services again.

(3) I've restarted server so many times so there is no problem of locking the account. I'm facing this tough time since last so many days.

(4) I've not checked about swaping files, what is that ? how should i check ?

Marcus_A · #6 (**permalink**) 01-21-04, 14:11

I think the swap space issue for this error is for AIX, not Windows.

sathyaram_s · #7 (**permalink**) 01-21-04, 14:14

Check if your db2diag.log file has any info .. C:\sqllib\db2\db2diag.log

Change the diaglevel to 4 ..

db2 update dbm cfg using diaglevel 4

which will give more detailed messages ...

Cheers
Sathyaram

Darsh · #8 (**permalink**) 01-21-04, 14:20

(1) I got this last message from db2diag.log file.

"2004-01-20-10.56.20.035000 Instance

B2 Node:000
PID:204(db2syscs.exe) TID:399 Appid:*LOCAL.DB2.040120165616
database_monitor sqm.sqlm_log_ev_err Probe:1 Database

IEBTDB"

Darsh · #9 (**permalink**) 01-21-04, 14:23

I forgot how i capture this error, but i capture this error from log files.

"[IBM][CLI Driver] SQL1403N The username and/or password supplied is incorrect. SQLSTATE=08004 "

Darsh · #10 (**permalink**) 01-21-04, 14:45

Darsh · #11 (**permalink**) 01-21-04, 15:32

sathyaram_s · #12 (**permalink**) 01-21-04, 15:39

Contact your administrator to unlock the user ...

You should read

http://www-306.ibm.com/cgi-bin/db2ww...9.htm#HDRNTSEC

to understand how DB2 works with NT password ... With your Windows and SQL Server background, I assume you'll understand this topic better than many others will

Cheers

Sathyaram

Darsh · #13 (**permalink**) 01-22-04, 08:58

sathyaram_s · #14 (**permalink**) 01-22-04, 11:02

It is an instance setting which indicates that the 'connect' will be authenticated on the client side rather than the server side ...

Search for authentication, trust_allclnts and trust_clntauth in you db2 manuals ...

I would generally prefer a SERVER Authentication to be set

Sathyaram

Darsh · #15 (**permalink**) 01-22-04, 16:08

(1) This document, is very nice , cleared my so many doubts.
Though, I'm feeling that something i'm missing.

so, what i did, i renamed few of the log file and system has generated new log file.

I'm getting this error message from db2diag.log file, while i try to connect to db2 through control center.

2004-01-22-14.58.00.218000 Instance

B2 Node:000
PID:204(db2syscs.exe) TID:399 Appid:*LOCAL.DB2.040122205759
database_monitor sqm.sqlm_log_ev_err Probe:1 Database

IEBTDB

Any idea please ?

Any suggestion please ?

With regards
darshna