Long transaction problem

When IDS will used up all the logical log? i.e. the log file below the current logical log file has open transaction also . thanks for your time.

If the percentage of logical logs between the oldest log with open transactions and the current log exceeds the setting of the ONCONFIG parameter LTXHWM the oldest open transaction will be halted and automatically rolled back. If the percentage exceeds LTXEHWM then all transactions are blocked (ie frozen) until that oldest transaction's rollback completes and the oldest logical logs are successfully backed up and freed for reuse. Autonomic settings (ex: AUTO_LOGS) can permit the engine to dynamically add more logical logs if these conditions happen and there is sufficient free space in the dbspaces containing logical logs to reduce the impact of so called "long transactions". Does that answer your question? Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Wed, Sep 7, 2016 at 10:46 AM, CHUAN LU <luchuan@cn.ibm.com> wrote: > When IDS will used up all the logical log? i.e. the log file below the > current > logical log file has open transaction also . > thanks for your time. > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e0102f15cdb1a52053bec775b