In a busy database environment, redo data generation can increase significantly, particularly with the required supplemental logging enabled on your source tables. As we know, an Oracle database will "recycle" its redo logs in a round-robin fashion, switching to the next log when full. GoldenGate scans the redo logs and writes its own Trail files to the
dirdat subdirectory. Although the Trail file data is typically a quarter the size of its equivalent redo data, if left unmanaged, the volume of files in
dirdat can be significant. In the worst case, filling the filesystem to 100% utilized. Obviously this is not ideal, so GoldenGate has provided an automated mechanism for purging Trail files from this area.
This is achieved ...