2.2 Supported Target Types

This topic lists the target types supported in Classic and Microservices instances.

• Target Types Supported in Classic
  
• Target Types Supported in Microservices
  

2.2.1 Target Types Supported in Classic

The target types supported in Oracle GoldenGate Enterprise Manager Classic instances are as follows:

• Oracle GoldenGate
  Oracle GoldenGate target type represents an Oracle GoldenGate classic instance. It's the parent target of Manager, Extract, and Replicat targets.
• Extract and Replicat
  On the Extract target and Replicat target pages, you can view the respective Oracle GoldenGate process metrics, set alerts for these metrics, view logs, configuration files, events, and monitor historical trends.
• Manager
  The Manager process controls all the Oracle GoldenGate processes in the classic instance. Part of its role is to generate information about critical monitoring events, which it passes to the agent. For target types Replicat, Extract, and Manager, you can control the process though start, stop, kill, and resume actions.

2.2.1.1 Oracle GoldenGate

Oracle GoldenGate target type represents an Oracle GoldenGate classic instance. It's the parent target of Manager, Extract, and Replicat targets.

The Oracle GoldenGate target displays the collective status of all the processes available in Oracle GoldenGate excluding the Initial Load processes. The following is an example that illustrates how the collective status of this target works: there may be 5 Extract and Replicat processes and 2 Initial Load processes in Oracle GoldenGate, out of which, only 2 are discovered and promoted in the Oracle Enterprise Manager. This means that a subset of the Oracle GoldenGate processes is being monitored in the Enterprise Manager. However, the Oracle GoldenGate target displays the collective status of all the processes available in Oracle GoldenGate, and does not display only the status of the processes that are monitored in the Enterprise Manager.

• GoldenGate Monitor Agent
  The GoldenGate Monitor Agent represents the GoldenGate Monitor agent that is connecting to the Oracle GoldenGate Instance.

2.2.1.1.1 GoldenGate Monitor Agent

The GoldenGate Monitor Agent represents the GoldenGate Monitor agent that is connecting to the Oracle GoldenGate Instance.

Version and details of other metrics are displayed on the Oracle GoldenGate Target page.

This topic discusses the GoldenGate Monitor Agent process for Oracle GoldenGate Enterprise Manager Plug-in Classic instance.

Metric	Description
GoldenGate Monitor Agent Status	UP arrow indicates Golden Gate Agent is up and running. Down arrow indicates Golden Gate agent is down or unreachable. 1 represents UP and 2 represents Down for setting incidents and alerts.
WebService Availability	Indicates whether or not the Webservice of Oracle GoldenGate is up and running. 0 represents down status and 1 represents up status . This metric is available only from Oracle GoldenGate Monitor Agent release 12.2.1.2.210930 onwards.
Host Name	Shows the name of GoldenGate Monitor Agent host.
Agent Port	Shows the port on which the GoldenGate Monitor Agent process is running.
User Name	Shows the user name to connect to the Monitor agent.
Agent Version	Indicates the version of GoldenGate Monitor Agent. This metric is available only from GoldenGate Monitor Agent 12.2.1.2.210930 version onwards
Agent Start Time	Shows the time number of milliseconds from January 1, 1970, 00:00:00 GMT to Oracle GoldenGate Monitor Agent start time. This metric is available only from Oracle GoldenGate Monitor Agent 12.2.1.2.210930 version onwards.
Installation Path	Shows the directory that contains the Oracle GoldenGate Monitor Agent executable file. This is the home directory of the Oracle GoldenGate Monitor Agent installation. This metric is available only from GoldenGate Monitor Agent 12.2.1.2.210930 version onwards.
Config Path	Shows the Oracle GoldenGate Monitor Agent configuration properties location. This metric is available only from Oracle GoldenGate Monitor Agent 12.2.1.2.210930 version onwards.

2.2.1.2 Extract and Replicat

On the Extract target and Replicat target pages, you can view the respective Oracle GoldenGate process metrics, set alerts for these metrics, view logs, configuration files, events, and monitor historical trends.

For more information, see Extract and Replicat.

2.2.1.3 Manager

The Manager process controls all the Oracle GoldenGate processes in the classic instance. Part of its role is to generate information about critical monitoring events, which it passes to the agent. For target types Replicat, Extract, and Manager, you can control the process though start, stop, kill, and resume actions.

This topic discusses the Manager process for Oracle GoldenGate Enterprise Manager Plug-in Classic instance.

Metric	Description
Host Name	Shows the name of the host system. Valid values: The fully qualified DNS name of the host, or its IP address
Manager Port	Shows the port on which the Manager process of the Instance is running on its local system. The default port number is 7809, but a different port could be specified for this Manager and can be identified by viewing the Manager parameter file or by issuing the INFO MANAGER command in GGSCI (if Manager is running). Valid values: The port number for the Manager process, as specified in the Manager parameter file
Start Time	Shows the time that an Oracle GoldenGate component received its startup information after it has been created. Valid values: 64-bit Julian GMT time stamp in microseconds
Version	Indicates the version of Oracle GoldenGate that the selected Oracle GoldenGate Instance represents. Valid values: X.x.x (major, minor, and maintenance version levels), for example 11.1.1
Working Directory	Shows the directory that contains the Manager executable file for the selected Oracle GoldenGate Instance. This is the home directory of the Oracle GoldenGate installation. Valid values: The full path name of the directory

2.2.2 Target Types Supported in Microservices

The target types supported in Oracle GoldenGate Enterprise Manager Microservices instances are as follows:

• Administration Service
  You can use the Administration Service to manage Extract and Replicat processes and to monitor their metrics. It is the parent target for Extract and Replicat targets. The Administration Service displays the following Process Summary details: Process Health Overview, Alert Overview, and the metrics details of the Processes.
• Extract and Replicat
  On the Extract target and Replicat target pages, you can view the respective Oracle GoldenGate process metrics, set alerts for these metrics, view logs, configuration files, events, and monitor historical trends.
• Service Manager
  The Service Manager page lists all the Oracle GoldenGate Miscroservices Architecture deployments. It's the parent target for the Deployment target, which in turn contains Administration Service, Receiver Service, Distribution Service, and Performance Metrics Server targets. If you have multiple deployments, then you can also filter using the Deployment drop-down list.
• Deployment
  The Deployment displays the status of target deployment, the location of your deployment configuration files including parameter files, location of deployment artifacts, configuration artifacts, and Oracle GoldenGate events of the deployment. It's the parent target for Administration Service, Receiver Service, Distribution Service, and Performance Metrics Service.
• Distribution Service
  You can view Path summary and the Path metrices, such as Path Details that include target encryption algorithm, critical, processing lag, auto restart, and Statistics like DDLs, DMLs, and Table Statistics in the Distribution Service detailed page.
• Receiver Service
  You can view Path summary and the Path metrices, such as Path Details that include target encryption algorithm, critical, processing lag, auto restart, and Statistics like DDLs, DMLs, and Table Statistics in the Receiver Service detailed page.

2.2.2.1 Administration Service

You can use the Administration Service to manage Extract and Replicat processes and to monitor their metrics. It is the parent target for Extract and Replicat targets. The Administration Service displays the following Process Summary details: Process Health Overview, Alert Overview, and the metrics details of the Processes.

The following process-related details are displayed in a tabular format:

• Name: Name of the process.
• Status: Status of the process, indicates whether or not the process is up and running. Status is denoted by up and down arrow icons.
• Type: Type of the process/target. For example, Classic Extract or Classic Replicat.
• Lag: Displays the delay time between the data fetch by the process and write to trail.
• Total Discards: Displays the number of discard operations by the process.
• Total Ignores: Displays the number of ignored operations performed by the process.

Using the Search option, you can also look up for a process in this view.

For a selected process, the following target metrics are displayed:

• Total Operations
• Total Inserts
• Total Updates
• Total Deletes
• Total Truncates

2.2.2.2 Extract and Replicat

On the Extract target and Replicat target pages, you can view the respective Oracle GoldenGate process metrics, set alerts for these metrics, view logs, configuration files, events, and monitor historical trends.

The following table lists the metrics used to monitor the Extract and Replicat processes. Metrics are fetched every 60 seconds by default from the targets. However, you can change the fetch frequency.

Metric	Description
Checkpoint Position	Valid for Extract and Replicat Shows a composite representation of the checkpoints that were persisted to disk most recently by Extract or Replicat. The value is captured by the monitoring agent when the attribute is published, right after the checkpoint gets persisted. Extract creates read and write checkpoints, and Replicat creates only read checkpoints. Each individual checkpoint within the composite Checkpoint Position consists of the RBA (relative bye address) of a record in the transaction log or trail (depending on the process and whether it is a read or write checkpoint) and the sequence number of the log or trail file that contains the record. There can be a series of read checkpoints in multiple data source log files (such as Extract from Oracle Real Application Cluster), and/or multiple write checkpoints such as in Extract configurations with multiple trail files. Valid values: Different databases use different representations of the position of a record in the log. Therefore, instead of numeric values, Checkpoint Position is published as a string of text characters encoded in UTF8. For each individual checkpoint within Checkpoint Position, the following are shown the way that they are returned by the GGSCI SEND group-name STATUS command: The values of the RBA (relative byte address) The file sequence number The time stamp
Delta Deletes	Valid for Extract and Replicat Shows the number of DELETE operations that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: A positive integer
Delta Discards	Valid for Extract and Replicat Shows the DISCARD operations that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: Positive integer.
Delta Executed DDLs	Valid for Extract and Replicat Shows the count of executed Data Definition Language (DDL) operations that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: Positive integer
Delta Ignores	Valid for Extract Shows the number of data manipulation language (DML) operations that through an error were configured to be ignored since the last fetched value. Valid values: Positive integer
Delta Inserts	Valid for Extract and Replicat Shows the number of data manipulation language (DML) INSERT operations that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: A positive integer
Delta Operation Per Second	Valid for Extract and Replicat Shows the number of operations (per second) that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: A positive integer
Delta Operations	Valid for Extract and Replicat Shows the total number of Data Definition Language (DDL) and Data Manipulation Language (DML) INSERT, UPDATE, DELETE, AND TRUNCATE operations that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: A positive integer
Delta Row Fetch Attempts	Valid for Extract Shows the number of row fetch attempts that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: Positive integer
Delta Row Fetch Failures	Valid for Extract Shows the number of row fetch failures that were processed by the selected Oracle GoldenGate process since the last fetched value. Valid values: Positive integer
Delta Truncates	Valid for Extract and Replicat Shows the number of TRUNCATE operations that were processed by the selected Oracle GoldenGate process in its current run session since the last fetched value. Valid values: A positive integer
Delta Updates	Valid for Extract and Replicat Shows the number of UPDATE (including primary key updates) operations that were processed by the selected Oracle GoldenGate process in its current run session since the last fetched value. Valid values: A positive integer
End of File	Valid for Extract and Replicat Shows whether or not the selected process has reached the end of the input from its data source (transaction log or trail file). Valid values: TRUE (at end of file) or FALSE. Note: End of File metrics value 0 means FALSE. For the alert template, ensure to use the stored metric values 0 and 1, where 0 means FALSE and 1 means TRUE. Note: For the alert template, ensure to use the stored metric value in milliseconds (since Unix Epoch) to all the following metrics: last_checkpoint_ts, last_processed_ts, last_operation_ts, start_time, last_checkpoint_ts, last_processed_ts, last_operation_ts, start_time.
Lag (sec)	Valid for Extract and Replicat Shows the time difference between the Last Operation Timestamp and the Last Processed Timestamp. This attribute represents the true lag between theOracle GoldenGate process and its data source. This lag value should match the value that is returned from the GGSCI command SEND groupGETLAG . Valid values: The lag time, in seconds
Last Checkpoint Timestamp	Valid for Extract and Replicat Shows the time when the last checkpoint was written by the process. Valid values: Datetime value in the format of MM/DD/YYYY HH:MM:SS {AM | PM}, for example: 01/14/2011 09:36:32 AM.
Last Operation Timestamp	Valid for Extract and Replicat Shows the time when an operation (INSERT, UPDATE, DELETE) was committed in the data source, as recorded in the transaction log. Valid values: Datetime value in the format of MM/DD/YYYY HH:MM:SS {AM | PM}, for example:01/14/2011 09:36:32 AM
Last Processed Timestamp	Valid for Extract and Replicat Shows the time when a valid record was returned to the selected process. For Extract, this time value is assigned when the record is processed after the container transaction commits (not the time when the record is read from the transaction log). For a Data Pump or Replicat, this time value is returned immediately, because all transactions in the trail are known to be committed. Valid values: Date time value in the format of MM/DD/YYYY HH:MM:SS {AM | PM}, for example: 01/14/2011 09:36:32 AM
Name	Valid for Extract and Replicat Name of the selected object. Valid values: Name of the object as displayed in the Oracle GoldenGate Monitor interface.
Seconds Since Last OGG Checkpoint	Valid for Extract and Replicat Time (in seconds) since the last OGG checkpoint.
Start Time	Valid for Extract and Replicat Shows the time that an Oracle GoldenGate component received its startup information after it has been created. Valid values: 64-bit Julian GMT time stamp in microseconds
Status	Valid for Extract and Replicat Shows the run status of the selected process. Note: The alert for Metric status is set for numeric value. For more information on setting metric alert, see Setting Metric Alerts and Incidents for Extract and Replicat.
Total Deletes	Valid for Extract and Replicat Shows the total number of DELETE operations that were processed by the selected Oracle GoldenGate process in its current run session. Valid values: A positive integer
Total Discards	Valid for Extract and Replicat Shows the total number of operations that were discarded by the selected Oracle GoldenGate process in its current run session. The records are written to the discard file that is associated with the process. Valid values: Positive integer.
Total Executed DDLs	Valid for Extract and Replicat Shows the total number of Data Definition Language (DDL) operations that were processed by the selected Oracle GoldenGate process in its current run session. Valid values: Positive integer
Total Ignores	Valid for Extract Shows the total number of Data Manipulation Language (DML) operations that were ignored by the process in its current run session. Errors are included in the Total Ignores metric. Valid values: Positive integer
Total Inserts	Valid for Extract and Replicat Shows the total number of Data Manipulation Language (DML) INSERT operations that were processed by the selected Oracle GoldenGate process in its current run session. The statistic reflects the total operations performed on all of the tables that are specified in the parameter file for that process. Note: If any tables are mapped to targets in the Extract configuration, the statistics will reflect the total operations for all of the targets. Valid values: A positive integer
Total Operations	Valid for Extract and Replicat Shows the total number of Data Definition Language (DDL) and Data Manipulation Language (DML) INSERT, UPDATE, DELETE, and TRUNCATE operations that were processed by the selected Oracle GoldenGate process in this current run session. Valid values: A positive integer
Total Row Fetch Attempts	Valid for Extract Shows the total number of row fetches that the selected process performed in its current run session. A fetch must be done sometimes to obtain row values when the information is incomplete or absent in the transaction log. Valid values: Positive integer
Total Row Fetch Failures	Valid for Extract Shows the total number of row fetches that the selected process was unable to perform in its current run session. Valid values: Positive integer
Total Truncates	Valid for Extract and Replicat Shows the total number of TRUNCATE operations that were processed by the selected Oracle GoldenGate process in its current run session. The statistic reflects the total operations performed on all of the tables that are specified in the parameter file for that process. Note: if any tables are mapped to targets in the Extract configuration, the statistics will reflect the total operations for all of the targets. Valid values: A positive integer
Total Updates	Valid for Extract and Replicat Shows the total number of UPDATE (including primary key updates) operations that were processed by the selected Oracle GoldenGate process in its current run session. The statistic reflects the total operations performed on all of the tables that are specified in the parameter file for that process. Note: If any tables are mapped to targets in the Extract configuration, the statistics will reflect the total operations for all of the targets. Valid values: A positive integer

2.2.2.3 Service Manager

The Service Manager page lists all the Oracle GoldenGate Miscroservices Architecture deployments. It's the parent target for the Deployment target, which in turn contains Administration Service, Receiver Service, Distribution Service, and Performance Metrics Server targets. If you have multiple deployments, then you can also filter using the Deployment drop-down list.

The Service Manager page also displays the Goldengate Home for each deployment. This page also lists the following for each deployment:

Details	Description
Service Name	Name of the service, for example: distsrvr:8062
Service Type	Type of the service, such as Administration Service, Distribution Service, Performance Metrics Service or Receiver Service.
Port	Port number
Status	Status of the service type. Valid Values: 1: Indicates UP status 0: Indicates DOWN status

Note:

For OCI GoldenGate Service, the Service Manager target does not exist.

2.2.2.4 Deployment

The Deployment displays the status of target deployment, the location of your deployment configuration files including parameter files, location of deployment artifacts, configuration artifacts, and Oracle GoldenGate events of the deployment. It's the parent target for Administration Service, Receiver Service, Distribution Service, and Performance Metrics Service.

In case of OCI GoldenGate Service, Deployment target is the parent target node and therefore only the Status is shown in the OGG Home page. Deployment status is calculated based on it's child targets. If any child is UP, then the deployment status is also UP, else it is marked DOWN.

Details	Description
Status	Shows the run status of the Deployment. The alert for Metric status is set for numeric value. Valid Values: 1: Indicates UP status 0: Indicates DOWN status
GoldenGate Home	The Oracle GoldenGate home that is created on a host computer is the directory that you choose to install the product. This read-only directory contains binary, executable, and library files for the product. The default directory path is: /ogg_install_location.
GoldenGate Etc Home	The location in which your deployment configuration files are stored including parameter files. The default directory path is: /ogg_deployment_location/etc.
GoldenGate Conf Home	The location in which each deployment information and configuration artifacts are stored. The default directory path is: /ogg_deployment_location/etc/conf.
GoldenGate SSL Home	The location in which each deployment security artifacts (certificates, wallets) are stored. The default directory path is: /ogg_deployment_location/etc/ssl.
GoldenGate Var Home	The location in which each deployment logging and reporting processing artifacts are stored. The default directory path is: /ogg_deployment_location/var.
GoldenGate Data Home	The location in which each deployment data artifacts (trail files) are stored. The default directory path is: /ogg_deployment_location/var/lib/data.
Managed by Service Manager	Indicates whether the deployment is managed by the Service Manager. Valid values: true or false.

2.2.2.5 Distribution Service

You can view Path summary and the Path metrices, such as Path Details that include target encryption algorithm, critical, processing lag, auto restart, and Statistics like DDLs, DMLs, and Table Statistics in the Distribution Service detailed page.

The Distribution Path Summary sumarizes the following:

• Number of paths
• Number of paths that are in Running state.
• Number of paths that are in Failed state.
• Other

You can also search for path details based on the column values of the following columns: Name, Status, Processing Lag, Source, Target, DB Name, and Extract. The search is case insensitive.

Path Information

Path Details	Description
Path Name	Path Name of the Distribution Service.
Description	Description provided for the path name. For example, the name of the Extract and Replicat names.
Status	Status of the Distribution path. The alert for Metric status is set for numeric value. Valid numeric values of the following status are: Uninitialized = 0 Running = 1 Unknown = 2 Paused =3 Stopping = 4 Stopped = 5 Killed = 6
Processing Lag	Difference between the time when extract wrote a transaction in the trail and the time when Distribution Service processes this transaction.
Source	Complete path name of the Distribution Service.
Target	Complete path name of the Receiver service.
DB Name	Name of the database from which the Extract target is fetching the data from.
Extract	Name of the Extract target (to which the data is fetched into) the Distribution Service is connected to.

Source/Target DB Details	Description
Source	Host Name: URL of the source host for example, localhost, if the source is on the same system. Port: Port number of the Distribution Service. Protocol Name: Data transfer protocol name. For exmple, Trail. Trail Name: Path takes the source trail and sends the data to a target trail, which can be consumed by any Replicats created later. Generated Source URI: A URI is automatically generated for the trail based on the Extract information. Source Trail File: Name of the file where the source trail file is generated. Trail Sequence Length: The length of the trail sequence number. Trail Size (MB): The maximum size of a file in a trail.
Target	Host Name: URL of the target host for example, localhost, if the source is on the same system. Port: Port number of the Receiver Server and the trail name of the Replicat. Protocol Name: Data transfer protocol name. For exmple, Trail. Trail Name: Path takes the source trail and sends the data to a target trail, which can be consumed by any Replicats created later. Generated Target URI: A target URI is automatically generated for the trail based on the target authentication method and target information. Source Trail File: Name of the file where the source trail file is generated. Trail Sequence Length: The length of the trail sequence number. Trail Size (MB): The maximum size of a file in a trail.

• Target Encryption Algorithm: The encryption algorithm for the target trail. For example, NONE, AES128, AES192, AES256.
• Critical: The default value is false. If the value is true, this indicates that the Distribution path is critical to the deployment.
• Processing Lag (Sec): Difference between the time when extract wrote a transaction in the trail and the time when Distribution Service processes this transaction.
• Since Lag Reported (Sec): Time since the last lag reported.
• Auto restart: The default value is false. If the value is true, the Distribution path restarts automatically if it's terminated.

Statistics

The Statistics tab shows you detailed information about the Total bytes sent logical change records (LCRs) and DDLs that were read from trails, LCRs and DDLs sent and procedure. It also provides information about the DML types, inserts, updates, upserts, and deletes.

The table information includes the values of Table Name, Inserts, Deletes, Upserts, LCRs read, and sent. You can search for records based on the values of any column of the table. This search is case insensitive.

2.2.2.6 Receiver Service

You can view Path summary and the Path metrices, such as Path Details that include target encryption algorithm, critical, processing lag, auto restart, and Statistics like DDLs, DMLs, and Table Statistics in the Receiver Service detailed page.

The Receiver Path Summary sumarizes the following:

• Number of paths
• Number of paths that are in Running state.
• Number of paths that are in Failed state.
• Other

You can also search for path details based on the column values of the following columns: Name, Status, Processing Lag, Source, Target, DB Name, and Extract. The search is case insensitive.

Path Information

Path Details	Description
Receiver Service Path Name	Path Name of the Receiver Service
Status	Status of the Receiver path. The alert for Metric status is set for numeric value. Valid numeric values of the following status are: Uninitialized = 0 Running = 1 Unknown = 2 Paused =3 Stopping = 4 Stopped = 5 Killed = 6
Processing Lag	Difference between the time when Replicat read a transaction in the trail and the time when Receiver Service processes this transaction.
Source	Complete path name of the Distribution service.
Target	Complete path name of the Receiver Service.
DB Name	Name of the database from which the Extract target is fetching the data from.
Extract	Name of the Extract target (to which the data is fetched into) the Receiver Service is connected to.

Path Details for a Non-Target Initiated path:

Path Details	Description
Name	Path Name of the Receiver Service
Target Trail File	Name of the target trail of the Replicat you created earlier.
Transfer Protocol	Data transfer protocol. For example, ogg.
Host	Host name of the Receiver path.
Port	Port number of the Receiver path.
Database	Name of the database from which the Extract target is fetching the data from.
Extract	Name of the Extract target (to which the data is fetched into) the Receiver Service is connected to.

Path Details for a Target Initiated path

Path Details	Description
Name	Path Name of the Receiver Service
Description	Description provided for the path name. For example, the name of the Extract and Replicat names.
Status	Status of the Receiver Service path. For example, Stopping, Running, or Stopped.
Database Name	Name of the database from which the Extract target is fetching the data from.
Extract	Name of the Extract target (to which the data is fetched into) the Receiver Service is connected to.

Source/Target DB Details	Description
Source	Host Name: URL of the source host for example, localhost, if the source is on the same system. Port: Port number of the Receiver Service. Protocol Name: Data transfer protocol name. For exmple, Trail. Trail Name: Path takes the source trail and sends the data to a target trail, which can be consumed by any Replicats created later. Generated Source URI: A URI is automatically generated for the trail based on the Extract information. Source Trail File: Name of the file where the source trail file is generated. Trail Sequence Length: The length of the trail sequence number. Trail Size (MB): The maximum size of a file in a trail.
Target	Host Name: URL of the target host for example, localhost, if the source is on the same system. Port: Port number of the Receiver Service and the trail name of the Replicat. Protocol Name: Data transfer protocol name. For exmple, Trail. Trail Name: Path takes the source trail and sends the data to a target trail, which can be consumed by any Replicats created later. Generated Target URI: A target URI is automatically generated for the trail based on the target authentication method and target information. Source Trail File: Name of the file where the source trail file is generated. Trail Sequence Length: The length of the trail sequence number. Trail Size (MB): The maximum size of a file in a trail.

• Target Encryption Algorithm: The encryption algorithm for the target trail. For example, NONE, AES128, AES192, AES256.
• Critical: The default value is false. If the value is true, this indicates that the Receiver path is critical to the deployment.
• Processing Lag (Sec): Difference between the time when Replicat read a transaction in the trail and the time when Receiver Service processes this transaction.
• Lag: Shows the time difference between the Last Operation Timestamp and the Last Processed Timestamp. This attribute represents the true lag between the Oracle GoldenGate process and its data source.

  This lag value should match the value that is returned from the GGSCI command SEND groupGETLAG.

• Since Lag Reported (Sec): Time since the last lag reported.
• Auto restart: The default value is false. If the value is true, the Receiver path restarts automatically if it's terminated.

Statistics

The Statistics tab shows you detailed information about the logical change records (LCRs) and DDLs that were read from trails, LCRs and DDLs sent and received, LCRs and DDLs filtered. It also provides information about the DML types, inserts, updates, upserts, and deletes.

The table information includes the values of LCRs read and sent. The search is case insensitive.

For a Target Initiated path, the Statistics tab displays the following:

• Network: The Network information includes details, such as target trail file name, port number, total messages written out, and so on. You can use this information to go back to the Distribution Server and tune the network parameters, if required.
• File IO: The File IO includes total bytes read, total bytes written to file, and total idle time (in seconds).
• DDL: The details displayed in the DDL table are LCR Read from Trails, LCR Sent, DDL Read from Trails, DDL Sent, and Procedure.
• DML: DML details that are displayed are Type, Inserts, Updates, Upserts, and Deletes.
• Table: This table consists of details like Table Name, Inserts, Deletes, Updates, Upserts, LCR Read, and LCR Sent.

For a Non-Target Initiated Path, the Statistics tab displays only the Network and File IO details.

Note:

Target-initiated paths for Microservices enable the Receiver Service to initiate a path to the Distribution Service on the target deployment and pull trail files. For more information, see About Target-Initiated Paths in the Step by Step Data Replication Using Oracle GoldenGate Microservices Architecture guide.