Siebel Remote: How to improve DbXtract performance for S_RR_* tables in 'Extracting enterprise tables' step - before new deployments
(Doc ID 2822844.1)
Last updated on JANUARY 27, 2023
Applies to:
Siebel CRM - Version 20.8 and laterInformation in this document applies to any platform.
Symptoms
Siebel Remote / Replication / Anywhere - on version: 20.8 (and later)
On a Siebel RR environment (i.e. UAT / Pre-Production):
ACTUAL BEHAVIOR: The task for Database Extract (DbXtract) or PDbXtract (Parallel Database Extract) as well - for extracting a Mobile Client's Local Database is taking long time to complete (~3-4hrs).
EXPECTED BEHAVIOR: Under normal circumstances, that extract for a single user should complete faster. (similar to the times it was taking on the pre-upgrade version environment - 15.8)
This was confirmed by the details collected from logs (- various DbXtract*.log) - showing time spent in that 'Enterprise tables' extraction step of up to 3-4hrs and a large number of records being extracted - like for instance:
The issue could be replicated at will in that environment with these steps:
1. Start a new task for DbXtract (or PDbXtract) for a Mobile Client user - either from srvrmgr or Server Admin views (UI);
2. Monitor its execution;
3. Observe that may take 3-4 hrs to complete.
Impact: Due to this issue, Remote users may not have their Local databases extracted in a timely manner. This could delay the preparation for the upcoming Go Live when all Mobile users need to be extracted.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |