DB2 - Problembeschreibung
Problem IT04060 | Status: Geschlossen |
PROFILE.ENV HAS WRONG OWNERSHIP AFTER DB2IUPGRADE, DB2ICRT, OR DB2IUPDT OF ANOTHER INSTANCE | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
In an environment with multiple instances, db2iupgrade/db2icrt/db2iupdt of an instance may alter the file ownership of another instance's profile.env. This is because the wrong instance (and wrong instance path) is temporarily set during db2iupgrade/db2icrt/db2iupdt. The incorrect ownership of profile.env will cause db2set commands to fail with permission error. For example, suppose a server has instances db2inst1 and db2inst2. After db2inst1 is upgraded, a db2iupgrade of db2inst2 results in an update to db2inst1's profile.env; db2inst1's profile.env will be owned by db2inst2, while db2inst2's profile.env remains unaltered. If another instance is created (e.g. db2icrt -u xxxxxxxx db2inst3), then db2inst2's profile.env will be owned by db2inst3. This problem is introduced in v10.5 FP4. The profile.env ownerships will need to be corrected manually by root. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to DB2 v10.5 Fix Pack 5 * **************************************************************** | |
Local-Fix: | |
N/A | |
Lösung | |
Problem first fixed in DB2 v10.5 Fix Pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.08.2014 19.10.2015 04.05.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |