Data Integration

 View Only
  • 1.  XMETA - Increased SQL Server Transactions

    Posted Thu January 28, 2021 05:17 PM
    Hello!

    Before 1/20/2021 our XMETA SQL Server transaction logs were averaging ~4MB size every 15min.   The morning of 1/20/2021,  we restarted services and since then the XMETA transactions logs have been MUCH larger than usual.   We're unable to decipher what's hitting XMETA, exactly,  through these *trn files;  only that something is being updated a LOT!  

    Anyone have tips/tricks for diagnosing what is going on here?  TY!


    ------------------------------
    Greg Brown
    Helzberg Diamonds - Data Warehouse Analyst
    gsbrown@helzberg.com
    ------------------------------

    #DataIntegration


  • 2.  RE: XMETA - Increased SQL Server Transactions

    Posted Fri January 29, 2021 10:26 AM
    Greg, because the logging quantity changed after restarting the services, it could be because a debugging environment variable was set that hadn't yet been "activated". Check the project variables, and any jobs that had modifications since the prior reboot to see if they set debugging variables at the job level.

    ------------------------------
    Brian Sprecher
    ------------------------------



  • 3.  RE: XMETA - Increased SQL Server Transactions

    Posted Fri January 29, 2021 01:17 PM
    Thanks, Brian!   You encouraged me to rummage through config files and logs again which led me to stumble upon the issue - DSOMD!!!

    Found in a log file that DSOMD service had stopped back on 11/22/2020
    2020-11-22 02:43:41,264 INFO com.ibm.datastage.runtime.omdmonapp.OMDMonApp.run(OMDMonApp.java:314) - Unexpected exception - application shutting down: Comparison method violates its general contract!

    This process loads operational metadata into OMD tables in XMETA and with that stopped it explains why our SQL transaction logging was much smaller in weeks leading up to our restart on 1/20/2021.  The restart of services on 1/20/2021 restarted this OMD collection and it spent 5 days "catching up" and logging ~1-2GB SQL Server transaction logs every 15min until it finished catching up 1/25/2021 afternoon.   So,  all of this explains why our SQL Server transaction logging went on a rollercoaster ride of lows,  to highs,  to mediums now with OMD processing normally again.

    ------------------------------
    Greg Brown
    ------------------------------