Oracle GoldenGate Subdirectories
Learn about the subdirectories of the Oracle GoldenGate Classic Architecture installation directories; it does not apply to the Oracle GoldenGate Microservices Architecture.
Table 1-2 Oracle GoldenGate Classic Architecture Installed Subdirectories
Directory | Description |
---|---|
|
Contains the checkpoint files for the bounded recover feature. |
|
Contains the property and XML files that are used to configure Oracle GoldenGate Monitor. |
|
Contains the data store that is used to persist information that is gathered from an Oracle GoldenGate instance for use by the Oracle GoldenGate Monitor application or within Oracle Enterprise Manager. |
|
Contains the checkpoint files created by Extract and Replicat processes, which store current read and write positions to support data accuracy and fault tolerance. Written in internal Oracle GoldenGate format. File name format is Do not edit these files. Examples:
|
|
Contains credential store files. |
|
The default location for Oracle GoldenGate trail files and extract files that are created by Extract processes to store extracted data for further processing by the Replicat process or another application or utility. Written in internal Oracle GoldenGate format. File name format is a user-defined two-character prefix followed by either a 9-digit sequence number (trail files) or the user-defined name of the associated Extract process group (extract files). Do not edit these files. Examples:
|
|
The default location for data definitions files created by the
These files may be edited to add definitions for newly created tables. If you are unsure of how to edit a definitions file, contact Oracle GoldenGate technical support. Example:
|
|
Contains trace, or dump, files that support the internal activity logging mechanism. This directory is only applicable to the Classic Architecture, see What is the Oracle GoldenGate Classic Architecture. |
|
Contains the Java executable files that support Oracle GoldenGate Monitor. |
|
Default location for status files. File name format is These files are only created while a process is running. The file shows the program name, the process name, the port number, and the process ID. Do not edit these files. Examples:
|
|
The default location for Oracle GoldenGate parameter files created by Oracle GoldenGate users to store run-time parameters for Oracle GoldenGate process groups or utilities. Written in external ASCII format. File name format is These files may be edited to change Oracle GoldenGate parameter values after stopping the process. They can be edited directly from a text editor or by using the Examples:
|
|
Not used by Oracle GoldenGate. |
|
The default location for process report files created by Extract, Replicat, and Manager processes to report statistical information relating to a processing run. Written in external ASCII format. File name format is Do not edit these files. Examples:
|
|
Contains training scripts and any user-created SQL scripts that support Oracle GoldenGate. |
|
The default location for storing transaction data when the size exceeds the memory size that is allocated for the cache manager. Do not edit these files. |
|
Contains Oracle GoldenGate wallet files. |
|
Contains sample files to help with the creation of user exits. |