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 IC91786 Status: Closed

DB2CLUSTER -CFS -ENTER -MAINTENANCE -ALL WILL STOP AIX TRACE VIA MMTRACE
STOP.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2cluster -cfs -enter -maintenance -all will stop AIX trace via 
mmtrace stop. 
 
mmtrace stop is calling trcstop, so the /usr/bin/trace stopped 
by mmtrace stop. 
 
From mmtrace script. 
function stopTrace 
{ 
  typeset sourceFile="mmtrace.sh" 
  [[ -n $DEBUG || -n $DEBUGstopTrace ]] && set -x 
 
  if [[ $osName = AIX ]] 
  then 
    # Stop the current trace 
    $trcstop >/dev/null 2>&1 
 
# Stop the current trace, producing a trace report if requested. 
if [[ $trace_action = "stop" || ($trace_action = "cycle" && 
$USERELAY -eq 0) ]] 
then 
  stopTrace 
  rc=$? 
  #  If stopTrace fails, remove the lock 
  if [[ $rc -ne 0 && $havelock = "yes" ]] 
  then 
    freeLock_local mmtraceExecLock 
  fi 
fi # end of if [[ $trace_action = "stop" ]] 
 
"There's no need to stop tracing on AIX during a GPFS upgrade. 
On Linux, it's necessary because the tracing subsystem is a part 
of GPFS. 
That said, if GPFS code is being updated, leaving tracing on for 
GPFS needs makes little sense. 
However, if tracing is enabled for troubleshooting something 
unrelated to GPFS, there's no need to stop it."
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 3.                   * 
****************************************************************
Local Fix:
You can manually re-enable AIX tracing using 'trace' facility 
provided by AIX. 
More details might be accessed from either AIX user manual or 
AIX experts.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList