IBM Support

IY98037: CLI APP CALLING NONEXISTENT STORED PROC WITH A NAME EXACTLY 27 CHARACTERS LONG WILL CAUSE BOTH V8 AND V9 DB SERVERS TO TRAP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The DB2 server will trap when a CLI application makes a call to
    a stored procedure that does not exist on the database server
    and the name of the stored procedure is exactly 27 characters
    long. The 27 characters include the schema name, plus the 'dot',
    plus the routine name. Therefore, if a procedure with an eight
    character schema name and an 18 character routine nameis called
    by a CLI application and the stored procedure does not exist on
    the database server, the database server will crash regardless
    of whether the server is at the version 8 release or the version
    9 release.
    .
    The symptoms for this problem are messages in the db2diag.log
    that show a sqleagnt_sigsegv from a db2agent process followed
    by further messages indicating "Error in agent servicing
    application"
    .
    The stack traces are not useful because the stack traceback is
    corrupt and is not displayed in the trap files that are produced
    by DB2. The only way to debug this problem was to manually
    unwind the stack that existed in the core file.
    

Local fix

  • Avoid calling nonexistent stored procedures from CLI
    applications where the procedure name is exactly 27 characters
    long (including the . (dot))
    

Problem summary

  • USERS AFFECTED: All
    PROBLEM DESCRIPTION: Calling a non-existent stored procedure
                         with a name that is exactly 27 characters
                         long ('schema name' + '.' + 'SP name') from
                         a CLI application will cause the DB2 engine
                         to trap on the server.
    .
                         The stack trace of the PID that crashed is
                         also corrupted and not useful.
    .
                         The core file is needed in order to see
                         what functions were being called by the PID
                         the db2diag.log only dumps information
                         indicating that the instance is coming down
                         and also provides the name of the stored
                         procedure that is being called when the
                         trap occurs.
    .
    PROBLEM SUMMARY: Please see the PROBLEM DESCRIPTION above.
    

Problem conclusion

  • Problem was first fixed in Version 9,
                        fixpack 4 (s071028).
    

Temporary fix

  • Avoid calling non-existent stored procedures that
                   are exactly 27 characters long, from a CLI
                   application.
    

Comments

APAR Information

  • APAR number

    IY98037

  • Reported component name

    DB2 CEE AIX

  • Reported component ID

    5765F3000

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / Pervasive

  • Submitted date

    2007-05-01

  • Closed date

    2007-11-28

  • Last modified date

    2008-03-11

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

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

    IY98039 IZ07982

Modules/Macros

  • ENGN_SQE
    

Fix information

  • Fixed component name

    DB2 CEE AIX

  • Fixed component ID

    5765F3000

Applicable component levels

  • R910 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
08 January 2022