DB2 - Problembeschreibung
Problem IC86408 | Status: Geschlossen |
CHANGES TO THE SOLARIS SMF DB2FM SERVICE MANIFEST AND METHODS. FIXES INCOMPLETE IMPLEMENTATION PROVIDED BY IC84200 | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
The following issues have been discovered: 1. The db2fmcu utility may fail to create the service manifest file. It attempts to create the file in the /var/svc/manifest/application/database directory which might not necessarily exist. Steps to reproduce (on a zone in which the /var/svc/manifest/application/database directory does not exist) a. invoke "./db2fmcu -u -p DB2DIR/bin/db2fmcd" as root Fix: Create the service manifest and startup method file in the DB2DIR/cfg directory. 2. The db2fmcu utility does not delete the service manifest and startup method files. In addition to this, it also disables the service instead of removing it from the repository. Steps to reproduce (on a zone in which the db2fm SMF service has been configured): a. invoke "./db2fmcu" -d as root Fix: the service manifest and startup method files are deleted and the service is removed from the repository. 3. Implementation does not support the disable method. Steps to reproduce (on a zone in which the db2fm SMF service has been configured): a. root@host01:bin# svcs database/db2fm STATE STIME FMRI online 16:50:48 svc:/application/database/db2fm:default b. root@host01:bin# svcadm disable db2fm c. root@host01:bin# svcs database/db2fm STATE STIME FMRI disabled 16:56:15 svc:/application/database/db2fm:default d. root@host01:bin# pgrep db2fmcd 15709 e. root@host01:bin# ps -fp 15709 UID PID PPID C STIME TTY TIME CMD root 15709 1599 0 16:50:49 ? 0:01 /opt/IBM/db2/V9.7B/bin/db2fmcd Fix: The current implementation of the disable method is a no-op, the fix is to issue a kill against the db2fmcd process in this case. APAR IC84200 should have fixed the issue, however did not completely resolve the issue. This APAR is to fix the following: 1. db2fmcu fails to create the manifest. -> The manifest and startup method will be created in the DB2DIR/cfg directory. 2. db2fmcu fails to clean up when asked to do so. -> Running db2fmcu -d will now delete the service and the corresponding manifest and startup method files. 3. Implementation does not support disable. -> Stop and refresh methods are now implemented. This APAR also updates service properties: before fix: general framework general/single_instance boolean true start method start/exec astring /lib/svc/method/db2fm start/timeout_seconds count 30 start/type astring method stop method stop/exec astring :true stop/timeout_seconds count 0 stop/type astring method startd framework startd/duration astring contract with fix: general framework general/single_instance boolean true network dependency network/entities fmri svc:/milestone/network:default network/grouping astring require_all network/restart_on astring none network/type astring service filesystem-local dependency filesystem-local/entities fmri svc:/system/filesystem/local:default filesystem-local/grouping astring require_all filesystem-local/restart_on astring none filesystem-local/type astring service filesystem-autofs dependency filesystem-autofs/entities fmri svc:/system/filesystem/autofs:default filesystem-autofs/grouping astring optional_all filesystem-autofs/restart_on astring none filesystem-autofs/type astring service start method start/exec astring /lib/svc/method/db2fm start/timeout_seconds count 60 start/type astring method stop method stop/exec astring :kill stop/timeout_seconds count 60 stop/type astring method refresh method refresh/exec astring ":kill -HUP" refresh/timeout_seconds count 60 refresh/type astring method startd framework startd/duration astring contract | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * SOLARIS * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 2 * **************************************************************** | |
Local-Fix: | |
N/A | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 2 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 06.09.2012 18.12.2012 18.12.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.2 | |
10.5.0.2 |