IBM Support

LI72704: ALTER TABLESPACE NO FILE SYSTEM CACHING ON LINUX FOR S/390 MAY RESULT IN TABLESPACE NOT BEING ACCESSIBLE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Currently, DIO on Linux for S/390 is only supported by DB2 if
    the underlying device is of the SCSI type. However, due to
    a bug in detecting SCSI devices, the ALTER TABLESPACE NO FILE
    SYSTEM CACHING statement issued on Linux for S/390 may result
    in the target tablespace becoming inaccessible.
    .
    The db2diag.log will contain messages similar to:
    .
    2007-11-12-12.28.11.905554-300 E1344A561          LEVEL: Warning
    PID     : 9440                 TID  : 2199111563136PROC : db2age
    INSTANCE: dbguest5             NODE : 000
    APPHDL  : 0-21                 APPID: *LOCAL.dbguest5.0711121728
    AUTHID  : DBGUEST5
    FUNCTION: DB2 UDB, oper system services, sqloseekread64,
              probe:20
    MESSAGE : ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic erro
              DIA8501C A buffer pool logic error has occurred.
    CALLED  : OS, -, unspecified_system_function
    OSERR   : EINVAL (22) "Invalid argument"
    .
    and
    .
    ADM6023I  The table space "<name>" (ID "<id>") is in state 0x"0"
              The table space cannot be accessed.  Refer to the
              documentation for SQLCODE -290.
    .
    Any attempt to access the tablespace, even for the purpose of
    re-enabling file system caching, results in:
    .
    SQL0290N  Table space access is not allowed.
    .
    If the affected tablespace is SYSCATSPACE, the database will
    become unusable as its activation will fail with:
    .
    SQL0902C  A system error (reason code = "") occurred.
    

Local fix

  • The cleanest workaround is to restore the database. If this is
    not feasible, please contact IBM Service for patching the
    SQLSPCS.1 and SQLSPCS.2 tablespace control files.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Same as the Error Description.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * First fixed in DB2 Version 9.1 Fix Pack 9.                   *
    ****************************************************************
    Currently, DIO on Linux for S/390 is only supported by DB2 if
    the underlying device is of the SCSI type. However, due to
    a bug in detecting SCSI devices, the ALTER TABLESPACE NO FILE
    SYSTEM CACHING statement issued on Linux for S/390 may result
    in the target tablespace becoming inaccessible.
    .
    The db2diag.log will contain messages similar to:
    .
    2007-11-12-12.28.11.905554-300 E1344A561          LEVEL:
    WarningPID     : 9440                 TID  : 2199111563136PROC :
    db2ageINSTANCE: dbguest5             NODE : 000
    APPHDL  : 0-21                 APPID:
    LOCAL.dbguest5.0711121728AUTHID  : DBGUEST5
    FUNCTION: DB2 UDB, oper system
    services, sqloseekread64,                  probe:20
    MESSAGE :
    ZRC=0x870F0002=-2029060094=SQLO_BPSE "Debug logic erro
    DIA8501C A buffer pool logic error has occurred.      CALLED  :
    OS, -, unspecified_system_function                    OSERR   :
    EINVAL (22) "Invalid argument"                        .
    and
    .
    ADM6023I  The
    table space "<name>" (ID "<id>") is in state 0x"0"          The
    table space cannot be accessed.  Refer to the
    documentation for SQLCODE -290.                       .
    Any attempt
    to access the tablespace, even for the purpose of   re-enabling
    file system caching, results in:                    .
    SQL0290N
    Table space access is not allowed.                    .
    If the
    affected tablespace is SYSCATSPACE, the database will    become
    unusable as its activation will fail with:               .
    SQL0902C
    A system error (reason code = "") occurred.
    

Problem conclusion

  • Upgrade to DB2 Version 9.1 Fix Pack 9.
    

Temporary fix

  • The cleanest workaround is to restore the database. If this is
    not feasible, please contact IBM Service for patching the
    
    
    SQLSPCS.1 and SQLSPCS.2 tablespace control files.
    

Comments

APAR Information

  • APAR number

    LI72704

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-13

  • Closed date

    2010-05-06

  • Last modified date

    2010-07-16

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

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

    LI72705

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

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:
17 October 2021