Siebel Remote - Big .DX Files Generated in DOCKING\TXNPROC After Re-enabling SvrTblCleanup Component (Doc ID 2991458.1)

Last updated on DECEMBER 12, 2023

Applies to:

Symptoms

On a Production Siebel Remote environment, after starting the Server Tables Cleanup (SvrTblCleanup) component was found to be not actually running for quite some time (~few months) due to an incorrect parameter set.
Once this has resumed working as expected, it was observed that some very large .DX files were created in the Docking\TXNPROC folder.
And this has resulted in remote transactions (txns) backlogs, despite seeing no errors on the Transaction Processor and Router components.


Under normal conditions, it would be expected to see some normal size .DX files being created. And no backlog accumulation.


The Steps to replicate the issue were:

1. Prevent SvrTblCleanup task / component from running for some time (- stop, disable it);
2. Wait until many records would accumulate in S_SRM_* and related tables (for some days or even more);
3. Then start this component to clean-up those records that are no longer needed;
4. Check the impact on the DX files generated in TXNPROC for Remote use.

Changes

 Correct the parameter that was causing earlier the SvrTblCleanup component to not start properly (- Threaded=False; as that was set to True before).

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.