DB2 FOR LUW / DB2FORLUW / A10 - DB2

Migration of 32-bit 9.7 databases to 64-bit version of DB2 v9.7, 
v9.8 or v10.1 does not revalidate the LANGUAGE SQL system 
routines the database, including system modules like 
`SYSIBMADM.UTL_MAIL'. 
 
Here is a sample error message when you call routine 
'SYSIBMADM.UTL_MAIL' : 
 
CALL UTL_MAIL.SEND_ATTACH_VARCHAR2(v_sender, v_recipients, 
NULL.NULL, v_subj, v_msg, NULL, NULL, 
v_attachment,False,null,v_att_name); 
 
DB21034E The command was processed as an SQL statement because 
it was not a valid Command Line Processor command. Durinq SQL 
processinq it returned: 
SQL0471N Invocation of routine 
"SYSIBMADM.UTL_MAIL.SEND_ATTACH_VARCHAR2" failed due to reason 
"1". SQLSTATE=5502

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* contact DB2 Support to obtain fix-up tool specific to        * 
* release and build level                                      * 
****************************************************************

Workaround for this issue is to create a new 64-bit database on 
a 64-bit instance (which will fix the issue with the system 
routines), then recreate all DDL, export the data from the 
existing database, and import it into the new one.  Basically, 
rebuild the database from scratch and import the data in.

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

There is no permanent resolution to this problem that can be put 
into fix pack, this has to be addressed per customer basis. 
In case of occurrence , APAR text  contains request to contact 
DB2 Support to obtain fix-up tool specific to release and build 
level. 
This tool has been added to 
/vbs/db2tools/dbappext/utility/src/pvmMigration. 
 
Run the internal-use-only 'db2svcpw' utility to generate a 
service mode password for the customer.  Provide the password, 
along with the 'pvmMigration' tool, to the customer experiencing 
the problem. 
 
Please ask the customer to : 
1. set up the service password.  (Substitute the actual password 
for 'password', below.) 
    export DB2SVCPW=password 
    db2stop 
    db2start 
 
2. Run the pvmMigration tool: 
    pmvMigration <dbname>

not known / see Local fix

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

07.05.2013
01.10.2013
01.10.2013