home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC95861 Status: Geschlossen

PURESCALE FAILS TO START MEMBER WHERE ONE OR MORE OF ITS ASSOCIATED GPFS
FILESYSTEMS IS SET TO AUTOMOUNT

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
In a AIX DB2 pureScale environment, a member may fail to start 
with the following error: 
 
$ db2start 
12/18/2012 11:48:09     1   0   SQL1063N  DB2START processing 
was successful. 
12/18/2012 11:48:59     0   0   SQL1677N  DB2START or DB2STOP 
processing failed due to a DB2 cluster services error. 
SQL6032W  Start command processing was attempted on "2" node(s). 
"1" node(s) were successfully started.  "0" node(s) were already 
started. "1" node(s) could not be started. 
 
The following error is seen in the db2diag.log at this time: 
 
2012-12-18-11.53.48.188126+060 I19455A370           LEVEL: 
Warning 
PID     : 15204568             TID : 1              PROC : 
db2instance 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: aixhost01 
EDUID   : 1 
FUNCTION: DB2 UDB, high avail services, 
sqlhaCheckMountResourcesOnHost, 
probe:4126 
DATA #1 : <preformatted> 
The mount db2mnt-db2-rs is not online on host aixhost01 
 
Additionally, the state of the resource as seen in the lssam 
output is set to "Stuck Online": 
 
Online IBM.ResourceGroup:db2mnt-db2-rg 
Control=MemberInProblemState Nominal=Online 
        '- Stuck online IBM.Application:db2mnt-db2-rs 
Control=MemberInProblemState 
                |- Stuck online 
IBM.Application:db2mnt-db2-rs:aixhost01 
                |- Online 
IBM.Application:db2mnt-db2-rs:aixhost02 
                |- Online 
IBM.Application:db2mnt-db2-rs:aixhost03 
                '- Online 
IBM.Application:db2mnt-db2-rs:aixhost04 
 
This issue is due to the filesystem, "/db2" in this case, having 
auto-mounting enabled. That is the mount attribute of its entry 
within the "/etc/filesystems" file is set to either "true" or 
"automatic".
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 pureScale users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.3                                           * 
****************************************************************
Local-Fix:
Disable auto-mounting for the filesystem in question by setting 
its "mount" attribute to "false" in the "/etc/filesystems" file.
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem Fixed In 10.5.0.3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.09.2013
03.03.2014
03.03.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList