IBM Support

IC87081: SQL0471N IS RETURNED UPON CALLING LANGUAGE SQL ROUTINES AFTER MIGRATION OF 32-BIT DATABASES TO 64-BIT VERSION

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as Permanent restriction.

Error description

  • Migration of 32-bit Version 9.7 databases to 64-bit versions of
    DB2 Version 9.7, 9.8, or 10.1 does not revalidate LANGUAGE SQL
    user and system routines, including system modules like
    'SYSIBMADM.UTL_MAIL'.
    
    Here is a sample error message that might appear 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. During SQL
    processinq it returned: SQL0471N Invocation of routine
    "SYSIBMADM.UTL_MAIL.SEND_ATTACH_VARCHAR2" failed due to reason
    "1". SQLSTATE=5502
    
    The purpose of this APAR is to create a tool called pvmMigration
    that will migrate both user and system 32-bit routines to 64-bit
    versions.  Please contact IBM DB2 Support to obtain the tool for
    your db2level.
    
    Note: It is recommended to upgrade first to at least DB2 Version
    9.7 Fix Pack 8 to use the tool.  It may work on earlier Fix
    Packs; however, this has not been tested.
    

Local fix

  • It is possible to correct a user routine by dropping and
    recreating it.
    
    In the absence of the 'pvmMigration' tool, it is possible to
    correct the system routines with the following workaround:
    
    First, create a new 64-bit database on a 64-bit instance; this
    will create fresh 64-bit versions of the system routines.  Once
    the database is created, 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
    from the old database into the new one.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 LUW v97 v101                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please contact DB2 support to obtain a tool, specific to     *
    * your release and build level, that will repair the system    *
    * module definitions in your database.                         *
    ****************************************************************
    

Problem conclusion

  • Please contact DB2 support to obtain a tool, specific to your
    release and build level, that will repair the system module
    definitions in your database.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC87081

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-09

  • Closed date

    2013-05-13

  • Last modified date

    2013-06-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC92134

Fix information

Applicable component levels



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC87081

Modified date: 04 June 2013


Translate this page: