Db2

Db2

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  how to track why so many internal commits are happening?

    Posted 2 days ago

    hi,

    the question is for learning purpose only, not in a real time client issue.

    i have a database activated and just left it alone and looked at database snapshot for commit statements and internal commits.

    No applications are connected, just the database is idle for more than 20 minutes. but i get more than 30 internal commits after some time. i just really idling not even any users connected. how to figure out why such behaviour or db2 decides to commit 40 times on idle database.

    i use db2 get snapshot for database statement to monitor internal commits monitor element.

    thanks,

    harish pathangay



    ------------------------------
    Harishkumar Pathangay
    ------------------------------


  • 2.  RE: how to track why so many internal commits are happening?

    Posted 2 days ago

    Hi,

    There are several places where an internal commit may be issued; most obvious is CONNECT_PROC, TERMINATE and CONNECT RESET, but also any automatic maintenance tasks, WLM tasks, monitoring tasks, STMM, Health Monitor may contribute to number of internal commits. 



    ------------------------------
    Jan Nelken
    Db2 (LUW) DBA
    Open for work
    Katowice or Krakow
    +48 783 109 863
    ------------------------------

    Original Message


Related Content