Episode Details
Back to EpisodesOracle GoldenGate 23ai: Managing Extract Trails and Files
Description
00:00
Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started!
00:25
Nikita: Welcome back to another episode of the Oracle University Podcast! I'm Nikita Abraham, Team Lead of Editorial Services with Oracle University, and I'm joined by Lois Houston, Director of Innovation Programs.
Lois: Hi there! In our last episode, we discussed the Replicat process. That was a good introduction, and you should give it a listen if you're interested in the fundamentals of GoldenGate 23ai.
00:49
Nikita: Nick Wagner, Senior Director of Product Management for Oracle GoldenGate, is back with us today to talk about how to manage Extract Trails and Files. Hi Nick, it's a pleasure to have you with us. So, we've spoken about trail files in our earlier episodes. But can you tell us about the kind of information that's actually stored in these files?
Nick: The trail files contain committed operations only. In an Oracle environment, the extract process is actually able to understand and read both committed and uncommitted transactions. It holds the uncommitted activity and the cache manager associated settings.
As a transaction is committed, it's then flushing that information to the trail file. All this information in the transaction is preserved, so we have not only the transaction itself, but the order of the operations within that transaction. All the changed columns, including the primary key and any scheduling columns are also captured, and this is controlled by the log or sub calls parameter and other parameters within the extract process.
The data captured depends on settings in the extract file and you can include additional information, including tokens. The trail files also contain metadata information, where the trail files are what we call self-describing, which means that as we start reading in new objects, we start writing the definition of those objects into the trail file themselves.
02:11
Lois: Nick, what does the structure of a trail file look like?
Nick: The trail files have a header information, which simply keeps information about what version of trail fi