IBM Support

IC97598: AFTER LOGS BECOME FULL, AN INSERT INTO A GLOBAL TEMPORARY TABLE (DGTT) FAILS WITH SQL0901N

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The following steps reproduce the problem (must be done on a
    non-catalog node):
    
    CONNECT TO TEST
    CREATE USER TEMPORARY TABLESPACE SYSTOOLSTMPSPACE IN IBMCATGROUP
    MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 4
    DECLARE GLOBAL TEMPORARY TABLE SESSION.TEMP_EMP (EMPNO  CHAR(6)
    NOT NULL, SALARY DECIMAL(9, 2), BONUS  DECIMAL(9, 2), COMM
    DECIMAL(9, 2)) WITH REPLACE ON COMMIT PRESERVE ROWS
    INSERT INTO SESSION.TEMP_EMP VALUES ('123456', 20.00, 10.00,
    5.00)
    DROP TABLE SESSION.TEMP_EMP
    ==> produces SQL0964C  The transaction log for the database is
    full.  SQLSTATE=57011
    DROP TABLE SESSION.TEMP_EMP
    DECLARE GLOBAL TEMPORARY TABLE SESSION.TEMP_EMP (EMPNO  CHAR(6)
    NOT NULL, SALARY DECIMAL(9, 2), BONUS  DECIMAL(9, 2), COMM
    DECIMAL(9, 2)) WITH REPLACE ON COMMIT PRESERVE ROWS
    INSERT INTO SESSION.TEMP_EMP VALUES ('123456', 20.00, 10.00,
    5.00)
    ==> produces SQL0901N  The SQL statement failed because of a
    non-severe system error.  Subsequent SQL statements can be
    processed.  (Reason "sqlrl_userTempIUD: tid/fid not found".)
    SQLSTATE=58004
    CONNECT RESET
    
    On a non-catalog node, when the logs are full db2 responds with
    SQL0964C on the first DROP TABLE.  Even though the DROP TABLE
    failed, the first INSERT still remains in the APM cache as
    valid.  On the
    second INSERT, db2 tries to use the first INSERT's tid/fid, thus
    resulting in the -901.
    
    On the catalog node, both DROP TABLE statements fail with
    SQL0964C.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 v10.1 fix pack 4.                             *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 v10.1 fix pack 4.
    

Temporary fix

  • N/A
    

Comments

APAR Information

  • APAR number

    IC97598

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-11-12

  • Closed date

    2014-09-22

  • Last modified date

    2014-09-22

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

    IC93140

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 10.1

Reference #: IC97598

Modified date: 22 September 2014