DB2 FOR LUW / DB2FORLUW / 970 - DB2

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>

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on DB2 V97 FP4 or lower                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DBI1309E ERROR IS RETURNED WHEN SETTING DB2_UTIL_MSGPATH AT  * 
* THE INSTANCE LEVEL USING DB2SET.                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 v97FP5.                                            * 
****************************************************************

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>

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

With APAR fix, the error message will not be returned and the 
registry can be set successfully.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC75835 IC75836 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

11.04.2011
12.12.2011
12.12.2011

9.7.FP5