DB2 - L

 View Only

  • 1.  IRLM error message when dropping multiple objects

    Posted Mar 11, 2022 10:33 AM
    We were dropping several objects when we got an IRLM error message:
    DXR142E 
    The drops worked without an IRLM error when done a few at a time.
    Is this an indication of a problem with one of our structures?
    These are obsolete objects not being used.
    Why would there be "inter-db2" interest?
    thanks
    Bill


    ------------------------------
    williamgiannelliMe
    ------------------------------


  • 2.  RE: IRLM error message when dropping multiple objects

    Posted Mar 11, 2022 10:44 AM
    Bill,

    You don't mention what type of objects you are dropping. If you are dropping a large number of tables and/or partitions then DB2 potentially has a lot of clean-up to do on SYSIBM.SYSCOPY. So you are updating (delete entries) from the DB2 catalog,  this might be where your inter-db2 interest comes from.

    You might modify you approach to do the following
    1) Break the DROP's into multiple smaller units of work 
    2) Run MODIFY RECOVER before the drop(s) to remove SYSCOPY rows

    HTH
    Jack

    ------------------------------
    Jack Campbell
    Saxon Consulting, Inc.
    ------------------------------

    Original Message


  • 3.  RE: IRLM error message when dropping multiple objects

    Posted Mar 11, 2022 11:51 AM
    Yup. Since these objects are obsolete and there's no need to maintain a UOW, a COMMIT every so many DROPs should free a lot of those catalog locks. (Catalog is almost all row-level locking now) That'll get you through the current effort.

    This raises an interesting possibility - the manuals state that NUMLKUS applies to catalog locks (except BIND activities). This has shown that whatever your NUMLKUS is set to, a single user is capable of depleting locks in the CF structure. Your current applications may not often take that many locks, but you may want to evaluate whether your lock structure is big enough in case some operation DOES push up against that limit.

    Unless this isn't Production - in which case, ignore that last bit. :)


    ------------------------------
    Mark Wieczorkowski
    ------------------
    Db2 Systems Programmer, SSA/DCS
    Principal - Solipsistic, LLC
    ------------------------------

    Original Message


  • 4.  RE: IRLM error message when dropping multiple objects

    Posted Mar 11, 2022 12:59 PM
    Maybe also use MODIFY to ditch all the image copies (and log references) too BEFORE doing the drops

    Phil G

    Sent from my iPad



    Original Message


  • 5.  RE: IRLM error message when dropping multiple objects

    Posted Mar 14, 2022 05:25 AM
    And possibly MODIFY STATISTICS if you have History Stats. If you gather these regularly and have objects with many partitions, then you could find you have a large number of rows in the History Tables

    ------------------------------
    Pete Woodman
    ------------------------------

    Original Message


  • 6.  RE: IRLM error message when dropping multiple objects

    Posted Mar 15, 2022 04:57 AM

    Good shout.  Some time ago here (IIRC) some drops timed out because there was years of stats history attempting to be removed in one UR when the TS they were for was being dropped.  Hadn't been an issue before, but that focused the mind a little.  So yes, Modify Recovery and Modify Stats before a no-going-back Drop is an excellent suggestion.

     

    Cheers,

     

     

    Raymond

     




    Original Message