- 论坛徽章:
- 0
|
网上搜索到的资料,仅供参考——慎用
这条记录是英文的,你查看一下错误日志,看看是不是和以下记录相符。我尝试操作了一下,但是没成功-_-!
Password expiryprevents IDS from staring.
Technote (FAQ)
This document applies only to the following language version(s) :
English
Problem
Unable to start IDS. db2cli.log reports that password expired.
Errors received before and after the password change are:
--------------------------------------------------------------------------------------------------------------
09/27/2004 09:43:50 AM native retcode = -30082; state = "08001"; message = "[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "1" ("PASSWORD EXPIRED"). SQLSTATE=08001
"
09/27/2004 09:44:51 AM native retcode = -30082; state = "08001"; message = "[IBM][CLI Driver] SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID").
SQLSTATE=08001
--------------------------------------------------------------------------------------------------------------
Other errors in ibmslapd.log:
--------------------------------------------------------------------------------------------------------------
Plugin of type DATABASE is successfully loaded from /lib/libback-config.so.
Error code -1 from odbc string:" SQLConnect " ldapdb2b .
09-27-2004 11:29:48 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
Error code -1 from odbc string:" SQLConnect " ldapdb2b .
Failed to initialize be_config.
Error encountered. Server starting in configuration only mode.
--------------------------------------------------------------------------------------------------------------
During the investigation, it was found that:
- changing the password for the ldapdb2 user did not help (after doing this remember to telnet in again as that user to make sure that the password isn't in a state where it needs to be changed on next login).
- db2 connect to ldapdb2 --> works.
- db2 connect to ldapdb2 user ldapdb2 --> fails with the same error as the ibmslapd startup (SQL30082N - security reason "24").
- dropping/recreating the existing ldapdb2 instance doesn't help.
- creating a NEW instance and database works.
Cause
This appears to be an OS issue.
Solution
In order to resolve this problem, need to do the following:
1. drop the ldapdb2 instance
2. remove ldapdb2 user id and its home directory
3. recreate the user (using a new UID) and home directory
4. recreate the instance
5. recatalog the database
Now should be able to connect using both:
db2 connect to ldapdb2
db2 connect to ldapdb2 user ldapdb2 |
|