|
Problem IC70660
|
Status: Closed |
SECURITY MESSAGE IN DB2DIAG.LOG WHEN RUNNING DB2DART |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2dart generates the following error in the db2diag.log:
2010-07-20-19.13.25.856000-240 E938H404 LEVEL: Error
(OS)
PID : 2432 TID : 1964 PROC :
db2dart.exe
INSTANCE: DB2_01 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloGetAccountSID,
probe:30
MESSAGE : ZRC=0x83000534=-2097150668
CALLED : OS, -, LookupAccountName
OSERR : 1332 "No mapping between account names and security
IDs was
done."
but still completes successfully. This can occur when
1. DB2_EXTSECURITY is NO
2. There is no local DB2ADMNS group |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2dart users *
****************************************************************
* PROBLEM DESCRIPTION: *
* The following "No mapping between account names and security *
* IDs was done" *
* errors are written to the db2diag.log when db2dart is *
* executed. *
* *
* 2010-07-20-19.13.25.856000-240 E938H404 LEVEL: *
* Error (OS) *
* PID : 2432 TID : 1964 PROC : *
* db2dart.exe *
* INSTANCE: DB2_01 NODE : 000 *
* FUNCTION: DB2 UDB, oper system services, sqloGetAccountSID, *
* probe:30 *
* MESSAGE : ZRC=0x83000534=-2097150668 *
* CALLED : OS, -, LookupAccountName *
* OSERR : 1332 "No mapping between account names and *
* security IDs was *
* done." *
* *
* db2dart executes without any errors. This can *
* occur when DB2_EXTSECURITY is set to NO (ie. not enabled) *
* and there is no local DB2ADMNS group. *
****************************************************************
* RECOMMENDATION: *
* db2dart executes successfully, so the messages can be *
* ignored. *
* *
* To work-around the problem, create a local DB2ADMNS group *
* and add the user to this group. This newly created DB2ADMNS *
* group does not require any privileges. *
* *
* The solution is included with FP10. *
**************************************************************** |
| Local Fix: |
None
The error message can be ignored because DB2DART is still
successful.
The work-around is to create DB2ADMNS group and add the ID to
it. You do not need to grant any permissions to this group,
group membership is all that is required to prevent the error
message from being logged. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 v9.7 FP4 |
| Workaround |
Create a local DB2ADMNS group and add the user to this group.
This newly created DB2ADMNS group does not require any
privileges. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.08.2010
02.05.2011
02.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
