Oracle
GoldenGate subdirectories
Directories
Name
|
Purpose
|
br
|
Contains
the checkpoint files for the bounded recover
feature.
|
cfg
|
Contains
the property and xml files that are used to configure
Oracle
GoldenGate
Monitor.
|
dirdb
|
Contains
the datastore 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.
|
dirchk
|
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 where is
a sequential number appended to aged files and is either cpe for Extract checkpoint
files or cpr for Replicat
checkpoint files.
Do
not edit these files.
Examples:
ext1.cpe
rep1.cpr
|
dirdat
|
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 sixdigit sequence number (trail files) or the user-defined
name of the associated
Extract
process group (extract files).
Do
not edit these 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. If you
are
unsure
of how to edit a definitions file, contact Oracle GoldenGate technical
support.
Example:
defs.dat
|
dirjar
|
Contains
the Java executable files that support Oracle GoldenGate Monitor.
|
dirout
|
This
directory is not used any more.
|
dirpcs
|
Default
location for status files. File name format 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 number, and the process
ID.
Do
not edit these files.
Examples:
mgr.pcm
ext.pce
|
dirprm
|
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<=""
p="">
name/user-defined
name>.prm or mgr.prm.
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
EDIT PARAMS command in GGSCI.
Examples:
defgen.prm
finance.prm
|
dirrec
|
Not
used by Oracle 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.
Do
not edit these files.
Examples:
fin2.rpt
mgr4.rpt
|
dirsql
|
Used
by the TRIGGEN utility to store SQL scripts before TRIGGEN
was
deprecated.
Currently used to store training scripts and any user-created
SQL
scripts
that support Oracle GoldenGate.
|
dirtmp
|
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.
|
dirwlt
|
Contains
the Oracle Wallet that supports Oracle GoldenGate
Monitor. This
directory
is not installed until the utility that creates the wallet is
run.
|
UserExitExamples
|
Contains
sample files to help with the creation of user
exits.
|
