|
Problem IT09405
|
Status: Closed |
LONG CONNECTION TIME POSSIBLE WHEN LARGE GROUP LIST HAS TO BE SCANNED TO FIND OUT IF USER IS DBSA USER |
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
You may notice that connections are taking long when you have a
large number of groups, eventually served by a directory
service.
An indication that this applies would be that you will find an
sqlexec thread taking considerable time in the function
atdbsal(). This can be investigated, for example, by taking
multiple stacks of the instance processes with means of the
operating system (using pstack, gstack, procstack, ...) .
A sample stack would be:
getgrent
atdbsal
isAdminuser
sqopendb
excommand
sq_execute
sqmain
spawn_thread
th_init_initgls
startup
Please note you will need to find the exact same thread for the
same connection attempt multiple times in this stack to verify
that this applies.
When you have only one DSBA group (UNIX would allow you to
allocate several groups with different names but one group id)
you can consider to set the environment variable
IFX_SIMPLE_GROUPS to 1. Then the exhaustive search through all
available groups will be skipped and under this condition
getgrgid() should be sufficient to determine if the user is in
the DBSA group or not.
When this condition is not met the workaround may lead wrongly
treat a DBSA user as non-DBSA user when this decision is made
for a group that is not returned via getgrgid(). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Customers with many connections and a large number of groups *
* eventually served by a directory service. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* The workaround to set ONCONFIG parameter *
* ADMIN_USER_MODE_WITH_DBSA to 0. *
* If this is not possible, update to IDS version 12.10.xC9. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.06.2015
10.07.2017
10.07.2017 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC9
|
| Problem solved according to the fixlist(s) of the following version(s) |
