• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (1)

1 MukeshDesai commented Permalink


What is also contributing to this error, as evidenced at 2 of my AVP customers, is the customer workload that saturates the network beyond the system capacity and db2 becomes a victim. One solution was to identify the time of error and what is running in the system. We found ETL team was running 20 concurrent LOAD jobs that brought the database to its knees and we eliminated the main culprit from the LOAD jobs that was causing this error. It was also time to put ETL under WLM controls. Based on my experience, its mainly work load induced error as these errors only start showing up when the system was stretched to its limits. Hope this helps.

Add a Comment Add a Comment