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 IC75836 Status: Geschlossen

DBI1309E ERROR IS RETURNED WHEN SETTING DB2_UTIL_MSGPATH AT THE INSTANCE
LEVEL USING DB2SET.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
SQL error DBI1309E is returned when trying to set db2 registry 
DB2_UTIL_MSGPATH at the instance level: 
 
Ex: 
 
As db2 instance owner: 
 
db2set DB2_UTIL_MSGPATH=<path_for_messages> 
 
DBI1309E  System error. 
 
Explanation: 
 
The tool encountered an operating system error. 
 
User response: 
 
A system error was encountered during registry access. Ensure 
that there is enough space on the file system where the registry 
is located, and that there is a valid LAN connection if the 
registry is remote. 
 
According to db2 Info center, this registry is db2 registry and 
can be set at instance level. 
 
 
http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?t 
opic=/com.ibm.db2.luw.admin.regvars.doc/doc/r0005669.html 
 
 
 
However, this registry can be set successfully globally as root 
user or as a system environment variable as db2 instance owner. 
 
 
Ex: 
 
. as root user: 
 
db2set -g DB2_UTIL_MSGPATH=<path_for_messages> 
 
. as db2 instance owner: 
 
export DB2_UTIL_MSGPATH=<path_for_messages> 
 
db2set -all 
 
[e] DB2_UTIL_MSGPATH=<path_for_messages>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users on DB2 V95 FP9 and prior                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v95 FP10                                      * 
****************************************************************
Local-Fix:
As a workaround to the issue, you can apply one of the following 
instructions. 
 
. To set it globally to be applied for all the db2 instances on 
the system, as root run: 
 
db2set -g DB2_UTIL_MSGPATH=<path_for_messages> 
 
or 
 
. to set it at the instance level, as db2 instance owner run: 
 
export DB2_UTIL_MSGPATH=<path_for_messages>
Lösung
First Fixed in DB2 v95 FP10
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
15.04.2011
05.09.2012
05.09.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP10
Problem behoben lt. FixList in der Version
9.5.0.10 FixList