JR35683: AFTER LOAD CLIENT FAILURE, DB2 TABLESPACE IS IN 0X20020 STATE, BUT LOAD QUERY SHOWS TABLE IN NORMAL STATE.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Note: This APAR fixes the problem only when client and server
    systems are of the same endian, i.e. both are big-endian
    platforms or both are little-endian platforms. APAR IC78755
    fixes the problem in all cases.
    Big-endian platforms are AIX, HP on IA64, Solaris SPARC, Linux
    on zSeries, Linux on pSeries.
    Little-endian platforms are Solaris x64, Linux on IA-64, Linux
    on AMD64 and Intel EM64T, 32-bit Linux on x86, Windows.
    
    If the input file is incorrect while loading a table with LOAD
    CLIENT, load encounters error, and the tablespace is left in
    "Load in progress" state.  For example:
    
    1:-
    ---
    
    LOAD CLIENT FROM C:\a.del OF DEL MODIFIED BY COLDEL0x09
    USEDEFAULTS METHOD P (1, 2, 3)  replace INTO AYSEL.TABLO1 (A, B,
    C) COPY NO INDEXING MODE AUTOSELECT
    
    SQL3039W  The memory available to LOAD for DATA BUFFER prohibits
    full
    LOAD parallelism.  Load parallelism of "4" will be used
    
    SQL3109N  The utility is beginning to load data from file
    "C:\a.del".
    
    SQL2036N  The path for the file or device "C:\a.del" is not
    valid.
    
    SQL3107W  There is at least one warning message in the message
    file.
    
    Number of rows read         = 0
    Number of rows skipped      = 0
    Number of rows loaded       = 0
    Number of rows rejected     = 0
    Number of rows deleted      = 0
    Number of rows committed    = 0
    
    
    2:-
    ---
    
    LOAD query table AYSEL.TABLO1
    
    SQL3039W  The memory available to LOAD for DATA BUFFER prohibits
    
    full LOAD parallelism.  Load parallelism of "4" will be used
    
    SQL3109N  The utility is beginning to load data from file
    "C:\a.del".
    
    SQL2036N  The path for the file or device "C:\a.del" is not
    valid.
    
    SQL3532I  The Load utility is currently in the "UNKNOWN" phase.
    
    Tablestate:
    Load in Progress
    
    
    3:-
    ---
    Customer terminates LOAD:
    
    LOAD CLIENT FROM C:\a.del OF DEL MODIFIED BY COLDEL0x09
    USEDEFAULTS METHOD P (1, 2, 3)  terminate INTO AYSEL.TABLO1
    
    SQL3110N  The utility has completed processing.  "0" rows were
    read from the input file.
    
    Number of rows read         = 0
    Number of rows skipped      = 0
    Number of rows loaded       = 0
    Number of rows rejected     = 0
    Number of rows deleted      = 0
    Number of rows committed    = 0
    
    
    4:-
    ---
    Customer checks the table state:
    
    LOAD query table AYSEL.TABLO1
    
    Tablestate:
    Normal
    
    
    5:-
    ---
    Customer checks the tablespace
    
    
    Name     = AYSELTS01
    Type     = System managed space
    Contents = All permanent data. Regular table space.
    State    = 0x20020
               Detailed explanation:
               Backup pending
               Load in progress
    
    
    Although no load job are running and table is in normal state,
    the tablespace is left in "Load in progress" state. As a result
    customer cannot take any backup.  Drop/Create Tablespace or
    db2stop/db2start solves the issue.  Deactivate the database or
    disconnect all clients from the database should also clear the
    "Load in progress" state.
    

Local fix

  • Deactivate the database or disconnect all clients from the
    database should clear the "Load in progress" state.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * db2 luw                                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Although no load job runs and table is in normal state,      *
    * tablespace is  left in "Load in progress" state.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * The fix will be fixed in db2_v95fp6.                         *
    * The future releases also include this fix.                   *
    * The customer needs to upgrade to db2_v95fp6 or higher        *
    * releases.                                                    *
    ****************************************************************
    

Problem conclusion

  • When the no load job runs and table is in normal state,
    tablespace will not be left in "Load in progress" state.
    The fix will be fixed in db2_v95fp6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR35683

  • Reported component name

    SPATIAL EXT SUN

  • Reported component ID

    5648D6102

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-17

  • Closed date

    2010-09-16

  • Last modified date

    2011-09-19

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

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

    JR35724 IC73677

Fix information

  • Fixed component name

    SPATIAL EXT SUN

  • Fixed component ID

    5648D6102

Applicable component levels

  • R950 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Replication Server

Software version:

950

Reference #:

JR35683

Modified date:

2011-09-19

Translate my page

Machine Translation

Content navigation