Q and A

Asked and Answered

Top Ten Performance Tips

What is a "high water mark" and what does it tell you?

Scott Hayes responds:

A high water mark is a maximum value observed by DB2. The observation period begins when the monitor switches are turned ON. High water marks can often be used to help set certain configuration values, to ensure sufficient resources are available for peak demand times.

I am using Circular Logs with all 4GB size used with 80+30 Logs as Pro. [and] Sec. logs. I am getting 'Transaction Logs FULL.' Any suggestions?

Scott Hayes responds:

In answer to your question below, if the circular logs are becoming full, then you have a connection to the database that has work (DML-Insert, Updates, Deletes) that hasn't been committed or rolled back. You should make sure your DB2 connections commit their work to avoid filling up the DB2 logs.

I have 22 million rows to be inserted and using commit after every 1000 rows generated. Do I need to increase commit point? I have few jobs running parallel.

Scott Hayes responds:

Try a commit every 500 inserts. More importantly, make sure there are no other connections that have not issued a commit. One idle connection that hasn't committed could cause your logs to fill during high insert volume from other connections. You might try terminating all connections except the insert jobs/scripts.

See a complete archive of reader/author Q&As .

Back to Top 10 Performance Tips by Scott Hayes.