【ogg 】Error Messages（OGG-10548to OGG-25191）

OGG-10548: Schema.table is required for heartbeattable.
Cause: The heartbeat table is required in GLOBALS with schema and table name.

Action: Edit the GLOBALS file and specify a fully qualified heartbeat table name (with schema) for the heartbeat table parameter.

OGG-10549: Four or more part table name is not supported.
Cause: Attempting to assign a table name that is four part or more, which is not supported.

Action: Report the error, and then restart the process.

OGG-10550: Failed to prepare fetch on table {0} due to key column {1} being dropped. Use KEYCOLS.
Cause: Unique row data could not be guaranteed to be fetched from the table because one or more key column has been dropped.

Action: Define a key or specify unique columns with the KEYCOLS clause of the TABLE statement.

OGG-10551: OCI error ({0,number,0}-{1}) when validating table {2}, SQL: {3}.
Cause: Validation of the table existence failed.

Action: Contact Oracle Support

OGG-10552: Unsupport option is FETCH; No row found. tablename:{0}
Cause: An attempt to fetch the unsupported LCR though the row was not found.

Action: Set UNSUPPORTED_OPTION to IGNORE if the unsupported LCR is irrelevant.

OGG-10553: Unsupport option is FETCH; Cannot fetch by rowid. tablename:{0}
Cause: Try to fetch the unsupported LCR. Either the fetch option disallow fetching by rowid or no valid rowid is received.

Action: Using rowid to fetch or set UNSUPPORTED_OPTION to IGNORE if the unsupported LCR is irrelevant.

OGG-10554: Stop of {0} {1} failed ({2})
Cause: The specified process cannot be stopped.

Action: Look for additional error messages that indicate why the process cannot be stopped, and then correct the problem.

OGG-10555: The current catalog login of "{0}" is not the same as the configured heartbeat catalog of "{1}".
Cause: When using two part names the dblogin (ODBCDSN) will determine the default catalog, the heartbeat table was already set up using another catalog.

Action: Log into the configured catalog.

OGG-10556: No data found when executing SQL statement <{0}>.
Cause: The database returned no data when the specified SQL statement was executed.

Action: Contact Oracle Support.

OGG-10557: No data found when executing SQL statement <{0}>.
Cause: The database returned no data when the specified SQL statement was executed.

Action: None

OGG-10558: Kill of {0} {1} failed ({2})
Cause: The specified process cannot be killed.

Action: Look for additional error messages that indicate why the process cannot be killed, and then correct the problem.

OGG-10559: File '{0}' deleted
Cause: The specified file was deleted.

Action: None

OGG-12000: General server error.
Cause: There was some internal problem that prevented proper processing of the request.

Action: Contact Oracle GoldenGate Support.

OGG-12001: Poorly formed service request payload.
Cause: The service request contained a payload what was incorrectly formatted or contained invalid values.

Action: Verify the service request payload specified by the client is correct.

OGG-12002: Poorly formed request URI.
Cause: The service request contained a URI what was incorrectly formatted or contained invalid values.

Action: Verify the service request URI specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12003: Poorly formed HTTP request context.
Cause: The service request contained a header or attribute what was incorrectly formatted or contained invalid values.

Action: Verify the service request headers and attributes specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12004: Service request handler error.
Cause: The service request handler returned an error.

Action: Review the message details and verify the service request was properly and completely formed. See the Oracle GoldenGate reference for valid values.

OGG-12005: No configuration file found at '{0}'. New configuration file created with default settgings.
Cause: Named configuration file was not found. A new configuration file with default settings was created.

Action: Verify the configuration specifications in the newly created configuration file is correct for the current environment. See the Oracle GoldenGate reference for valid values.

OGG-12006: Loaded configuration file from '{0}'.
Cause: Report the location from which the configuration was loaded.

Action: None. Informational only.

OGG-12007: Unable to access the configuration file at '{0}'.
Cause: Unable to access the configuration at the specified location.

Action: Verify that the location is accessible and that the file permissions allows read access. See the Oracle GoldenGate reference for valid values.

OGG-12008: Unable to parse the configuration at line {1,number,0} column {2,number,0} in file '{0}'.
Cause: Unable to parse the configuration information in the file at the specified location.

Action: Verify that the configuration information formats are valid. See the Oracle GoldenGate reference for valid values.

OGG-12009: Unable to completely read the configuration file at '{0}'.
Cause: Unable to access the configuration at the specified location.

Action: Verify that the location is accessible and that the file permissions allows read access. See the Oracle GoldenGate reference for valid values.

OGG-12010: The requested service completed successfully but did not return a result.
Cause: Service request was not required to produce results to be returned to the client.

Action: None

OGG-12011: The HTTP Verb '{0}' is invalid for '{0} {1}'.
Cause: The verb provided in the HTTP URI is invalid for this service request.

Action: Verify the HTTP URI specifies a valid verb. See the See the Oracle GoldenGate reference for valid values.

OGG-12012: Poorly formed HTTP request context for '{0} {1}'.
Cause: The HTTP request context contained a header or attribute what was incorrectly formatted or contained invalid values.

Action: Verify the HTTP context specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12013: Poorly formed request URI for '{0} {1}'.
Cause: The request URI (Uniform Resource Identifier) incorrectly formatted or references an invalid resource path.

Action: Verify the URI specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12014: The HTTP Accept media-type '{0}' is deprecated for '{1} {2}'.
Cause: The media-type value provided in the HTTP Accept header is deprecated.

Action: Update the request to specify an actively support media type. This media type may be treated as an error in future releases. See the Oracle GoldenGate reference for valid values..

OGG-12015: The HTTP Accept value '{0}' is invalid for '{1} {2}.
Cause: The media-type value provided in the HTTP Accept header is invalid for this service requests. The HTTP Accept header in the service request specifies what response format the client is able to accept.

Action: Verify the HTTP Accept value specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12016: The request URI template '{3}' placeholder name '{0}' conflicts with the request context names for '{1} {2}'.
Cause: The URI template defines names for dynamic placeholders that conflict with names in the request context.

Action: Resolve Internal.

OGG-12017: Poorly formed HTTP response context for '{0} {1}'.
Cause: The HTTP response context contained a header or attribute what was incorrectly formatted or contained invalid values.

Action: Verify the HTTP context specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12018: Poorly formed request payload for '{0} {1}'.
Cause: The service request payload was incorrectly formatted or was expressed in an invalid or unsupported format.

Action: Verify the URI specified by the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12019: The request payload for '{0} {1}' defines a root level array. Root level arrays are not currently supported
Cause: The root of the payload document is defined as an array, which is not currently supported.

Action: Change the payload root document from an array to named values or objects. See the Oracle GoldenGate reference for valid values.

OGG-12020: The request payload for '{0} {1}' is not defined as an object.
Cause: The root of the JSON payload document is not defined as an object.

Action: Define the JSON payload root document as an object. See the Oracle GoldenGate reference for valid values.

OGG-12021: Poorly formed response from service handler for '{0} {1}'.
Cause: The response returned by the service handler registered for this request was poorly formed.

Action: Contact Oracle GoldenGate Support.

OGG-12022: The response payload for '{0} {1}' is empty.
Cause: The service request handler returned an empty response.

Action: Contact Oracle GoldenGate Support.

OGG-12023: Service request handler error.
Cause: The service request handler returned an error. There was some problem processing the request.

Action: Verify that the service request from the client is correct. See the Oracle GoldenGate reference for valid values.

OGG-12024: No service handler registered for '{0} {1}'.
Cause: No service handler is registered for the service request URI.

Action: Contact Oracle GoldenGate Support.

OGG-12025: The handler method registered for '{0} {1}' caused an exception: {2} - {3}.
Cause: The handler method caused an exception. See error messages for details.

Action: Contact Oracle GoldenGate Support.

OGG-12026: Node '{0}' at postion {1,number,0} in JsonPath '{2}' is missing.
Cause: Unable to locate the specified node in the JSON document instance specified by the JsonPath.

Action: Verify that the both the JSON document and the JsonPath specification is correct. See the Oracle GoldenGate reference for valid values.

OGG-12027: There is no JsonPath specified. The JsonPath is empty.
Cause: The JsonPath has not been initialize or the specification is empty.

Action: Verify the JsonPath specification describes a valid path. See the Oracle GoldenGate reference for valid values.

OGG-12028: No service handler implemented for '{0} {1}'.
Cause: No service handler is implemented for the service request URI.

Action: Contact Oracle GoldenGate Support.

OGG-12029: The {0} with name '{1}' does not exist.
Cause: The requested item does not exist.

Action: Check the request URI for accuracy.

OGG-12030: The {0} with name '{1}' already exists.
Cause: The requested item already exists.

Action: Check the request URI for accuracy.

OGG-12050: The wrl configuration is missing .
Cause: The Wallet Resource Locator (wrl) was not found in the security configuration.

Action: Verify that the wrl value in the security configuration is present and refers to a valid Oracle Wallet location.

OGG-12051: The configured communications role '{0}' is not recognized.
Cause: The value configured for the communications role does not describe a recognized role.

Action: Verify that the role value in the security configuration refers to a valid communications role.

OGG-12052: The communications role configuration is missing.
Cause: The communications role was not found in the security configuration.

Action: Verify that the role value in the security configuration is present and refers to a valid communications role.

OGG-12053: The communications protocol configuration is missing.
Cause: The communications security protocol was not found in the security configuration.

Action: Verify that the protocol value in the security configuration is present and refers to a valid communications protocol.

OGG-12054: The communications protocol configuration '{0}' is not recognized.
Cause: The communications security protocol was not recognized.

Action: Verify that the protocol value in the security configuration refers to a valid communications security protocol.

OGG-12055: Expected communications security configuration id '{1}' but received '{0}'.
Cause: The communications security configuration id did not match the expected value.

Action: Verify that the 'configId' value in the security configuration matches the expected value.

OGG-12056: Communications security configuration id is missing.
Cause: The communications security configuration id was not found in the security configuration.

Action: Verify that the 'configId' value in the security configuration is present and matches the expected value.

OGG-12057: Method for specified URI must be GET.
Cause: Methods other than GET are only valid for handlers under URI services.

Action: Verify that both URI and METHOD are correct.

OGG-12058: Internal error, context key not present.
Cause: Internal error.

Action: Contact Oracle Support.

OGG-12059: Internal error, a pointer could not be retrieved.
Cause: Internal error.

Action: Contact Oracle Support.

OGG-12060: The client submitted an empty HTTP Authorization header.
Cause: The client submitted an empty HTTP Authorization header value as part of the service request.

Action: Correct the client request to include a valid Authorization header value.

OGG-12061: HTTP Authorization header is invalid or not properly formed - '{0}'.
Cause: The client submitted an invalid, incomplete or poorly formed HTTP Authorization header value as part of the service request.

Action: Correct the client request to include a valid and properly formed Authorization header value.

OGG-12062: The service request for '{0} {1}' specifies an authenticated user that is not authorized for this request.
Cause: The service request specified a user who is authenticated to the server but is not authorized to use the service interface or resource.

Action: Verify that the user is authorized to use the service interface or resource.

OGG-12063: The service request for '{0} {1}' does not included authorization information.
Cause: The service request does not include authorization information.

Action: Provide the authorization information in the HTTP Authorization header and retry the request.

OGG-12064: The authorization information for '{0} {1}' is missing, invalid or not properly formed.
Cause: The client submitted an invalid, incomplete or poorly formed HTTP Authorization header value as part of the service request.

Action: Correct the client request to include a valid and properly formed Authorization header value.

OGG-12065: Successfully {0} {1} users.
Cause: The import, update, export or delete processing of user specifications will successful.

Action: None

OGG-12066: Failed to {0} {1} users.
Cause: The import, update, export or delete processing of user specifications failed.

Action: None

OGG-12067: Successfully {0} {1} users.
Cause: The import, update, export or delete processing of user specifications was successful.

Action: None

OGG-12068: Failed to {0} {1} users.
Cause: The import, update, export or delete processing of user specifications failed.

Action: None

OGG-12069: User import file '{0}' does not exist or cannot be read, error {1} - {2}.
Cause: The file specified to import, update, export or delete users and roles could not be opened or read.

Action: Ensure the specified file exists and is readable.

OGG-12070: '{0}' cannot be located in the user database for the specified role. '{1}'.
Cause: The specified user does not exist in the database for the given role.

Action: Ensure the specified user exists.

OGG-12071: '{0}' does not exist for the specified role. '{1}'.
Cause: The specified user does not exist as a service resource for the given role.

Action: Ensure the specified user resource exists.

OGG-12072: The expected authorization object was not present in the request for '{0}'.
Cause: An authorization object was expected but not present for this request.

Action: Check that a security session is in effect for this request.

OGG-12073: User role requirement not met. An authorization role of '{0}' is required for '{1}'.
Cause: The authorization role of the user did no meet the resource's role requirementwas.

Action: Check that the user role is valid for the requested resource.

OGG-12074: The inbound Communication Security interface can not be initialized because in the configuration file, the '/config/securityDetails/network/inbound' property is not present.
Cause: In the configuration file of the service, the /config/securityDetails/network/inbound property is not present or does not fit the expected value.

Action: Verify that /config/securityDetails/network/inbound property is in the configuration file and matches the expected value.

OGG-12075: The outbound Communication Security interface can not be initialized because the '/config/securityDetails/network/outbound' property is not in the configuration file.
Cause: In the configuration file of the service, the /config/securityDetails/network/outboundproperty is not set or does not match the expected value.

Action: Verify that /config/securityDetails/network/outbound property is in the configuration file and matches the expected value.

OGG-12076: The Communication Security interface was not initialized properly for the {0} interface.
Cause: There was an error while configuring CommSec.

Action: Verify that /config/securityDetails/network/inbound or /config/securityDetails/network/outbound are set in the configuration file and match the expected value.

OGG-12077: User '{0}' already exists for the specfied role '{1}'.
Cause: Cannot complete the request because the specified user already exists for the specified role.

Action: Ensure the user does not already exist for the specified role when creating a user role entry.

OGG-12078: Unable to complete the request. User authorization required with authorization services disabled.
Cause: Cannot complete the request because user authorization is required on a server configured with authorization disabled.

Action: Use a request that does not requred authorization or configure the server to enable authorization services.

OGG-12100: Required JSON element '{0}' is missing
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12101: JSON element '{0}' is the incorrect type
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12102: JSON object '{0}' has additional items which are not allowed
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12103: JSON element '{0}' does not match the expected '{1}' format
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12104: JSON element '{0}' is missing the required '{1}' property
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12105: JSON element '{0}' must contain the enum value '{1}'
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12106: JSON element '{0}' must be one of the enum values
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12107: JSON element '{0}' dependencies are not met
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12108: JSON element '{0}' has an invalid additional property, '{1}'
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12109: JSON element '{0}' matches disallowed schema
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12110: JSON element '{0}' value does not match the required pattern
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12111: JSON element '{0}' does not match any schemas
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12112: JSON element '{0}' matches more than one schema
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12113: JSON element '{0}' value is not an even multiple of {1}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12114: JSON object '{0}' exceeds the maximum number of allowed properties of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12115: JSON object '{0}' has less than the minimum number of required properties of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12116: JSON array '{0}' exceeds the maximum number of allowed items of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12117: JSON object '{0}' has less than the minimum number of required properties of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12118: JSON string '{0}' exceeds the maximum allowable length of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12119: JSON string '{0}' does not meet the minimum required length of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12120: JSON element '{0}' is greater than the maximum allowed value of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12121: JSON element '{0}' is less than the minimum allowed value of {1,number,0}
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12122: JSON object requires exactly one of element '{0}' or '{1}'
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it conforms to the JSON schema.

OGG-12123: A PATCH operation that changes the property '{0}' is not allowed
Cause: The JSON property specified cannot be changed with a PATCH operation.

Action: Remove the identified property from the PATCH request.

OGG-12124: The value of property '{0}' is not valid
Cause: The value for the specified JSON property cannot be used.

Action: Correct the value of the identified property.

OGG-12125: A POST operation that uses the property '{0}' is not allowed
Cause: The JSON property specified cannot be used with a POST operation.

Action: Remove the identified property from the POST request.

OGG-12126: URI scheme '{0}' is incorrect. It does not match the server's security configuration.
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it matches with the server security setup.

OGG-12127: Given URI '{0}' is not valid.
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that it contains correct URI.

OGG-12128: The scheme of the given URI '{0}' is not recognizable or missing.
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that the scheme part of the URI is correct.

OGG-12129: The address of the given URI '{0}' is not recognizable or missing.
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that the host address part of the URI is correct.

OGG-12130: The port of the given URI '{0}' is not recognizable or missing.
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that the host port part of the URI is correct.

OGG-12131: The name of the trail file in the given URI '{0}' is incorrect.
Cause: The JSON item does not validate against the provided JSON schema.

Action: Correct the JSON so that the trail file name follows the requirement.

OGG-12132: An operation that sets path status to 'killed' is not allowed
Cause: You cannot change the status to killed.

Action: Specify another status.

OGG-12133: An operation that sets path status to 'stopping' is not allowed
Cause: You cannot change the status to stopping.

Action: Specify another status.

OGG-12134: An operation that sets path status to 'uninitialized' is not allowed
Cause: You cannot change the status to uninitialized.

Action: Specify another status.

OGG-12135: Property '{0}' is not valid with given URI schema '{1}'. The URI schema must be '{2}' to be able to use this property.
Cause: The JSON property is incompatible with the provided URI schema.

Action: Correct the JSON to use the correct URI schema or remove this property from your request.

OGG-12136: The endpoint path name '{0}' is different from specified name '{1}'.
Cause: The endpoint path name is different from specified name.

Action: The endpoint path name and specified name must be the same.

OGG-12137: Authorization information (username/password, or domain/alias) is required with given URI schema '{0}'.
Cause: The authorization information is not provided when non-secure WebSocket protocol is used.

Action: Correct the JSON to provide with authorization information (either username/password or domain/alias) in your request.

OGG-12138: Credential Domain '{0}' does not match any pre-imported entry.
Cause: The Credential Domain is incorrect.

Action: Correct the JSON to provide with the correct domain name in your request.

OGG-12139: Credential Alias '{0}' could not be found in Credential Domain '{1}'.
Cause: The specified Credential Alias does not exist in the specified Credential Domain.

Action: Correct the JSON to provide with the correct credential alias in your request.

OGG-12150: No log files found for application '{0}'.
Cause: There were no log files found for the specified application in the standard logging directory.

Action: No action required.

OGG-12151: Log '{0}' for application '{1}' is read-only.
Cause: The specified log is read-only and cannot be disabled or deleted.

Action: No action required.

OGG-12300: Service Manager is terminating.
Cause: The Oracle GoldenGate Service Manager cannot continue due to unrecoverable errors.

Action: Examine the errors and contact Oracle Support if necessary.

OGG-12301: The inventory locator, '{0}', does not exist or is unreadable.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12302: The inventory locator, '{0}', is missing the '{1}' property.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12303: The inventory locator, '{0}', describes an inventory at '{1}' that does not exist.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12304: The deployment registry in the inventory, '{0}', does not exist or is unreadable.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12305: The deployment registry in the inventory, '{0}', is not writable.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12306: The deployment registry in the inventory, '{0}', is invalid.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12307: The configuration data for deployment '{0}' does not exist or is unreadable.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12308: The configuration data for deployment '{0}' is not writable.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12309: The configuration data for deployment '{0}' is invalid.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12310: The inventory locator, '{0}', cannot be written to.
Cause: The Oracle GoldenGate Inventory locator is used to specify the location of the Oracle GoldenGate Inventory on the local system. The inventory locator and the inventory are created by the Oracle GoldenGate installation process. If these resources were not created, or have incorrect permissions for the Oracle GoldenGate account, then Oracle GoldenGate services cannot be managed.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12311: The '{1}' directory, '{2}', for deployment '{0}' cannot be created. Error {3,number,0}, {4}
Cause: The Oracle GoldenGate Service Manager could not create the specified directory.

Action: Ensure installation procedures were followed correctly and contact Oracle Support if necessary.

OGG-12312: The Service Manager deployment, '{0}', cannot be deleted.
Cause: An attempt was made to delete the Service Manager deployment.

Action: The Service Manager deployment is permanent and cannot be deleted.

OGG-12420: The maximum filesystem path length of {2,number,0} for {0, choice,0#environment variable|1# file path} '{1}' has been exceeded.
Cause: The file system path value set for the variable is longer than the maximum defined for file system paths.

Action: Use a short file system path value, up to the maximum number of characters supported by the operating system. Be sure to allow for the length of base filename added to the overall path.

OGG-13000: With procedural Replication, only single output trail is allowed.
Cause: Multiple output trails are not supported if procedural Replication is enabled.

Action: Make sure only one trail file is specified in the Extract parameter file.

OGG-13001: Invalid action specified for REPERROR PROCEDURE , Must be either IGNORE, ABEND, DISCARD
Cause: The specified action is invalid for Procedure REPERROR parameter

Action: Check the Oracle GoldenGate documentation for REPERROR syntax for procedure.

OGG-13002: Procedural Replication requires format release 12.3 or higher.
Cause: The format release must be 12.3 or later when procedural Replication is enabled.

Action: Ensure that the proper format release is specified in the Extract parameter file.

OGG-13003: PROCEDURETRANDATA operations are not supported for this DB version.
Cause: Oracle GoldenGate Procedural Replication is supported for an Oracle Database release 12.2 or later.

Action: Upgrade to a supported Oracle Database release.

OGG-13004: PROCEDURETRANDATA operation failed because of the following SQL error: {1}
Cause: The specified SQL error prevented PROCEDURETRANDATA operation from enabling supplemental logging for the specified schema.

Action: Fix the SQL error and then retry the PROCEDURETRANDATA operation.

OGG-13005: PROCEDURETRANDATA supplemental logging has been enabled
Cause: The ADD PROCEDURETRANDATA command enabled supplemental logging for procedures. Informational only.

Action: None

OGG-13006: PROCEDURETRANDATA supplemental logging has been disabled
Cause: The procedure-level supplemental logging is disabled by default or as the result of the DELETE PROCEDURETRANDATA command. Informational only.

Action: None

OGG-13007: Procedure level supplemental logging is enabled
Cause: Procedure-level supplemental logging is enabled as the result of the ADD PROCEDURETRANDATA command. Informational only.

Action: None

OGG-13008: Procedure level supplemental logging is disabled
Cause: Procedure-level supplemental logging is disabled as the result of the ADD PROCEDURETRANDATA command. Informational only.

Action: None

OGG-13009: Procedure Replication requires trail with OBJECTDEFS.
Cause: The NO_OBJECTDEFS option was specified when procedural Replication was enabled.

Action: Remove the NO_OBJECTDEFS option from the EXTTRAIL or RMTTRAIL parameter.

OGG-13010: Skipping procedural Replication records
Cause: Procedure Replication is only supported by Replicat in Integrated mode on Oracle Database release 12.2 and later.

Action: Use Replicat with Integrated mode on an Oracle Database release 12.2 and later.

OGG-13011: Invalid Procedure Feature configuration: if 'AQ' or 'ALL_SUPPORTED' features are included, the 'RULE' feature cannot be excluded
Cause: The AQ feature relies on procedures from the RULE feature.

Action: Either exclude the AQ feature or include the RULE feature.

OGG-13012: Extended trandata information and validation for individual tables is not supported by this Database version.
Cause: Extended trandata information and validation for individual tables is supported for an Oracle Database release 12.2 and later.

Action: Upgrade to a supported Oracle Database release.

OGG-14000: Successfully created heartbeat table "{0}".
Cause: Heartbeat table has been created. Information only.

Action: None

OGG-14001: Successfully created heartbeat seed table "{0}".
Cause: Heartbeat seed table has been created. Information only.

Action: None

OGG-14002: Implicit column function heartbeat routing has incorrect format.
Cause: Column function used to parse heartbeat routing is incorrect.

Action: Contact Oracle Support.

OGG-14003: Successfully populated heartbeat seed table with "{0}".
Cause: Heartbeat seed table populated. Information only.

Action: None

OGG-14004: Successfully created procedure "{0}" to update the heartbeat tables.
Cause: Update procedure for heartbeat tables created. Information only.

Action: None

OGG-14005: Successfully created scheduler job "{0}" to update the heartbeat tables.
Cause: Scheduler job for updating heartbeat tables created. Information only.

Action: None

OGG-14006: Heartbeat seed table "{0}" does not exist.
Cause: Heartbeat seed table does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat tables.

OGG-14007: Heartbeat seed table "{0}" dropped.
Cause: Heartbeat seed table dropped. Information only.

Action: None

OGG-14008: Heartbeat table "{0}" does not exist.
Cause: Heartbeat table does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat tables.

OGG-14009: Heartbeat table "{0}" dropped.
Cause: Heartbeat table dropped. Information only.

Action: None

OGG-14010: Heartbeat history table "{0}" does not exist.
Cause: Heartbeat history table does not exist.

Action: Use the command ADD HEARTBEATTABLEto add the heartbeat tables.

OGG-14011: Heartbeat history table "{0}" dropped.
Cause: Heartbeat history table dropped. Information only.

Action: None

OGG-14012: Procedure "{0}" does not exist.
Cause: Update procedure for heartbeat tables does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat tables update procedure.

OGG-14013: Procedure "{0}" dropped.
Cause: Update procedure for heartbeat tables dropped. Information only.

Action: None

OGG-14014: Scheduler job "{0}" does not exist.
Cause: Scheduler job for updating heartbeat tables does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the scheduler job.

OGG-14015: Scheduler job "{0}" dropped.
Cause: Scheduler job for updating heartbeat tables dropped. Information only.

Action: None

OGG-14016: Successfully created heartbeat history table "{0}".
Cause: Heartbeat history table has been created. Information only.

Action: None

OGG-14017: Successfully created procedure "{0}" to purge the heartbeat history table.
Cause: Purge procedure for heartbeat history table created. Information only.

Action: None

OGG-14018: Successfully created scheduler job "{0}" to purge the heartbeat history table.
Cause: Scheduler job for purging heartbeat history table created. Information only.

Action: None

OGG-14019: Procedure "{0}" does not exist.
Cause: Purge procedure for heartbeat history table does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat history purge procedure.

OGG-14020: Procedure "{0}" dropped.
Cause: Purge procedure for heartbeat history table dropped. Information only.

Action: None

OGG-14021: Scheduler job "{0}" does not exist.
Cause: Scheduler job for purging heartbeat history table does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the scheduler job.

OGG-14022: Scheduler job "{0}" dropped.
Cause: Scheduler job for purging heartbeat history table dropped. Information only.

Action: None

OGG-14023: Successfully created heartbeat lag view "{0}".
Cause: Heartbeat Lag View has been created. Information only.

Action: None

OGG-14024: Successfully created heartbeat lag history view "{0}".
Cause: Heartbeat Lag History View has been created. Information only.

Action: None

OGG-14025: Heartbeat lag view "{0}" does not exist.
Cause: Heartbeat Lag view does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat lag view.

OGG-14026: Heartbeat lag view "{0}" dropped.
Cause: Heartbeat lag view dropped. Information only.

Action: None

OGG-14027: Heartbeat lag history view "{0}" does not exist.
Cause: Heartbeat Lag history view does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat lag history view.

OGG-14028: Heartbeat lag history view "{0}" dropped.
Cause: Heartbeat lag history view dropped. Information only.

Action: None

OGG-14029: Frequency of scheduler job "{0}" modified.
Cause: Frequency of scheduler job for updating heartbeat tables has been modified. Information only.

Action: None

OGG-14030: Frequency of purge scheduler job "{0}" modified.
Cause: Frequency of scheduler job for purging heartbeat history table has been modified. Information only.

Action: None

OGG-14031: Retention time of heartbeats modified.
Cause: Retention time of heartbeat records in history table has been modified. Information only.

Action: None

OGG-14032: Successfully added supplemental logging for heartbeat seed table "{0}".
Cause: Added supplemental logging for heartbeat seed table for all columns. Information only.

Action: None

OGG-14033: Successfully added supplemental logging for heartbeat table "{0}".
Cause: Added supplemental logging for heartbeat table for all columns. Information only.

Action: None

OGG-14034: Heartbeat entries with [{0}] deleted.
Cause: Heartbeat entries with given process name deleted from heartbeat table. Information only.

Action: None

OGG-14035: The heartbeat table name cannot contain a wildcard.
Cause: The heartbeat table name specified with HEARTBEATTABLE in the GLOBALS file cannot contain a wildcard.

Action: Specify a non-wildcarded name.

OGG-14036: Schema is required for heartbeattable : "{0}".
Cause: Either GGSCHEMA should be mentioned in GLOBALS or a schema name must be specified for the heartbeat table in the HEARTBEATTABLE parameter in GLOBALS. Neither available.

Action: Edit the GLOBALS file and specify a fully qualified heartbeat table name (with schema) for the HEARBEATTABLE parameter, or mention GGSCHEMA in GLOBALS.

OGG-14037: Catalog login required to add heartbeat tables.
Cause: Catalog login required to add heartbeat tables.

Action: Login to a pdb and retry the command.

OGG-14038: Catalog login required to delete heartbeat tables.
Cause: Catalog login required to delete heartbeat tables.

Action: Login to a pdb and retry the command.

OGG-14039: Catalog login required to alter heartbeattable.
Cause: Catalog login required to alter heartbeat table.

Action: Login to a pdb and retry the command.

OGG-14040: Catalog login required to delete heartbeatentry.
Cause: Catalog login required for command 'delete heartbeatentry'.

Action: Login to a pdb and retry the command.

OGG-14041: "{0}" exists already.
Cause: Heartbeat object exists already.

Action: Rename object and retry the command again.

OGG-14042: Catalog name not supported for heartbeat table "{0}".
Cause: Catalog name not supported for heartbeat table

Action: Use a two part name or a table name along with GGSCHEMA.

OGG-14043: Invalid ADD HEARTBEATTABLE specification {0}.
Cause: Invalid ADD HEARTBEATTABLE specification.

Action: None

OGG-14044: Invalid ALTER HEARTBEATTABLE specification {0}.
Cause: Invalid ALTER HEARTBEATTABLE specification.

Action: None

OGG-14045: Invalid DELETE HEARTBEATENTRY specification {0}.
Cause: Invalid DELETE HEARTBEATENTRY specification.

Action: None

OGG-14046: The ADD HEARTBEATTABLE option: {0} is ignored.
Cause: The ADD option of the HEARTBEATTABLE parameter is not valid or supported.

Action: Do not specify the ADD option for the HEARTBEATTABLE parameter.

OGG-14047: Job {0} is currently running. Retry command.
Cause: An attempt was made to drop a job that is currently running.

Action: Reissue the command.

OGG-14048: Invalid DELETE HEARTBEATTABLE specification {0}.
Cause: Invalid DELETE HEARTBEATTABLE specification.

Action: None

OGG-14050: Invalid frequency for scheduler job {0}.
Cause: Invalid input for repeat interval.

Action: Specify a valid frequency between 0 and 7999.

OGG-14051: Invalid retention time for scheduler job {0}.
Cause: Invalid input for retention time.

Action: Allowed values for retention time are 1 to 999.

OGG-14052: No Heartbeat entries with [{0}], none deleted.
Cause: Heartbeat entries with given process name did not exist and were not deleted from heartbeat table. Information only.

Action: None

OGG-14053: Invalid heartbeat record encountered.
Cause: An invalid heartbeat record was encountered. The trail file may be corrupt. The invalid record will be skipped.

Action: Verify that the trail file is not corrupt.

OGG-14054: Lag from heartbeat table requires DBLOGIN.
Cause: Detailed lag report from heartbeat table requires DBLOGIN.

Action: Log into the database to view detailed lag report.

OGG-14055: Successfully created {0} "{1}".
Cause: Heartbeat object has been created. Informational only.

Action: None

OGG-14056: Successfully deleted {0} "{1}".
Cause: Heartbeat object has been deleted. Informational only.

Action: None

OGG-14057: Could not retrieve heartbeat table frequency interval.
Cause: There was an internal problem retrieving the heartbeat table frequency interval. For instance, the dblogin session login does not have enough privileges to access the relevant database table information, or an internal error occurred.

Action: Execute thedblogin command using a login with more privileges or contact Oracle Support.

OGG-14058: Could not retrieve heartbeat table purge frequency interval.
Cause: There was an internal problem retrieving the heartbeat table purge frequency interval. For instance, the dblogin session login does not have enough privileges to access the relevant database table information, or an internal error occurred.

Action: Execute the dblogin command using a login with more privileges or contact Oracle Support.

OGG-14059: Could not retrieve heartbeat table retention time interval.
Cause: There was an internal problem retrieving the heartbeat table retention time interval. For instance, the dblogin session login does not have enough privileges to access the relevant database table information, or an internal error occurred.

Action: Execute the dblogin command using a login with more privileges or contact Oracle Support.

OGG-14060: Invalid INFO HEARTBEATTABLE specification {0}.
Cause: Invalid INFO HEARTBEATTABLE specification.

Action: None

OGG-14061: data store uses LMDB environment files.
Cause: The data store uses LMDB files for its environment resources.

Action: No action required.

OGG-14062: Dblogin required before exttrail in parameter file to enable heartbeats.
Cause: Heartbeats are disabled if DBLOGIN is not present before the first EXTTRAIL in the parameter file.

Action: Reorder the DBLOGIN details to appear above the first EXTTRAIL in the Extract parameter file.

OGG-14063: DDL operations on Heartbeat objects are ignored.
Cause: DDLs on heartbeat objects such as seed, heartbeat and history table, lag view and historical lag view, update and purge procedure are ignored.

Action: None

OGG-14064: Could not delete heartbeat table entries for group name {0}: ({1}).
Cause: Undefined

Action: Undefined

OGG-14065: Heartbeat table "{0}" does not exist in "{1}".
Cause: Heartbeat table does not exist.

Action: Use the command ADD HEARTBEATTABLE to add the heartbeat tables.

OGG-14067: Heartbeat entries with [{0}] deleted from "{1}".
Cause: Heartbeat entries with the given process name were deleted from heartbeat table. Information only.

Action: None

OGG-14068: Schema is required for commandtable : "{0}".
Cause: Either GGSCHEMA should be mentioned in GLOBALS or a schema name must be specified for the command table using the COMMANDTABLE parameter in GLOBALS. Neither is available.

Action: Edit the GLOBALS file and specify a fully qualified command table name (with schema) for the COMMANDTABLE parameter, or mention GGSCHEMA in GLOBALS.

OGG-14069: Catalog login required to add command tables.
Cause: Catalog login required to add command tables.

Action: Login to a pdb and retry the command.

OGG-14070: Catalog login required to delete command tables.
Cause: Catalog login required to delete command tables.

Action: Login to a pdb and retry the command.

OGG-14071: Catalog login required to alter COMMANDTABLE.
Cause: Catalog login required to alter COMMANDTABLE.

Action: Login to a pdb and retry the command.

OGG-14072: Catalog login required to delete commandentry.
Cause: Catalog login required for command DELETE COMMANDENTRY.

Action: Login to a pdb and retry the command.

OGG-14073: "{0}" exists already.
Cause: The Command Table object exists already.

Action: Rename the Command Table object and retry the command again.

OGG-14074: Catalog name not supported for command table "{0}".
Cause: Catalog name is not supported for Command Table.

Action: Use a two part name or a table name along with GGSCHEMA.

OGG-14075: Invalid ADD COMMANDTABLE specification {0}.
Cause: Invalid ADD COMMANDTABLE specification.

Action: None

OGG-14076: Invalid ALTER COMMANDTABLE specification {0}.
Cause: Invalid ALTER COMMANDTABLE specification.

Action: None

OGG-14077: Invalid DELETE COMMANDTABLEENTRY specification {0}.
Cause: Invalid DELETE COMMANDTABLEENTRY specification.

Action: None

OGG-14078: The ADD COMMANDTABLE option: {0} is ignored.
Cause: The ADD option of the COMMANDTABLE parameter is not valid or supported.

Action: Do not specify the ADD option for the COMMANDTABLE parameter.

OGG-14079: The command table name cannot contain a wildcard.
Cause: The command table name specified with COMMANDTABLE in the GLOBALS file cannot contain a wildcard.

Action: Specify a non-wildcarded name.

OGG-14080: data store uses Metrics Server data store.
Cause: The data store uses Metrics Server data store.

Action: No action is required.

OGG-14081: This Operation is Invalid For Metrics Server data store.
Cause: The Operation is invalid for the Metrics Server data store.

Action: No action is required.

OGG-14082: Purge Complete, {0} Messages Removed, {1} Status Changes Removed.
Cause: The data store has been purged.

Action: No action is required.

OGG-14083: data store Purge Failed.
Cause: The data store purge failed.

Action: No action is required.

OGG-14084: Invalid or Missing Number of Days.
Cause: Invalid or missing value for max monitoring days.

Action: No action is required.

OGG-14085: Successfully enabled partitioning for heartbeat history table {0}.
Cause: Partitioning enabled on heartbeat table. Information only.

Action: No action is required.

OGG-14086: Successfully disabled partitioning for heartbeat history table {0}.
Cause: Partitioning disabled on heartbeat table. Information only.

Action: No action is required.

OGG-14087: Successfully disabled supplemental logging for heartbeat seed table "{0}".
Cause: Disabled supplemental logging for heartbeat seed table. Information only.

Action: None

OGG-14088: Successfully disabled supplemental logging for heartbeat table "{0}".
Cause: Disabled supplemental logging for heartbeat table. Information only.

Action: None

OGG-14500: ({0}) line {1}: Parsing error, parameter [{2}]: {3}
Cause: Parameter specification is invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-14501: Parameter file {0} has unicode byte order mark and CHARSET parameter
Cause: Parameter file is Unicode with byte order mark and CHARSET parameter is used.

Action: Remove CHARSET parameter or save using the encoding specified by CHARSET parameter.

OGG-14502: ({0}) line {1}: Unexpected value "{2}", first parameter must be one of: REPLICAT, SPECIALRUN, GENLOADFILES.
Cause: A fatal error was found while reading the parameter file.

Action: See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.

OGG-14503: ({0}) line {1}: Unexpected value "{2}", first parameter must be one of: EXTRACT, SOURCEISTABLE, SOURCEISFILE.
Cause: A fatal error was found while reading the parameter file.

Action: See the Oracle GoldenGate reference for valid values.

OGG-14504: Unable to locate the parameter definitions file.
Cause: Problem locating the static repository file for parameter definitions.

Action: Contact Oracle Support.

OGG-14505: ({0}) line {1}: Parameter [{2}] is not valid for this database version.
Cause: This parameter is not applicable to the running process database version.

Action: See the Oracle GoldenGate reference for valid values.

OGG-14550: The number of trail/file definitions exceeded maximum allocated {0, number, 0}.
Cause: The number of RMTFILE or RMTTRAIL definitions exceeded the maximum.

Action: Reduce the number of trail/file definitions to the permitted number. For more information, see the Oracle GoldenGate Reference for Oracle GoldenGate for Windows and UNIX.

OGG-14551: Error loading AES library.
Cause: Loading AES library failed.

Action: Contact Oracle Support.

OGG-14600: Specifying EXCLUDETAG + in conjunction with EXCLUDETAG NULL is not allowed.
Cause: EXCLUDETAG + and EXCLUDETAG NULL are mutually exclusive.

Action: Verify the EXCLUDETAG option. See the Oracle GoldenGate reference documentation.

OGG-14601: Specifying EXCLUDETAG NULL in conjunction with any other EXCLUDETAG option is not allowed.
Cause: Specifying EXCLUDETAG NULL in conjunction with any other EXCLUDETAG option is not allowed.

Action: Verify the EXCLUDETAG option. See the Oracle GoldenGate reference documentation.

OGG-14602: Specifying EXCLUDETAG + in conjunction with other EXCLUDETAG options.
Cause: EXCLUDETAG + was specified in conjunction with other EXCLUDETAG options.

Action: Verify the EXCLUDETAG option. See the Oracle GoldenGate reference documentation.

OGG-14603: The following generic error has occurred. {0}.
Cause: A generic error has occurred.

Action: Contact Oracle GoldenGate support with the following debug information: 1) Report files. 2) Parameter files. 3) Activity log files. 4) Snapshot of the top active processes on the server with maximum memory usage.

OGG-15000: TRANLOGOPTIONS BUFSIZE should be in the range [{0} - {1}].
Cause: BUFSIZE specified in the parameter file is not within the permissible range.

Action: Specify a number in the specified range for BUFSIZE.

OGG-15050: Error loading Java VM runtime library: ({0,number,0} {1})
Cause: The Java VM runtime library can not be found or loaded.

Action: Make sure Java VM runtime library (i.e.:libjvm.so/jvm.dll) is in the search path (LD_LIBRARY_PATH or PATH). In Linux, libjvm.so is located under $(JAVA_HOME)/lib/amd64/server/libjvm.so. In Windows, jvm.dll is can be found under %JAVA_HOME%\bin\server.

OGG-15051: Java or JNI exception: {0}
Cause: The Java or JNI subsystem returned an exception. Possible causes include an incorrect Java version, lack of memory or disk space to complete the operation, or other internal Java-related errors.

Action: Look for additional information related to this error in the JVM log or dump files, or on the console. The specific resolution is dependent on the type of failure.

OGG-15052: Using Java class path: {0}
Cause: The classpath tells Java where to look in the filesystem for files that contain the classes.

Action: None

OGG-15053: Java method {1}({2}) is not found in class {0}
Cause: The Oracle GoldenGate binary does not match the Java module.

Action: Reinstall the Oracle GoldenGate packages using the instructions in the Oracle GoldenGate installation guide for your database.

OGG-15101: Cannot support hierachy-enabled tables with with not-null ACL/Owner. object id: {0}
Cause: Cannot support HET tables with not-null ACL/Owner.

Action: Do not use HETs with not-null ACL/Owner with GoldenGate.

OGG-15102: Credential store created in {0}.
Cause: Credential store has been created. Informational only.

Action: None

OGG-15103: Unable to create a new credential store.
Cause: There was a problem when creating a new credential store.

Action: Verify that the directory exists and has the proper read/write permissions or contact Oracle Support.

OGG-15104: A credential store already exists.
Cause: A credential store has already been created. Informational only.

Action: None

OGG-15105: Credential store location was not found.
Cause: The specified credential store directory does not exist or it is not accessible.

Action: Verify that the directory exists and has the proper read/write permissions or contact Oracle Support.

OGG-15106: Credential store deleted.
Cause: Credential store has been deleted. Informational only.

Action: None

OGG-15107: Unable to delete credential store.
Cause: There was a problem when deleting the credential store.

Action: Verify that the directory exists and has the proper read/write permissions and the credential store exists or contact Oracle Support.

OGG-15108: Unable to open credential store .
Cause: There was a problem when opening the credential store.

Action: Verify that the directory exists and has the proper read/write permissions and the credential store exists or contact Oracle Support.

OGG-15109: Credential domain '{0}' not found in credential store.
Cause: The specified credential store domain could not be found in the credential store.

Action: Make sure that the specified credential store domain was spelled correctly, the credential store location is correct, or contact Oracle Support.

OGG-15110: Alias '{0}' not found in credential store.
Cause: The specified credential alias could not be found in the credential store.

Action: Make sure that the specified credential store domain and alias were spelled correctly, the credential store location is correct, or contact Oracle Support.

OGG-15111: Entry already exists in credential store.
Cause: There was a problem updating the credential store because the specified credential already exists.

Action: Make sure that the specified credential store domain and alias were spelled correctly, the credential store location is correct, specify a different credential alias, or contact Oracle Support.

OGG-15112: Unable to alter credential store.
Cause: There was a problem updating the credential store.

Action: Make sure that the specified credential store domain and alias were spelled correctly, the credential store location is correct, specify a different credential alias, or contact Oracle Support.

OGG-15113: Unable to save credential store.
Cause: There was a problem saving the credential store to disk.

Action: Verify that the directory exists and has the proper read/write permissions, or contact Oracle Support.

OGG-15114: Credential store altered.
Cause: Credential store has been altered. Informational only.

Action: None

OGG-15115: Reading from credential store.
Cause: The credential store is being read. Informational only.

Action: None

OGG-15116: No information found in credential store.
Cause: Credential store at the specified location is empty. Informational only.

Action: None

OGG-15117: Unable to retrieve information from credential store.
Cause: There was a problem retrieving information from the credential store.

Action: Contact Oracle Support.

OGG-15118: Missing table name specification.
Cause: The name of the table is missing while trying to execute a trandata command.

Action: Specify the name of the table.

OGG-15119: Bad table specification syntax {0}.
Cause: The table name was incorrectly specified and it was not possible to process it.

Action: Try again with a correct table name specification. If the correct table syntax cannot be determined, contact Oracle Support.

OGG-15120: Schema name is required for table specification {0}.
Cause: The table specification does not include a schema name and no default schema was found in GLOBALS file.

Action: Specify the schema name in the table specification.

OGG-15121: Error obtaining the list of tables for {0} : {1}.
Cause: There was a problem retrieving the list of tables for the specified table name.

Action: Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.

OGG-15122: No viable tables matched specification {0}.
Cause: The specified table name does not match any table in the database.

Action: Verify that the table name was specified correctly and that the table exists in the database.

OGG-15123: Invalid mode specified for PREPARECSN: '{0}'.
Cause: The specified PREPARESCNmode is not valid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15124: Table {0} does not exist.
Cause: The specified table does not exist in the database.

Action: Verify that the table specification is correctly spelled.

OGG-15125: The list of columns specified for the supplemental logging operation is empty.
Cause: There was an attempt to perform a TRANDATA operation specifying a list of columns, such as adding table supplemental logging, but the aforementioned list is empty.

Action: Add the proper values to the column list and retry the operation again.

OGG-15126: Column {0} not found in table {1}.
Cause: The column name specified for the supplemental logging operation does not exist.

Action: Verify that the column and table specification is correctly spelled.

OGG-15127: No supplemental logging data columns defined for table {0}.
Cause: There was an error adding supplemental logging to the specified table because no columns were found.

Action: Verify that the attributes for adding supplemental logging were correctly specified or try listing the table columns. If the problem cannot be resolved contact Oracle Support.

OGG-15128: Could not find definition for {0}. Error: {1}
Cause: The DDL metadata could not be obtained from the source database because of the error that is shown in the message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15129: Could not find definition of primary key for {0}. Error: {1}
Cause: The primary key DDL metadata could not be obtained from the source database because of the error that is shown in the message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15130: No key found for table {0}. All viable columns will be logged.
Cause: Informational only.

Action: None

OGG-15131: Logging of supplemental redo log data is already enabled for table {0}.
Cause: Informational only.

Action: None

OGG-15132: Logging of supplemental redo data enabled for table {0}.
Cause: Informational only.

Action: None

OGG-15133: TRANDATA for scheduling columns has been added on table {0}.
Cause: Informational only.

Action: None

OGG-15134: TRANDATA for all columns has been added on table {0}.
Cause: Informational only.

Action: None

OGG-15135: TRANDATA for instantiation CSN has been added on table {0}.
Cause: Informational only.

Action: None

OGG-15136: TRANDATA for instantiation CSN has been disabled on table {0}.
Cause: Informational only.

Action: None

OGG-15137: TRANDATA is already disabled for table {0}.
Cause: Informational only.

Action: None

OGG-15138: Failed to disable TRANDATA for table {0} due to {1}.
Cause: There was a problem deleting the supplemental logging for the specified table.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15139: TRANDATA for scheduling columns has been disabled on table {0}.
Cause: Informational only.

Action: None

OGG-15140: TRANDATA for all columns has been disabled on table {0}.
Cause: Informational only.

Action: None

OGG-15141: Logging of supplemental redo log data is already disabled for table {0}.
Cause: Informational only.

Action: None

OGG-15142: Logging of supplemental redo log data disabled for table {0}.
Cause: Informational only.

Action: None

OGG-15143: No command was specified.
Cause: Could not execute the send command because no input was specified.

Action: Ensure that you specify a correct and complete command. See the Oracle GoldenGate reference documentation for the correct syntax for the SEND command.

OGG-15144: Program type {0} is not supported to receive commands.
Cause: There was an attempt to send a command to an unsupported Oracle GoldenGate application.

Action: See the Oracle GoldenGate reference documentation for the supported programs that can receive and interpret remote commands.

OGG-15145: {0} {1} does not exist.
Cause: There was an attempt to send a command to an nonexistent Oracle GoldenGate process group.

Action: Verify that the group name and the process type were spelled correctly and try again.

OGG-15146: Manager not currently running.
Cause: The command could not be sent to the target manager because it is not currently running.

Action: Start the target manager.

OGG-15147: {0} not currently running.
Cause: The command could not be sent to the target program because it is not currently running.

Action: Start the target application process.

OGG-15148: {0} {1} not currently running.
Cause: The command could not be sent to the group application because it is not currently running.

Action: Start the group application process.

OGG-15149: {0} {1} is initializing, please try the command later.
Cause: The command could not be sent to the group application because it is in initialization state.

Action: Wait a few seconds and then try the command again.

OGG-15150: Unable to send command {0} to thread. Send to coordinator using THREADS option instead.
Cause: Sending parameter updates directly to a Replicat thread is not allowed.

Action: Specify the THREADS option in the command.

OGG-15151: The THREADRANGE option is invalid for this command: {0}. Use THREADS option instead.
Cause: There was an invalid option in the specified command.

Action: Verify the usage of THREADRANGE option by referring to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.

OGG-15152: Thread specification exceeds configured MAXTHREADS value: {0,number,0}.
Cause: The specified value for the THREADS option is not in range with the number of maximum threads allowed.

Action: Specify a valid value for THREADS option in the command. See the Oracle GoldenGate reference documentation or contact Oracle Support for assistance.

OGG-15153: Invalid multiple {0} specification.
Cause: The command contains multiple specifications for a single option.

Action: See the Oracle GoldenGate reference documentation for the correct syntax for the command.

OGG-15154: Expected argument or value after {0} not found.
Cause: There is a missing value for the specified option.

Action: See the Oracle GoldenGate reference documentation for the correct syntax for the command.

OGG-15155: The {0} option is missing for the {1} command.
Cause: There is a missing required option for the specified command.

Action: See the Oracle GoldenGate reference documentation to know the correct syntax for the command.

OGG-15156: The {0} option is invalid for the {1} command because Replicat {2} is not integrated.
Cause: The specified option cannot be used with the command in the current Replicat mode.

Action: Ensure that the specified Replicat group name is spelled correctly, verify the Replicat mode, and then retry the command with the proper options.

OGG-15157: Could not find port information for {0} {1}.
Cause: Oracle GoldenGate could not find the listening port for the specified process.

Action: Contact Oracle Support.

OGG-15158: Coordinated Replicat thread {0} is not running.
Cause: The command could not be executed because the specified Replicat thread is not running.

Action: Start the Replicat thread and try again. If the error cannot be resolved, contact Oracle Support.

OGG-15159: Could not find port info for Coordinated Replicat thread {0}.
Cause: Oracle GoldenGate could not find the listening port for the specified process.

Action: Contact Oracle Support.

OGG-15160: No active Replicat threads match the specified thread list: {0}.
Cause: There was a valid specified thread list but the command could not be executed because none are active.

Action: None

OGG-15161: Could not initialize the connection with {0} {1} ({2}).
Cause: Oracle GoldenGate could not establish a connection with the specified process.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15162: There was a problem sending a message to MANAGER ({0}).
Cause: The communication with the manager process failed due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15163: There was a problem sending a message to {0} {1} ({2}).
Cause: The communication with the process failed due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15164: Could not retrieve the information about open transactions due to the next error: {0}
Cause: There was a problem executing the SHOWTRANS command in the Extract process due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15165: Extract is currently in recovery mode (reading transactions from trail file). Please try again in a few minutes.
Cause: Extract cannot perform the request because it is in recovery mode. Informational only.

Action: Retry the operation in a few minutes.

OGG-15166: Long running transaction feature is not supported for this database.
Cause: Extract cannot perform the request because that feature is not supported currently for the database being used.

Action: None

OGG-15167: Command {0} is not supported for {1}. This command is only valid for primary Extract processes.
Cause: The specified command could not be executed because it was sent to an Oracle GoldenGate application that does not support it.

Action: Verify that the process type and the group name were spelled correctly and that they refer to a primary Extract process.

OGG-15168: No transactions found.
Cause: Informational only.

Action: None

OGG-15169: Could not process the tracing command due to the next error: {0}
Cause: There was a problem executing the tracing operation command due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15170: Tracing command operation successfully processed. {0}
Cause: Informational only.

Action: None

OGG-15171: Tracing command operation successfully processed.
Cause: Informational only.

Action: None

OGG-15172: STOP request will be executed immediately ({0} aborted).
Cause: Informational only.

Action: None

OGG-15173: Could not skip the specified transaction due to the next error: {0}
Cause: There was a problem executing the SKIPTRANS command in the Extract process due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15174: Skiptrans operation successfully processed. {0}
Cause: Informational only.

Action: None

OGG-15175: Transaction [{0}] not found.
Cause: Extract could not process the SKIPTRANS command because the specified transaction id was not found.

Action: Verify that the transaction id specification was spelled correctly. If you cannot resolve the problem, contact Oracle Support.

OGG-15176: Unknown request "{0}".
Cause: The specified request is not recognized as a valid operation.

Action: See the Oracle GoldenGate reference documentation for the correct syntax for the command.

OGG-15177: Unknown parameters for command {0}: "{1}".
Cause: The specified parameters for the command are invalid.

Action: See the Oracle GoldenGate reference documentation for the correct syntax for the command.

OGG-15178: RESUME is invalid for a Coordinated Replicat thread.
Cause: The specified command cannot be used with a Coordinated Replicat thread.

Action: Verify that the process type and the group name were spelled correctly and that they do not refer to a Coordinated Replicat thread.

OGG-15179: Profiles reloaded.
Cause: The collection profiles for performance metrics have been loaded successfully.

Action: None

OGG-15180: Not enabled.
Cause: The collection profiles for performance metrics are disabled and cannot be loaded.

Action: Enable the collection profiles and try again.

OGG-15181: Not loaded.
Cause: The collection profiles for performance metrics could not be loaded correctly.

Action: Contact Oracle Support.

OGG-15182: Invalid JSON formatted response.
Cause: The response from the target process is not a valid JSON object. The data may have been corrupted during transmission or the target process did not build a correct JSON response.

Action: Try the operation again. If the problem persists, contact Oracle Support.

OGG-15183: Missing table name specification.
Cause: The name of the table is missing while trying to execute the specified command.

Action: Specify the name of the table.

OGG-15184: A catalog name {0} is specified in an environment where the database does not support catalogs.
Cause: The database does not support catalogs.

Action: Provide a table name specification that is valid for your database.

OGG-15185: A wildcarded catalog name {0} is specified in an environment where the database does not support wildcards for catalog names.
Cause: Wildcarded catalogs are not supported by this database.

Action: See the rules for catalog wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.

OGG-15186: Could not retrieve logon catalog name.
Cause: A database error may be preventing the process from retrieving the logon catalog name.

Action: Contact Oracle Support.

OGG-15187: Retrieving table definition for table specification {0} is prohibited when logged on to database {1}.
Cause: An attempt to retrieve the table definition failed because the process is not logged on to the root level database.

Action: Either log on to the root database or specify a catalog name in the logon to the current database.

OGG-15188: Could not retrieve default catalog name.
Cause: A database error may be preventing the process from retrieving the default catalog name.

Action: Contact Oracle Support.

OGG-15189: Default catalog name {0} will be used for table specification {1}.
Cause: A default catalog name will be used for the table specification.

Action: None

OGG-15190: Cannot use default catalog for table specification {0} while logged into the root level of a database.
Cause: The TABLE parameter does not include a catalog name.

Action: Specify the fully qualified table name including the catalog name.

OGG-15191: Logon catalog name {0} will be used for table specification {1}.
Cause: The specified catalog name will be used for the table specification.

Action: None

OGG-15192: Wildcards in schema names are not supported. Provide full name for {0}.
Cause: Wildcarded schema names are not supported by this database.

Action: Provide full name for the specified table.

OGG-15193: Cannot obtain database tables information because verification of database login failed with next error: {0}.
Cause: A request for information about database tables was attempted without first issuing a DBLOGIN command or establishing a database connection.

Action: Establish a database connection or issue the DBLOGIN command, and then retry this operation.

OGG-15194: Directory {0} does not exist yet.
Cause: The specified directory does not exist yet in the Oracle GoldenGate environment.

Action: Create the directory using the CREATE SUBDIRS command.

OGG-15200: Data target not specified
Cause: The Oracle GoldenGate Extract process is configured with an unknown data target type.

Action: Recreate the Extract group with a supported data target type, such as EXTRACT_TRAILS.

OGG-15300: GLOBALS file GGSCHEMA parameter must be specified.
Cause: The action performed by Oracle GoldenGate requires that the GGSCHEMA parameter is specified in the GLOBALS file.

Action: Edit the GLOBALS file and supply the DDL schema name.

OGG-15301: Cannot update Oracle sequence information because verification of database login failed with next error: {0}.
Cause: A request to flush an Oracle sequence was attempted without first issuing a DBLOGIN command or establishing a database connection.

Action: Establish a database connection or issue the DBLOGIN command, and then retry this operation.

OGG-15302: Bad sequence specification syntax {0}.
Cause: An invalid Oracle sequence specification was entered.

Action: Try again with a correct sequence specification. If the correct sequence syntax cannot be determined, contact Oracle Support.

OGG-15303: Sequence {0} schema cannot have wildcards.
Cause: Wildcarded schema names are not supported by this database.

Action: Provide the full name for the specified schema.

OGG-15304: Schema name is required for sequence specification {0}.
Cause: The sequence specification does not include a schema name.

Action: Specify the schema name in the sequence specification.

OGG-15305: Catalog name is missing for sequence specification {0}.
Cause: The sequence specification does not include a catalog name.

Action: Specify the catalog name in the sequence specification.

OGG-15306: Sequence {0} catalog cannot have wildcards.
Cause: Wildcarded catalogs are not supported by this database.

Action: See the rules for catalog wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.

OGG-15307: A catalog name {0} is specified in an environment where the database does not support catalogs.
Cause: The database does not support catalogs.

Action: Provide a sequence specification that is valid for your database.

OGG-15308: Logon catalog name {0} will be used for sequence specification {1}.
Cause: The specified catalog name will be used for the sequence specification.

Action: None

OGG-15309: Sequence schema {0} does not exist.
Cause: The specified sequence schema could not be found.

Action: Make sure that the specified sequence schema was spelled correctly, or contact Oracle Support.

OGG-15310: Sequence {0} does not exist.
Cause: The specified sequence could not be found.

Action: Make sure that the specified sequence was spelled correctly, or contact Oracle Support.

OGG-15311: Successfully flushed {0} sequence(s) {1}.
Cause: Informational only.

Action: None

OGG-15312: Cannot obtain database version information because verification of database login failed with next error: {0}.
Cause: A request for information about database version was attempted without first issuing a DBLOGIN command or establishing a database connection.

Action: Establish a database connection or issue the DBLOGIN command, and then retry this operation.

OGG-15313: Could not retrieve database version information due to the next error: {0}.
Cause: There was a problem obtaining database version information due to the specified error message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15314: Error retrieving OS version ({0},{1}).
Cause: There was a problem obtaining the operating system version information due to the specified error message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15315: Replicat synchronization is not supported for {0} {1}. This action is valid only for integrated, coordinated, or parallel Replicats.
Cause: The specified command could not be executed because it was sent to an Oracle GoldenGate application that does not support it.

Action: Verify that the process type and the group name were spelled correctly and that they refer to a integrated, coordinated, or parallel Replicat process.

OGG-15316: Could not perform the Replicat synchronization operation due to the next error: {0}
Cause: There was a problem executing a synchronization operation in the Replicat process due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15317: Cannot determine Replicat synchronization state. {0} is not a Coordinator.
Cause: There was a problem determining the Replicat synchronization state because the specified group name is not a coordinated Replicat.

Action: Verify that the process type and the group name were spelled correctly and that they refer to a coordinated Replicat process.

OGG-15318: Could not look up table {0} due to the next error: {1}
Cause: There was a problem looking for the specified table name in the database due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15319: History table {0} does not exist.
Cause: The history table could not be found in the database.

Action: Create the history table and try the operation again.

OGG-15320: Sequence {0} not found in history table {1}.
Cause: The history table does not contain the specified DDL sequence number.

Action: Contact Oracle Support.

OGG-15321: Marker table name for DDL sequence {0} not found.
Cause: Oracle GoldenGate was not able to retrieve the DDL metadata property information correctly.

Action: None

OGG-15322: Marker sequence number for DDL sequence {0} not found.
Cause: Oracle GoldenGate was not able to retrieve the DDL metadata property information correctly.

Action: None

OGG-15323: DDL operation for DDL sequence {0} not found.
Cause: Oracle GoldenGate was not able to retrieve the DDL metadata property information correctly.

Action: None

OGG-15324: Stopping DDL dump due to a SQL error.
Cause: The DDL dump operation will be aborted because there was an error executing an SQL statement.

Action: Verify logs and previous error or warning messages to know the exact SQL error and correct the problem. If you cannot resolve the problem, contact Oracle Support.

OGG-15325: DBLOGIN required for DDL dump operation.
Cause: A database connection is necessary to perform the DDL dump operation.

Action: Establish a database connection or issue the DBLOGIN command, and then retry this operation.

OGG-15326: SQL error: [{0}], statement [{1}].
Cause: There was an error executing the specified SQL statement.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15327: SQL error when preparing statement [{1}]: [{0}].
Cause: There was an error preparing the specified SQL statement.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15328: DDL history table {0} is empty (no rows to dump).
Cause: Informational only.

Action: None

OGG-15329: Dumping DDL metadata for DDL sequence {0}.
Cause: The specified DDL sequence information is being dumped into the DUMPDDL tables. Informational only.

Action: None

OGG-15330: Forcetrans operation successfully processed. {0}
Cause: Informational only.

Action: None

OGG-15331: Transaction [{0}] not found.
Cause: Extract could not process the FORCETRANS command because the specified transaction id was not found.

Action: Verify that the transaction id specification was spelled correctly. If you cannot resolve the problem, contact Oracle Support.

OGG-15332: Command [{0}] not supported for this database.
Cause: The specified command could not be executed because it is not valid for this database.

Action: See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.

OGG-15333: Command [{0}] is not supported by an Extract data pump or for any data source that is not supported by the ADD TRANDATA command.
Cause: The specified command could not be executed because it is not valid for this process type.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15334: Command [{0}] is not supported by Replicat.
Cause: The specified command could not be executed because it is not valid for this process type.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15335: {0} request processed.
Cause: The specified SEND request was successfully processed.

Action: None

OGG-15336: Could not process the TRANLOGOPTIONS request due to the next error: {0}
Cause: There was a problem executing the TRANLOGOPTIONS command due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15337: Lag information has not been collected yet.
Cause: Informational only.

Action: None

OGG-15338: Timestamp mismatch between source and target. Accurate Lag Information Unavailable.
Cause: The last value of the process lag is invalid.

Action: Contact Oracle Support.

OGG-15339: Statements can only have one THREAD, THREADS, or THREADRANGE parameter.
Cause: The specified parameters for the command are invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15340: Invalid THREAD/THREADS specification.
Cause: The specified parameters for the command are invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15341: Invalid THREADRANGE specification.
Cause: The specified parameters for the command are invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15342: Table specification {0} is invalid. {1}
Cause: The specified name of the table is invalid.

Action: Verify that the table name was written correctly and correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15343: {0} {1} set for {2} tables and {3} wildcard entries.
Cause: Informational only.

Action: None

OGG-15344: No tables found matching {0} to set {1} for {2}.
Cause: Informational only.

Action: None

OGG-15345: Missing or invalid INTEGRATEDPARAMS options {0}.
Cause: The specified parameters for the command are invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15346: Error parsing INTEGRATEDPARAMS parameters: {0}.
Cause: There was a problem parsing the INTEGRATEDPARAMS command due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15347: No TCP connections.
Cause: There are no remote host connections configured for this Extract process.

Action: None

OGG-15348: Missing end quote for VAMMESSAGE.
Cause: The VAM message received by Extract is not formatted correctly.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15349: Could not process the VAM request due to the next error: {0}
Cause: There was a problem processing the VAM command due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15350: Could not process the VAM request.
Cause: There was a problem processing the VAM command.

Action: Contact Oracle Support.

OGG-15351: Bounded recovery is off.
Cause: Informational only.

Action: None

OGG-15352: Command [{0}] not recognized.
Cause: The specified BR command is invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15353: Bounded recovery is already running.
Cause: Informational only.

Action: None

OGG-15354: Bounded recovery is already stopped.
Cause: Informational only.

Action: None

OGG-15355: Unknown command {0}.
Cause: The specified command is invalid.

Action: Verify the syntax and then issue the command again. See the Oracle GoldenGate reference for valid values.

OGG-15356: Not enough memory to execute command.
Cause: The process could not allocate heap memory.

Action: Verify that the server has sufficient free RAM. If not, add more RAM and then restart the process.

OGG-15357: Error on command initialization.
Cause: There was an error initializing the internal context to execute the CACHEMGR command.

Action: Contact Oracle Support.

OGG-15358: Failed to retrieve recovery information due to next error: {0}
Cause: There was a problem retrieving the process recovery information due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15359: Invalid table specification {0} for {1}.
Cause: The table name was incorrectly specified and it was not possible to process it.

Action: Try again with a correct table name specification. If the correct table syntax cannot be determined, contact Oracle Support.

OGG-15360: Expecting schema name for table specification {0}.
Cause: The table specification does not contain required schema name.

Action: Try the operation again providing the table with the schema name.

OGG-15361: Multiple rates specified. Using {0}.
Cause: Multiple instances of the option REPORTRATE were provided. The command will proceed using the first option specified.

Action: None

OGG-15362: Invalid value '{0}' for {1}. Report rate must be HR, MIN, or SEC
Cause: The specified value is not a valid one for REPORTRATE.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15363: Invalid STATS request: {0}.
Cause: The specified option is not a valid one for STATS command.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15364: No active Replication maps.
Cause: Informational only.

Action: None

OGG-15365: No active Extraction maps.
Cause: Informational only.

Action: None

OGG-15366: Successfully reset statistics.
Cause: Informational only.

Action: None

OGG-15367: Fully qualified table name {0} is not found in the Oracle GoldenGate configuration.
Cause: There was no match for the specified table in the tables statistics list.

Action: Verify that the table specification is spelled correctly.

OGG-15368: Statistics for Coordinated Replicat have not been collected yet.
Cause: Informational only.

Action: None

OGG-15369: TCP stats reset.
Cause: Informational only.

Action: None

OGG-15370: Command [{0}] not recognized.
Cause: The specified RTC command is invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15371: RTC can not be resumed.
Cause: There was a problem trying to resume the Redo Thread Coordinator.

Action: Contact Oracle Support.

OGG-15372: RTC is successfully resumed.
Cause: Informational only.

Action: None

OGG-15373: RTC can not be suspended.
Cause: There was a problem trying to suspend the Redo Thread Coordinator.

Action: Contact Oracle Support.

OGG-15374: RTC is successfully suspended.
Cause: Informational only.

Action: None

OGG-15375: Invalid command: {0}.
Cause: The specified PROBE command is invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15376: Missing options: {0}.
Cause: There is a missing required option for the specified PROBE command.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15377: Probe is dumped to {0}.
Cause: The PROBE command result was dumped to the specified file.

Action: None

OGG-15378: Failed to dump probes to {0}.
Cause: There was an error trying to dump the PROBE command result to the specified file.

Action: Make sure that enough disk space is available, the file directory exists and that it has proper writing permissions assigned. If you cannot resolve the problem, contact Oracle Support.

OGG-15379: Probe configuration {0} is sucessfully loaded.
Cause: The PROBE configuration was correctly loaded from the specified file.

Action: None

OGG-15380: Failed to load probe configuration {0}.
Cause: There was an error trying to load the PROBE configuration from the specified file.

Action: Make sure that the specified file exists and that it has proper reading permissions assigned. If you cannot resolve the problem, contact Oracle Support.

OGG-15381: Ignored {0}.
Cause: The specified parameter id is not valid and will be ignored.

Action: See the Oracle GoldenGate reference for valid values. If you cannot resolve the problem, contact Oracle Support.

OGG-15382: Failed to retrieve parameter information due to next error: {0}
Cause: There was a problem retrieving the parameter information due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15383: Unknown {0}.
Cause: The specified parameter id is not recognized.

Action: See the Oracle GoldenGate reference for valid values. If you cannot resolve the problem, contact Oracle Support.

OGG-15384: Param '{0}' is not loaded into dictionary.
Cause: The specified parameter name cannot be found in the parameter dictionary.

Action: Contact Oracle Support.

OGG-15385: File '{0}' could not be opened.
Cause: There was an error trying to open the specified file.

Action: Make sure that enough disk space is available, the file directory exists and that it has proper writing permissions assigned. If you cannot resolve the problem, contact Oracle Support.

OGG-15386: Missing begin quote for VAMMESSAGE.
Cause: The VAM message received by Extract is not formatted correctly.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15387: STOP request pending. Recovery is not complete. This normal stop will wait and checkpoint recovery's work when recovery has finished. To force Extract to stop now, use the SEND EXTRACT {0}, FORCESTOP command.
Cause: The STOP request will be executed after the checkpoint recovery work is finished.

Action: None

OGG-15388: STOP request pending end-of-transaction ({0} records so far).
Cause: The STOP request will be executed after finishing processing the pending transaction.

Action: None

OGG-15389: STOP request pending completion of recovery mode.
Cause: The STOP request will be executed after the recovery work is finished.

Action: None

OGG-15390: STOP request pending fetch from fetch database. To force Extract to stop now, use the SEND EXTRACT {0}, FORCESTOP command.
Cause: The STOP request will be executed after the pending fetch is finished.

Action: None

OGG-15391: Error retrieving {0} next checkpoint.
Cause: There was a problem obtaining the process checkpoint information.

Action: Contact Oracle Support.

OGG-15392: Invalid checkpoint type.
Cause: Oracle GoldenGate was not able to recognize the process checkpoint type.

Action: Contact Oracle Support.

OGG-15393: Unknown checkpoint error.
Cause: Oracle GoldenGate was not able to process the checkpoint information correctly.

Action: Contact Oracle Support.

OGG-15394: Lag unknown (timestamp mismatch between source and target).
Cause: The last value of the process lag is invalid.

Action: Contact Oracle Support.

OGG-15395: Low watermark position not available.
Cause: The low watermark position stored in the Integrated Replicat table is empty or contains an invalid value.

Action: Contact Oracle Support.

OGG-15396: High watermark position not available.
Cause: The high watermark position stored in the Integrated Replicat table is empty or contains an invalid value.

Action: Contact Oracle Support.

OGG-15397: Could not query Integrated Replicat lag.
Cause: There was a problem executing a query to retrieve the lag information from the Integrated Replicat table.

Action: Contact Oracle Support.

OGG-15398: STOP request pending. There are open, long-running transactions. Before you stop Extract, make the archives containing data for those transactions available for when Extract restarts. To force Extract to stop, use the SEND EXTRACT {0}, FORCESTOP command.
Cause: The STOP request will not be executed because there are open, long-running transactions pending.

Action: Look at the recovery information to know what the oldest database file needed for restart is.

OGG-15399: Recovery information: {0}
Cause: Informational only.

Action: None

OGG-15400: Could not process the STOP command due to the next error: {0}
Cause: There was a problem executing the STOP command due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15401: The STOP command is invalid for a Coordinated Replicat thread.
Cause: A Coordinated Replicat process received a request to stop one of the threads.

Action: Verify that the group name in the stop request was specified correctly.

OGG-15402: Could not force the transaction to the trail file due to the next error: {0}
Cause: There was a problem executing the FORCETRANS command in the Extract process due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-15403: Unrecognized parameter '{0}'. Expected '{1}'.
Cause: The specified command parameter is invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15404: Unrecognized parameter '{0}'.
Cause: The specified command parameter is invalid.

Action: See the Oracle GoldenGate reference for valid values.

OGG-15405: The container list for REGISTER EXTRACT cannot be empty.
Cause: The REGISTER EXTRACT command was issued with the DATABASE CONTAINER option, but no container list was supplied.

Action: Supply a container list for the DATABASE CONTAINER option. See the Oracle GoldenGate reference for valid values.

OGG-15406: Missing opening parenthesis in container list for REGISTER EXTRACT command.
Cause: A parenthesis is missing from the container list specification for REGISTER EXTRACT command.

Action: Add the parenthesis. See the Oracle GoldenGate reference for valid values.

OGG-15407: Missing closing parenthesis in container list for REGISTER EXTRACT command.
Cause: A parenthesis is missing from the container list specification for REGISTER EXTRACT command.

Action: Add the parenthesis. See the Oracle GoldenGate reference for valid values.

OGG-15408: Cannot specify both '{0}' and '{1}' at the same time.
Cause: Mutually exclusive command arguments were specified.

Action: Remove one of the arguments and try again. See the Oracle GoldenGate reference for valid values.

OGG-15409: Alias '{0}' not found in credential store domain '{1}'.
Cause: The specified alias-credential group are not contained in current credential store.

Action: Verify the alias and credential group were typed correctly.

OGG-15410: Alias '{0}' not found in credential store domain '{1}'.
Cause: The specified credential alias could not be found in the credential store.

Action: Make sure that the specified credential store domain and alias were spelled correctly, the credential store location is correct, or contact Oracle Support.

OGG-15411: Missing group specification for {0}
Cause: Group name for Extract or Replicat is not specified.

Action: Make sure a group name is specified for Extract or Replicat. For more information, see the Oracle GoldenGate reference documentation.

OGG-15412: Function {0} not implemented.
Cause: An internal error occurred.

Action: Contact Oracle Support.

OGG-15413: Failed to bind SSL functions with TLSAdapter.
Cause: An internal error occurred.

Action: Contact Oracle Support.

OGG-15414: Missing archive log file for Thread {0} Seqnum {1}, SCN 0x{2}.
Cause: Unable to find the archive log file at the expected SCN.

Action: Check that the archive log files are placed in the recommended location. For more information, see the Oracle GoldenGate reference documentation.

OGG-15415: Log archive destination at the source database must be configured with the NOREGISTER attribute for destination id '{0}'.
Cause: Oracle redo transport is misconfigured at the source database.

Action: Use the NOREGISTER option in log_archive_dest_'{0}' at the source database.

OGG-15416: Count of standby redo logs {0} and online redo logs {1} cannot be 0 for downstream real-time.
Cause: Count of standby redo logs and online redo logs cannot be 0 for downstream real-time.

Action: Check that the count of standby redo logs and online redo logs are not 0 for downstream real-time.

OGG-15417: Standby redo logs were not detected for destination id '{0}'.
Cause: Missing standby redo log file attribute for downstream real-time.

Action: Check that the standby redo log file attribute is set for destination '{0}'.

OGG-15418: Usage of template clause for log archive destination '{0}' will cause redo transport to only send archived redo to downstream.
Cause: Template clause forces archive log only redo shipment.

Action: Template clause forces archive log only redo shipment. Validate that this is the desired behavior or remove this option.

OGG-15419: Standby Redo Logs were not detected on the downstream database.
Cause: Standby Redo Logs were not detected on the downstream database.

Action: Validate the downstream configuration to determine if archived only redo shipment is desired. If not, configure standby redo logs on the downstream database.

OGG-15420: MaxSize of standby redo logs {0} must not be less than online redo logs {1}.
Cause: The size of the standby redo logs must be configured to be greater than or equal to the size of the online redo logs at the source database.

Action: Check the size of configured standby redo logs and make sure they are at the recommended setting.

OGG-15421: For each database instance, the count of standby redo logs {0} is recommended to be 1 greater than the online redo logs {1}.
Cause: Standby redo log count is recommended to be 1 greater than the online redo log for each database instance.

Action: Check that the number of standby redo log count is at least 1 greater than number of online redo log for each thread.

OGG-15422: Source database has a misconfigured global_name '{0}' with missing domain.
Cause: Source databases must have a global_name with valid domain or Extract may use the downstream domain name, which could cause a failure to connect to the source database instance.

Action: Add the domain suffix to the global_name in the source database.

OGG-15423: The number of tables to be captured, exceeds the maximum (50,000), for which filtering by table name can be performed. Filter by table name has been disabled.
Cause: The number of tables to be captured exceeds the maximum (50,000), for which filtering by table name can be performed.

Action: To allow filtering for this Extract group, reduce the number of tables specified to less than 50,000.

OGG-15424: One or more table specifications, contain wildcard character(s). Filter by table name is not supported with wildcard specifications. Filter by table name has been disabled.
Cause: One or more table specifications contain wildcard characters. Filter by table name is not supported with wildcard specifications.

Action: To allow filtering for this Extract group, remove all wildcard characters from all table specifications.

OGG-15425: Replicat tasks cannot be altered.
Cause: Replicat tasks cannot be altered once created.

Action: To alter a Replicat task, delete the task and re-create it.

OGG-15426: {0} {1} started
Cause: The specified process was started.

Action: None

OGG-15427: Redo transport experienced a lag of {0}secs at thread {1}.
Cause: Redo transport experienced a lag at a thread that was more than normal.

Action: Check the condition of redo transport and run health checks to isolate possible transport issues from that database instance.

OGG-15428: Redo transport lag at thread {0} returned to acceptable levels.
Cause: Redo transport lag at thread returned to acceptable levels.

Action: No action required.

OGG-15429: Thread {0} not responding to command {1} in timely manner.
Cause: The named thread is not responding to named command in pre-determined time.

Action: None

OGG-15430: No database connection was initialized while getting database information.
Cause: No database connection was initialized while getting database information.

Action: Contact Oracle Support.

OGG-15431: Cannot register REPLICAT '{0}' because it was not created with integrated apply mode.
Cause: The specified REPLICAT does not use integrated apply mode and cannot be registered.

Action: Recreate or ALTER the REPLICAT to use integrated apply mode and try again.

OGG-15432: Could not find a valid log archive destination with matching db_unique_name of '{0}' in source database.
Cause: A valid log archive destination with a db_unique_name matching the downstream database is required on source database.

Action: Verify that the log archive destination in source database has a valid entry matching the downstream db_unique_name.

OGG-15433: Could not find any online redo logs on source database.
Cause: Online redo logs are needed in the source database to support real time downstream mining.

Action: Verify that the source database has valid online redo logs configured.

OGG-25050: The HANDLEDLFAILOVER option of the TRANLOGOPTIONS parameter cannot be specified when the NOUSERID parameter is specified and there is no Active Data Guard standby database.
Cause: The HANDLEDLFAILOVER option of the TRANLOGOPTIONS parameter cannot be specified when the NOUSERID parameter is specified and there is no Active Data Guard standby database.

Action: Contact Oracle Support.

OGG-25051: Query to source database to retrieve standby became primary SCN failed.
Cause: Failed to query standby_became_primary SCN from the source database.

Action: Contact Oracle Support.

OGG-25052: The primary database has undergone a role transition. Temporarily suspend the HANDLEDLFAILOVER behavior for {0} seconds to allow time for standby database reinstatement. Note that for the duration of this timeout period, Extract will not throttle trail generation. Therefore, there is a potential for data divergence between the Oracle GoldenGate target database and the reinstating Oracle Data Guard standby database.
Cause: The primary database has undergone a role transition. Temporarily disable the HANDLEDLFAILOVER parameter to allow standby database reinstatement.

Action: None

OGG-25053: Timeout waiting for {0} seconds for standby database reinstatement. Now enforcing HANDLEDLFAILOVER.
Cause: The timer for temporarily disabling the HANDLEDLFAILOVER parameter expired. Re-enable HANDLEDLFAILOVER.

Action: None

OGG-25054: Specification of TRANLOGOPTOINS MINEFROMACTIVEDG FORCE will force Classic Extract to mine redo aggressively even though Oracle Managed Redo Process(MRP) is not running on the Active Data Guard Standby database. This may lead to data inconsistency between the Active Data Guard Standby database and Oracle GoldenGate target databases. Record SCN is {0}, applied SCN is {1}.
Cause: Oracle Managed Redo Process (MRP) is not running. Because the TRANLOGOPTIONS parameter includes the MINEFROMACTIVEDG FORCE option, Classic Extract will continue mining redo from the Active Data Guard database. This may lead to data inconsistencies between the Active Data Guard database and Oracle GoldenGate target databases.

Action: Start the Oracle Managed Redo Process (MRP).

OGG-25071: The UPDATE operation is trying to modify a column that is part of Distribution Clause of the table {0} on Netezza. The UPDATE will be converted into DELETE followed by INSERT.
Cause: The UPDATE operation is trying to modify a column that is part of Distribution Clause of the table on Netezza. The UPDATE will be converted into DELETE followed by INSERT.

Action: Contact Oracle Support.

OGG-25091: Failed to obtain mining character set.
Cause: Extract failed to determine the character set of the mining database.

Action: Contact Oracle Support.

OGG-25092: Sequence update did not succeed, error: {0}.
Cause: Replicat failed to update the sequence value.

Action: Examine the errors and contact Oracle Support if necessary.

OGG-25093: Invalid command format.
Cause: The JSON format for command entered is invalid. The corresponding record will be skipped.

Action: Verify the JSON format of the command.

OGG-25094: Invalid command table record encountered.
Cause: An invalid command table record was encountered. The trail file may be corrupt. The invalid record will be skipped.

Action: Verify that the trail file is not corrupt.

OGG-25101: The shared resources pool has reach its maximum capacity.
Cause: The shared pool is full and cannot allocate more resources.

Action: Avoid creating numerous distribution paths.

OGG-25102: Too many requests for distpath '{0}' are in the queue.
Cause: Too many requests were sent for the same distribution path in a short period of time.

Action: Avoid sending too many requests at once for the same distribution path to Distribution Server.

OGG-25103: ERROR: {0} system call: bytes-to-do: {1,number,0} bytes-done: {2,number,0} fd: {3,number,0} error{4,number,0} ({5})
Cause: File access failed at the operating system level.

Action: Correct Oracle Support.

OGG-25104: ERROR: {0} system call, unexpected EOF: bytes-to-read: {1,number,0} bytes-done: {2,number,0} fd: {3,number,0} error{4,number,0} ({5})
Cause: File read encountered an unexpected EOF.

Action: Correct Oracle Support.

OGG-25105: ERROR: {0} system call: offset-requested: {1,number,0} from: {2,number,0} fd: {3,number,0} error{4,number,0} ({5})
Cause: File access failed at the operating system level.

Action: Correct Oracle Support.

OGG-25106: Failed to create checkpoint file {0}
Cause: The process could not create the checkpoint file.

Action: Check the operating system privileges on the file, and ensure that the process has read and write privileges. Ensure that the file is not corrupted. If the file remains unwritable, contact Oracle Support.

OGG-25107: Error retrieving current checkpoint timestamp
Cause: The process could not read the checkpoint timestamp.

Action: Check the operating system privileges on the file, and ensure that the process has read and write privileges. Ensure that the file that caused the error is not corrupted. If the process cannot open the next checkpoint file, contact Oracle Support.

OGG-25108: Failed to set the Oracle session tag: {0}
Cause: Oracle Database was not able to set the session tag.

Action: Make sure that the login user has Oracle GoldenGate administration privileges. If the error persists, contact Oracle Support.

OGG-25109: The '{0}' tag is reserved for Internal use, please choose another value for the SETTAG option
Cause: The specified value of the tag is reserved for Internal use.

Action: Choose another value for the SETTAG option.

OGG-25110: The database role {0} is unsupported
Cause: The application connected to a database with an unsupported role.

Action: Specify a connection to a valid database.

OGG-25111: The received message has a poorly formed HTTP header, it was expected an HTTP {0} command
Cause: A poorly formed command was received and cannot be executed.

Action: If this message continues to appear, contact Oracle Support.

OGG-25112: The received message has a wrong URL in the HTTP header, it was expected an HTTP {0} {1}
Cause: A poorly formed command was received and cannot be executed.

Action: If this message continues to appear, contact Oracle Support.

OGG-25113: The received message has a poorly formed HTTP header, there is no '\r \r ' string to delimit the payload from the header
Cause: A poorly formed command was received and cannot be executed.

Action: If this message continues to appear, contact Oracle Support.

OGG-25114: There was a problem communicating with {0} {1}, the HTTP response was {2,number,0} {3}.
Cause: The communication with the process failed because the response status was not expected.

Action: If this message continues to appear, contact Oracle Support.

OGG-25115: There was a problem communicating with {0} {1}, the HTTP response does not have any payload.
Cause: The communication with the process failed because the response does not have any payload.

Action: If this message continues to appear, contact Oracle Support.

OGG-25116: There was a problem sending/receiving a message to/from {0} {1} ({2}).
Cause: The communication with the process failed due to the specified message.

Action: Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.

OGG-25117: The target host/port string is poorly formed, we expect a string like 'host.port' with the port being greater than 0, and we have '{0}'.
Cause: The target address/port string is poorly formed, the command cannot be sent to this address.

Action: If this message continues to appear, contact Oracle Support.

OGG-25118: Maximum apply parallelism {0} requested is less than minimum apply parallelism {1}. This is not a supported combination.
Cause: Incorrect combination of values for maximum and minimum apply parallelism.

Action: Change your minimum and maximum apply parallelism values such that maximum apply parallelism is greater than or equal to minimum apply parallelism.

OGG-25119: Failed to create missing sub-directories.
Cause: Creating directories failed.

Action: Manually create all the directories.

OGG-25121: Classic Extract should not be using an Exadata source.
Cause: Oracle Exadata source.

Action: Use different Extract mode that supports Oracle Exadata.

OGG-25122: No data found when quering for source database.
Cause: No data found when querying for source.

Action: Contact Oracle Support for help.

OGG-25123: Query only supported from DB version 11.2
Cause: Invalid Oracle Database release.

Action: Use Oracle Database release 11.2 and later.

OGG-25124: Parameter {0} is not supported by Parallel Replicat
Cause: The specified parameter is incompatible with Parallel Replicat.

Action: Remove the parameter and restart Replicat.

OGG-25125: Automatic Conflict Detection and Resolution is not configured for the sharded table {0}.
Cause: Automatic conflict detection and resolution feature is not configured for the sharded table.

Action: Configure the automatic conflict detection and resolution feature for the sharded table.

OGG-25126: An unrecoverable error was detected by the remote side. (Reply received is '{0}')
Cause: An unrecoverable error on a distribution path was detected by the remote side. The path cannot continue or restart.

Action: Examine previously issued error messages for possible causes and actions. Contact Oracle Support if the error persist.

OGG-25127: Received an error reply requesting a graceful shutdown. (Reply received is '{0}'.)
Cause: Error detected on the remote side, too many (greater or equal to 1000) paths have been started.

Action: Distribution Server will kill the path.

OGG-25128: RESOLVECONFLICT is not supported when the target table is enabled for Automatic Conflict Detection and Resolution
Cause: The target table has been configured with Automatic Conflict Detection and Resolution and is incompatible with RESOLVECONFLICT mapping options.

Action: Either remove Automatic Conflict Detection and Resolution on the target object or the conflicting RESOLVECONFLICT mapping options.

OGG-25129: DATA CAPTURE CHANGES enabled for SYSIBM.SYSTABLES. This may allow the capture of data related to SYSIBM.SYSTABLES when APIFILTER is used.
Cause: If APIFILTER is enabled and DATA CAPTURE CHANGES is enabled for SYSIBM.SYSTABLES, then APIFILTER can be used to capture systables data when filtering with a list of databases and table IDs.

Action: To enable DATA CAPTURE CHANGES for SYSIBM.SYSTABLES, use this GGSCI command: ADD TRANDATA sysibm.systables. This allows processing to be done with APIFILTER, when no other conditions exist that would force NOAPIFILTER. For example, the need to capture change data for any table that includes one or more LOB columns.

OGG-25130: SYSIBM.SYSTABLES is queued in the list of database and table IDs that may be used with APIFILTER.
Cause: If APIFILTER is enabled and DATA CAPTURE CHANGES is enabled for SYSIBM.SYSTABLES, then the SYSIBM.SYSTABLES database and table ID is added to the list of APIFILTER IDs.

Action: To enable DATA CAPTURE CHANGES for SYSIBM.SYSTABLES, use this GGSCI command: ADD TRANDATA sysibm.systables. This allows processing to be done with APIFILTER, when no other conditions exist that would force NOAPIFILTER. For example, the need to capture change data for any table that includes one or more LOB columns.

OGG-25131: APIFILTER is filtering with a list of database and table IDs when reading log records.
Cause: If APIFILTER is enabled and DATA CAPTURE CHANGES is enabled for SYSIBM.SYSTABLES, then APIFILTER will be used to capture data using a list of IDs.

Action: To enable DATA CAPTURE CHANGES for SYSIBM.SYSTABLES, use this GGSCI command: ADD TRANDATA sysibm.systables. This allows processing to be done with APIFILTER, when no other conditions exist that would force NOAPIFILTER. For example, the need to capture change data for any table that includes one or more LOB columns.

OGG-25132: APIFILTER is not filtering with a list of database and table IDs when reading log records.
Cause: If APIFILTER is enabled and DATA CAPTURE CHANGES is enabled for SYSIBM.SYSTABLES, then APIFILTER will be used to capture data but without a list of IDs.

Action: To enable DATA CAPTURE CHANGES for SYSIBM.SYSTABLES, use this GGSCI command: ADD TRANDATA sysibm.systables. This allows processing to be done with APIFILTER, when no other conditions exist that would force NOAPIFILTER. For example, the need to capture change data for any table that includes one or more LOB columns.

OGG-25133: The REMOTESCHEMA value in the TRANLOGOPTIONS line in the EXTRACT param file cannot be longer than {0} characters.
Cause: The process cannot use a schema name that is greater than the maximum DB2 z/OS schema name length.

Action: Use a remote schema name that is not longer than the maximum length of a DB2 z/OS schema name.

OGG-25134: The EXCLUDEUSER value in the TRANLOGOPTIONS line in the EXTRACT param file cannot be longer than {0} characters.
Cause: The process cannot use a user name that is greater than the maximum DB2 z/OS user name length.

Action: Use a user name that is not longer than the maximum length of a DB2 z/OS user name.

OGG-25135: This transaction cannot be forced to Extract trail because of PL/SQL error. Please check log for more information.
Cause: The request of SEND EXTRACT FORCETRANS failed due to PL/SQL query failure.

Action: Check the connection between Oracle GoldenGate and Oracle RDBMS. Ensure that the transaction Xid and pdbUid provided are valid.

OGG-25136: This transaction cannot be forced to Extract trail because the feature does not support CDB mode Oracle Database releases early than 12.2.0.2.
Cause: The request of SEND EXTRACT FORCETRANS failed because the feature does not support CDB mode Oracle Database releases early than 12.2.0.2.

Action: Use a CDB mode Oracle Database with a release equal to or later than 12.2.0.2.

OGG-25137: Missing file name (and optionally DETAIL)
Cause: Missing a file name (and optionally DETAIL).

Action: Add a file name and optionally DETAIL.

OGG-25138: THREAD value not used (since this is a single threaded process)
Cause: Can't specify a thread number for non-threaded Extract.

Action: Don't specify a thread number for non-threaded Extract.

OGG-25139: This transaction cannot be forced to Extract the trail until at least one other transaction appears in the log and is processed by the Extract. Reissue the command after at least one other transaction has been processed.
Cause: This transaction cannot be forced to Extract trail until at least one other transaction appears in the log and is processed by the Extract.

Action: Reissue the command after at least one other transaction has been processed.

OGG-25140: Cannot skip transaction {0} because it's not the oldest one. Only the oldest transaction can be skipped
Cause: The transaction can't be skipped if it isn't the oldest because it can't be skipped until the ones older than it are processed.

Action: Skip the oldest transaction.

OGG-25141: Cannot force transaction {0} to trail file because it's not the oldest one. Only the oldest transaction can be forced to trail file
Cause: The transaction can't be forced if it isn't the oldest because it can't be forced until the ones older than it are processed

Action: Force the oldest transaction.

OGG-25142: Are you sure you sure you want to skip transaction {0}? (y/n)
Cause: Double-check before you skip the transaction.

Action: Input y to skip this transaction or n to stop the skip operation.

OGG-25143: Are you sure you sure you want to force transaction to trail file {0} (y/n)?
Cause: Double-check before you force the transaction.

Action: Input y to force this transaction to trial or n to stop the force operation.

OGG-25144: Extract is currently in recovery mode for thread #{0} (reading transactions from trail file). Please try again in a few minutes
Cause: Extract is currently in recovery mode (reading transactions from trail file).

Action: Wait for all transactions to be in memory (recovery complete) before continuing.

OGG-25145: Extract is currently in recovery mode (reading transactions from trail file). Please try again in a few minutes
Cause: Extract is currently in recovery mode (reading transactions from the trail file.

Action: Wait a few minutes, and the retry.

OGG-25146: Long running transaction feature is not supported for this database
Cause: The long running transaction feature is not supported for this database.

Action: Check the database support for long running transaction.

OGG-25147: THREAD option not applicable to this Extract configuration (Extract not configured with THREADS)
Cause: The THREAD option not applicable to this Extract configuration.

Action: Check THREAD option and Extract configuration.

OGG-25148: THREAD number not valid (there are only {0} threads)
Cause: The THREAD number is not in the valid range.

Action: Check the THREAD number.

OGG-25149: THREAD value not a valid number (1, 2, 3...)
Cause: The THREAD number is not valid.

Action: Check the THREAD number.

OGG-25150: Missing value for THREAD option
Cause: Missing a value for the THREAD option.

Action: Input a value for the THREAD option.

OGG-25151: Missing value for DURATION option
Cause: Missing a value for the DURATION option.

Action: Input a value for DURATION option

OGG-25152: Missing value for COUNT option
Cause: Missing a value for the COUNT option.

Action: Input a value for COUNT option.

OGG-25153: COUNT value not a valid number (1, 2, 3...)
Cause: The COUNT value is not a valid number.

Action: Check COUNT value.

OGG-25154: Long transaction report finished on {0}
Cause: Long transaction report finished.

Action: None

OGG-25155: Starting long transaction report on {0}
Cause: Long transaction report finished.

Action: None

OGG-25156: No transactions found
Cause: No transactions found.

Action: None

OGG-25157: Transaction {0} forced to trail file
Cause: The transaction has been forced to the trail file.

Action: None

OGG-25158: Transaction {0} skipped
Cause: The transaction has been skipped.

Action: None

OGG-25159: COUNT option cannot be used with transaction ID
Cause: The COUNT option cannot be used with transaction ID.

Action: Delete the COUNT option.

OGG-25160: DURATION option cannot be used with transaction ID
Cause: The DURATION option cannot be used with transaction ID.

Action: Delete the DURATION option.

OGG-25161: TABULAR option cannot be used with transaction ID
Cause: The TABULAR option cannot be used with transaction ID.

Action: Delete the TABULAR option

OGG-25162: File {0} could not be opened
Cause: The file could not be opened.

Action: Check the file name.

OGG-25163: This transaction ID {0} is present in multiple threads. Please specify THREAD option and try again
Cause: This transaction ID is present in multiple threads.

Action: Specify THREAD option and try again.

OGG-25164: Writing transaction report to file.
Cause: Writing transaction report to file.

Action: None

OGG-25165: Unrecognized option {0}
Cause: Unrecognized option.

Action: Check option.

OGG-25166: Query for this request returned no data
Cause: The query for this request returned no data.

Action: None

OGG-25167: Error attempting to delete LOB column number {0,number,0}, error text: {1}.
Cause: The process could not delete LOB memory data for the specified column. Ensure that the column data exists.

Action: Exclude the table from the TABLE statement and contact Oracle Support, if column data exists.

OGG-25168: The specified GGSCHEMA name '{0}' in the GLOBALS file does not exist in the database, or you do not have permission to use it. Specify a valid GGSCHEMA name in the GLOBALS file.
Cause: The GGSCHEMA name specified in the GLOBALS file does not exist in the database, or the user does not have permission to use it.

Action: Create the GGSCHEMA in the database with proper permissions for the Oracle GoldenGate database user.

OGG-25169: {0}
Cause: The specified database error occurred.

Action: Follow the directions in the error message to resolve the problem, or contact Oracle Support.

OGG-25170: The following OGG CDC object(s) is missing for table {0}: {1}. Run ADD TRANDATA for table {0} to re-enable supplemental logging.
Cause: The process could not find the required Oracle GoldenGate objects in the current database.

Action: Ensure that the Oracle GoldenGate required local object(s) exist in the database for the given table. If objects are missing, then use ADD TRANDATA for the table to create the Oracle GoldenGate objects.

OGG-25188: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE specified connecting to unsupported database version. Option will be ignored.
Cause: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE was specified while connecting to database version other than DB2 V11.

Action: Remove TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE.

OGG-25189: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE used against V11R1 or above is not needed. Option will be ignored.
Cause: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE was specified while connecting to a database version DB2 V11 or above.

Action: Remove TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE.

OGG-25190: Stored procedures required for log reading, OGGINITB and OGGREADB, not found and TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE is in effect.
Cause: DB2 V11 versions of stored procedures, OGGINITB and OGGREADB, required for log reading are not found and TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE is in effect.

Action: Ensure that DB2 V11 versions of stored procedures, OGGINITB and OGGREADB, are correctly installed or remove TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE.

OGG-25191: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE is in effect but stored procedures, OGGINITB and OGGREADB, required for log reading are not compatible with connected database.<
Cause: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE is in effect, but the DB2 V11 versions of the stored procedures, OGGINITB and OGGREADB, are not compatible with the connected database.

Action: Remove TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE and ensure that the DB2 V10 versions of the stored procedures, OGGINITA and OGGREADA, are installed..