IBM Support

PK61794: SQLCODE-904 WITH RC00C90097 HAPPENS ON READ ONLY SQLS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Read only SQLs get SQLCODE-904 with RC00C90097 when the object
    is COPY pending.
    But RC00C90097 should happen on an update operation.
    In data-sharing environment, local buffer is invalidated when
    other member updates the page.
    If the accessed local buffer is invalidated, the buffer is
    refreshed.
    During the refresh, write claim may happen.
    This write claim caused RC00C90097.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 data sharing users.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Read-only SQL fails with a reason code  *
    *                      implying an update was attempted, such  *
    *                      as RC00C90097 (copy pending) or         *
    *                      RC00C90080 (object started ACCESS=RO).  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If DB2 detects that a cached page has been cross-invalidated and
    needs to be refreshed, it has to acquire an exclusive page latch
    to perform the refresh.  If page latch contention exists, this
    may drive a code path which requests a write claim and upgrades
    the pageset P-lock.  The write claim will fail if the object is
    in a read-only state such as copy pending, even though there is
    no attempt being made to update the page.
    

Problem conclusion

  • The page latch logic has been modified to avoid driving a P-lock
    upgrade and write drain if an exclusive latch is being acquired
    just to refresh an invalidated page.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK61794

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-02-27

  • Closed date

    2008-04-28

  • Last modified date

    2008-06-02

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

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

    UK35941 UK35942

Modules/Macros

  • DSNB1LTS DSNB1LTX DSNDPCB
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R810 PSY UK35941

       UP08/05/13 P F805

  • R910 PSY UK35942

       UP08/05/13 P F805

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 June 2008