home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC83109 Status: Closed

SQL0444N REASON CODE: "6" WHEN MOVING LEGACY DATABASES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Getting error: 
 
SQL0444N  Routine "*_GET_FCM" (specific name "MON_GET_FCM") is 
implemented 
with code in library or path 
"...M\SQLLIB\bin\routine\db2dbroutext", function 
"monGetFcm" which cannot be accessed.  Reason code: "6". 
SQLSTATE=42724 
 
After doing db2updv97 -d on a UDB databases.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* SQL0444N REASON CODE: "6" WHEN MOVING LEGACY DATABASES       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in fix pack 7 of v9.7                            * 
****************************************************************
Local Fix:
N/A
available fix packs:
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

Solution
First fixed in fix pack 7 of v9.7
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC83858 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.05.2012
29.01.2013
29.01.2013
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList