Db2 for z/OS & Db2ZAI

Expand all | Collapse all

"CDC Remote Source Db2 z/os lock on database"

  • 1.  "CDC Remote Source Db2 z/os lock on database"

    Posted Fri October 16, 2020 01:27 PM
    @Manas Dasgupta has a question I was wondering if someone here might be able to help out with?

    "So overnight, CDC Capture caused one of our batch utility jobs to abend because of contention. CDC would have had to held on to the lock for a while to have caused a utility timeout.
    Under what circumstances does CDC take lock on a source database?"

    ------------------------------
    Isaiah Brown
    ------------------------------


  • 2.  RE: "CDC Remote Source Db2 z/os lock on database"

    Posted Mon October 19, 2020 03:14 AM
    Hello Isaiah,
    as far as I know if you add a new table under replication and let CDC do the Alter Data Capture change,
    CDC will put an exclusive lock.
    Not sure if this could be your case.
    Regards

    ------------------------------
    Chiara Baldan
    ------------------------------



  • 3.  RE: "CDC Remote Source Db2 z/os lock on database"

    Posted Mon October 19, 2020 03:29 PM
    i checked with some folks and got the following answer to the your question
    CDC for z/OS does not acquire locks on any tables on the source -- it is the DB2 IFI which now acquires a lock when reading the compression dictionary for compressed tables during replication -- the lock is charged to the calling application. The LOGREADCOMMITINTERVAL parameter in CDC for z/OS can be set to have CDC issue periodic commits to release the lock if they are problematic for your client. DB2 recommends a setting of 30.

    ------------------------------
    David Williams
    ------------------------------