How Does FBDA Operate And How Can We Manage The Workload Better (Doc ID 2101765.1)

Last updated on NOVEMBER 07, 2023

Applies to:

Goal

Over the last 2+ years, we have utilized Oracle Total Recall (FBDA) to keep a history of changes for many tables in our main database. During that time, we've experienced quite a few performance problems and have worked with Oracle support to gather information and have gotten patches to correct issues, when needed. During this time, as part of various SRs, I have asked for information on how FBDA does its processing and have not gotten a complete answer. I would like to formally request more information on how FBDA does its work.

1. From what I can tell, when data is modified in an FBDA-enabled table, the changes are registered in a temporary system table. That data is then merged into another temporary system table and deleted from the first one. After this, the data is merged into the main system FBDA table and deleted from the previous temp table. Is this correct?

2. What triggers the processing of data through the path laid out in #1? We see an FBDA process that runs and will run some statements, but we also see MERGE, DELETE, and INSERT statements against the FBDA tables run by application sessions. How and why are those run? Does that happen every time a modification to an FBDA-enabled table occurs?

3. Are records written to the FBDA system table when inserting records? There is some confusion here on this.

4. Why would the processing of FBDA records cause contention and waits for the main table? How can we reduce that?

5. How can we control when the management of the FBDA data happens? What triggers the processing? Time? Amount of changes? Something else? Can that be tuned? Is it possible to delay the processing until after hours?

Thank you for your help in getting answers for these questions.
Rick
 

Solution

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