Informix - Problem description
Problem IC99525 | Status: Closed |
DEBUG FILE FOR MAPPED USER IS NOT PRE-PENDED WITH THE USERNAME | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
When you connect to an Informix instance with a mapped user that has a non-OS surrogate ID an explain file will be written to the directory $INFORMIXDIR/users/server_SERVERNUM/uid_UID USERNAME_sqexplain.out (if no location for it is specified). The SERVERNUM will be the servernum of the instance, the UID the uid of the mapped user and the USERNAME the name of the mapped user. From the documentation you would expect to find the debug file in the same directory with the user name of the mapped user pre-pended to it. As example if you would name the debug file "mydebug.out" then you would expect it to be written to $INFORMIXDIR/users/server_SERVERNUM/uid_UID/USERNAME_mydebug.out . However, currently it will be written to $INFORMIXDIR/users/server_SERVERNUM/uid_UID/mydebug.out. If several mapped users would run an SPL with active tracing then all would use the same file. If the debug file is having a relative pathname it would not be the filename we would expect. For a non-mapped user the relative path would turn out to be starting with the user's home directory. In this case the debug files for different users would be in different locations and hence different files. One could circumvent this to a degree by adding HOME 'MAPPED_USER_HOME_DIRECTORY' to the user creation, but this would mean additional administrative overhead and the create user statement would then have to include the UID/USER and GROUP properties as well (just trying to specify HOME in the PROPERTIES of CREATE USER would result in a syntax error). | |
Problem Summary: | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Comment | |
version 12.10.xC6 will have this fix for mapped users. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.02.2014 30.12.2015 30.12.2015 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
12.10.xC6 |