GoldenGate Subdirectories List Usage

In our GoldenGate installation Guide, we mentioned that you have to execute CREATE SUBDIRS command as a part of the installation, which would create the required working directories for the GoldenGate program to work properly. In this post,we will provide a short explanation of what each of these sub directories mean and their importance in the functionality of the program as a whole. [ An excerpt from Oracle Documentation ]

dirchk
This sub-directory 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 GoldenGate format.

The File name format is . where is a sequential number appended to aged files and is either cpe for Extract checkpoint files or cpr for Replicat checkpoint files.

Examples:
ext1.cpe
rep1.cpr

dirdat
This is the default location for GoldenGate trail files and extract files created by Extract processes to store records of extracted data for further processing, either by the Replicat process or another application or utility. Written in internal GoldenGate format.

File name format is a user-defined two-character prefix followed by either a six-digit sequence number (trail files) or the user-defined name of the associated Extract process group (extract files).

Examples:
rt000001
finance

dirdef
The default location for data definitions files created by the DEFGEN utility to contain source or target data definitions used in a heterogeneous synchronization environment. Written in external ASCII. File name format is a user-defined name specified in the DEFGEN parameter file.These files may be edited to add definitions for newly created tables.

Example:
defs.dat

dirpcs
Default location for status files. File name is . where is the name of the group and is either pce (Extract), pcr (Replicat), or pcm (Manager). These files are only created while a process is running. The file shows the program name, the process name, the port and process id that is running.

Examples:
mgr.pcm
ext.pce

dirprm

The default location for GoldenGate parameter files created by GoldenGate users to store run-time parameters for GoldenGate process groups or utilities. Written in external ASCII format. File name format is .prm or mgr.prm.These files may be edited to change GoldenGate parameter values. They can be edited directly from a text editor or by using the EDIT PARAMS command in GGSCI.

Examples:
defgen.prm
finance.prm


dirrec
Currently not used by GoldenGate.

dirrpt
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 .rpt where is a sequential number appended to aged files.
Examples:
FIN2.rpt
MGR4.rpt

dirsql
The default location for scripts created by the TRIGGEN utility to contain SQL syntax for creating GoldenGate logging triggers and GoldenGate log tables. Written in external format.File name format is a user-defined name or the defaults of GGSLOG (table-creation script) or the table name (trigger-creation script), with the extension of .sql.

Examples:
ggslog.sql
account.sql

dirtmp
The default location for storing large transactions when the size exceeds the allocated memory size.