【ogg 】Error Messages（OGG-08001 to OGG-10545）

OGG-08001: Could not retrieve error detail after failed to allocate OCI error handle. OCI status: {0}.
Cause: Failed to create OCI environment by OCIEnvNslCreate() call.

Action: Review the OCI status code in the message and verify that the Oracle Database is properly configured.

OGG-08002: Could not allocate OCI error handle. OCI status: {0}.
Cause: Failed to allocate OCI error handle.

Action: Review the OCI status code in the message and verify that the Oracle Database is properly configured.

OGG-08003: OCI error handle was successfully allocated with the informational message. OCI return code: {0}, Description: {1}.
Cause: OCI error handle was allocated, but OCI returns an informational message.

Action: None

OGG-08004: OCI operation failed. OCI Error Code: {0}, Error Detail: {1}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08005: OCI SQL operation failed. OCI Error Code: {0}, Error Detail: {1}, SQL: {2}.
Cause: An error occurred in the OCI while executing the SQL.

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

OGG-08006: Failed to retrieve OCI error detail. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08007: Failed to allocate the server context. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08008: Failed to allocate the service context. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08009: Failed to attach the remote server {1}. OCI status: {0}.
Cause: Could not attached to the remote server.

Action: Check if Oracle database configuration and the remote server is accessible.

OGG-08010: Failed to attach the server. OCI status: {0}.
Cause: Could not attached to the server.

Action: Ensure that the Oracle Database configuration and the server is accessible.

OGG-08011: Failed to set the server context attribute. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08012: Failed to set the external name {1} attribute. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08013: Failed to set the internal name {1} attribute. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08014: Failed to allocate the session context. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08015: Failed to set the user name {1} attribute. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08016: Failed to set the password attribute. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08017: A connect descriptor is required for connection creation.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08018: Module attribute was not set to the OCI session.
Cause: The OCI session module attribute was not set because the module name was not specified by the application.

Action: None

OGG-08019: Failed to allocate describe handle. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08020: Failed to retrieve OCI error detail on OCI session begin failure.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08021: Oracle password may be expired soon. Error code: {0}, Error Detail: {1}.
Cause: Oracle Database password for the user may be expired soon.

Action: This ignorable error may become critical in future when the password is expired. Update the password before it is expired.

OGG-08022: Failed to begin the OCI session. Error code: {0}, Error Detail: {1}.
Cause: Could not begin the OCI session.

Action: Check the error detail and fix the problem.

OGG-08023: Failed to set the OCI session attribute. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08024: Failed to end the OCI session. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08025: Failed to detach from the server. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08026: Failed to free the service context. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08027: Failed to free the session context. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08028: Failed to free the server context. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08029: Failed to free the describe handle. OCI status: {0}.
Cause: This is an internal OCI error.

Action: Contact Oracle Support.

OGG-08030: Username required for database connection.
Cause: A username was not supplied.

Action: Supply a password.

OGG-08031: Password required for database connection.
Cause: A password was not supplied.

Action: Supply a password.

OGG-08032: Invalid username specification for OS authentication.
Cause: The username for OS authentication was specified in an invalid format.

Action: Specify the username for OS authentication in the correct format. See the Oracle GoldenGate documentation.

OGG-08033: Fetched data size {0} exceeds requested storage size.
Cause: An attempt was made to store fetched data in storage of inadequate size.

Action: Use the correct storage type for the fetched data.

OGG-08034: An attempt was made to store database type {0} as an integer.
Cause: An attempt was made to store fetched data as an invalid type.

Action: Use the correct storage type for the fetched data.

OGG-08035: The database connection has begun failover.
Cause: Transparent Application Failover (TAF) has initiated a reconnect.

Action: None

OGG-08036: The database connection failover has completed.
Cause: Transparent Application Failover (TAF) has completed a reconnect.

Action: None

OGG-08037: The database connection failover is being retried because of an error.
Cause: Transparent Application Failover (TAF) was unable to reconnect. The reconnect is being retried.

Action: None

OGG-08038: The database connection failover has been aborted.
Cause: Transparent Application Failover (TAF) reconnect was aborted.

Action: Restart the application.

OGG-08039: Mixing bind by position and bind by name is unsupported.
Cause: An application attempted to bind by one column by position and one column by name.

Action: Do not mix bind methods.

OGG-08040: Statement has not been prepared before executing.
Cause: An application attempted to execute a statement before is has been prepared.

Action: Prepare the statement before execution.

OGG-08041: Requested column result index {0} exceeds total fetched results {1}.
Cause: An application attempted to obtain results beyond total fetched.

Action: Do not retrieve fetch results beyond total returned.

OGG-08042: Invalid operation for a connection to a non-container database.
Cause: An application attempted to execute a container specific operation on a non-container connection.

Action: Do not attempt this operation on a non-container connection.

OGG-08043: Requested connection character set {0} is invalid.
Cause: An application requested to create a connection with an invalid character set.

Action: Specify a valid character set.

OGG-08044: Requested connection national character set {0} is invalid.
Cause: An application requested to create a connection with an invalid national character set.

Action: Specify a valid national character set.

OGG-08045: Invalid column conversion request for column type {0}.
Cause: An attempt was made to retrieve a column value into an incompatible type.

Action: Retrieve the column as a compatible type.

OGG-08046: External authentication is unsupported for connections retrieved through a session pool.
Cause: An application attempted create a connection using a session pool with unsupported external authentication.

Action: Do not use external authentication for connection credentials.

OGG-08047: Session pool destroy failed with error {0}.
Cause: An attempt to destroy a session pool failed with the reported error.

Action: Correct the error reported.

OGG-08048: Failed to initialize time zone information. Check location of ORACLE_HOME.
Cause: Received ORA-01804 while trying to initialize OCI environment. Ensure that your ORACLE_HOME setting is valid.

Action: Correct the error reported.

OGG-08100: {0}
Cause: A generic information message was printed, check the message for more detail.

Action: None

OGG-08101: Invalid TARGETEXTTRAIL name.
Cause: The name of the trail file specified is not correct.

Action: Verify the correct usage of enclosing quotes.

OGG-08102: Invalid file name.
Cause: The name of the trail file specified is not correct.

Action: Verify the correct specification of path and trail filename.

OGG-08103: file portion must be two characters.
Cause: The name of the trail file specified is larger than two characters.

Action: Specify a filename consisting of only two characters.

OGG-08104: EXTRACT group does not exist.
Cause: The specified Extract group has not been added.

Action: Add the Extract group first or use an existing one.

OGG-08105: EXTRACT is running, cannot be altered.
Cause: The Extract process cannot be modified when running.

Action: Stop the Extract process first.

OGG-08106: Trails cannot be used with an EXTRACT task.
Cause: The specified Extract group is defined as a task process and do not use trail files.

Action: Alter the Extract group or add a new one.

OGG-08107: TARGETEXTTRAIL already exists.
Cause: The specified trail file was previously added.

Action: Specify a different trail file name.

OGG-08108: TARGETEXTTRAIL does not exist.
Cause: The specified trail file has not been added.

Action: Add the specified trail file.

OGG-08109: Unable to get current checkpoint data {0}.
Cause: There was an error retrieving the checkpoint information for the specified process.

Action: Verify that options like RBA and SEQNO are correctly specified. Otherwise, contact Oracle Support.

OGG-08110: Login failed. {0}
Cause: There was an error while logging into the database.

Action: Check credentials. Refer the printed message for more details.

OGG-08111: {1} is not a valid value for argument {0}, expected value {2}.
Cause: The value is not valid for reported argument.

Action: None

OGG-08112: Cannot {0} {1} - Legacy protocol disabled in the Oracle GoldenGate Admin Server
Cause: The configuration setting for the enableLegacyProtocol in the Oracle GoldenGate Admin Server is set to 'false'.

Action: Change the enableLegacyProtocol setting to 'true' to enable the legacy protocol.

OGG-08113: Cannot {0} {1} - Oracle GoldenGate Receiver Server is not running
Cause: The Oracle GoldenGate Receiver Server must be running for Admin Server to handle legacy requests for a Server Collector.

Action: Start the Oracle GoldenGate Receiver Server.

OGG-08114: Command '{0} {1}' is not supported by the Oracle GoldenGate Admin Server
Cause: The Oracle GoldenGate Admin Server does not recognize or support the specified command.

Action: Contact Oracle Support.

OGG-08115: The Task Manager is disabled in the Oracle GoldenGate Admin Server
Cause: The configuration setting for the enableTaskManager in the Oracle GoldenGate Admin Server is set to 'false'.

Action: Change the enableTaskManager setting to true to enable the Task Manager.

OGG-08116: Connections with names of the form 'domain.alias' are read-only
Cause: Connections with names of the form domain.alias are automatically created from credentials and are read-only.

Action: Remove the period from the connection name.

OGG-08117: PASSIVE/ALIAS Extract processes are not supported.
Cause: Oracle GoldenGate Services Edition does not support creation of passive Extract processes.

Action: Use the Oracle GoldenGate Distribution Server to specify a connection initiated by the Receiver Server.

OGG-08118: EXTRACT tasks cannot be registered.
Cause: Extract tasks cannot be registered with the database.

Action: Remove the registration option.

OGG-08119: Trails cannot be added for the specified group
Cause: The specified group is of a type that does not support adding trails.

Action: Specify a different group.

OGG-08120: No files found for specified trails.
Cause: Files do not exist for the trails specified.

Action: Ensure that the trail files are present on the system.

OGG-08200: {0} {1} does not exist.
Cause: The specified process does not exist.

Action: Check process type or process name.

OGG-08201: {0} {1} is RUNNING. Stop the process to execute this command.
Cause: The specified process is currently RUNNING. The command cannot be executed unless the process is STOPPED.

Action: Stop the process, and then issue the command.

OGG-08202: Could not delete file {0} ({1,number,0}, {2})
Cause: Moved from ggFragment.

Action: None

OGG-08203: Could not delete DB checkpoint for {0} {1} ({2})
Cause: Moved from ggFragment.

Action: None

OGG-08204: Deleted {0} {1}.
Cause: Moved from ggFragment.

Action: None

OGG-08209: ERROR: {0}.
Cause: Used by GGSCI to print into console, but by Admin Server to log elsewhere.

Action: None

OGG-08210: WARNING: {0}.
Cause: Used by GGSCI to print into console, but by Admin Server to log elsewhere.

Action: None

OGG-08211: {0}.
Cause: Cause is not known before hand, check error message for more detail.

Action: None

OGG-08216: ERROR: Cannot register or unregister EXTRACT {0} because no database login was provided. Use DBLOGIN to establish a connection.
Cause: Undefined

Action: Undefined

OGG-08217: A root container connection is required when registering or unregistering Extract for a container database.
Cause: Undefined

Action: Undefined

OGG-08218: A root container connection to the downstream database is required when registering or unregistering Extract on a container database.
Cause: Undefined

Action: Undefined

OGG-08219: The user must have common user privileges on the downstream database when registering or unregistering Extract on a container database.
Cause: Undefined

Action: Undefined

OGG-08220: The user must have common user privileges when registering or unregistering Extract for a container database.
Cause: Undefined

Action: Undefined

OGG-08221: Cannot register or unregister EXTRACT {0} because of the following SQL error: {1}.
Cause: Undefined

Action: Undefined

OGG-08222: EXTRACT {0} must be registered with the database to perform this operation.
Cause: Undefined

Action: Undefined

OGG-08223: ERROR: One or more containers must be specified when registering Extract for a container database.
Cause: Undefined

Action: Undefined

OGG-08224: ERROR: CONTAINER option was specified though the database does not support containers.
Cause: Undefined

Action: Undefined

OGG-08225: Extract {0} successfully registered containers with database at SCN {1}.
Cause: Undefined

Action: Undefined

OGG-08226: Extract {0} successfully dropped containers from database.
Cause: Undefined

Action: Undefined

OGG-08227: Container list contains too many containers.
Cause: Undefined

Action: Undefined

OGG-08228: Invalid container name {0}.
Cause: Undefined

Action: Undefined

OGG-08229: ERROR: Database container {0} is not registered.
Cause: Undefined

Action: Undefined

OGG-08230: ERROR: The global name of database container {0} could not be retrieved. Ensure the container is not in restricted mode.
Cause: Undefined

Action: Undefined

OGG-08231: ERROR: Drop container for EXTRACT {0} is already in progress; wait then try again.
Cause: Undefined

Action: Undefined

OGG-08232: ERROR: Database container {0} has already been registered.
Cause: Undefined

Action: Undefined

OGG-08233: ERROR: The global name of the database container {0} is in restricted mode.
Cause: Undefined

Action: Undefined

OGG-08234: ERROR: Database container {0} does not exist.
Cause: Undefined

Action: Undefined

OGG-08235: ERROR: Database container {0} is not open.
Cause: Undefined

Action: Undefined

OGG-08236: Wildcard is not allowed in container name {0}.
Cause: Undefined

Action: Undefined

OGG-08237: ERROR: This EXTRACT {0} cannot be used as a SHARE candidate. Use SHARE AUTOMATIC for finding a valid share candidate.
Cause: Undefined

Action: Undefined

OGG-08238: ERROR: This database does not have the required patch to support a SHARE clause. Remove the SHARE clause.
Cause: Undefined

Action: Undefined

OGG-08239: ERROR: Downstream Integrated Extract requires SCN clause in conjunction with the SHARE clause. See REGISTER with the SHARE clause in the Oracle GoldenGate documentation.
Cause: Undefined

Action: Undefined

OGG-08240: ERROR: The SHARE clause is not supported when registering Extract for a container database.
Cause: Undefined

Action: Undefined

OGG-08241: ERROR: This EXTRACT {0} is already registered with the database.
Cause: Undefined

Action: Undefined

OGG-08242: ERROR: The Logmining server failed to locate dictionary for PDB {0}.
Cause: Undefined

Action: Undefined

OGG-08243: WARNING: EXTRACT {0} failed to archive the current logfile on the source database because of the following SQL error: {1}. See Extract user privileges in the Oracle GoldenGate documentation.
Cause: Undefined

Action: Undefined

OGG-08244: Root container {0} can not be specified in any REGISTER CONTAINER command because it is automatically registered.
Cause: Undefined

Action: Undefined

OGG-08245: Container {0} was specified more than once in the container list.
Cause: Undefined

Action: Undefined

OGG-08246: Wrong syntax.
Cause: Undefined

Action: Undefined

OGG-08247: Cannot unregister REPLICAT {0} because no database login was provided. Use DBLOGIN to establish a connection.
Cause: An UNREGISTER REPLICAT command was issued without first issuing a DBLOGIN command.

Action: Issue the DBLOGIN command, and then issue UNREGISTER REPLICAT again.

OGG-08248: ERROR: One or more containers or patterns specified do not match any containers in the database.
Cause: Undefined

Action: Undefined

OGG-08250: {0} is not allowed for {1} {2}
Cause: A command was issued with an invalid option for the given mode.

Action: Use a valid option for the given mode.

OGG-08251: This command is being forced
Cause: A command was issued with the bang (!) option. You are not be prompted for confirmation.

Action: None

OGG-08252: ERROR: Wildcard not allowed for this command.
Cause: Undefined

Action: Undefined

OGG-08253: ERROR: Invalid command.
Cause: Undefined

Action: Undefined

OGG-08254: Could not delete file {0} ({1,number,0}, {2})
Cause: Undefined

Action: Undefined

OGG-08255: {0} {1} not currently running.
Cause: A process that is not currently running was tried to be stopped.

Action: None

OGG-08256: {0} {1} is initializing, please try the command later.
Cause: A command for a process that is in an initialization stage was tried to be executed.

Action: Retry the command later.

OGG-08257: 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-08258: Data source is required for {0} {1}.
Cause: No data source was specified.

Action: Specify a data source.

OGG-08259: Specified data source is not known.
Cause: An unsupported data source was detected.

Action: Specify a supported data source.

OGG-08260: Apply mode is required for {0} REPLICAT.
Cause: No apply mode was specified.

Action: Specify an apply mode.

OGG-08261: Specified apply mode is not known.
Cause: An unsupported apply mode was detected.

Action: Specify a supported apply mode.

OGG-08262: EXTFILE or EXTTRAIL required for ADD REPLICAT.
Cause: No valid data source was specified.

Action: Specify either EXTTRAIL or EXTFILE.

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

Action: Contact Oracle Support.

OGG-08264: Berkeley DB Repository Version Mismatch Error
Cause: The Berkeley DB Version used by the repository does not match the dirbdb files.

Action: Delete and recreate the data store.

OGG-08265: ERROR: Database container {0} is unsupported
Cause: The specified container is unsupported.

Action: Remove the unsupported container name from the requested container list.

OGG-08266: Using trail named '{1}' instead of requested name '{0}'.
Cause: Trail file name and path specifications are not case-sensitive.

Action: None

OGG-08270: {0} option is not supported for register command with the current release
Cause: The specified feature is not supported by current Oracle GoldenGate release.

Action: This will be handled internally.

OGG-08271: The '{0}' operation is not available for trace tables.
Cause: The specified operation does not apply to trace tables.

Action: Do not use the specified operation for trace tables.

OGG-08272: Trail file '{0}' already exists.
Cause: The specified trail file was found in the local filesystem.

Action: Purge old trail files prior to starting the Extract process.

OGG-08273: {0} {1} does not exist.
Cause: The specified process does not exist.

Action: Check process type or process name.

OGG-08276: Auto-restart rule '{0}' has been added.
Cause: Informational only.

Action: None

OGG-08277: Auto-restart rule '{0}' has been updated.
Cause: Informational only.

Action: None

OGG-08278: Auto-restart rule '{0}' has been deleted.
Cause: Informational only.

Action: None

OGG-08500: {0}
Cause: A generic information message was printed, check the message for more detail.

Action: None

OGG-08501: Requested Operation on path {0} failed
Cause: The operation on the specified path failed.

Action: Check the syntax of the path specification in the service request.

OGG-08502: Path {0} not found
Cause: A path specified in the service request cannot be found in the system.

Action: Verify the path name in the service request.

OGG-08503: Path {0} already exists
Cause: The specified path name already exists in the system.

Action: Use a different path name or verify the path name in the service request.

OGG-08504: DistSrvr Shared Context is not initialized
Cause: The shared context for Distribution Server cannot be initialized.

Action: Contact Oracle Support.

OGG-08505: DistSrvr TPC {0} is not valid
Cause: The TPC thread for a distribution path cannot be started with invalid command context.

Action: Contact Oracle Support.

OGG-08506: DistSrvr failed to add path {0}
Cause: The Distribution Server failed to add the specified path to the system.

Action: Contact Oracle Support.

OGG-08507: Target path {0}, is prefixed by an unsuported protocol
Cause: Protocol specified at the URL is not known to DistSrvr.

Action: Specify one of the following supported protocols: ogg, ogg2, ws

OGG-08508: The request for adding a distribution path '{0}' has been processed and the requested distribution path will be added asynchronously.
Cause: Informational only.

Action: None

OGG-08509: The begin time string {0} is invalid.
Cause: The begin time value specified is invalid.

Action: Specify a valid ISO8601 formatted time string for the begin time.

OGG-08510: The path specification contains invalid property: {0}.
Cause: The given path specification in the service request is invalid.

Action: Check the syntax of the path specification in the service request.

OGG-08511: The path '{0}' has been added.
Cause: Informational only.

Action: None

OGG-08512: The path '{0}' has been updated.
Cause: Informational only.

Action: None

OGG-08513: The path '{0}' has been started.
Cause: Informational only.

Action: None

OGG-08514: The path '{0}' has been stopped.
Cause: Informational only.

Action: None

OGG-08515: The path '{0}' has been killed.
Cause: Informational only.

Action: None

OGG-08516: The path '{0}' has been deleted.
Cause: Informational only.

Action: None

OGG-08517: The operation for path '{0}' timed out.
Cause: Distribution Server timed out waiting for the request to be completed.

Action: Query the status of the path and retry the request if necessary.

OGG-08518: Request on path {0} failed, which is caused by '{1}'.
Cause: The operation on this path failed with the specified cause.

Action: Review the cause and correct the issues before retry.

OGG-08519: The path '{0}' is already started.
Cause: Informational only.

Action: None

OGG-08520: The path '{0}' is already stopped.
Cause: Informational only.

Action: None

OGG-08521: The path '{0}' is already killed.
Cause: Informational only.

Action: None

OGG-08522: Invalid command context.
Cause: The distribution path command context contains an invalid internal state and cannot complete the operation.

Action: Contact Oracle Support.

OGG-08523: The path '{0}' has been suspended.
Cause: Informational only.

Action: None

OGG-08524: The path '{0}' is already in the process of stopping.
Cause: Informational only.

Action: None

OGG-08525: The network connection could not be established.
Cause: The connection between the Distribution Server and the Receiver Server or the Manager could not be established. This can be due to a network problem or an error in the setup.

Action: Verify the URI provided for the Distribution Path. Check that the Receiver Server or the Manager is running and listening on the expected port.

OGG-08526: The specified encryption algorithm '{0}' is not suported for trail encryption. Only AES is supported.
Cause: The specified encryption algorithm is not supported.

Action: Change the encryption algorithm. Currently only AES128, AES192, and AES256 algorithms are supported.

OGG-08527: The AES library was loaded.
Cause: Informational only.

Action: None

OGG-08528: The AES library could not be loaded.
Cause: The AES library could not be loaded.

Action: Contact Oracle Support.

OGG-08529: Invalid command received for path '{0}'.
Cause: An internal error occurred.

Action: Contact Oracle Support.

OGG-08530: Path '{0}' could not be reloaded.
Cause: An error occurred while trying to reload an existing path.

Action: Look the logs to see which error could have caused the issue and contact Oracle Support.

OGG-08531: A problem occurred while reloading existing paths.
Cause: An error occurred while trying to reload an existing path.

Action: Look the logs to see which error could have caused the issue and contact Oracle Support.

OGG-08532: A problem occurred while getting the list of the existing path names.
Cause: An error occurred while trying to get the list of the existing path names.

Action: Look the logs to see which error could have caused the issue and contact Oracle Support.

OGG-08533: Handler returned unexpected status '{0}'.
Cause: An error occurred in one of the path handlers.

Action: Look the logs to see which error could have caused the issue and contact Oracle Support.

OGG-08534: The path name '{0}' cannot be modified to '{1}'.
Cause: A distribution path name cannot be modified.

Action: A distribution path name cannot be modified.

OGG-08535: Failed to initialize the data source for path {0}
Cause: The path cannot be started due to a failure in initializing the data source for the distribution path.

Action: Look at the logs to see which error could have caused the issue and contact Oracle Support.

OGG-08536: Failed to initialize the data target for path {0}
Cause: The path cannot be started due to a failure in initializing the data target for the distribution path.

Action: Look at the logs to see which error could have caused the issue and contact Oracle Support.

OGG-08537: A PATCH operation that changes the target URI values other than the host and port is not allowed
Cause: The property specified cannot be changed with a PATCH operation.

Action: Correct the property from the PATCH request.

OGG-10000: The column data type '{0}' is not supported Oracle GoldenGate.
Cause: The specified data type is not supported by Oracle GoldenGate.

Action: Contact the Oracle GoldenGate administrator or Oracle Support.

OGG-10001: The wildcarded catalog specification is missing from the MAP parameter in the Extract parameter file.
Cause: The wildcarded catalog specification is missing from the MAP parameter in the Extract parameter file.

Action: Specify a wildcarded catalog in the MAP parameter.

OGG-10002: The wildcarded schema specification is missing from the MAP parameter in the Extract parameter file.
Cause: The wildcarded schema specification is missing from the MAP parameter in the Extract parameter file.

Action: Specify a wildcarded schema in the MAP parameter.

OGG-10003: The environment variable INFORMIXSERVER is not set.
Cause: The INFORMIXSERVER environment variable must be set to specify the Informix server.

Action: Set the INFORMIXSERVER variable to the correct Informix server.

OGG-10004: Unable to start capture for columns {1} of table "{0}". Verify whether ADD TRANDATA was issued.
Cause: Oracle GoldenGate is unable to capture transaction data for the specified table.

Action: Issue the ADD TRANDATA command for the specified table. If the problem persists, contact Oracle Support.

OGG-10005: Unable to activate CDC session with session id '{0}'.
Cause: The process could not start a CDC session.

Action: Check if the session id value is greater than 0. This indicates that the CDC session was not opened successfully. Contact Oracle Support.

OGG-10006: Unable to reposition CDC session with session id '{0}'.
Cause: The process could not reposition the CDC session.

Action: Check if the session ID value is greater than 0. This indicates that the CDC session was not opened successfully. Contact Oracle Support.

OGG-10007: Unable to allocate '{0}' bytes of heap memory.
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-10009: The CDC reader reached the end of the current CDC record.
Cause: The CDC reader reached the end of the current CDC record.

Action: None

OGG-10010: The CDC session timed out. Start CDC with no timeout value.
Cause: The CDC session being read by the CDC reader timed out.

Action: Check the timeout value used when starting the CDC session. The CDC session must be started with no timeout.

OGG-10011: Unable to read the transaction user name for user id '{0}'. Defaulting to username 'informix.'
Cause: The process is using the default user name of 'Informix' because it could not read the transaction user name for the specified user id.

Action: Check for possible corruption in the /etc/passwd entry for the respective user id.

OGG-10012: Unable to end capture session for the table "{0}".
Cause: The process could not end its capture session for the specified table.

Action: None. This will be handled internally.

OGG-10013: Unable to close CDC session with session id '{0}'.
Cause: The process could not close its CDC session.

Action: None. This will be handled internally.

OGG-10014: Resolution column {2} is not part of column group used in conflict resolution {0}:{1}
Cause: The Resolution column is not part of the apply columns list.

Action: Modify the parameter file to include the resolution column in the apply column list.

OGG-10015: The specified decimal column has an unknown scale and cannot be processed. Table: {0} Column: "{1}".
Cause: The specified decimal column has an unknown scale and cannot be processed.

Action: Recreate or alter the decimal column with a fixed value of scale.

OGG-10016: The specified decimal column has an unknown scale and cannot be processed. Table: {0} Column: "{1}".
Cause: The specified decimal column has an unknown scale and cannot be processed.

Action: Recreate or alter the decimal column with a fixed value of scale.

OGG-10017: The interval column with a length {3} digits will be truncated to {4} digits. Table: {0} Column: {1} Data type: {2}
Cause: The interval column length is greater than the expected value.

Action: Recreate or alter the interval column to a smaller length. See the Oracle GoldenGate reference documentation for more details.

OGG-10018: Metadata property {0} is missing. The default value of {1} is used.
Cause: A value for the specified metadata property is missing.

Action: The upgrade of the Oracle GoldenGate software was not performed correctly. See the Oracle GoldenGate upgrade instructions and the release notes for more details.

OGG-10019: BOUNDED RECOVERY: BR not being used for restore. Extract will revert to normal recovery for this recovery and then turn on Bounded Recovery again.
Cause: Extract was unable to recover from the last Bounded Recovery checkpoint.

Action: Examine the Extract report file for messages related to the bounded recovery failure and then contact Oracle Support. Report any failure of a bounded recovery to Oracle, even if Extract fully recovers.

OGG-10020: DDL statement succeeded with the following message: {0}.
Cause: The DDL statement succeeded. This message is informational and does not indicate a problem.

Action: None

OGG-10021: The locale of at least one source database does not match the locale of the other databases.
Cause: At least one of the source databases in this configuration has a locale that is different from the locale of the other databases in this configuration.

Action: Stop Extract and set all of the source databases in this configuration to the same locale. To prevent loss of data, re-synchronize the affected data.

OGG-10022: Unable to start capture for {1} columns of table "{0}". Verify whether at least a non-LOB column is in the table.
Cause: Oracle GoldenGate is unable to capture transaction data for the specified table. LOB columns are not supported as a key by Oracle GoldenGate.

Action: Include at least one non-LOB column in the table and then run ADD TRANDATA. For column types that are supported as a key, see the Oracle GoldenGate documentation for your database. If the problem persists, contact Oracle Support.

OGG-10023: Unable to activate a CDC session because none of the tables have at least a non-LOB column.
Cause: Oracle GoldenGate is unable to capture transaction data for the specified table. LOB columns are not supported as a key by Oracle GoldenGate.

Action: Include at least one non-LOB column in the table and then run ADD TRANDATA. For column types that are supported as a key, see the Oracle GoldenGate documentation for your database. If the problem persists, contact Oracle Support.

OGG-10024: CREATE/ALTER TABLE statements with encrypted columns that use IDENTIFIED clause are not supported. The DDL statement is ignored: {0}.
Cause: IDENTIFIED clause in encrypted columns is supported only in triggerless Extract.

Action: Remove IDENTIFIED clause.

OGG-10025: Oracle GoldenGate is incompatible with the current Informix Server version {0}. The supported Informix Server versions are {1}.
Cause: Oracle GoldenGate is incompatible with the current Informix Server version.

Action: Make sure you install a compatible Informix Server version.

OGG-10026: CDC error record received with {0}.
Cause: Oracle GoldenGate capture received a CDC record error and so cannot continue.

Action: Refer to the Informix documentation to resolve the error based on the error message, and then restart the capture process.

OGG-10027: An invisible column was encountered in table {0}. Oracle GoldenGate support for invisible columns requires Integrated Capture mode and trail format RELEASE 12.2 or later.
Cause: Invisible columns are supported in Integrated Capture mode only and require trail format RELEASE 12.2 or later.

Action: Exclude the table from the Extract parameter file by using the TABLEEXCLUDE parameter.

OGG-10028: The DELETE TRANDATA command failed for the specified table, error [{1}], operation [{0}]
Cause: The DELETE TRANDATA command failed.

Action: None. This will be handled internally.

OGG-10029: SHOWSYNTAX cannot be used with DBOPTIONS(SKIPTEMPLOB). DBOPTIONS(SKIPTEMPLOB) is disabled.
Cause: The parameter file contains the SHOWSYNTAX parameter, which is not compatible with the DBOPTIONS(SKIPTEMPLOB) parameter. DBOPTIONS(SKIPTEMPLOB) is disabled.

Action: Remove SHOWSYNTAX to use DBOPTIONS(SKIPTEMPLOB) or remove the DBOPTIONS(SKIPTEMPLOB) parameter to use SHOWSYNTAX.

OGG-10030: The bulk load process encountered unsupported data type {1}-{0} in column "{2}".
Cause: The specified data type is not supported by the BULKLOAD initial load method.

Action: Reconfigure Oracle GoldenGate to use a load method that supports the specified data type, or remove the table that contains this data type from the initial load configuration.

OGG-10031: Setting current Edition for DDL operation to [{0}].
Cause: The process is setting the session Edition for the DDL operation. This is an informational message.

Action: None

OGG-10032: Transaction {0} not found. The record at RBA {1} was ignored.
Cause: Extract ignored the record because it could not find the start of the transaction.

Action: Reposition Extract to start capture before the start of the transaction. For more information, see the START EXTRACT command.

OGG-10033: The catalog name is missing in the stored procedure {0}.
Cause: The catalog name is missing in the stored procedure.

Action: Provide the catalog name of the stored procedure to be executed and restart the process.

OGG-10034: The following database error has occurred. {0}.
Cause: A database error has occurred.

Action: Refer to the IBM Informix documentation to correct the database error.

OGG-10035: Error when parsing Informix Server version {0} .
Cause: Error when parsing Informix Server version.

Action: Refer to Oracle GoldenGate Installing and Configuring Oracle GoldenGate for Informix for supported Informix versions.

OGG-10036: The SYSCDC functions required for Oracle GoldenGate capture are not installed in the current database.
Cause: The SYSCDC functions required for Oracle GoldenGate capture are not installed in the current database.

Action: Check the ODBC data source configuration. The Database field should point to the CDC database. If the CDC database is not created, run the SQL script $INFORMIXDIR/etc/syscdcv1.sql as informix user and rerun the capture process.

OGG-10037: A capture process was unable to open a new CDC session due to the error {0}.
Cause: A capture process was unable to open a new CDC session.

Action: Refer to the IBM Informix documentation to correct the CDC error.

OGG-10038: 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-10039: Invalid input for VAM PARAMS {0} in the capture parameter file.
Cause: Invalid input for VAM PARAMS in the extract parameter file.

Action: Refer to the Oracle GoldenGate reference.

OGG-10040: Capture process cannot handle CDC record type {0}.
Cause: Capture process cannot handle CDC record type.

Action: Refer to the Oracle GoldenGate reference.

OGG-10041: CDC session is still valid and the error received {0} can be ignored.
Cause: Oracle GoldenGate capture received a CDC error code which is informational and could be ignored.

Action: None

OGG-10042: Use of your Informix server's current logical log file {0} exceeds the warning threshold of {1}%. Oracle GoldenGate capture is currently positioned at logical log file {2}, indicating a capture lag. Your Informix server may overwrite or archive log file {2} before the capture finishes processing it. Take action to prevent data loss.
Cause: The use of the current logical log file exceeds the warning threshold, but the Oracle GoldenGate capture is positioned at an older log file. This difference indicates a critical capture lag, because the current log could be overwritten or archived before the capture process is able to process it.

Action: If your Informix server overwrites the logical log that the Oracle GoldenGate capture process is reading, then the Oracle GoldenGate capture would fail. Review the following options to prevent the error: 1) If possible, add a new logical log file. 2) If possible, stop any operations on the Informix server, except read-only operations, until this warning message is no longer displayed.. 3) If possible, make the Informix instance read-only using the onmode -c blockcommand. The Informix instance can be unblocked with the onmode -c unblock command. Refer to the Informix documentation before using these commands.

OGG-10100: Invalid read of parameter {0} from definitions file.
Cause: Problem reading from the static repository file for parameter definitions

Action: Contact Oracle Support.

OGG-10101: Incompatible parameter file version {0} for current running version {1}.
Cause: An incompatible version of the parameter repository file is being used.

Action: Contact Oracle Support.

OGG-10102: Error loading parameter with ID# {0} from the repository file.
Cause: Problem reading from the static repository file for parameter definitions

Action: Contact Oracle Support.

OGG-10103: ({0}) line {1}: Parsing error, value "{2}" is out of legal range ({3}) for [{4}].
Cause: Specified parameter value is out of the legal range for that value.

Action: Refer to the Oracle GoldenGate reference for the valid range.

OGG-10104: ({0}) line {1}: Parsing error, value "{2}" is not a valid argument for "{3}".
Cause: Specified value is not valid.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10105: ({0}) line {1}: Parsing error, parameter [{2}] is expected to immediately precede [{3}].
Cause: Specified parameter needs to be specified immediately after another.

Action: Refer to the Oracle GoldenGate reference for the proper specification.

OGG-10106: ({0}) line {1}: Parsing error, parameter [{2}] is expected to precede [{3}].
Cause: Specified parameter needs to be specified after another.

Action: Refer to the Oracle GoldenGate reference or the proper specification.

OGG-10107: ({0}) line {1}: Parsing error, parameter [{2}] conflicts with parameter [{3}].
Cause: Specified parameter cannot be specified with another.

Action: Refer to tthe Oracle GoldenGate reference for the proper specification.

OGG-10108: ({0}) line {1}: Parsing error, parsing encountered an error.
Cause: Issue found while parsing the parameter files.

Action: Contact Oracle Support.

OGG-10109: ({0}) line {1}: Parsing error, parameter with name "{2}" is not defined.
Cause: Referring to a parameter name that has not been defined.

Action: Use the correct name or define the name prior to usage.

OGG-10110: An unexpected error occurred while parsing parameter information.
Cause: An unexpected internal error occurred.

Action: Contact Oracle Support.

OGG-10111: Error opening parameter definition file: {0}. errno: {1,number,0} - {2}
Cause: Problem opening from the static repository file for parameter definitions.

Action: Check the error code to solve the problem. Contact Oracle Support.

OGG-10112: {0} cannot be used with {1}
Cause: The specified parameters are incompatible or mutually exclusive.

Action: Remove one of the parameters, depending on the required Oracle GoldenGate configuration. For help, see the Oracle GoldenGate reference documentation.

OGG-10113: Error creating Parallel Replicat recovery table
Cause: There was an error when Parallel Replicat tried to create its recovery table.

Action: Fix any associated SQL errors and restart Replicat.

OGG-10114: Error reading Parallel Replicat recovery table: {0}
Cause: There was an error when Parallel Replicat tried to read from its recovery table.

Action: Fix the error specified in the message and restart Replicat.

OGG-10115: Error cleaning up Parallel Replicat recovery table
Cause: There was an error when Parallel Replicat tried to cleanup its recovery table.

Action: Fix any associated SQL errors and restart Replicat.

OGG-10116: Parallel Replicat is not supported on this platform
Cause: Parallel Replicat is not supported on this platform.

Action: Drop the Replicat and create a new one that is not a Parallel Replicat.

OGG-10117: Wildcard name "{0}" not supported for TARGETCATALOG parameter
Cause: The parameter file contains a TARGETCATALOG parameter specifying a wildcard name.

Action: Change the parameter to specify a non-wildcard name.

OGG-10118: Missing catalog name in TARGETCATALOG specification
Cause: The parameter file contains a TARGETCATALOG specification that does not specify a catalog name.

Action: Add a catalog name to the TARGETCATALOG specification.

OGG-10119: Invalid catalog name in TARGETCATALOG specification: "{0}"
Cause: The parameter file contains a TARGETCATALOG specification that specifies an invalid catalog name.

Action: Specify a valid catalog name for the TARGETCATALOG parameter.

OGG-10120: Use of a default catalog is not supported for Parallel Replicats when applying to multiple target catalogs without a common user login.
Cause: The parameter file contains a MAP with a target table name that does not specify a catalog name. This is not supported for a Parallel Replicat when it is applying to multiple target catalogs unless the login specified is for a common user.

Action: Add a TARGETCATALOG specification for the MAP statement, specify the catalog in the MAP statement, or change the USERID parameter to specify a common user.

OGG-10121: Value not specified for NUM_MAPPERS
Cause: The parameter file contains the NUM_MAPPERS parameter without a value specified.

Action: Specify a value for the NUM_MAPPERS parameter.

OGG-10122: Value not specified for NUM_APPLIERS
Cause: The parameter file contains the NUM_APPLIERS parameter without a value specified.

Action: Specify a value for the NUM_APPLIERS parameter.

OGG-10123: Parallelism greater than 1 is not supported in Standard Edition of Oracle.
Cause: Standard Edition of Oracle only supports a parallelism set to 1.

Action: Set parallelism to 1 or use the Enterprise Edition.

OGG-10124: ({0}) line {1}: Parsing error, value "{2}" is not one of the legal values {3} for [{4}].
Cause: A specified value does match any value in the accepted list of valid strings.

Action: Refer to the Oracle GoldenGate reference.

OGG-10125: ({0}): Required parameter [{1}] is missing.
Cause: A parameter is required but has not been specified.

Action: Refer to the Oracle GoldenGate referenc for the proper specification and include the required parameter.

OGG-10126: The GLOBALS file is missing.
Cause: The GLOBALS file is missing.

Action: See the Oracle GoldenGate reference.

OGG-10127: ({0}) line {1}: Parsing error, required parameter option [{2}] is missing.
Cause: A parameter option is required though has not been specified.

Action: See the Oracle GoldenGate reference.

OGG-10128: Timestamp {0,date} {0,time} is not found within LRI range {1}.{2} - {3}.{4}.
Cause: The provided timestamp to the position in the log does not fall within the provided LRI range.

Action: Extract abends.

OGG-10129: LOOK UP END LRI can not be processed without a LOOK UP BEGIN LRI.
Cause: Only an LOOK UP END LRI was provided and LOOK UP BEGIN LRI is required.

Action: None

OGG-10130: Multiple logins were specified for the same catalog. Only the first will be used
Cause: The parameter file contains multiple logins that connect to the same catalog.

Action: Remove the unnecessary logins.

OGG-10131: A USERID parameter was specified after a MAP or TABLE parameter
Cause: The parameter file contains a USERID specification after a MAP or TABLE parameter. USERID must be specified before any MAP or TABLE parameters.

Action: Move the USERID specification so that it is before all MAP and TABLE parameters.

OGG-10132: No login was specified for catalog {0}
Cause: The parameter file contains a catalog for which it does not specify a login.

Action: Specify a login for the catalog using the USERID parameter.

OGG-10133: Default target catalog name {0} will be used for target table name {1} mapping.
Cause: A default target catalog name is specified with the TARGETCATALOG parameter and will be used when mapping the specified target table.

Action: None

OGG-10134: Ignoring TARGETCATALOG parameter {0} specified for MAP parameter '{1}' which contains a catalog specification.
Cause: The MAP clause already specifies a catalog name for the specified target table.

Action: Remove the TARGETCATALOG parameter or remove the catalog name from the target table name.

OGG-10135: Parallel Replicat requires a CHECKPOINTTABLE with a catalog name when applying to multiple target catalogs.
Cause: The parameter file specifies multiple target catalogs, but Replicat's CHECKPOINTTABLE does not have a catalog name specified.

Action: Modify the parameter file so that there is only one target catalog, or recreate the Replicat with a CHECKPOINTTABLE that has a catalog name.

OGG-10136: Replicat encountered an error and was unable to update the CHECKPOINTTABLE (Error: {0}).
Cause: Replicat encountered an error while updating the CHECKPOINTTABLE.

Action: Resolve the error shown in the message.

OGG-10137: Parallel Replicat does not support TARGET specifications containing wildcard catalogs.
Cause: The parameter file contains a MAP statement that specifies a wildcard catalog.

Action: Modify the parameter file so that there are no TARGET specifications containing wildcard catalogs.

OGG-10138: When Parallel Replicat is applying to multiple target catalogs, EVENTACTIONS options will only affect operations on the same target catalog.
Cause: The parameter file for a Parallel Replicat that is applying to multiple target catalogs contains an EVENTACTIONS specification.

Action: None

OGG-10139: Parameter file {0}: Validity check: {1}
Cause: The specified parameter file has been parsed and validated.

Action: If the validity check failed, check the syntax and values of the parameters.

OGG-10140: ({0}) line {1} column {2}: Parsing error, unexpected value "{3}".
Cause: Parameter parser encountered an unexpected value.

Action: Seethe Oracle GoldenGate reference for the proper specification.

OGG-10141: ({0}) line {1} column {2}: Parsing error, value "{3}" syntax error.
Cause: Parameter parser encountered a syntax error.

Action: See the Oracle GoldenGate reference for the proper specification.

OGG-10142: Attempt to load parameter [{0}] with ID# {1} failed. No parameter with that name matches the current running configuration.
Cause: Parameter parser could not load a specific parameter definition.

Action: Contact Oracle Support.

OGG-10143: ({0}) line {1}: Parameter [{2}] is unrecognized. No parameter definition with that name could be found.
Cause: Parameter parser could not find a specific parameter definition.

Action: See the Oracle GoldenGate reference.

OGG-10144: ({0}) line {1}: Parameter [{2}] is not valid for this configuration.
Cause: This parameter is not recognized for this running process.

Action: See the Oracle GoldenGate reference.

OGG-10145: ({0}) line {1}: Parsing error, parameter [{2}] is missing a required value.
Cause: This parameter is missing a required value.

Action: See the Oracle GoldenGate reference.

OGG-10146: Invalid algorithm: {0} Use AES128 AES192 AES256 or BLOWFISH.
Cause: Invalid encryption algorithm specified.

Action: Resolve the error shown in the message.

OGG-10147: ({0}) line {1}: Parsing error, parameter [{2}] cannot be specified multiple times.
Cause: This parameter cannot be specified more than once.

Action: See the Oracle GoldenGate reference.

OGG-10148: Original expression [{0}] -- Expanded expression [{1}]
Cause: Comparison of original parameter expression and expression after expansion.

Action: None

OGG-10149: ({0}) line {1}: Parsing error, option [{2}] for parameter [{3}] is missing a required value.
Cause: This option is missing a required value.

Action: See the Oracle GoldenGate reference.

OGG-10150: ({0}) line {1}: Parsing error, option [{2}] for parameter [{3}] cannot be specified multiple times.
Cause: This option cannot be specified more than once.

Action: See the Oracle GoldenGate reference.

OGG-10151: ({0}) line {1}: Parsing error, parameter [{3}] has unrecognized keyword or extra value "{2}".
Cause: Specified parameter value is not valid.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10152: ({0}) line {1}: Parsing error, option [{3}] for parameter [{4}] has unrecognized value "{2}".
Cause: Specified option value is not valid.

Action:Refer to the Oracle GoldenGate reference for the legal values.

OGG-10153: SHELL contains DDL argument {0} is not allowed for DML record.
Cause: The specification of @DDL() as SHELL argument is not allowed for DML records, since the information is not available.

Action: Verify that @DDL() argument for the SHELL expression is removed in the TABLE specification.

OGG-10154: Schema level PREPARECSN set to mode {1} on schema "{0}"
Cause: Schema-level PREPARECSN command has been processed on the ADD SCHEMATRANDATA command. Informational only.

Action: None

OGG-10155: Instantiation CSN filtering is enabled on table {0} at CSN {1}
Cause: Instantiation Filtering is enabled and the source table have an instantiation CSN set; Replication for this table will begin after the instantiation CSN

Action: None

OGG-10156: Ignoring Instantiation CSN for table {0} as a FILTER clause is specified on mapping configuration for table {0}.
Cause: Instantiation Filtering is enabled and the source table have instantiation information set. However the table already has a FILTER on CSN in the Replicat mapping configuration. Manual FILTER rules have precedence, so instantiation CSN is ignored for this table.

Action: None

OGG-10157: Disabling Instantiation filtering as source database global name cannot be resolved.
Cause: Instantiation Filtering is enabled, but the Source Database Global Name cannot be resolved.

Action: Use the DBOPTIONS SOURCE_DB_NAME REPLICAT option or a 12.2 trail format with source metadata information enabled.

OGG-10158: ({0}) line {1}: Parsing error, [{2}] is required to be specified on line {3}.
Cause: Specified parameter is required to be on a specific line.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10159: ({0}) line {1}: Parsing error, parameter [{2}] is missing a required unit value.
Cause: This parameter is missing a required unit value.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10160: ({0}) line {1}: Parsing error, option [{2}] for parameter [{3}] is missing a required unit value.
Cause: This option is missing a required unit value.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10161: Logical end of file reached on {0} at RBA {1,number,0}.
Cause: A logical end of file was reached while reading the trail file.

Action: None

OGG-10162: End of file reached on {0}.
Cause: The end of file was reached while reading the trail file.

Action: None

OGG-10163: An unexpected number of bytes were read from the last block in {0}. Expected {1}, read {2}.
Cause: While reading from the trail file, the number of bytes read was different than expected.

Action: None

OGG-10164: Trail file {0} has a logical file size.
Cause: The file size of the trail file is a logical file size. This file size can be lower than the physical file size.

Action: None

OGG-10165: The trail file {0} has found to be corrupt after RBA {1,number,0}.
Cause: The trail file has found to be corrupt. The file has been logically shortened in order to be used.

Action: None

OGG-10166: Source database name for instantiation filtering is set both in the Replicat parameter file and in the trail metadata for Table {0}. Value from the parameter file will take precedence: {1}
Cause: Source database name is set both in the Replicat configuration and in the trail file metadata.

Action: Remove the DBOPTIONS SOURCE_DB_NAME from the Replicat configuration, unless you want to override the Source Database Global Name.

OGG-10167: ({0}) line {1}: Parsing error, one of the following parameters or options [{2}] is expected to immediately precede [{3}].
Cause: Parameter or option needs to be specified immediately after one of the parameters or options in the shown list.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10168: ({0}) line {1}: Parsing error, one of the following parameters or options [{2}] is expected to precede [{3}].
Cause: Parameter or option needs to be specified after one of the parameters or options in the shown list.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10169: ({0}): Parsing error, one of the following parameters or options [{1}] is required to be used with [{2}].
Cause: One of the required parameters in the displayed list is missing.

Action:Refer to the Oracle GoldenGate reference for the legal values.

OGG-10170: ({0}): Parsing error, one of the following parameters [{1}] is required to be used in this file.
Cause: One of the required parameters in the displayed list is missing.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10171: ({0}) line {1}: Parsing error, parameters or options [{2}] conflict with parameter [{3}].
Cause: Specified parameters cannot be specified with one another.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10172: ({0}) line {1}: Parsing error, [{2}] requires at least one option to be used.
Cause: Specified parameter requires at least one option to be used.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10173: {0}
Cause: A parameter parsing error was detected, but can be ignored.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10174: ({0}): Fatal error in parser [{1}].
Cause: A fatal error was found while reading the parameter file.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10175: ({0}) line {1}: Parsing error, [{2}] is obsolete.
Cause: The specified parameter is obsolete and not valid for the current release of Oracle GoldenGate.

Action: Remove the parameter from the parameter file. Consult the current release notes and documentation for any newer parameters or enhanced functionality that is related to this parameter and for any required migration steps, or contact Oracle Support.

OGG-10176: ({0}) line {1}: Parsing error, [{2}] is deprecated.
Cause: The specified parameter is deprecated and not valid for the current release of Oracle GoldenGate.

Action: Remove the parameter from the parameter file. Consult the current release notes and documentation for any newer parameters or enhanced functionality that is related to this parameter and for any required migration steps, or contact Oracle Support.

OGG-10177: ({0}) line {1}: Parsing error, range "{2}" is invalid.
Cause: Specified range is not valid.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10178: Transactions containing table {0} are not scheduled in parallel due to missing columns in trail records. This prevents Replicat from applying transactions in parallel.
Cause: The trail records for the specified table do not contain all the columns required for Parallel Replicat to compute dependencies between transactions. This prevents Replicat from applying transactions in parallel.

Action: Ensure that all the required columns are supplementally logged in the source database and specify the LOGALLSUPCOLS in the primary Extract parameter file.

OGG-10180: Transactions containing table {0} cannot be scheduled in parallel because this table has an unique index on virtual columns. This prevents Replicat from applying transactions in parallel.
Cause: The specified table has at least one unique index defined on a virtual column, such as a functional-based index. This prevents Replicat from applying transactions in parallel.

Action: If possible, change all unique indexes on virtual columns to a non-unique index. Contact Oracle Support.

OGG-10181: All unique indexes on virtual columns of table {0} are ignored in scheduling transactions in parallel.
Cause: All unique indexes on virtual columns are ignored as specified by the DBOPTIONS parameter.

Action: None

OGG-10200: PLSQL operation found [{0}]
Cause: A PLSQL operation was processed. Informational only.

Action: None

OGG-10201: PLSQL operations [{0}] from [{1}] feature found and will not be logged individually. Check the statistics for details.
Cause: A high logging volume PLSQL operation was processed. Check the statistics for more details.

Action: None

OGG-10300: Could not capture the transaction record for table:"{0}" due to CDC error {1}. Verify whether ADD TRANDATA was issued.
Cause: Oracle GoldenGate is unable to capture transaction data for the specified table.

Action: Issue the ADD TRANDATA command for the specified table.

OGG-10301: The table "{0}" having column "{1}" with data type {2}:{3} is not supported by Oracle GoldenGate.
Cause: The specified column data type is not supported by Oracle GoldenGate.

Action: Refer to the Informix Oracle GoldenGate documentation for the data types supported by Oracle GoldenGate. Remove the table from Extract list or alter table for data capture.

OGG-10302: The column "{1}" in table "{0}" having data type {2}:{3} is ignored by CDC capture.
Cause: The specified column is ignored for CDC capture by Oracle GoldenGate.

Action: Refer to the Informix Oracle GoldenGate documentation for the columns ignored for CDC data capture. Verify whether this column is added into fetchcol list in Extract parameter file. Otherwise, data will not be captured for this column.

OGG-10303: Extract VAM PARAMS {0} specified is invalid and unsupported.
Cause: The parameter specified in Extract parameter file is invalid.

Action: Refer to the Oracle GoldenGate documentation for the list parameters supported in the Extract parameter file. Rectify or remove the parameter, if it is not supported.

OGG-10351: Generic error {0} noticed. Error description - {1}.
Cause: Undefined

Action: Undefined

OGG-10352: Could not complete the send operation.
Cause: The data channel contains an invalid internal state and cannot complete the send request. Previous errors were detected.

Action: Contact Oracle Support.

OGG-10353: Duplicate request to write trail {0} received. Ignoring new request.
Cause: The Receiver Server is already processing a trail with the same name as a new request.

Action: Change the target trail name for one of the conflicting Distribution Path.

OGG-10354: Stopping path writing trail {0} from {1} due to incoming primary request from {2} to write the same trail.
Cause: The Receiver Server received a higher priority request to write to a trail already being processed.

Action: Change the target trail name for one of the conflicting Distribution Path.

OGG-10356: The number of connections exceeded maximum allowed, {0, number, 0}.
Cause: The Receiver Server can only support a certain number of concurrent connections.

Action: Close some connections before trying again.

OGG-10357: The limitation of concurrent connections, set as {0, number, 0} exceeded the maximum allowed by the Operating System {1, number, 0}.
Cause: The maximum concurrent connection number has to be set to a value smaller than what the Operating System allowed.

Action: Specify a smaller number.

OGG-10358: The number of connections exceeded maximum allowed.
Cause: There can only be a certain number of concurrent connections, due to a limitation in the Operating System.

Action: Close some connections before trying again.

OGG-10359: Conflict detected, duplicate request for target trail file received.
Cause: The Receiver Server is already processing a trail with the same name as a new request.

Action: Change the target trail name for one of the conflicting Distribution Path.

OGG-10360: Conflict detected, duplicate request for target trail file received with 'haOverride' activated.
Cause: The Receiver Server is already processing a trail with the same name as a new request.

Action: Change the target trail name for one of the conflicting Distribution Path.

OGG-10361: Distsrvr expected a message from recvsrvr that was not received.
Cause: A probable cause is that the Receiver Server failed or was stopped.

Action: Try restarting the distribution path or both the Distribution Server and Receiver Server. If the problem persists, contact Oracle Support.

OGG-10362: A message was expected to complete the negotiation, but no message was received.
Cause: A probable cause is that the other end failed or was stopped.

Action: Try restarting the distribution path or both the Distribution Server and Receiver Server. If the problem persists, contact Oracle Support.

OGG-10363: Unable to create channel because the URI schema '{0}' is unrecognizable.
Cause: The URI schema for the Distribution Path was not recognized.

Action: Verify the URI provided for the Distribution Path.

OGG-10364: Incorrect port or port range specification {0}. This specification will be ignored.
Cause: Invalid syntax for a port or a range of ports found while processing the dynamicPortList property of the server configuration.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10365: Incorrect port or port range specification {0}. Error: {1}. This specification will be ignored.
Cause: Invalid syntax for a port or a range of ports found while processing the dynamicPortList property of the server configuration.

Action: Refer to the Oracle GoldenGate reference for the legal values.

OGG-10366: Ending port {0} must be greater than or equal to starting port {1}. This specification will be ignored.
Cause: The specified port number at the end of the port range in the dynamicPortList property of the server configuration is a lower value than the one at the beginning of the range.

Action: Edit the dynamicPortList property to specify a valid range that increases in value. Correct: 7830-7835 ; Incorrect: 7835-7830.

OGG-10367: Maximum number of dynamic ports ({0}) reached. Ignoring the rest of ports.
Cause: The specified number of ports the dynamicPortList property of the server configuration is greater than the maximum allowed.

Action: Edit the dynamicPortList property to specify a number of ports less than the maximum allowed.

OGG-10368: Error starting Server Application
Cause: There was an error starting the Server Application.

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

OGG-10369: Command '{0}' is not supported by Oracle GoldenGate Receiver Server
Cause: Oracle GoldenGate Receiver Server does not recognize or support the specified command.

Action: Contact Oracle Support.

OGG-10370: Error processing legacy Collector configuration parameters.
Cause: There was an error processing the legacy Collector configuration in Receiver Server.

Action: Verify that the configuration parameters were specified correctly in the Extract data pump parameter file.

OGG-10371: There was a problem loading the Receiver Server shared context. {0}
Cause: An internal error occurred when trying to load the shared context. Possible causes include a corrupted or incorrect resources file.

Action: Contact Oracle Support.

OGG-10372: Unexpected name pattern for path {0}.
Cause: An internal error occurred and an incorrect path name was generated in Receiver Server.

Action: Contact Oracle Support.

OGG-10373: Invalid socket value when receiving network data: {0}.
Cause: An internal error occurred and an incorrect socket file descriptor was generated when trying to receive data from the TCP layer. Possible causes include the communication channel being closed or the number of connections exceeding the maximum allowed.

Action: Look for problems with network connectivity between the source and target systems. Verify that the number of connections have not exceeded the operating system limitation. If you cannot resolve the problem, contact Oracle Support.

OGG-10374: Invalid null DMA buffer when flushing the data onto the network
Cause: A probable cause is that the remote process is stopped or killed.

Action: Ensure that the remote process is running. Contact your Network Administrator to rule out any other network issues before contacting Oracle Support.

OGG-10402: System-period and Bitemporal tables are not supported with 'INSERTALLRECORDS'
Cause: Replicat parameter file contains either of the temporal table parameters(SUPPRESSTEMPORALUPDATES/NOSUPPRESSTEMPORALUPDATES) along with INSERTALLRECORDS.

Action: Use only one of the parameters at a time.

OGG-10403: Column {1} of Table {0} is an auto generated column and is ignored.
Cause: The column is one among SYS_START, SYS_END, and TS_ID columns. These columns are auto filled by a database manager.

Action: Mark such columns as Unused and ignore them.

OGG-10451: DDL operation included [{0}], optype [{1}], objtype [{2}], catalog {5}, objowner {3}, objname {4}
Cause: The specified DDL operation was included in DDL Replication because it meets the criteria of an INCLUDE clause.

Action: None

OGG-10452: DDL operation excluded [{0}], optype [{1}], objtype [{2}], catalog {5}, objowner {3}, objname {4}
Cause: The specified DDL operation was excluded from DDL Replication because it meets the criteria of an EXCLUDE clause or was not included in an INCLUDE clause.

Action: None

OGG-10453: DDL operation excluded by user exit [{0}], optype [{1}], objtype [{2}], catalog {5}, objowner {3}, objname {4}
Cause: The specified user exit excluded the specified DDL. This is informational only.

Action: None

OGG-10454: DDL operation ignored due to EMI [{0}], optype [{1}], objtype [{2}], catalog {5}, objowner {3}, objname {4}
Cause: The specified DDL operation was ignored according to the rule specified in EVENTACTIONS.

Action: None required.

OGG-10455: DDL RENAME found, old owner "{0}" object "{1}", new owner "{2}" object "{3}", catalog {4}
Cause: A RENAME operation was processed. Informational only.

Action: None

OGG-10456: Metadata not invalidated for "{1}".{2} because of {0} [{3}], catalog {4}
Cause: Usually this message is for DDL operations that do not affect metadata, such as TRUNCATE TABLE or ANALYZE TABLE. This message explains why Extract did not clear the metadata (remove it from the DDL cache). It is beneficial not to clear metadata if possible: retaining it improves performance because the process does not need to re-read the metadata for the next DML operation.

Action: None

OGG-10457: DDL RENAME found, old owner "{0}" object "{1}", new owner "{2}" object "{3}", RENAME converted to ALTER TABLE, new operation [{4}], catalog {5}
Cause: A RENAME was converted to the equivalent ALTER TABLE RENAME. The reason is that RENAME does not support the use of a schema name, but a schema name is required in case the DDL statement on the target maps to a different schema.

Action: None

OGG-10458: Metadata not invalidated for "{1}".{2} because of {0}, catalog {3}
Cause: Usually this message is for DDL operations that do not affect metadata, such as TRUNCATE TABLE or ANALYZE TABLE. This message explains why Extract did not clear the metadata (remove it from the DDL cache). It is beneficial not to clear metadata if possible: retaining it improves performance because the process does not need to re-read the metadata for the next DML operation.

Action: None

OGG-10459: Invalid heartbeat object being added.
Cause: The heartbeat object being added is invalid.

Action: Contact Oracle Support.

OGG-10460: Failed to process operation on tombstone table {0}.
Cause: Extract process failed to process DML LCR on tombstone tables.

Action: Contact Oracle GoldenGate Support.

OGG-10461: Failed to retrieve tombstone timestamp value for table "{0}".
Cause: Extract process failed to retrieve tombstone timestamp information in order to generate a CDR token.

Action: Contact Oracle GoldenGate Support.

OGG-10462: Schema "{0}" have {1} prepared tables for instantiation
Cause: Schema contains tables which are prepared for instantiation CSN export. By default, all tables should be prepared.

Action: None

OGG-10463: Instantiation CSN has been set successfully.
Cause: GGSCI command SET_INSTANTIATION_CSN was successfully executed.

Action: None

OGG-10464: Instantiation CSN has been cleared successfully.
Cause: GGSCI command CLEAR_INSTANTIATION_CSN was successfully executed.

Action: None

OGG-10465: Found invalid length of {0} on inline securefile LOB
Cause: Extract detects an invalid length on inline securefile LOB data from redo data. Fetching will be used instead to get correct version of LOB data.

Action: None

OGG-10466: Found invalid flag of {0} on inline securefile LOB
Cause: Extract detects an invalid flag on inline securefile lob data from redo data. Fetching will be used instead to get correct version of LOB data.

Action: None

OGG-10467: Table {0}.{1} cannot be natively captured. {2}
Cause: Extract found a new table that cannot be natively captured by Oracle GoldenGate. This message provide more detail on why the table cannot be natively captured, including column name and type.

Action: Check the metadata of table and take appropriate action.

OGG-10468: 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-10469: 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-10470: Error encountered during gathering support information on table {0}.
Cause: Error encountered during process to gather support information on the table.

Action: Contact Oracle Support.

OGG-10471: ***** Oracle GoldenGate support information on table {0}.{1} ***** {2}
Cause: Oracle GoldenGate support related information on this table.

Action: It's for your information only.

OGG-10472: System partitoned table {0} is only supported with integrated dictionary.
Cause: Oracle GoldenGate Integrated Extract does not support system partitioned table when not using integrated dictionary for metadata.

Action: Use integrated dictionary or take the table out of Replication.

OGG-10501: Heartbeat object "{0}" already exists.
Cause: The heartbeat object already exists.

Action: If you want a new object, delete all existing heartbeat objects and recreate them.

OGG-10502: Heartbeat object "{0}" does not exist.
Cause: The heartbeat object does not exist.

Action: None

OGG-10503: Heartbeat object "{0}" creation failed.
Cause: The heartbeat object creation failed.

Action: None

OGG-10505: Job schedule [{0}] does not exist.
Cause: Job schedule updating heartbeat tables does not exist.

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

OGG-10506: Job schedule [{0}] dropped.
Cause: Job schedule for updating the heartbeat tables was dropped. Informational only.

Action: None

OGG-10507: Job [{0}] does not exist.
Cause: Job updating for heartbeat tables does not exist.

Action: Use the command ADD HEARTBEATTABLEto add the job.

OGG-10508: Job [{0}] dropped.
Cause: Job for updating the heartbeat tables was dropped. Informational only.

Action: None

OGG-10509: Job schedule [{0}] does not exist.
Cause: Job schedule for purging heartbeat tables does not exist.

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

OGG-10510: Job schedule [{0}] dropped.
Cause: Job schedule for purging heartbeat tables dropped. Informational only.

Action: None

OGG-10511: Job [{0}] does not exist.
Cause: Job for purging heartbeat tables does not exist.

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

OGG-10512: Job [{0}] dropped.
Cause: Job for purging the heartbeat tables was dropped. Informational only.

Action: None

OGG-10513: The job scheduler database({0}) does not exist. Configure database {0} and add Oracle GoldenGate Replication user with correct role to create and run the heart beat job.
Cause: SYBMGMTDB is not configured to run the heart beat job.

Action: Configure SYBMGMTDB and add Oracle GoldenGate replication user with appropriate role to continue. Follow the SAP/Sybase provided instructions to configure the job scheduler database.

OGG-10515: To create and run heart beat jobs, user({2}) must be created or added in job scheduler database({0}) and it must have ({1}) roles enabled.
Cause: The user is either not added or created in SYBMGMTDB database or user has not proper roles (Replication_role, js_admin_role, js_user_role) enabled.

Action: Add and create a Oracle GoldenGate Replication user in SYBMGMTDB database and add appropriate role to continue. Follow the SAP/Sybase provided instructions to configure the job scheduler database.

OGG-10520: Table or view ({0}) exists in the database({1}).
Cause: Table or view already exists in the current database.

Action: Execute the DELETE HEARTBEATTABLE command to drop the table.

OGG-10521: Procedure ({0}) exist in the database({1}) .
Cause: Procedure already exist in the current database.

Action: Execute the DELETE HEARTBEATTABLE command to drop the procedure.

OGG-10522: Scheduled job ({0}) already exist.
Cause: The scheduled job exists.

Action: Execute the DELETE HEARTBEATTABLE command to drop the schedule job.

OGG-10523: Cannot alter heattbeat scheduler job, hearttable(s) ({0},{1},{2}) do not exist in the database.
Cause: The heartbeat table and scheduler job does not exist.

Action: Use the ADD HEARTBEATTABLE command to add the heartbeat table and to schedule the job.

OGG-10524: User({2}) must be added in jobs scheduler database({0}) and it must have ({1}) roles enabled to create and run heart beat jobs.
Cause: The user is not the valid user in SYBMGMTDB database to run the job scheduler.

Action: Add an Oracle GoldenGate Replication user in the SYBMGMTDB database and then add an appropriate role to continue. User can follow the SAP/Sybase provided instructions to configure the job scheduler database.

OGG-10525: getSchemaVersion - Unable to obtain schema version for {0}.{1}
Cause: The catalog and schema are not valid.

Action: Correct the catalog and schema for the heartbeat table.

OGG-10526: User {0} must have sa_role to create table(s)for user ({1}).
Cause: The user logged in does not have sa_role to create tables for other users of the database.

Action: Add the sa_role to the logged in user.

OGG-10532: Logging of supplemental log data is disabled for table {0}.
Cause: Logging of supplemental log data is disabled. Information only.

Action: None

OGG-10533: Unable to open {0}, err {1} {2}
Cause: A file error was returned when attempting to open/create a required file.

Action: Evaluate the file system error and correct.

OGG-10534: Error {0}, {1} writting to {2}
Cause: A file error was returned when attempting to write to a required file.

Action: Evaluate the file system error and correct.

OGG-10535: Successfully created heartbeat rate table "{0}".
Cause: Heartbeat rate table has been created. Informational only.

Action: None

OGG-10536: Successfully populated heartbeat rate table.
Cause: Heartbeat seed table populated. Informational only.

Action: None

OGG-10538: Unable to stop the heartbeat process.
Cause: Unknown error; Contact Oracle support.

Action: None

OGG-10540: Unable to start the heartbeat process.
Cause: Unknown error; Contact Oracle support.

Action: None

OGG-10541: Manager restarted the heartbeat process.
Cause: Unknown error; If the error persists, contact Oracle support.

Action: None

OGG-10544: The hearbeat process was unable to open $RECEIVE.
Cause: Unknown error; Contact Oracle support.

Action: None

OGG-10545: The heartbeat process was unable to obtain required rate values.
Cause: Unknown error; Delete and re-add heartbeat configuration using the heartbeat table commands from GGSCI.

Action: None