Technical Blog Post
DB2 LUW : Why does db2rbind xxxx -l rbind.log fail with "Database Manager cannot be started."?
We are creating a new system on AIX 7.1 / DB2 WSE 10.5 FP8. But
db2rbind xxxx -l rbind.log failed with "Database Manager cannot be started."
There is a user who gets this error however there also a user who can run it without the error.
Here is the associated db2diag.log message:
2017-01-04-184.108.40.206117+540 I483628A844 LEVEL: Warning
PID : 12845180 TID : 1 PROC : db2start
INSTANCE: db2inst1 NODE : 000
EDUID : 1
FUNCTION: DB2 UDB, base sys utilities, sqlestrt.C::main, probe:1636
MESSAGE : Error encountered during db2start execution
DATA #1 : unsigned integer, 4 bytes
DATA #2 : unsigned integer, 4 bytes
DATA #3 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1366 sqlerrml: 16
sqlerrmc: IBMLDAPgroups 7
sqlerrp : SQLESTRT
sqlerrd : (1) 0x805C0197 (2) 0x00000197 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
Why does db2rbind xxxx -l rbind.log fail with "Database Manager cannot be started."?
Generally speaking, the above message, "-1366" (SQL1366N) and the keyword
"IBMLDAPgroups 7", most likely is caused by unexpected LDAP configuration. So it might
be suggested to check LDAP configuration to see if there any problem or not with
referencing below page:
It it does not help, it might be needed to collect more information or data, such as
db2trc and suggested to open a PMR to clarify the reason why.
Here is one of helpful links to collect data for further investigation.
Collecting data: Read first for DB2 for Linux, UNIX, and Windows products
Here is one of good articles, would be recommended to review:
DB2 FAQ - Frequently Asked Questions about DB2 for Linux, UNIX and Windows
Here is the main page for all DB2 versions' manuals.
IBM DB2 database product documentation
Hope this helps.