home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC78327 Status: Closed

DB2 TOOLS AND STORED PROCEDURES FAIL WITH ERROR SQL1042C

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
If you mount the instance's home directory on a NFS v4 
filesystem on SUSE SLES 10 SP2 many DB2 tools and stored 
procedures fail with the SQL1042C error. The reason is 
executables residing on NFS v4 on SUSE SLES 10 SP2 are required 
to have the read bit set in addition to the execute bit. The DB2 
tools under <INSTANCE_HOME>/sqllib/adm do not have the read bit 
set for "other" therefore these tools cannot be executed. 
 
SQL1042C 
An unexpected system error occurred. 
Explanation: 
 
A system error occurred. Some possible reasons for this error 
are: 
 
    * The database manager is not installed correctly or the 
environment is not set up correctly. 
    * On UNIX-based systems, db2iupdt may need to be run in 
order to update the DB2 instance to enable acquisition of a new 
system configuration or access to function associated with the 
installation or removal of certain product options, FixPaks, or 
modification levels.
Problem Summary:
On NFS V4 it was identified fencid running any SPs or starting a 
Control center will fail with sql1042 because of permission 
problems.
Local Fix:
Add read permission for "other" for all files in 
<INSTANCE_HOME>/sqllib/adm that have only execute permission for 
"other".
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.08.2011
12.03.2012
12.03.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList