I have a situation where a third-party application accessing a DB2 database periodically fills up the log files
which eventually leads to filesystem full problems. Since we don't have anyway of modifying third-party vendor
code to add commits or such things, I am wondering if they is any way possible to make DB2 take a commit
outside of the application accessing the DB2 database? When this happens, the server/database is rebooted and the application
restarted. I will like to eliminate this problem.
What I am trying to say is this: Can DB2 Checkpointing for example be used in anyway to "induce" a kind of
commit for the system and application without having to reboot every time I have a system full stoppage?
Any and all suggestions is appreciated.
LSB Version: :core-3.0-ia32:core-3.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch
Distributor ID: RedHatEnterpriseES
Description: Red Hat Enterprise Linux ES release 4 (Nahant Update 9)