IBM Support

PM54299: SQLCODEN302 ADB9011E AN UNEXPECTED SQLCODE WAS FOUND IN INSERT ADBCVERLINES WHEN UNDER DB2 R810 CM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 Administration Tool for z/OS Change Management function
    issues a message:
    ADB9033I The SQLCA sqlcode is -302.
    ADB9011E An unexpected sqlcode was found in Insert adbcverlines.
    when running on a DB2 R810 subsystem in Compatability Mode/CM as
    the QUALIFIER column of table ADBCVERLINES was defined as
    VARCHAR(8) while the program was using VARCHAR(128).
    
    Sample member ADBCHAM8 instructed customers to run the job when
    moving "FROM DB2 V7 TO DB2 V8 (FULL FUNCTION MODE)" therefore
    the ALTER to change the column to VARCHAR(128) was not executed.
    

Local fix

  • Run the ADBCHAM8 member.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the DB2 Administration Tool for     *
    *                 z/OS who run on a DB2 R810 subsystem         *
    *                 in Compatibility Mode (CM) or Enabling       *
    *                 New Function Mode (ENFM).                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS    *
    *                      Change Management function issues a     *
    *                      message SQLCODE=-302/SQLCODEN302:       *
    *                                                              *
    *                      ADB9033I The SQLCA sqlcode is -302.     *
    *                      ADB9011E An unexpected sqlcode was      *
    *                      found in error_function.                *
    *                                                              *
    *                      when running on a DB2 R810 subsystem    *
    *                      in Compatibility Mode/CM as the         *
    *                      QUALIFIER column of table               *
    *                      ADBCVERLINES was defined as             *
    *                      VARCHAR(8) while the program was        *
    *                      using VARCHAR(128).                     *
    *                                                              *
    *                      Submit the SAMP job ADBCHAM8 to         *
    *                      migrate the change management table     *
    *                      from DB2 R710 to DB2 compatibility      *
    *                      mode according to instruction, the      *
    *                      job issues a message SQLCODE=-614/      *
    *                      SQLCODEN614:                            *
    *                                                              *
    *                      DSNT408I SQLCODE = -614, ERROR:         *
    *                      THE INDEX CANNOT BE CREATED OR          *
    *                      ALTERED, OR THE LENGTH OF A COLUMN      *
    *                      CANNOT BE CHANGED BECAUSE               *
    *                      THE SUM OF THE INTERNAL LENGTHS         *
    *                      OF THE COLUMNS FOR THE INDEX            *
    *                      IS GREATER THAN THE ALLOWABLE           *
    *                      MAXIMUM.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The length of column QUALIFIER in table ADBCVERLINES is 8
    characters, but the insert value is more than 8 characters.
    
    When submitting member ADBCHAM8, a SQLCODE=-614/SQLCODEN614
    error is displayed:
    
    DSNT408I SQLCODE = -614, ERROR:  THE INDEX
    CANNOT BE CREATED OR ALTERED, OR THE
    LENGTH OF A COLUMN CANNOT BE CHANGED
    BECAUSE THE SUM OF THE INTERNAL LENGTHS
    OF THE COLUMNS FOR THE INDEX
    IS GREATER THAN THE ALLOWABLE MAXIMUM.
    
    DB2 R810 in the Compatibility Mode and Enabling New Function
    Mode will encounter problems when creating the index because
    the combined key length is 256. DB2 R810 does not support a
    combined key length of 256 until New Function Mode is enabled.
    

Problem conclusion

  • New SAMP job ADBCHU14 has been added to instruct the users on
    how to migrate the Change Management table from DB2 R710 to DB2
    R810 in Compatibility Mode or DB2 R810 Enabling New Function
    Mode.
    
    Updated SAMP job ADBCHAN7 to instruct the users on how to
    migrate the Change Management table from DB2 R710 to DB2 R810
    Compatibility Mode or DB2 R810 Enabling New Function Mode
    and update all QUALIFIER column to CHAR(18).
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM54299

  • Reported component name

    DB2 ADMIN TOOL

  • Reported component ID

    568851500

  • Reported release

    720

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-12-13

  • Closed date

    2012-02-06

  • Last modified date

    2012-03-01

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

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

    UK75978

Modules/Macros

  •    ADBCHAM8 ADBCHAN7 ADBCHU14
    

Fix information

  • Fixed component name

    DB2 ADMIN TOOL

  • Fixed component ID

    568851500

Applicable component levels

  • R720 PSY UK75978

       UP12/02/08 P F202

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"720","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 March 2012