1. Error Messages Reference for Oracle GoldenGate
  2. OGG-00001 to OGG-40000

1 OGG-00001 to OGG-40000

OGG-00001: Execution cannot continue - Program Terminating
This is a generic message that indicates a process failure.
Action:
Look for other messages in the process report and error log that provide more context for this failure. If you cannot determine and resolve the problem, contact Oracle Support.
OGG-00002: Missing directory name
The directory name is missing from the DIRECTORY option of the TRANSMEMORY or LOBMEMORY parameter.
Action:
Specify a directory for temporary storage with the DIRECTORY option, or use the default storage by removing the DIRECTORY option.
OGG-00003: Missing directory name end quote
A trailing (end) quote is missing from the directory specification in the DIRECTORY option of the TRANSMEMORY or LOBMEMORY parameter.
Action:
Enclose the directory name within double quotes.
OGG-00004: Directory too long
The directory name that is specified with the DIRECTORY option of TRANSMEMORY or LOBMEMORY exceeds the length limit that is supported by the operating system.
Action:
Specify a directory that has a path name that is within the operating system limitations.
OGG-00005: Invalid number for directory file size
The DIRECTORY option of TRANSMEMORY or LOBMEMORY contains an invalid value for the maximum file size, such as a non-numeric value or an invalid size specifier.
Action:
Specify a valid value. See the Oracle GoldenGate reference documentation for valid directory size and valid size specifiers (such as GB for gigabytes and MB for megabytes).
OGG-00006: Directory options must be enclosed in parentheses
The directory specification of the DIRECTORY option of TRANSMEMORY or LOBMEMORY is not enclosed within parentheses.
Action:
Enclose the entire directory specification in parentheses, as in this example: DIRECTORY (c:\test\dirtmp, 3000000000, 300000000)
OGG-00007: Invalid number for directory size
The DIRECTORY option of TRANSMEMORY or LOBMEMORY contains an invalid value for the maximum directory size, such as a non-numeric value or an invalid size specifier.
Action:
Specify a valid value. See the Oracle GoldenGate reference documentation for valid directory size and valid size specifiers (such as GB for gigabytes and MB for megabytes).
OGG-00008: Missing directory file size
The file size specification is missing from the DIRECTORY option of TRANSMEMORY or LOBMEMORY.
Action:
Specify a fully qualified directory name, a maximum directory size, and the maximum size of each file, as in: DIRECTORY (c:\test\dirtmp, 3000000000, 300000000).
OGG-00009: Directory parentheses must contain valid options
The DIRECTORY option of TRANSMEMORY or LOBMEMORY contains parentheses but no specification within them.
Action:
Specify a fully qualified directory name, a maximum directory size, and the maximum size of each file, as in: DIRECTORY (c:\test\dirtmp, 3000000000, 300000000).
OGG-00010: Missing directory size and directory file size
The DIRECTORY option of TRANSMEMORY or LOBMEMORY does not contain a specification for the maximum directory and file size.
Action:
Specify a fully qualified directory name, a maximum directory size, and the maximum size of each file, as in: DIRECTORY (c:\test\dirtmp, 3000000000, 300000000).
OGG-00011: Missing directory file size
The DIRECTORY option of TRANSMEMORY or LOBMEMORY does not contain a specification for the maximum file size.
Action:
Specify a fully qualified directory name, a maximum directory size, and the maximum size of each file, as in: DIRECTORY (c:\test\dirtmp, 3000000000, 300000000).
OGG-00012: Command line error:invalid startup syntax: {0}
An unknown parameter is specified for the Extract or Replicat process that is being started from the command line
Action:
Correct the syntax. The command can only contain PARAMFILE and REPORTFILE parameters, for example: /oggdir/extract paramfile dirprm/ext.prm reportfile /user/reports/ext.rpt.
OGG-00013: Missing {0} argument at startup.
An argument is missing from the specified parameter.
Action:
Supply the correct syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00014: Unrecognized parameter: {0}. Parameter could be misspelled or unsupported.
The specified parameter is not valid for this version of Oracle GoldenGate.
Action:
Check the parameter file for the correct syntax, spelling, and any required terminators such as the semi-colon. Also make certain the parameter is supported for this version of Oracle GoldenGate. To do both of those things, check the reference documentation for your version of Oracle GoldenGate.
OGG-00015: {0} is not supported. Check spelling or see Oracle GoldenGate Reference Guide for supported parameters.
The specified parameter is not valid for this version of Oracle GoldenGate.
Action:
Check the parameter file for the correct syntax, spelling, and any required terminators such as the semi-colon. Also make certain the parameter is supported for this version of Oracle GoldenGate. To do both of those things, check the reference documentation for your version of Oracle GoldenGate.
OGG-00016: {0} is not supported. Check spelling or see Oracle GoldenGate Reference Guide for supported parameters.
The specified parameter is not valid for this version of Oracle GoldenGate.
Action:
Check the parameter file for the correct syntax, spelling, and any required terminators such as the semi-colon. Also make certain the parameter is supported for this version of Oracle GoldenGate. To do both of those things, check the reference documentation for your version of Oracle GoldenGate.
OGG-00017: Not enough stack space. Specify FUNCTIONSTACKSIZE greater than {0,number,0}
The size of the memory stack that is used for processing Oracle GoldenGate column-conversion functions needs to be increased.
Action:
Add the FUNCTIONSTACKSIZE parameter to the parameter file before the point where parameters that contain conversion functions are listed, and set it to at least the value shown in the error message. The value specifies the number of function arguments to allow in a parameter clause.
OGG-00018: {0} ignored when running as a RMTTASK.
The specified parameter is not supported for a remote task and is being ignored.
Action:
Remove the parameter from the parameter file to avoid future messages like this.
OGG-00019: No GROUP value given for RMTTASK in Extract parameter file. Correct: GROUP group_name.
The RMTTASK parameter is missing the required GROUP clause.
Action:
Add the GROUP clause so that the syntax is RMTTASK REPLICAT, GROUP group_name, where group_name is the name of the Replicat group on the target.
OGG-00020: The GROUP value in RMTTASK in the Extract parameter file is too long.
The name of the group in the GROUP clause of RMTTASK is probably too long. An Oracle GoldenGate group name can be up to eight characters long.
Action:
Reduce the length of the group name.
OGG-00021: The REPLICAT parameter in RMTTASK in the Extract parameter file is not present.
The RMTTASK parameter requires the REPLICAT keyword.
Action:
The correct syntax is RMTTASK REPLICAT, GROUP group_name, where group_name is the name of the Replicat group on the target.
OGG-00022: The GROUP clause in RMTTASK line in the Extract parameter file is not present.
The RMTTASK parameter is missing the required GROUP clause.
Action:
Add the GROUP clause so that the syntax is RMTTASK REPLICAT, GROUP group_name, where group_name is the name of the Replicat group on the target.
OGG-00023: TCPBUFSIZE and TCPFLUSHBYTES are not supported in RMTTASK mode
The RMTHOST parameter contains the TCPBUFSIZE or TCPFLUSHBYTES option (or both), which are not supported for a remote task.
Action:
Remove these options from the parameter file.
OGG-00024: Cannot specify both FORMATASCII and ENCRYPTTRAIL for '{0}'
ENCRYPTTRAIL and NOENCRYPTTRAIL cannot be used when FORMATASCII is used to write data to a file in ASCII format. The trail or file must be written in the default Oracle GoldenGate canonical format when encryption is used.
Action:
Remove either FORMATASCII or ENCRYPTTRAIL from the parameter file, depending on the configuration requirement.
OGG-00026: Bulk load not implemented for this database type.
The BULKLOAD parameter is being used for Replicat against a database that is not an Oracle database.
Action:
Do not use the BULKLOAD initial load method. See the Oracle GoldenGate administration documentation for other supported load methods.
OGG-00027: {0} was not specified. Check Oracle GoldenGate documentation for correct usage.
The specified parameter is required but missing from the parameter file.
Action:
Add the parameter. See the Oracle GoldenGate reference documentation for help with syntax and usage.
OGG-00028: Failed to retrieve column handle for table {0}, column #{1,number,0} while getting table definition.
The process could not retrieve the metadata for the specified table. Most likely, the table does not exist.
Action:
Exclude the table from the TABLE or MAP statement.
OGG-00029: Failed to retrieve column list handle for table {0} while getting table definition.
The process could not retrieve the metadata for the specified table. Most likely, the table does not exist.
Action:
Exclude the table from the TABLE or MAP statement.
OGG-00030: Could not resolve parameter {0}. Check spelling and usage in parameter file.
Oracle GoldenGate could not resolve the specified parameter. It might be misspelled or used incorrectly.
Action:
Check the Oracle GoldenGate reference documentation for correct syntax and usage.
OGG-00031: Unspecified parameter name.
There are no runtime substitution parameters specified.
Action:
To use parameter substitution, declare a runtime parameter instead of an actual value, and precede the runtime parameter name with a question mark (?), such as EXTFILE ?EXTFILE. Then, before starting the process, use the shell of the operating system to pass the runtime values by means of an environment variable. For more information, see the Oracle GoldenGate administration documentation.
OGG-00032: Parameter {0} was already specified.
The specified parameter appears more than once in the parameter file.
Action:
Remove all but one instance of this parameter, and make sure it is the one that contains the correct options and values for your intended configuration.
OGG-00033: Parameter {0} was already specified ({1})
The specified parameter appears more than once in the parameter file.
Action:
Remove all but one instance of this parameter, and make sure it is the one that contains the correct options and values for your intended configuration.
OGG-00034: Missing value for startup parameter {0}.
A value was not given for the specified parameter.
Action:
Specify a value for this parameter. For permissible values, see the Oracle GoldenGate reference documentation.
OGG-00035: {0} does not take any additional parameters
Too many values are supplied for the specified parameter.
Action:
See the Oracle GoldenGate reference documentation for correct syntax, options, and values.
OGG-00036: No tables specified in parameter file
The parameter file does not contain a TABLE or MAP parameter to specify the tables that are to be processed by Oracle GoldenGate.
Action:
Add one or more TABLE parameters to an Extract parameter file or one or more MAP parameters to a Replicat parameter file.
OGG-00037: {0} file {1} already exists
The specified file name already exists.
Action:
Specify a different file name or delete the existing file.
OGG-00038: Could not start TCP/IP (status {0,number,0}, err {1,number,0})
There was a Windows Sockets (Winsock) error when Oracle GoldenGate attempted to start TCP/IP services.
Action:
Fix the problem that is reported in the Winsock error message.
OGG-00039: Invalid timeout value {0}
The value for the Collector timeout was not between 1 and 1800 seconds.
Action:
Specify a value between 1 and 1800 for the -w Collector parameter.
OGG-00040: Missing timeout value
A value for the -w Collector timeout parameter was not provided.
Action:
Specify a value between 1 and 1800 seconds for the -w Collector parameter.
OGG-00041: Data source not specified
The Oracle GoldenGate Extract (capture) process is configured with an unknown data source type.
Action:
Recreate the Extract group with a supported data source type, such as TRANLOG, VAM, EXTTRAILSOURCE, or SOURCEISTABLE. For a complete list of data source options, see the ADD EXTRACT command in the Oracle GoldenGate reference documentation.
OGG-00042: {0} may not be used with this type of Extract
The specified parameter is not valid for use with the current Extract configuration.
Action:
Remove the parameter. For help with configuring Extract for your requirements, see the Oracle GoldenGate documentation.
OGG-00044: PASSTHRU parameter can only be used with an extract data pump
The PASSTHRU parameter is specified in the parameter file of a primary Extract or a Replicat group.
Action:
Remove PASSTHRU or create the Extract group to be a data pump, as applicable to your requirements.
OGG-00045: Trails cannot be used with {0}
A remote task is specified for this configuration of Oracle GoldenGate, but the RMTTRAIL or EXTTRAIL parameter is also used.
Action:
Remove the trail parameters.
OGG-00047: Expected {0} parameter for task
The RMTTASK parameter is missing from the parameter file.
Action:
Add the RMTTASK parameter.
OGG-00049: Trails cannot be used when SOURCEISTABLE/SOURCEISFILE is specified
The ADD EXTRACT command that created the Extract process was issued with the SOURCEISTABLE or SOURCEISFILE option to create a remote task. A remote task does not use disk storage for data, but a trail parameter was specified in the parameter file.
Action:
Remove the EXTTRAIL or RMTTRAIL parameter.
OGG-00051: Must specify extract file when specifying {0}
The SPECIALRUN parameter is being used, but there is no EXTFILE or EXTTRAIL parameter to specify the output storage file.
Action:
Add an EXTFILE or EXTTRAIL parameter.
OGG-00052: No replication maps specified
There are no MAP parameters in the Replicat parameter file to specify source and target table mappings.
Action:
Add one or more MAP parameters to the Replicat parameter file.
OGG-00053: No extraction maps specified
There are no TABLE parameters in the Extract parameter file to specify source tables for which to capture data.
Action:
Add one or more TABLE parameters to the Extract parameter file.
OGG-00054: Remote task entry encountered in the parameter file without a remote host entry given first
The RMTTASK parameter is used in the Extract parameter file to specify a remote task, but the target host is not specified with the RMTHOST parameter.
Action:
Add the RMTHOST parameter to the Extract parameter file. For help with configuring a remote task, see the Oracle GoldenGate administration documentation. For more information about RMTHOST and RMTTASK, see the Oracle GoldenGate reference documentation.
OGG-00055: {0} is not supported for passive mode
The Extract group was created as a passive Extract by using the ADD EXTRACT command with the PASSIVE option, but the parameter file for this group contains the specified parameter, which is not supported in passive mode.
Action:
Remove the parameter from the Extract parameter file.
OGG-00056: Too many trail/file definitions in passive mode
This Extract process is configured in PASSIVE mode, but there are multiple RMTFILE or RMTTRAIL definitions.
Action:
Remove all but one RMTFILE or RMTTRAIL definition.
OGG-00057: Only remote trail/file is allowed in passive mode.
The Extract group was added in PASSIVE mode, but the parameter file specifies an EXTTRAIL or EXTFILE local trail or file.
Action:
Remove the specification for the local file, and use the RMTTRAIL or RMTFILE parameter instead.
OGG-00058: Begin time ({0,date} {0,time}) must precede end time ({1,date} {1,time})
The parameter file contains a parameter that takes a begin and end time as input, but the end time is listed before the begin time.
Action:
Edit the parameter syntax to specify the begin time before the end time. For help, see the Oracle GoldenGate reference documentation.
OGG-00059: Oracle GoldenGate sets error {0,number,0} to {1} internally, cannot override the error response to {2}.
The REPERROR parameter contains a response rule for the specified error number, but this error is handled internally by Oracle GoldenGate, and the REPERROR setting is ignored.
Action:
Remove the REPERROR rule that caused the error.
OGG-00061: DEFERAPPLYINTERVAL cannot be less than EOFDELAY.
The DEFERAPPLYINTERVAL parameter is used in the parameter file to control how long Replicat waits before applying data to the target; however, the value is lower than the value of EOFDELAY, which controls how often Replicat checks for new data in the trail.
Action:
Set DEFERAPPLYINTERVAL to a higher value than that of EOFDELAY.
OGG-00062: DEFERAPPLYINTERVAL cannot be greater than 1 week.
The value of DEFERAPPLYINTERVAL is set to more than seven days (one week).
Action:
Reduce the value to seven or fewer days (or the equivalent seconds, minutes, or hours). See the Oracle GoldenGate reference documentation for valid units.
OGG-00063: CHECKOPCOMPLETE: No operation type was set in the VAMRead
The operation type attribute of the record that is being passed by the VAM API was not set by the VAM module.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00064: CHECKOPCOMPLETE: The DDL database object type has an invalid operation type: {0,number,0}
The operation type attribute for the record that is being passed by the VAM API does not match one of the DDL database object types.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00065: CHECKOPCOMPLETE: The table database object type has an invalid operation type: {0,number,0}
The operation type attribute for the record being passed by the VAM API does not match the table database object type.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00066: CHECKOPCOMPLETE: The database object type is invalid: {0,number,0}
The database object type attribute for the record being passed by the VAM API does not match any known database object types.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00067: CHECKOPCOMPLETE: No DDL statement was received for a record with a DDL database object type
No DDL statement was given by the VAM API for the DDL record that is being processed.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00068: CHECKOPCOMPLETE: No object name was set for operation type: {0,number,0}
The object name attribute for the record being passed by the VAM API was not set by the VAM module.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00069: CHECKOPCOMPLETE: No object owner was set for operation type: {0,number,0}
The object owner attribute for the record being passed by the VAM API was not set by the VAM module.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00070: CHECKOPCOMPLETE: No timestamp was set for operation type: {0,number,0}
The timestamp attribute for the record being passed by the VAM API was not set by the VAM module.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00071: CHECKOPCOMPLETE: No transaction identifier was set for operation type: {0,number,0}
The transaction identifier attribute for the record being passed by the VAM API was not set by the VAM module.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00073: CHECKOPCOMPLETE: No before keys in primary key update were added for operation type: {0,number,0}
No before image key fields were sent for a primary key update record being passed by the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00074: CHECKOPCOMPLETE: Before key in primary key update was not added for column(s): {1}: Operation type: {0,number,0}
No before image key fields were sent for a primary key update record being passed by the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00075: CHECKOPCOMPLETE: Key column was not added for column(s) {1}: Operation type: {0,number,0}
The value for the after image key column required for an update record was not passed by the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00076: GG_OBJ_RECORD: GG_ATTR_OBJECT_NAME: Object owner attribute was already set as part of the object name
The object owner attribute for the record being passed by the VAM API was already included in the object name attribute.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00077: GG_OBJ_RECORD: GG_ATTR_OBJECT_NAME: Object owner attribute must be set before the object name is set
The object owner attribute for the record being passed by the VAM API was set after the object name attribute was set. It is a VAM API requirement that it be set before the object name attribute.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00078: DDL processing is not implemented for this target
A DDL record was encountered in the transaction log. Oracle GoldenGate does not support the capture or replication of DDL for this type of database.
Action:
Because DDL was applied on the source but not replicated, the source and target definitions are out of synchronization. Future DML may result in errors. You can ignore this message and accept the inconsistencies, or you can apply the DDL on the target before allowing DML operations on this object. Stop and start Replicat after the DDL changes are made.
OGG-00079: Metadata object processing is not implemented for this target
The VAM API does not support the exchange of table metadata for the database being used.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00080: Invalid I/O type encountered {0,number,0}
This message is specific to the Teradata VAM implementation. An end transaction record was expected, but another record type was received.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00081: GG_OBJ_METADATA: GG_ATTR_MD_COLUMN_COUNT: Column count must be greater than zero
An insert, update, or delete record was sent by the VAM API, but no columns for the record were received.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00082: GG_OBJ_METADATA: GG_ATTR_MD_COLUMN_COUNT: Previous table not completed
The metadata processing for the current table was not complete when an attempt was made to start processing the metadata for the next table in the sequence.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00083: Transaction list update: Number of transactions has changed
This message is specific to the Teradata VAM implementation. Recovery processing cannot complete because the recovery trail file has been updated by another process after recovery processing started.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00084: Transaction list processing only available in maximum protection mode
This message is specific to the Teradata VAM implementation. Recovery processing is only supported in maximum protection mode and maximum performance mode was specified.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00085: {1}:Invalid attribute {0,number,0}.
The attribute type set by the VAM module is unknown.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00086: {1}:Attribute {0,number,0} has invalid value
The attribute value set by the VAM module is invalid for the attribute type.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00087: Transaction list update: Transaction ID has changed for index {0,number,0}
This message is specific to the Teradata VAM implementation. Recovery processing cannot complete because the recovery transaction list passed to the VAM module is no longer valid.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00088: {1}: Attribute {0,number,0}: The pointer to the return parameter for the attribute length cannot be null
No return buffer was given to hold the length of the value when the VAM module is retrieving a value from the VAM kernel.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00089: Object {0,number,0}: Attribute {1,number,0}: Attribute is invalid for object
The attribute type assigned by the VAM module is invalid for the VAM API object type it is setting.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00090: Transaction list is not available for the generic VAM
The functionality being requested is only available for the Teradata VAM implementation.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00091: {0}
The error message that is displayed is returned from a separate sub-subsystem called by the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00092: {0}: A maximum return length of zero and a null pointer to the return parameter for the attribute length are an invalid combination
No return buffer was given to hold the length of the value when the VAM module is retrieving the length of value from the VAM kernel.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00094: Object {0,number,0}: Attribute {1,number,0}: Length must be greater than zero
The attribute for the object being passed to the VAM API by the VAM module must contain a value.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00095: {1}: Attempting to add attribute {0,number,0} before index set for column
A column attribute is being passed to the VAM API by the VAM module before the column index identifying that column has been set.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00096: {3}: Attribute {0,number,0} Length given ({2,number,0}) exceeds maximum length allowed ({1,number,0})
The length of the attribute being passed to the VAM API by the VAM module exceeds the maximum length allowed for that attribute type.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00097: {0}: Invalid length for an integer value
An integer value is being passed to the VAM API by the VAM module, but the length given is not either 1, 2, 4 or 8 bytes, which are the only lengths allowed.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00098: Object {0,number,0}: Attribute {1,number,0}: Invalid length {2,number,0}
A C/C++ int value is being passed to the VAM API by the VAM module, but the length given is not the same as the length of an int as returned by that compiler.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00099: {0}: Invalid data format type
The data format type assigned by the VAM module is invalid for the VAM API attribute type it is setting.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00100: {1}: Attribute {0,number,0}: Column is not nullable.
A null value was passed to the VAM API by the VAM module for a column whose metadata marked it as not nullable.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00101: {1}: Attribute {0,number,0}: Only integers are scalable.
A decimal scale was passed to the VAM API by the VAM module for a column data type for which it is invalid.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00102: {1}: Attribute {0,number,0}: Scale does not match table definition
The decimal scale passed to the VAM API by the VAM module for a column does not match the table metadata definition.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00103: {1}: {0}: GG_ATTR_MD_COLUMN_COUNT not set
A metadata attribute from the Extract parameter file is being retrieved via the VAM API by the VAM module before the metadata processing has started for that table.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00104: VAM module calling GGColMetadataAddByIndex without setting GG_ATTR_MD_COLUMN_COUNT with the number of columns to be added
A column metadata attribute is being passed to the VAM API by the VAM module before the column processing has started.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00105: {0}: Table lookup in database has either not taken place or failed: Check return code of GGAttrSet for GG_ATTR_OBJECT_NAME
The VAM module is attempting to continue processing the metadata for a table after the VAM API returned an error code on a previous call.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00106: {0}: Adding column before operation type set
A column value is being passed to the VAM API by the VAM module before the operation type was set for the record.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00107: GG_OBJ_RECORD: Invalid VAM operation type {0,number,0}
The operation type attribute being passed to the VAM API by the VAM module for the VAM API record object is unknown.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00108: No transaction ID was given in Direct Call Interface interface call.
No transaction identifier was given in the Direct Call Interface call when the VAM module was sending a record via the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00109: {0} requires maximum protection mode
This message is specific to the Teradata VAM implementation. The VAM module sent a prepare transaction record via the VAM API in maximum performance mode. This is only allowed in maximum protection mode.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00110: {0}: VAM session using local ASCII format timestamps for position time: Integer format Julian GMT timestamps invalid.
The VAM module is sending timestamps in a Julian format as an integer value while the session protocol is to use ASCII timestamps.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00111: {0}: VAM session using integer format Julian GMT timestamps for position time: Local ASCII format timestamps invalid.
The VAM module is sending timestamps in an ASCII format while the session protocol is to use a Julian format passed as an integer.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00112: GG_OBJ_RECORD: {0} must be set before {1}
A required attribute in the VAM API record object was not set in the right order by the VAM module.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00113: GG_OBJ_RECORD: GG_ATTR_BEFORE_AFTER can only be used with GG_OPTYPE_UPDATE for primary key updates
The VAM module tried to add a before key for a record that is not a primary key update.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00115: GG_OBJ_RECORD: Attribute {0,number,0}: Null pointer passed for value
No buffer was given for the VAM kernel to retrieve the value when the VAM module is setting an attribute value via the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00116: VAMMessage error returned by VAM
A call from GGSCI to the VAMMessage function implemented by the user in the VAM module returned with an error.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00117: VAMMessage called before VAM module initialized.
A call from GGSCI to the VAMMessage function was made before the VAM module was initialized by a call to VAMInitialize.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00118: {1}: Index {0,number,0} is not in sequential order
A column was sent out of sequential order by the VAM module when sending the columns for an insert, update or delete record.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00119: {1}: Index {0,number,0} is out of range of columns added to record
A column index was sent by the VAM module that is greater than the number of columns available for the table, when sending the columns for an insert, update or delete record.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00120: The maximum length allowed for LOB row ID was exceeded
The maximum size of the buffer available to hold the unique ID generated for a LOB column was exceeded by the length of the ID that was generated.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00121: {1}: Invalid VAM action {0,number,0}.
An invalid action type was passed by the VAM module when generating an informational, warning or error message to be sent to and output by the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00122: Large column support is not implemented in this release
The maximum column size was exceeded for the column value sent by the VAM module by the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00123: No columns given in DCI interface call
An insert, update or delete record was sent in the Direct Call Interface call to the VAM API but no columns for the record were received.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00124: Input data format must be set to zero
The data format type was set by the VAM module for an attribute passed to the VAM API that does not possess a data type. The data format value should be set to zero in this case.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00125: Object {0,number,0}: Attribute {1,number,0}: Column values can not be set directly
An attempt was made to use one of the deprecated column attributes that were originally used to set column values directly.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00126: Object {0,number,0}: Attribute {1,number,0}: String does not contain a value
An attribute value was sent by the VAM module as a null-terminated string, but the null-terminated string has a length of zero instead of a value (required).
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00127: Object {0,number,0}: Attribute {1,number,0}: Maximum length allowed exceeded
The attribute value set by the VAM module for the transaction identifier in the VAM API record object exceeds the maximum length allowed for transaction identifier.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00128: Large column processing in progress: invalid data format
An invalid data format type was passed by the VAM module when processing large and LOB columns that are sent in blocks across the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00129: Adding column before metadata retrieved
The VAM module is sending the column values for a table via the VAM API before the metadata exchange for that table has taken place.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00130: Table {0}: Column {1} has invalid type for a key column
The data type of the primary key of this table is not supported by Oracle GoldenGate as a key.
Action:
Specify an alternate key by using a KEYCOLS clause in the parameter file. For more information, see the Oracle GoldenGate reference documentation. For supported data types in keys, see the Oracle GoldenGate installation and setup documentation for your database.
OGG-00133: GG_OBJ_METADATA: {0} returned an error
There was an error trying to retrieve metadata with the specified VAM function.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00134: VAM attempting retrieve GG_ATTR_MD_KEYCOLS when GG_ATTR_MD_KEYCOLS_COUNT is set to zero and there are no key columns to return
During the table metadata exchange the VAM module is attempting to retrieve the value of the KEYCOLS array specified in the Extract parameter file when there are no KEYCOLS values to retrieve.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00135: GG_OBJ_METADATA: Table {0} has no key columns specified and no columns that can be used as key columns
The specified table contains no defined key columns and no other columns that Oracle GoldenGate can use as key columns. Oracle GoldenGate will attempt to use all of the columns as a key, or you can specify a KEYCOLS clause in the source TABLE and target MAP parameters. For more information, see the Oracle GoldenGate reference documentation.
Action:
None
OGG-00136: {0} is a deprecated VAM API function and is no longer in use.
An incompatible version of the VAM API module is being used.
Action:
Contact Oracle Support to obtain the current version.
OGG-00137: GG_OBJ_COLUMN: Invalid integer type {0,number,0}
An invalid integer was passed by the VAM module when sending the columns for an insert, update or delete record via the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00138: A SORTTRANLOG extract requires either a TERADATA or a VAMTRD pre-processor define to build successfully
This message is specific to the Teradata VAM implementation. The executable was built without the defines that are required in order to enable the functionality being requested.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00139: Extract was not built with VAM functionality included
This Extract build does not include a VAM module.
Action:
Obtain the correct Extract build for your database from Oracle.
OGG-00140: Error {0,number,0}, source {1,number,0} - {2}
Inter-process communication failed. This error is related to the Oracle GoldenGate vendor access module (VAM).
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00141: {1} Invalid VAM type:{0,number,0}
The Extract type was not given in the TRANLOGOPTIONS clause in the Extract parameter file for the Teradata implementation of the VAM API.
Action:
Specify the correct Extract type, either COMMITTEDTRANLOG, CREATETRANLOG, or SORTTRANLOG. If the problem persists, contact Oracle Support.
OGG-00142: {0}: Adding column before table owner set
The VAM module sent a column through the VAM API for an insert, update or delete operation before it set the required record attribute that specifies the object owner of the record.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00143: {0}: Adding column before table name set
The VAM module sent a column through the VAM API for an insert, update or delete operation before it set the required record attribute specifying the object name of the record.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00144: Fatal error reported by VAM reader thread
A fatal error was reported in another thread in the multi-threaded VAM Extract, and this thread terminated because of that error.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00145: Call to {0} returned with error status {1,number,0}
One of the VAM API functions implemented in the VAM module returned an error status on completion of the call to that function in the VAM kernel.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00146: Call to {0} returned with error status {1,number,0}: {2}
One of the VAM API functions implemented in the VAM module returned an error status on completion of the call to that function in the VAM kernel, after previously reporting a fatal error in the call.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00147: Call to {0} returned with error status {1,number,0}: {2}
The VAM API VAMControl function returned an error when being called as part of the shutdown processing caused by a previously reported fatal error.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00148: Prepare is invalid in maximum performance mode
This message is specific to the Teradata VAM implementation. The VAM module sent a prepare transaction record via the VAM API in maximum performance mode. This is only allowed in maximum protection mode.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00149: Rollbacks of transactions are not allowed in maximum protection mode
This message is specific to the Teradata VAM implementation. The VAM module sent a rollback transaction record via the VAM API, but only successfully committed transactions can be sent by the VAM module for the Teradata implementation.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00150: No value set for table name
The metadata for the table in the VAM kernel does not contain a valid table name. This is required for the standard header structure used to preface each output trail file record to identify the table in that file.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00151: The GG_ATTR_OP_COMPLETE attribute was not checked after adding a record before the VAMRead completed
The optional validation checking is on, and the VAM module did not make the final call to verify that the validation was successful. This validation checking is on by default in debug builds to ensure that the VAM module completed all of the requirements for sending a record via the VAM API. It is designed to be used for development by third-parties that are building their own VAM module as a dynamic link library or shared library.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00152: Begin transaction - transaction {0} already exists in file memory
A duplicate begin-transaction identifier was encountered for a database transaction. An identifier must be unique to maintain transaction integrity.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00153: Invalid GG_ATTR_OPTYPE: {0}: Transaction type is invalid for VAM generic mode.
The VAM module sent an unknown or invalid operation type via the VAM API. An example of an invalid operation is a prepare-transaction record for implementations that do not support a two-phase commit mechanism. This can occur in the Teradata implementation, where Extract is in COMMITTEDTRANLOG mode and does not support prepare-transaction records (although in CREATETRANLOG and SORTTRANLOG modes it does).
Action:
If using the Teradata implementation, check that Extract is being run in CREATETRANLOG or SORTTRANLOG mode. If the problem persists contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00154: GG_OBJ_METADATA: The new table entry pointer is null
Table metadata is being looked up by the VAM module as the table is encountered dynamically, and there was an error in the defined protocol for exchanging the table metadata.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00155: GG_OBJ_METADATA: Table name has a length of {0,number,0}, but the maximum allowed is {1,number,0}
The name of the table contains too many characters to be supported by Oracle GoldenGate.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00156: GG_OBJ_METADATA: Owner name has a length of {0,number,0}, but the maximum allowed is {1,number,0}
The owner name of the table contains too many characters to be supported by Oracle GoldenGate.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00157: GG_OBJ_METADATA: Number of tables processed ({1,number,0}) does not match the number given ({0,number,0})
The table metadata is being exchanged statically in the VAMInitialize function from the VAM module to the VAM kernel or vice-versa, and the number of tables that require a metadata exchange does not match the number of tables that were exchanged.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00158: GG_OBJ_METADATA: REP_get_table_by_name returned without finding a match
A TABLE parameter in the Extract parameter file lists a table explicitly by its full name, but Oracle GoldenGate could not find the table name in the metadata dictionary that was retrieved from the database catalog.
Action:
Check the parameter file for errors in the TABLE specification. Make certain that the table exists in the database.
OGG-00159: GG_OBJ_METADATA: WILDCARD_check_table returned without finding a match
The TABLE parameter in the Extract parameter file contains a wildcarded table list, but no tables to satisfy it could be found in the metadata dictionary that was retrieved from the database catalog.
Action:
Check the parameter file for errors in the TABLE specification. Make certain that the database contains tables that match the wildcard specification and which you want to be captured.
OGG-00160: GG_OBJ_METADATA: WILDCARD_getNextStaticTable returned with no entry found
The TABLE parameter in the Extract parameter file contains a wildcarded table list, but no tables to satisfy it could be found in the metadata dictionary that was retrieved from the database catalog.
Action:
Check the parameter file for errors in the TABLE specification. Make certain that the database contains tables that match the wildcard specification and which you want to be captured.
OGG-00161: More than one output queue file specified for CREATETRANLOG VAM
This is specific to the Teradata implementation of the VAM API. The Extract group is configured in CREATETRANLOG mode, but there is more than one EXTTRAIL entry in the Extract parameter file. In this mode, Extract can only write to one local trail.
Action:
Edit the Extract parameter file to remove the extra EXTTRAIL specifications, and then restart the Extract process.
OGG-00162: Remote queue file specified for CREATETRANLOG VAM
This is specific to the Teradata implementation of the VAM API. The Extract group is configured in CREATETRANLOG mode, but there is a RMTTRAIL parameter in the Extract parameter file.
Action:
Replace the RMTTRAIL parameter with an EXTTRAIL parameter. In CREATETRANLOG mode, Extract must write to one local trail, not a remote trail.
OGG-00163: Checkpointing is mandatory
This message is specific to the Teradata VAM implementation. Checkpointing is required for this implementation and checkpointing was not initialized.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00164: The maximum item identifier length ({0,number,0}) has been exceeded
The VAM module set an attribute through the VAM API with a value that is longer than the maximum defined for that attribute in the VAM API specifications.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00165: No options parameters were specified in the parameter file
The DSOPTIONS parameter is missing from the parameter file, but is required to specify the processing actions that this Extract group performs.
Action:
Add DSOPTIONS with the correct processing options for this Extract group. For help with configuring Extract for Teradata, see the Oracle GoldenGate installation and setup documentation for the Teradata database.
OGG-00166: Lookup failure on table {0}
The specified table is listed in the TABLE parameter but the metadata for this table could not be found.
Action:
Check the parameter file for a misspelling of the table name. If there are no mistakes in the parameter file, make certain that the table exists in the database. If the table exists and the parameter file is correct, contact Oracle Support.
OGG-00167: Only wildcarded table definitions are allowed in the parameter file for the transaction reader implementation of the VAM
In the Teradata VAM implementation, tables can only be looked up as they are encountered dynamically, so the table metadata cannot be exchanged statically in the VAM API VAMInitialize function.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00168: WILDCARDRESOLVE DYNAMIC parameter is mandatory for the transaction reader implementation of the VAM
The WILDCARDRESOLVE parameter is not set to DYNAMIC, which is the required setting for the VAM implementation.
Action:
Edit the parameter file to change WILDCARDRESOLVE to DYNAMIC, or add WILDCARDRESOLVE DYNAMIC if it is not present.
OGG-00169: No VAM parameters were specified in the parameter file
The parameter file for this VAM-based Extract process does not contain the VAM parameter. This parameter is required for VAM-based Extract groups for this source database.
Action:
Add the VAM parameter with the associated PARAMS clause to the Extract parameter file. For syntax per source database type, see the Oracle GoldenGate reference documentation.
OGG-00170: No VAM PARAMS items were found in the param file
The parameter file for this VAM-based Extract process does not contain the VAM parameter with PARAMS options. PARAMS input is required for VAM-based Extract groups for this source database.
Action:
Add the VAM parameter with the PARAMS clause to the Extract parameter file. For syntax and required input for PARAMS per source database type, see the Oracle GoldenGate reference documentation.
OGG-00171: The PARAMS section in the VAM options is invalid
The PARAMS clause of the VAM parameter in the Extract parameter file is incorrect.
Action:
Check the parameter syntax for typographical errors. For syntax and valid options, see the VAM parameter in the Oracle GoldenGate reference documentation.
OGG-00172: No VAM PARAMS section was found in the param file
The parameter file for this VAM-based Extract process does not contain the VAM parameter with the PARAMS option. This parameter is required for VAM-based Extract groups for this source database to specify VAM input parameters.
Action:
Add the VAM parameter with the PARAMS clause to the Extract parameter file. For syntax and required input for PARAMS per source database type, see the Oracle GoldenGate reference documentation.
OGG-00173: The {0} option is not implemented in this release
The specified option is not supported in this release of Oracle GoldenGate.
Action:
For valid syntax, see the Oracle GoldenGate reference documentation.
OGG-00174: {0} is incompatible with the other options given
The specified parameter option is being used with other, incompatible options.
Action:
To determine the correct syntax and valid options, see the Oracle GoldenGate reference documentation.
OGG-00175: Length of VAM load module exceeds maximum allowed
The length of the name of the VAM load module exceeds the allowed length.
Action:
Rename the module to an acceptable length, then specify the new name wherever the module is specified in parameters, then restart the Extract process.
OGG-00176: No VAM load module was specified in the param file
The VAM load module is not specified with the VAM parameter in the Extract parameter file.
Action:
Specify the load module with VAM and then restart Extract.
OGG-00177: {0} is not supported for VAM based extracts.
The specified parameter is not supported for a VAM-based Extract.
Action:
Remove the parameter from the parameter file, and then restart the Extract process.
OGG-00178: {0}
The specified VAM error occurred.
Action:
Resolve the problem according to the error message or contact Oracle Support.
OGG-00179: Operation type {0,number,0} is invalid: Rollback to savepoint in a transaction is not allowed
The Oracle GoldenGate VAM does not support partial rollback operations. A transaction must be either committed or rolled back in its entirety.
Action:
Contact Oracle Support.
OGG-00180: The transaction reader VAM cannot be run in single-threaded mode if HAVEPTHREADS is defined as a pre-processor build directive
The VAM API kernel was built in multi-threaded mode, but the rest of the Extract executable was built in single-threaded mode.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00181: The transaction reader VAM cannot be run in multi-threaded mode unless HAVEPTHREADS is defined as a pre-processor build directive
The VAM API kernel was built in single-threaded mode, but the rest of the Extract executable was built in multi-threaded mode.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00182: VAM API running in single-threaded mode
The Oracle GoldenGate VAM is running in single-threaded mode. Informational only.
Action:
None
OGG-00183: VAM API running in multi-threaded mode
The Oracle GoldenGate VAM is running in multi-threaded mode. Informational only.
Action:
None
OGG-00184: {0} is not supported for SQL/MX ODBC replicat.
The specified parameter is not supported by Replicat for a SQL/MX database.
Action:
Remove the parameter, and then restart the process.
OGG-00185: Warning table {0} does not exist in SQL/MX db.
The specified table is listed in the Oracle GoldenGate parameter file but does not exist in the database.
Action:
Edit the parameter file to remove the table, or add the table to the database.
OGG-00186: Encountered SQL/MX fetching from table {0}
A fetch from the specified table failed.
Action:
Look for further error messages to determine the cause.
OGG-00187: TMFVAM_read Record version mismatch.
The record version does not match the version that Extract expects. This indicates that the vamserv module is not the same version as that of Extract.
Action:
Install the version of vamserv that matches the version of Extract.
OGG-00188: TMFVAM Error {1,number,0} returned from {0}
The specified error occurred in the vamserv module.
Action:
If you cannot determine the cause and resolution based on the error text, contact Oracle Support.
OGG-00189: TMFVAM_init() was not called
This is an internal logic error.
Action:
Contact Oracle Support.
OGG-00190: Unable to determine the Guardian filename for '{0}'
Extract cannot determine a valid Guardian filename. The symlink is either missing or pointing to an invalid file name.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00191: Error {1,number,0} Completing I/O to {0}
An interprocess message from Extract to the vamserv module failed.
Action:
Not recoverable. Restart Extract. If the problem persists, contact Contact Oracle Support.
OGG-00192: Unknown response code {1,number,0} from {0}
Extract received a message from the vamserv module that it cannot process.
Action:
Not recoverable. Restart Extract. If the problem persists, contact Contact Oracle Support.
OGG-00193: Error {1,number,0} Posting WRITEREAD request to {0}
Extract encountered a file system error while initiating a request to vamserv.
Action:
Not recoverable. Restart Extract. If the problem persists, contact Contact Oracle Support.
OGG-00194: Error '{0}' process not open.
The VAMSERV process is has not been opened for interprocess communication.
Action:
Not recoverable. Restart Extract. If the problem persists, contact Contact Oracle Support.
OGG-00195: File open error {2,number,0} on process {0}, application name ({1}).
An open on the vamserv process failed.
Action:
Not recoverable. Restart Extract. If the problem persists, contact Contact Oracle Support.
OGG-00196: PROCESS_CREATE_ error {1,number,0},{2,number,0} on {0}
The creation of a vamserv process failed. The OS error is shown in the message text.
Action:
Evaluate the OS error in the message and take the appropriate action. If the problem persists, contact Oracle Support.
OGG-00197: Missing argument
A parameter contains a missing or invalid input argument.
Action:
Edit the parameter file to correct the syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00198: Missing/invalid argument
A parameter contains a missing or invalid input argument.
Action:
Edit the parameter file to correct the syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00199: Table {0} does not exist in target database
The specified table that is named in the Replicat parameter file does not exist in the target database.
Action:
Verify the table specification in the parameter file and in the database. Edit the parameter file accordingly.
OGG-00200: Table name missing
A parameter requires the name of a table as input, and the name was not supplied.
Action:
Edit the parameter file to supply the table name.
OGG-00201: Column {0} not found
A column that is specified in the parameter file cannot be found in the table metadata.
Action:
Verify the column specification in the parameter file and in the table definition. Edit the parameter file accordingly.
OGG-00202: Record definition name missing
The DEF option for a TABLE parameter in a DEFGEN parameter file is missing a value that specifies the definitions template.
Action:
Specify the name of the definitions template.
OGG-00203: Unknown param for Table/File {0}
The TABLE or FILE parameter contains an unknown or invalid option.
Action:
Verify that the TABLE or FILE syntax is correct, and look for typographical errors. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-00204: Missing {0} specification
The specified parameter syntax is required.
Action:
Add the specified syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00205: Syntax error in size specification: {0}
The size given as input to this parameter is either invalid or supplied in an invalid format.
Action:
Specify a valid size specification for this parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-00206: Invalid {0} specification
The parameter contains an invalid input specification.
Action:
Specify a valid input specification for this parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-00207: Invalid {0} specification ({1})
The parameter contains an invalid input specification.
Action:
Specify a valid input specification for this parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-00208: Missing/invalid {0} specification
An input specification is missing or invalid for the parameter.
Action:
Specify a valid input specification for this parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-00209: Missing value for {0}
The specified parameter does not contain an input value.
Action:
Specify a value for this parameter. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00210: Invalid option for {0}
The parameter could not be parsed because it contains an invalid option.
Action:
Fix the syntax. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00211: Invalid option: {0}
The parameter could not be parsed because the specified option is invalid.
Action:
Fix the syntax. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00212: Invalid option for {0}: {1}
The parameter could not be parsed because the specified option is invalid.
Action:
Fix the syntax. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00213: Missing or invalid option for {0}
The parameter could not be parsed because a given option is either invalid or missing.
Action:
Check the syntax for the specified parameter. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00214: Value must be between {0,number,0} and {1,number,0}
The value is not valid.
Action:
Supply a value that is within the stated range.
OGG-00215: Value for {0} must be between {1,number,0} and {2,number,0}
The value given for the specified parameter is not valid.
Action:
Supply a value that is within the stated range.
OGG-00216: Value for {0} must be numeric, found {1}
An invalid value was given for the specified parameter.
Action:
Provide a numeric value. For valid values, see the Oracle GoldenGate reference documentation.
OGG-00217: Value for {0} must be numeric
An invalid value was given for the specified parameter.
Action:
Provide a numeric value. For valid values, see the Oracle GoldenGate reference documentation.
OGG-00218: Invalid value for {0}
An invalid value was given for the specified parameter.
Action:
Provide a valid value. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00219: Invalid value for {0}: {1}
The specified parameter contains an invalid value.
Action:
Fix the problem that is shown in the error in the message text. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-00220: Invalid number of arguments for {0} {1}
The specified parameter requires more option arguments than were provided.
Action:
Add the required arguments. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-00221: Invalid parameter {0} setting for option {1}: value: {2}.
The specified option of this parameter is set to an invalid value.
Action:
Specify a valid value. For more information, see the Oracle GoldenGate reference documentation.
OGG-00222: The column(s) used for the @RANGE filter for table {0} contain only NULL value(s) or missing value(s): There must be at least one non-NULL value present
The columns that are specified for the @RANGE filter contain only null values or column values are missing.
Action:
Specify columns that have values, or remove the columns specification so that @RANGE uses the KEYCOLS clause (if one exists) or the primary key as the columns on which to allocate the range. For more information, see the Oracle GoldenGate reference documentation for @RANGE.
OGG-00240: Already specified USERID or PASSWORD
There are duplicate USERID or PASSWORD database credentials specified in the parameter file. Only one set of credentials is allowed.
Action:
Remove the invalid credentials statements, and then restart the process.
OGG-00241: Error on key name {0}. Detail: {1}
There was an error parsing the encryption key name that is specified with the ENCRYPT option.
Action:
Fix the problem according to the error text that is given in the message.
OGG-00242: No KEYNAME given for BLOWFISH encryption
BLOWFISH encryption is specified, but the KEYNAME option is not included to specify the key name.
Action:
Add the KEYNAME option to the ENCRYPT clause, as in ENCRYPT BLOWFISH, KEYNAME key_name. For more information, see the Oracle GoldenGate security documentation.
OGG-00243: A KEYNAME was supplied but encryption was not specified
A KEYNAME parameter was specified without an accompanying ENCRYPT parameter.
Action:
Specify an ENCRYPT parameter with an optional algorithm, or remove the KEYNAME parameter. For help with syntax, see the Oracle GoldenGate security documentation.
OGG-00244: KEYNAME is not supported for GGS encryption
A KEYNAME parameter was specified incorrectly.
Action:
Remove the KEYNAME parameter or use valid ENCRYPT syntax. For help, see the Oracle GoldenGate security documentation.
OGG-00245: Not logged on, cannot execute statement
Login credentials were not provided with the SOURCEDB or TARGETDB to execute the query or stored procedure.
Action:
Add the SOURCEDB or TARGETDB parameter to the parameter file, including the USERID portion if required for your database. See the Oracle GoldenGate reference documentation for correct syntax for your database.
OGG-00246: Maximum input column length exceeded for col {0,number,0}
The size of the specified input or output parameter exceeds the supported length.
Action:
Shorten the length of the column to 10,000 bytes or less.
OGG-00247: Invalid query - all result columns must be named explicitly (col {0,number,0})
The process could not find the name of a column that is specified in an output parameter for SQLEXEC.
Action:
Check the Sybase error log to find the error that is associated with this SQLEXEC execution, and resolve the problem based on that message.
OGG-00248: Invalid query specified: {0}
The specified syntax is not a valid query for SQLEXEC.
Action:
Fix the query syntax and then restart the process. For help with using SQLEXEC, see the Oracle GoldenGate reference documentation.
OGG-00249: Cannot handle an input parameter of type {0}
The specified SQLEXEC statement in the parameter file contains an unsupported parameter or column type.
Action:
Specify a valid parameter or column type, and then restart the process. For help with using SQLEXEC, see the Oracle GoldenGate reference documentation.
OGG-00250: Stored procedure/function {0} does not exist
The SQLEXEC parameter refers to a stored procedure or function, but it does not exist in the database.
Action:
Check the spelling of the name of the procedure or function in the parameter file. Create the procedure, if needed, and then restart the process.
OGG-00251: Stored procedure/function {0} does not exist ({1})
The SQLEXEC parameter refers to a stored procedure or function, but it does not exist in the database.
Action:
Refer to the database error shown in the message, and check the spelling of the name of the procedure or function in the parameter file. Fix the problem according to the error message, and then restart the process.
OGG-00252: ODBC driver does not adequately support stored procedures (level={0,number,0})
The current version of the ODBC driver does not support stored procedures. Conformance level 2 is required.
Action:
Upgrade to the ODBC driver that has a conformance level 2 (SQL_OAC_LEVEL2).
OGG-00254: {0} is a deprecated parameter
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-00255: {0} value is too small, defaulting to minimum value ({1,number,0})
The value that is specified for the parameter is smaller than the allowable minimum value. The minimum value is being used.
Action:
None
OGG-00256: Missing or invalid cache item count
The value for the SPMAXCACHEITEMS parameter is missing.
Action:
Enter a valid value and then restart the process.
OGG-00257: Dynamic wildcarding is not supported for SOURCEISTABLE extract
WILDCARDRESOLVE DYNAMIC (the default) is specified, but SOURCEISTABLE is being used. This combination is not supported.
Action:
Set WILDCARDRESOLVE to IMMEDIATE.
OGG-00258: Missing table name specification
The name of the source table is missing from the TABLE or MAP parameter.
Action:
Specify the name of the source table.
OGG-00259: Schema name cannot be wildcarded
Oracle GoldenGate does not support wildcarded schema names in parameter files or commands.
Action:
Spell out the schema name in the parameter or command specification, and then restart the process.
OGG-00260: Tandem $Volume.Subvol Name can not be wildcarded
A wildcard has been specified as part of a file name. Oracle GoldenGate does not support the wildcarding of Guardian file names.
Action:
Change the parameter file to uniquely list each file by name.
OGG-00261: Immediate wildcard resolution is not currently supported for c-tree (use WILDCARDRESOLVE DYNAMIC)
WILDCARDRESOLVE IMMEDIATE is not supported for c-tree.
Action:
Change WILDCARDRESOLVE to DYNAMIC, and then restart the process.
OGG-00264: Unable to replace wildcard '*' with source table name.
The wildcard resolution failed.
Action:
Examine the wildcarded table names to make certain that the syntax is correct. Keep in mind that for source objects, you can use a partial name with a wildcard (like hq.t_*) but for target objects, you cannot use a wildcard with a partial name, because the asterisk is replaced with the name of the source object. Therefore, a target wildcarded specification can only be an asterisk (like rpt.*). For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-00265: Unable to replace wildcard '*' with owner name.
This message is deprecated.
Action:
None
OGG-00266: Could not open obey file {0} (err {1,number,0}, {2})
The process could not open the specified OBEY file because of the operating system error that is shown in the message text.
Action:
Fix the cause of the error (typically lack of read privilege) and then restart the process.
OGG-00267: Obey file {0} does not exist
The file that is specified with OBEY does not exist.
Action:
Compare the specified file name with the actual name of the obey file. Make the appropriate corrections, and then restart the process.
OGG-00268: Parameter unterminated
OBEY is used without a file name as input.
Action:
Use the correct syntax of OBEY file_name.
OGG-00269: No obey file specified
No file name is given for the OBEY parameter.
Action:
Specify the name of the obey file, and then restart the process.
OGG-00270: Nested obey files not supported
There are one or more nested OBEY files in the current OBEY file. OBEY statements cannot be nested within other OBEY statements.
Action:
Remove the nested OBEY statement, or merge the contents into the main OBEY statement. As an alternative to using nested OBEY files, you can use macros to call frequently used parameters, and then call the macro in the OBEY statement. For more information, see the Oracle GoldenGate documentation.
OGG-00271: Invalid options specified
The OBEY parameter contains more than one input file name.
Action:
Fix the syntax to specify only one file, and then restart the process.
OGG-00272: Invalid MACRO invocation ({0})
There is a syntax error in the invocation of the specified macro.
Action:
Correct the macro syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00273: Missing parameter name {1} in macro {0}
The parameter name is used in the body of MACRO but is not specified in the PARAMS list.
Action:
Add the parameter to the PARAMS list.
OGG-00274: Invalid MACRO invocation (macro {0}, {2,number,0} params specified, {1,number,0} required)
The invocation of the specified macro does not supply the same number of parameter values as the macro definition.
Action:
Edit the invocation syntax to specify the correct number of parameter values. Remember to separate values with commas.
OGG-00275: Quoted string not terminated in MACRO invocation
A macro is invoked in the parameter file, with a quoted string as a parameter value, but the ending quote marks are missing.
Action:
Add the ending quote marks.
OGG-00276: Missing open parentheses in MACRO {0} invocation
A macro is invoked in the parameter file, but a parentheses is missing.
Action:
Add the parentheses. For help, see the Oracle GoldenGate reference documentation.
OGG-00277: No definition found for MACRO {0}
A definition for the specified macro could not be found.
Action:
Define the macro within the MACRO parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-00278: Invalid MACRO definition (body too long)
The body of the macro definition is too long.
Action:
Shorten the body length to 99999 bytes or less.
OGG-00279: Invalid MACRO definition. The BEGIN keyword is not specified in the MACRO {0}.
Invalid MACRO definition. The BEGIN keyword is not specified in the MACRO {0}.
Action:
Add the BEGIN keyword. For help, see the Oracle GoldenGate reference documentation.
OGG-00280: Duplicate MACRO name {0}
There are two identical macro names in the parameter file.
Action:
Change one of the names to a different, unique value.
OGG-00281: Invalid MACRO name
The name in the MACRO statement is invalid.
Action:
Make certain that the name is one word (alphanumeric with no spaces) and begins with a valid macro character (# symbol or one defined with the MACROCHAR parameter). For additional help, see the Oracle GoldenGate reference documentation.
OGG-00282: Invalid MACRO definition
The macro definition is not valid.
Action:
Examine the macro syntax to find errors. For help, see the Oracle GoldenGate documentation.
OGG-00283: Duplicate macro parameter name {0} in the macro {1}.
The MACRO parameter contains a duplicate parameter name.
Action:
Remove the duplicate name or change it to a unique one.
OGG-00284: Too many parameters specified in macro
The PARAMS clause of the MACRO definition is too long.
Action:
Reduce the size of PARAMS to a maximum of 9999 bytes and no more than 99 parameters.
OGG-00285: Invalid macro parameter name in the MACRO {0}. ({1} - must begin with {2})
The name of the parameter is not preceded by the macro character.
Action:
Add the macro character that is shown in this error message. This character must precede all macro parameter names.
OGG-00286: Invalid trailing characters in MACRO
The MACRO statement ends with the wrong character.
Action:
Terminate the MACRO statement with the END keyword and a semicolon (END;).
OGG-00287: Invalid MACRO definition (params too long)
The PARAMS clause of the MACRO definition is too long.
Action:
Reduce the size of PARAMS to a maximum of 9999 bytes and no more than 99 parameters.
OGG-00288: Unrecognized option in DDL statement [{0}]
The specified option is not a valid one for the DDL parameter.
Action:
Specify a valid option. See the Oracle GoldenGate reference documentation for help with syntax.
OGG-00289: Unrecognized option in DDLOPTIONS [{0}]
The specified option is not a valid one for DDLOPTIONS.
Action:
Specify a valid option. See the Oracle GoldenGate reference documentation for help with syntax.
OGG-00290: Error decoding encrypted password in DDLOPTIONS DEFAULTUSERPASSWORD [{0}]
The encrypted password is not correct.
Action:
In GGSCI, encrypt the password with the ENCRYPT PASSWORD command and then copy and paste it into the DEFAULTUSERPASSWORD syntax. Check the Oracle GoldenGate reference documentation for the appropriate options to use with DEFAULTUSERPASSWORD and ENCRYPT PASSWORD.
OGG-00291: Password missing in DDLOPTIONS DEFAULTUSERPASSWORD
A clear-text or encrypted password is not specified for DEFAULTUSERPASSWORD.
Action:
Specify a password. See DDLOPTIONS in the Oracle GoldenGate reference documentation for parameter encryption options.
OGG-00292: Error code specified in DDLERROR, but no action (IGNORE, DISCARD, ABEND) [{0}]
An action for handling the error is not specified for the error code in the DDLERROR statement.
Action:
Specify one of the actions, and then restart the process. For more information, see DDLERROR in the Oracle GoldenGate reference documentation.
OGG-00293: Error action for DDLERROR already specified (IGNORE, DISCARD, ABEND) [{0}]
The DDLERROR parameter contains duplicate error-handling (action) specifications.
Action:
Remove the duplicate syntax, and then restart the process.
OGG-00294: Error code or DEFAULT already specified in DDLERROR [{0}]
The DDLERROR parameter contains duplicate specifications for the same error code or the DEFAULT keyword.
Action:
Remove the duplicate syntax, and then restart the process.
OGG-00295: Not a valid option for [MAXRETRIES numberOfSeconds] [{0}]
The RETRYOP option of DDLERROR has a MAXRETRIES option, but an invalid value was supplied.
Action:
Specify a value between 1 and 10000, and then restart the process.
OGG-00296: Not a valid option for [RETRYDELAY numberOfSeconds] [{0}]
An invalid value is given for RETRYDELAY.
Action:
Specify RETRYDELAY in the form of a number of seconds that represents the desired delay before retrying the operation.
OGG-00297: Error code or DEFAULT already specified in DDLERROR
The DDLERROR parameter contains duplicate specifications for the same error code or the DEFAULT keyword.
Action:
Remove the duplicate syntax, and then restart the process.
OGG-00298: error with property {1} in node {0}: {2}
An element or attribute is missing from the XML message. This is an internal error in Oracle GoldenGate Veridata Server.
Action:
Contact Oracle Support.
OGG-00299: invalid true/false value ({2}) for expected property {1} in node {0}
A boolean attribute in an XML message does not have a true/false value. This is an internal error in Oracle GoldenGate Veridata Server.
Action:
Contact Oracle Support.
OGG-00300: maximum length exceeded ({2,number,0}), property {1} in node {0}
An XML message has an element or attribute that exceeds the defined limit. This is an internal error in Oracle GoldenGate Veridata Server.
Action:
Contact Oracle Support.
OGG-00301: could not find expected property {1} for {0}
An XML message is missing an expected attribute. This is an internal error in Oracle GoldenGate Veridata Server.
Action:
Contact Oracle Support.
OGG-00302: Invalid compare files
A report, trace, status, or parameter file name in an XML message cannot be opened. This is an internal error in Oracle GoldenGate Veridata Server.
Action:
Contact Oracle Support.
OGG-00303: {0}
The syntax of the specified parameter is incorrect.
Action:
Check for spelling errors, or see the Oracle GoldenGate reference documentation for the correct syntax.
OGG-00304: {0}
This is an informational message that displays the result of checking permission.
Action:
None
OGG-00306: Directory name missing
This message is deprecated.
Action:
None
OGG-00307: user name missing
This message is deprecated.
Action:
None
OGG-00308: Missing end quote
This message is deprecated.
Action:
None
OGG-00309: Delimiter value missing
This message is deprecated.
Action:
None
OGG-00310: Extension specifier missing
This message is deprecated.
Action:
None
OGG-00311: Did not recognize argument: {0}.
This message is deprecated.
Action:
None
OGG-00312: Closing parenthesis missing for {0}
This message is deprecated.
Action:
None
OGG-00313: Opening parenthesis missing for {0}
This message is deprecated.
Action:
None
OGG-00314: Cannot specify COLUMNS or EXCLUDECOLUMNS more than once
This message is deprecated.
Action:
None
OGG-00315: Delimiter must be a single character
This message is deprecated.
Action:
None
OGG-00316: Delimiter must be a decimal value or enclosed in single quotes
This message is deprecated.
Action:
None
OGG-00317: Delimiter must be between 1 and 127
This message is deprecated.
Action:
None
OGG-00318: No columns specified for trigger
This message is deprecated.
Action:
None
OGG-00319: Invalid rule specification
A rule in the ACCESSRULE parameter is not formatted properly.
Action:
Correct the syntax and restart Manager. Note that this parameter is deprecated. For more information, contact Oracle Support.
OGG-00321: Invalid or missing argument in run command
An argument in a Manager parameter is either missing or invalid.
Action:
Correct the parameter syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00322: Missing group specifier
A process was not specified for the specified parameter to act upon.
Action:
This parameter accepts values of ER, EXTRACT, or REPLICAT. For more information, see the Oracle GoldenGate reference documentation.
OGG-00323: Missing group specification for {0}
A process was not specified for the specified parameter to act upon.
Action:
This parameter accepts values of ER, EXTRACT, or REPLICAT. For more information, see the Oracle GoldenGate reference documentation.
OGG-00324: Must specify EXTRACT, REPLICAT or ER for group type
A process was not specified for the specified parameter to act upon.
Action:
This parameter accepts values of ER, EXTRACT, or REPLICAT. For more information, see the Oracle GoldenGate reference documentation.
OGG-00325: Must specify ER, EXTRACT, or REPLICAT for {0}
A process was not given for the specified parameter to act upon.
Action:
This parameter accepts values of ER, EXTRACT, or REPLICAT. For more information, see the Oracle GoldenGate reference documentation.
OGG-00326: Missing file set parameter ({0})
The process was not given a set of file names to act upon.
Action:
Make certain that any parameters in the Manager parameter file that require file names contain them in a valid format. For help, see the Oracle GoldenGate reference documentation.
OGG-00327: Too many {0} entries (max is {1,number,0})
There are too many instances of the specified parameter.
Action:
Reduce the instances of this parameter to the permitted number. You may be able to combine options from these multiple instances into fewer instances or one instance of this parameter. For more information, see the Oracle GoldenGate reference documentation.
OGG-00328: The maximum number of {0} parameters allowed is {1,number,0}
There are too many instances of the specified parameter.
Action:
Reduce the instances of this parameter to the permitted number. You may be able to combine options from these multiple instances into fewer instances or one instance of this parameter. For more information, see the Oracle GoldenGate reference documentation.
OGG-00329: Invalid protocol ({0})
An unsupported communications protocol was specified.
Action:
Specify either TCP or UDP as the protocol.
OGG-00330: Ending port must be greater than or equal to starting port ({0})
The specified port number at the end of the DYNAMICPORTLIST range of ports is a lower value than the one at the beginning of the range.
Action:
Edit the parameter to specify a valid range that increases in value. Correct: 7830-7835 ; Incorrect: 7835-7830.
OGG-00331: Invalid ending port number ({0})
The specified port number at the end of the DYNAMICPORTLIST range of ports is not valid.
Action:
Edit the Manager parameter file to specify a valid port range, and then restart Manager. An example is 7830-7835.
OGG-00332: Invalid port range ({0})
An invalid range of port numbers is specified for the DYNAMICPORTLIST parameter in the Manager parameter file.
Action:
Specify a valid range of port numbers. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-00333: Invalid port number ({0})
The TCP/IP port number that is specified in the Manager parameter file is not a valid port number.
Action:
Specify a valid, unused port number for the PORT parameter in the Manager parameter file, and then restart Manager.
OGG-00334: Must specify {0} or {1}
One of the two required parameters must be included in the parameter file, but not both.
Action:
Add the required parameters, and then restart the process.
OGG-00335: Invalid specifier {0} for AFTER option, expected DAYS or HOURS
The PURGEOLDTASKS parameter is being used with the AFTER option, but the syntax is not correct.
Action:
Specify AFTER n {DAYS │ HOURS}.
OGG-00336: Must specify DAYS or HOURS for AFTER option
The PURGEOLDTASKS parameter is being used with the AFTER option, but the syntax is not correct.
Action:
Use one of the time specifiers in this syntax: AFTER n {DAYS │ HOURS}. Restart the process after correcting the syntax.
OGG-00337: Missing history table name
The PURGEOLDHISTORY parameter is being used, but the name of the DDL history table is not the default name, and the user-defined name is not specified with the DDLTABLE parameter in the GLOBALS file.
Action:
Specify the name of the DDL history table with DDLTABLE, and then restart the process.
OGG-00338: SQL clause not specified
The SQL for the QUERY clause is missing.
Action:
Specify the query in the QUERY clause. For help with syntax, see SQLEXEC in the Oracle GoldenGate reference documentation.
OGG-00339: Invalid interval for SQLEXEC
The interval that is defined with the EVERY option is not a whole, positive integer.
Action:
Change the value to 1 or greater, and then restart the process.
OGG-00340: SQLEXEC interval must be 1 or greater
The interval that is defined with the EVERY option is not a whole, positive integer.
Action:
Change the value to 1 or greater, and then restart the process.
OGG-00341: Error in SQLEXEC clause, id {0}: Missing/invalid argument for {1}
An argument is missing or incorrect in the specified syntax.
Action:
Check for a typographical error, and refer to the SQLEXEC reference documentation for help with syntax.
OGG-00342: Error in SQLEXEC clause, id {0}: Invalid value for {1} option ({2})
The specified option contains an invalid value.
Action:
Check the SQLEXEC documentation in the Oracle GoldenGate reference documentation for valid values.
OGG-00343: Error in SQLEXEC clause, id {0}: Invalid TRACE options
The TRACE syntax is incorrect.
Action:
Specify TRACE with either ALL to trace input and output parameters for each invocation of the procedure or query (the default) or ERROR to trace the parameters for each invocation only after a SQL error occurs.
OGG-00344: Error in SQLEXEC clause, id {0}: Unrecognized option for SQLEXEC: {1}
The SQLEXEC statement contains the specified incorrect syntax.
Action:
Check for a typographical error, and refer to the SQLEXEC reference documentation for help with syntax.
OGG-00345: Error in SQLEXEC clause, id {0}: SPNAME or QUERY is required
The SQLEXEC statement does not contain a clause that specifies whether it will execute a procedure (SPNAME) or a query (QUERY).
Action:
Add the SPNAME or QUERY clause, based on syntax for SQLEXEC in the Oracle GoldenGate reference documentation.
OGG-00346: Error in SQLEXEC clause, id {0}: ID is required when QUERY specified
The ID specification is missing from the SQLEXEC statement. It is required so that a name can be used by Oracle GoldenGate to reference the column values returned by the query.
Action:
Add the ID clause. For help, see SQLEXEC in the Oracle GoldenGate reference documentation.
OGG-00347: Error in SQLEXEC clause, id {0}: Invalid PARAMS specification ({1})
The specified SQLEXEC clause contains a PARAMS specification that has a syntax error.
Action:
Fix the PARAMS clause according to the syntax listed for SQLEXEC in the Oracle GoldenGate reference documentation.
OGG-00348: Error in SQLEXEC clause, id {0}: Missing/invalid PARAMS specification for stored proc {1}
The specified SQLEXEC clause requires a PARAMS specification to supply input parameters.
Action:
Add a PARAMS clause, or fix any syntax errors in the existing one. For help with syntax, see SQLEXEC in the Oracle GoldenGate reference documentation.
OGG-00349: Error in SQLEXEC clause, id {0}: Missing equals sign for param specifier ({1})
The parameter specifier must be in the format of parameter = value.
Action:
Fix the error, and then restart the process. For more help with syntax, see the Oracle GoldenGate reference documentation.
OGG-00350: Error in SQLEXEC clause, id {0}: Invalid parameter name: {1}
There is an invalid parameter in the specified SQLEXEC clause.
Action:
Check for a typographical error in the parameter name. For valid parameters, see SQLEXEC in the Oracle GoldenGate reference documentation. Fix the syntax, and then restart the process.
OGG-00351: Error in SQLEXEC clause, id {0}: Error in PARAM clause for {1}
There is a syntax error in the specified SQLEXEC clause.
Action:
Fix the syntax for the specified parameter in the PARAMS clause, and then restart the process. For help, see SQLEXEC in the Oracle GoldenGate reference documentation.
OGG-00352: Error in SQLEXEC clause, id {0}: Missing required parameter: {1}
A required parameter is missing from the specified SQLEXEC clause.
Action:
Check the Oracle GoldenGate reference documentation for the correct SQLEXEC syntax and required options.
OGG-00353: Could not find stored procedure param ({0})
A parameter is specified in a PARAMS clause of a SQLEXEC statement but cannot be found in the procedure.
Action:
Compare the procedure with the PARAMS clause, and either add the required parameter to the procedure, or remove it from the SQLEXEC statement.
OGG-00354: Invalid BEFORE column: {0}
An invalid column name was specified.
Action:
Specify the correct column name in your input.
OGG-00355: Programming error registering BEFORE image resource
A before image was registered twice to handle an update statement.
Action:
This is an internal error. Contact Oracle Support.
OGG-00356: Must specify COMPARE before destination files or TABLE entries
This message is deprecated.
Action:
None
OGG-00357: Missing equal sign
An equal sign is missing from the DDL history.
Action:
Contact Oracle Support.
OGG-00360: {0} cannot be used with {1}
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-00361: Must specify both {0} and {1}
Both of the specified parameters must be included in the parameter file.
Action:
Add the required parameters, and then restart the process.
OGG-00362: {0} must be specified before {1}
The order of the parameters in the parameter file is incorrect.
Action:
Change the order of the parameters, and then restart the process.
OGG-00363: {0} must occur before SOURCEDEFS/TARGETDEFS entries to have an effect. Parameter ignored.
The NUMFILES or ALLOCFILES parameter is specified after the SOURCEDEFS or TARGETDEFS parameter.
Action:
Place NUMFILES or ALLOCFILES before SOURCEDEFS or TARGETDEFS in the parameter file.
OGG-00364: REPERROR clause {0} is not valid with DEFAULT/DEFAULT2. Parameter ignored.
The REPERROR syntax is incorrect.
Action:
Correct the syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00365: {0} cannot be specified more than once per TABLE
The specified option can only be used once in a TABLE statement.
Action:
Remove any extra instances of this option.
OGG-00366: Invalid column specified in {0}: {1}
The specified column does not exist. This message can apply to any of several different parameters that take a column name as input.
Action:
Check the parameter file for parameters or options that take a column name as input, and verify that the name(s) are valid. Specify a valid name or remove the parameter.
OGG-00367: Error in {0} list: {1}
There is a syntax error in the specified parameter, such as a missing double quote.
Action:
Check and correct the syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00368: Already specified column list for current table
There are two or more COLS clauses for the same specified table.
Action:
Remove all but one COLS clause for this table.
OGG-00369: Error in token clause for {0}
The TOKENS clause of the specified parameter contains an error in syntax.
Action:
Fix the syntax error. For correct syntax, see the Oracle GoldenGate reference documentation.
OGG-00370: Invalid function definition
There is a syntax error in the definition of a column function, such as a missing parenthesis or an unmatched quote mark.
Action:
Fix the syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00371: Function definition exceeds max length of {0,number,0}
This message is deprecated.
Action:
None
OGG-00372: Missing TOKEN value/function
The TOKENS clause of TABLE does not contain a value.
Action:
Supply a value that can be a constant that is enclosed within double quotes or the result of an Oracle GoldenGate column-conversion function.
OGG-00373: Bad TOKEN name
The name of the token in the TOKENS clause is invalid.
Action:
Supply an ASCII alphanumeric name of any length. TOKENS is not case-sensitive.
OGG-00374: Expected TOKEN name
The name of the token in the TOKENS clause is missing.
Action:
Supply an ASCII alphanumeric name of any length. TOKENS is not case-sensitive.
OGG-00375: Error in FILTER clause
The FILTER statement in TABLE or MAP contains a syntax error.
Action:
Correct the syntax error. For more information, see the TABLE and MAP reference documentation.
OGG-00376: FILTER condition missing
The FILTER statement in TABLE or MAP does not contain a filter expression.
Action:
Add a filter expression. For more information, see the TABLE and MAP reference documentation.
OGG-00377: Query/Table {0} already identified
Table metadata is resolved, but the table is specified by the QUERY parameter. This parameter is deprecated.
Action:
Remove the QUERY parameter.
OGG-00378: Missing query statement
The query statement is missing from the QUERY parameter. This parameter is deprecated.
Action:
Add the query statement.
OGG-00379: Missing query name
The query name is missing from the QUERY parameter. This parameter is deprecated.
Action:
Add the query name.
OGG-00380: TIMEZONE must be LOC, GMT or SOURCE
An invalid option is specified for TIMEZONE.
Action:
Provide a value that is one of 'LOC', 'SOURCE', or 'GMT'.
OGG-00381: Invalid option
A parameter contains an invalid argument.
Action:
Edit the parameter file to specify the correct argument. For help, see the Oracle GoldenGate reference documentation.
OGG-00382: Invalid option for {0}
The specified parameter contains an invalid option.
Action:
Specify the correct option syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00383: Invalid parameter value
The specified parameter contains an invalid value.
Action:
Specify the correct value. For help, see the Oracle GoldenGate reference documentation.
OGG-00384: Parameter {0} must not have the schema name but only the table name part.
Schema values are not allowed when specifying the table name for this parameter.
Action:
Remove the schema name from the table name.
OGG-00385: Expecting table name after parameter {0}.
The specified parameter requires a table name.
Action:
Specify the name of the table to be used with the parameter.
OGG-00386: Expecting schema name after {0}
The GGSCHEMA parameter in the GLOBALS file does not specify the schema that contains the database objects that support DDL synchronization for Oracle.
Action:
Edit the GLOBALS file and supply the DDL schema name.
OGG-00387: Expecting service name after {0}
The MGRSERVNAME parameter in the GLOBALS file does not contain a Windows service name for Manager.
Action:
Edit the GLOBALS file and supply the service name of Manager in the MGRSERVNAME parameter.
OGG-00388: Missing argument (line {0,number,0})
The process is generating a BCP format file to load data into a SQL Server table based on a template file, but the template file name is missing.
Action:
Provide a template file name with the GENLOADFILES parameter.
OGG-00389: Invalid files section entry (line {0,number,0})
The section on the specified line of the template contains an invalid entry.
Action:
Specify a valid file entry. For help, see GENLOADFILES in the Oracle GoldenGate reference documentation.
OGG-00390: {1} entry missing from template (line {0,number,0})
The specified section is missing from the control file template.
Action:
Specify a valid entry. For help, see GENLOADFILES in the Oracle GoldenGate reference documentation.
OGG-00391: Cannot replace template {1}. Replacement too big. (line {0,number,0})
While generating a BCP format file for loading a SQL Server table based on a template file, the startup template parameter is too long.
Action:
Correct the template parameter that is shown in the message.
OGG-00392: Bad delimiter specified
An invalid delimiter value is specified for the DELIMITER parameter in FORMATASCII.
Action:
Specify a valid delimiter. For help, see the Oracle GoldenGate reference documentation.
OGG-00393: Missing delimiter
The DELIMITER parameter in FORMATASCII is missing the delimiter specification.
Action:
Specify the delimiter. For help, see the Oracle GoldenGate reference documentation.
OGG-00394: Command is too long
A command in the parameter file is too long.
Action:
Look for a syntax error like a missing delimiter or white space.
OGG-00395: Argument is too long
A command argument in the parameter file is too long.
Action:
Look for a syntax error like a missing delimiter or white space.
OGG-00396: Command '{0}' not terminated by semi-colon
A command is not terminated by a semi-colon.
Action:
Add the semi-colon.
OGG-00397: Missing {1} option for {0}
The specified parameter requires the specified option.
Action:
Add the option and then restart the process. See the Oracle GoldenGate reference documentation for help with syntax.
OGG-00398: String before WITH in DDLSUBST cannot be empty
The DDLSUBST statement does not contain the string in the source DDL that is to be replaced in the target DDL.
Action:
Supply a search string in this clause: DDLSUBST search_string WITH new_string. For more help, see the Oracle GoldenGate reference documentation.
OGG-00399: Missing string after WITH in DDLSUBST
The string that replaces the source string in the target DDL is missing.
Action:
Supply a replacement string in this clause: DDLSUBST search_string WITH new_string.
OGG-00400: DDLSUBST parsing error: {0}
The specified error occurred while processing the DDLSUBST parameter.
Action:
Fix the problem based on the reported error, and then restart the process.
OGG-00401: DDL Replication must be enabled in order to use {0} (use DDL statement earlier)
DDL replication is not enabled.
Action:
Install (if applicable) and enable DDL replication. For help, see the Oracle GoldenGate administration documentation.
OGG-00402: WILDCARDRESOLVE parameter must be set to DYNAMIC when DDL replication is enabled.
The WILDCARDRESOLVE parameter is not set to DYNAMIC.
Action:
Set WILDCARDRESOLVE to DYNAMIC and restart the process.
OGG-00403: There can be only one DDL filtering statement. If DDL filter is long, use ampersand (&) sign to continue it on another line.
The parameter file contains more than one DDL statement.
Action:
Combine the filtering in the statements into one DDL statement. See the Oracle GoldenGate reference documentation for help with syntax. You can divide a long DDL statement onto separate lines by using an ampersand at the end of each line.
OGG-00405: {0} must be used with DDL replication.
The specified parameter is required when using DDL replication.
Action:
Add the parameter, and then restart the process. See the Oracle GoldenGate reference documentation for more information about this parameter.
OGG-00406: DDL replication is not compatible with {0} parameter.
The specified parameter cannot be used when DDL replication is enabled.
Action:
Remove the parameter from the parameter file, and then restart the process.
OGG-00407: Not a valid error code for DDLERROR [{0}]
The specified error code is not valid.
Action:
Specify a valid error code, or use the DEFAULT option. See the Oracle GoldenGate reference documentation for correct DDLERROR syntax.
OGG-00408: RETRYOP not specified prior to RETRYDELAY
RETRYOP MAXRETRIES must be specified before RETRYDELAY in the DDLERROR syntax.
Action:
Fix the syntax. See the Oracle GoldenGate reference documentation for correct DDLERROR syntax.
OGG-00409: Error code or DEFAULT not specified prior to RETRYOP
The DDLERROR parameter does not specify an error type.
Action:
Fix the syntax by providing an error type. See the Oracle GoldenGate reference documentation for correct DDLERROR syntax.
OGG-00410: Parameter {0} value is limited by the DBMS to a maximum of {1,number,0}.
The number specified in MAXSQLSTATEMENTS is greater than the maximum active statements allowed by the underlying database.
Action:
Adjust the MAXSQLSTATEMENTS value to be at most the maximum number supported by the database.
OGG-00411: Must be PURGE or APPEND
The file specification is missing the PURGE or APPEND option.
Action:
Specify the appropriate option.
OGG-00412: Invalid DISCARDFILE option. Valid options are PURGE, APPEND, MAXBYTES, or MEGABYTES
The DISCARDFILE parameter contains an invalid option.
Action:
Valid options are APPEND or PURGE and MAXBYTES or MEGABYTES.
OGG-00413: {0} must include both date and time
An incomplete timestamp is supplied in the parameter file.
Action:
Edit the parameter file to include both a date and time in the timestamp, in the format of YYYY-MM-DD HH:MI:SS[.CCCCCC].
OGG-00414: Invalid {0} format
An invalid date and time are specified for the BEGIN or END parameter.
Action:
Specify a valid date and time.
OGG-00415: {0}
The user exit contains a bad argument.
Action:
Supply a valid argument. See the Oracle GoldenGate reference documentation for user exit syntax.
OGG-00416: Value for {0} must be greater than 0
The value for the specified parameter must be greater than zero.
Action:
Supply a valid value.
OGG-00417: Value for {0} must be greater than or equal to 0
The value for the specified parameter must be greater than, or equal to, zero.
Action:
Supply a valid value.
OGG-00418: Error encountered when verifying deferrable constraint
The state of the target constraints could not be verified.
Action:
Look for a subsequent error message that states the reason for the failure.
OGG-00419: TARGET doesn't have deferrable constraint when HANDLETPKUPDATE specified
The parameter file contains the HANDLETPKUPDATE parameter, and the integrity constraints on the target tables are not set to DEFERRABLE. If the target constraints are not DEFERRABLE, Replicat handles the errors according to existing rules specified with the HANDLECOLLISIONS and REPERROR parameters, or else it abends.
Action:
Create the constraints on the target tables as DEFERRABLE INITIALLY IMMEDIATE.
OGG-00420: The value for {0} is too long
The specified parameter value is too long to fit into the internal buffer that is assigned to it at runtime.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-00422: {0} specification must be enclosed in quotes
The specified parameter must be in quotes.
Action:
Edit the parameter file to add the quotes. For syntax help, see the Oracle GoldenGate reference documentation.
OGG-00423: Could not find definition for {0}
The process could not find a definition for the specified table when building the object cache on startup.
Action:
Remove the table from the TABLE and/or MAP parameter. If using wildcards, you can exclude the table with TABLEEXCLUDE or MAPEXCLUDE.
OGG-00424: {0}, table {1} does not exist in target database
Replicat could not find metadata for the specified table in the target database. The table is listed in the MAP statement either explicitly or as the result of a wildcard.
Action:
Remove the table from the MAP parameter. If using wildcards in that parameter, you can exclude the table with MAPEXCLUDE.
OGG-00425: No DB login established to retrieve a definition for table {0}
The DBLOGIN command must be issued before issuing commands that interact with the database or sourcedefs must be used.
Action:
Issue DBLOGIN or provide sourcedefs or use automatic metadata in trail.
OGG-00427: Must be IGNORE, DISCARD, ABEND, EXCEPTION, TRANSABORT, TRANSDISCARD, TRANSEXCEPTION or RETRYOP
The response is not set correctly in a REPERROR statement.
Action:
See the Oracle GoldenGate reference documentation for REPERROR syntax.
OGG-00428: Missing error number for REPERROR
The error specification is either missing or invalid.
Action:
Supply a valid SQL error number, a user-defined error that is set with RAISEERROR, or the DEFAULT keyword. For more information, see the MAP and REPERROR reference documentation.
OGG-00429: Must be error number or DEFAULT
An invalid argument was supplied for the error specification.
Action:
Supply a valid SQL error number, a user-defined error that is set with RAISEERROR, or the DEFAULT keyword. For more information, see the MAP and REPERROR reference documentation.
OGG-00430: RESET not valid REPERROR on MAP statement
REPERROR is being used in a MAP statement, and the RESET option is included. This option is only supported for REPERROR at the root level of the parameter file (as a standalone REPERROR statement).
Action:
Remove RESET from REPERROR in the MAP file.
OGG-00431: Unable to set {0}
The specified option for RMTHOST is not valid.
Action:
Correct the syntax. For help, see the Oracle GoldenGate reference documentation.
OGG-00432: Unable to set {0} value to {1,number,0}
The specified parameter does not support the given value.
Action:
Specify a valid value. For help, see the Oracle GoldenGate reference documentation.
OGG-00433: No RMTHOST has been specified yet
The parameter file does not contain the RMTHOST parameter.
Action:
Add the RMTHOST parameter.
OGG-00434: Missing file name
A file name is expected for EXTFILE or RMTFILE.
Action:
Specify a file name for this parameter.
OGG-00435: Valid options for {0} are: {1}.
An invalid argument was specified for EXTTRAIL, EXTFILE, RMTTRAIL, or RMTFILE.
Action:
See the Oracle GoldenGate reference guide for valid options for the specified parameters.
OGG-00436: Table {0} is not defined
The process could not find metadata for the specified table. The DEFGEN utility probably was not run for the specified table, or it was run but the definitions were not added to the existing source- or target-definitions file.
Action:
Make certain that the table is specified correctly in the TABLE or MAP parameter. If so, then run DEFGEN for the table and add those definitions to the file that is specified with SOURCEDEFS or TARGETDEFS.
OGG-00437: Record definition {0} is not defined
The process could not find metadata for the specified table that is in a DDL operation. The DEFGEN utility probably was not run for the specified table, or it was run but the definitions were not added to the existing source- or target-definitions file.
Action:
Make certain that the table is specified correctly in the TABLE or MAP parameter. If so, then run DEFGEN for the table and add those definitions to the file that is specified with SOURCEDEFS or TARGETDEFS.
OGG-00438: Error retrieving GGS logtrail next checkpoint
The process could not open the next checkpoint.
Action:
Make certain that the process has read and write privileges on the checkpoint. Make certain that the file that caused the error is not corrupted. If the process cannot open the next checkpoint, contact Oracle Support.
OGG-00442: Cannot support DB checkpointing for this database.
The checkpoint table feature (database checkpointing) is not supported for the current database. The ADD CHECKPOINTTABLE command might have been issued, or parameters that support a checkpoint table might exist.
Action:
Remove the CHECKPOINTTABLE parameter from the GLOBALS file, if present. Issue ADD REPLICAT without any CHECKPOINTTABLE options.
OGG-00443: Get checkpoint error
The reporting process encountered an I/O error while reading the checkpoint file.
Action:
Check the health of the file system where Oracle GoldenGate is installed. Correct any problems that could cause this error, and then restart the process. If the problem persists, contact Oracle Support.
OGG-00444: Get next checkpoint error
The reporting process encountered an I/O error while reading the checkpoint file.
Action:
Check the health of the file system where Oracle GoldenGate is installed. Correct any problems that could cause this error, and then restart the process. If the problem persists, contact Oracle Support.
OGG-00445: Detected migrated group {0}, updating DB checkpoint dir from {1} to {2}
The Replicat checkpoint table in the database was pointing to an invalid directory for the checkpoint file that is stored on disk. Every time that Replicat updates the checkpoint table, it verifies the location of the checkpoint file. If there is a mismatch, Replicat updates the table with the correct location. This is an informational message to notify you that the directory for the checkpoint file was the first value shown in the message, but now is the second one shown.
Action:
None
OGG-00446: {0}
An error was encountered while processing the checkpoint file.
Action:
Contact Oracle Support.
OGG-00447: Could not find definition for {0}, error {1}
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-00448: DDL record definition found in sourcedefs file(s) will be ignored, continuing
DDL was executed on a table that has a source definitions file specified for it with the SOURCEDEFS parameter. This is informational only.
Action:
None
OGG-00449: Target not resolved for source {0}.
The process could not find the specified target table.
Action:
Create the target table or use IGNOREMISSINGTABLES in the DDLERROR parameter.
OGG-00450: Source sequence {0} cannot be resolved in any MAP statement
The process could not find the specified target sequence.
Action:
Create the target sequence or use IGNOREMISSINGTABLES in the DDLERROR parameter.
OGG-00451: Source sequence {0} could not be resolved, error [{1}].
The specified sequence could not be found.
Action:
Make certain the sequence exists.
OGG-00452: Target sequence {0} could not be resolved, error [{1}].
The process could not find the specified target sequence.
Action:
Create the target sequence or use IGNOREMISSINGTABLES in the DDLERROR parameter.
OGG-00453: DDL Replication is not supported for this database
Oracle GoldenGate does not support DDL replication for the current database.
Action:
Remove any parameters that apply to DDL replication. See the Oracle GoldenGate reference documentation for more information.
OGG-00454: Cannot initialize DDL/sequence processing, error [{0}]
Oracle GoldenGate could not initiate DDL processing because the specified error occurred.
Action:
If you cannot resolve the problem based on the error that is returned, contact Oracle Support.
OGG-00455: Problem in resolving {0}: {1}, try to fix this issue in order to avoid possible fatal error
The process could not resolve the metadata for the specified table. The cause of the problem is stated in the message text.
Action:
Try to resolve the problem to avoid a fatal error. If you cannot resolve the problem, contact Oracle Support.
OGG-00456: Object that is not replicated. The object "{0}" was renamed to "{1}" even though DDLOPTIONS NOCROSSRENAME is in effect. This may result in new (renamed) objects not processed correctly.
The DDLOPTIONS parameter includes NOCROSSRENAME, and the table was renamed to one that is included in a TABLE statement (probably because of a wildcard). This can cause the object to be replicated incorrectly, depending on whether a target exists and how it is defined. This might also cause data to be replicated that you do not want to be replicated.
Action:
Ensure that the source and target tables match, for both the original and renamed tables. If you cannot resolve the problem, contact Oracle Support.
OGG-00457: Object {0} was renamed even though it's marked excluded with NORENAME. Renamed object (if included) may or may not be picked up (you should not rename objects marked with NORENAME)
The object is specified in a TABLEEXCLUDE parameter that has the NORENAME option enabled, and the table was renamed to one that is included in a TABLE statement (probably because of a wildcard). This can cause the object to be replicated incorrectly, depending on whether a target exists and how it is defined. This might also cause data to be replicated that you do not want to be replicated.
Action:
Ensure that the source and target tables match, for both the original and renamed tables. If you cannot resolve the problem, contact Oracle Support.
OGG-00458: Cannot find metadata property {0}. DDL metadata [{1}]
A metadata property that Oracle GoldenGate needs to resolve is not present.
Action:
Contact Oracle Support.
OGG-00459: Cannot find metadata property {1} for object {0}. DDL metadata [{2}]
A metadata property that Oracle GoldenGate needs to resolve the specified object is not present.
Action:
Contact Oracle Support.
OGG-00461: Cannot find metadata property {1} for column {0}. DDL metadata [{2}]
A metadata property that Oracle GoldenGate needs to resolve the specified object is not present.
Action:
Contact Oracle Support.
OGG-00462: Error in substitute string in DDL statement. DDL metadata [{0}]
Oracle GoldenGate could not perform string substitution in the DDL statement.
Action:
Contact Oracle Support.
OGG-00463: Cannot substitute string in DDL statement, old statement = [{0}], new statement is too big. DDL metadata [{1}]
The size of the substitute string that is specified in the DDLSUBST parameter is larger than the size that the database supports.
Action:
Supply a string that is a supported size.
OGG-00464: Cannot remove DDL comments in DDL statement. DDL metadata [{0}]
Oracle GoldenGate could not parse the DDL statement for comments.
Action:
Contact Oracle Support.
OGG-00465: Cannot restructure string in DDL statement for {0}, statement = [{1}]. DDL metadata [{2}]
Oracle GoldenGate could not process internal changes to the DDL data.
Action:
Contact Oracle Support.
OGG-00466: Cannot restructure string in DDL statement for {0}. DDL metadata [{1}]
Oracle GoldenGate could not process internal changes to the DDL data.
Action:
Contact Oracle Support.
OGG-00467: Wrong parameter when getting ddl property. DDL metadata [{0}]
An unexpected parameter was encountered when processing DDL data.
Action:
Contact Oracle Support.
OGG-00468: Wrong format of ddl property string (missing equal sign). DDL metadata [{0}]
The DDL is of a format that is not known to or supported by Oracle GoldenGate.
Action:
Contact Oracle Support.
OGG-00469: Wrong format of ddl property string (missing starting delimiter). DDL metadata [{0}]
The DDL is of a format that is not known to or supported by Oracle GoldenGate.
Action:
Contact Oracle Support.
OGG-00470: Wrong format of ddl property string (missing end delimiter). DDL metadata [{0}]
The DDL is of a format that is not known to or supported by Oracle GoldenGate.
Action:
Contact Oracle Support.
OGG-00471: DDL metadata item too big. DDL metadata [{0}]
The DDL data exceeds the allocated space.
Action:
Contact Oracle Support.
OGG-00472: Expected number in metadata, can't convert it. DDL metadata [{0}]
A number was expected for this metadata, but it was not in numerical format.
Action:
Contact Oracle Support.
OGG-00473: Error in restructure string in DDL statement when removing DDL signature string, trail record = [{0}]
The string could not be processed.
Action:
Contact Oracle Support.
OGG-00474: Cannot restructure string in DDL statement when removing DDL signature string, statement = [{0}]. DDL metadata [{1}]
The string could not be processed.
Action:
Contact Oracle Support.
OGG-00475: DDL is too large. DDL is ignored. Details: {0}.
The DDL exceeds 2 MB, the maximum that is supported by Oracle GoldenGate.
Action:
Apply the DDL manually.
OGG-00476: Gathering metadata for {0} not successful even though object was resolved, retrying [{1,number,0}] times with {2,number,0} second interval
Extract could not obtain metadata for the specified object, and is trying again.
Action:
Extract may produce other warning or error messages prior to or in between these messages. Examine the Extract report file for more information. If the problem persists, contact Oracle Support.
OGG-00477: Successfully added TRAN DATA for table {0}.{1}, operation [{2}]
Extract successfully added supplemental log data for the table.
Action:
None
OGG-00479: Successfully deleted TRAN DATA for [{0}] DDL operation, table {1}.{2}, operation [{3}]
Extract successfully deleted the supplemental log data for the table. Extract sometimes creates temporary supplemental log data groups, and those are eventually deleted.
Action:
None
OGG-00480: Derived object name "{0}" mapped to "{1}"
The specified derived object name was mapped to the target name, because a MAP statement exists for the derived object.
Action:
None
OGG-00482: DDL found, operation [{0}]
A DDL operation was found in the data source.
Action:
None
OGG-00483: DDL operation successful
Oracle GoldenGate successfully processed a DDL operation.
Action:
None
OGG-00484: Executing DDL operation{0,choice,0#│1# trying again due to RETRYOP parameter}
Oracle GoldenGate is executing a DDL operation.
Action:
None
OGG-00485: Comments removed (REMOVECOMMENTS {0}), DDL operation remained the same
DDLOPTIONS contains the REMOVECOMMENTS option, but the DDL contains no comments.
Action:
None
OGG-00486: Comments removed from DDL operation (REMOVECOMMENTS {0}), new operation [{1}]
The comments were removed from the DDL operation according to the DDLOPTIONS parameter with REMOVECOMMENTS.
Action:
None
OGG-00487: DDL operation included [{0}], optype [{1}], objtype [{2}], objowner "{3}", objname "{4}"
The specified DDL operation was included in DDL replication because it meets the criteria of an INCLUDE clause.
Action:
None
OGG-00488: DDL operation excluded [{0}], optype [{1}], objtype [{2}], objowner "{3}", objname "{4}"
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-00489: DDL is of mapped scope, after mapping new operation [{0}]
The DDL operation is of MAPPED scope. This is a DDL operation that is included in a TABLE or MAP statement.
Action:
None
OGG-00490: DDL operation is of unmapped scope
The DDL operation is of UNMAPPED scope. This is a DDL operation that is supported for use in a TABLE or MAP statement, but its base object name is not included in one of those parameters.
Action:
None
OGG-00491: DDL operation is of default scope
The DDL operation is of the default OTHER scope. This is a DDL operation that cannot be mapped.
Action:
None
OGG-00492: DDL error ignored: error code [{0}], filter [{1}], error text [{2}]
The specified DDL error was ignored according to the response rule in the DDLERROR parameter.
Action:
None
OGG-00493: Error in DDL ignored, [{0,number,0}] more errors left to ignore, input data [{1}]
DDLOPTIONS with SKIPTRIGGERERROR is used in the parameter file, and the trigger error was ignored. Because SKIPTRIGGERERROR specifies a maximum number of trigger errors that can be ignored, this message shows how many are remaining.
Action:
None
OGG-00494: DDL error discarded: error code [{0}], filter [{1}], error text [{2}]
The specified DDL error was ignored according to the response rule in the DDLERROR parameter.
Action:
None
OGG-00495: DDL error ignored for next retry: error code [{0}], filter [{1}], error text [{2}], retry [{3,number,0}]
The specified DDL error was ignored according to the response rule in the DDLERROR parameter. The DDL will be retried for the specified number of times according to the RETRYOP option.
Action:
None
OGG-00496: DDL error ignored [RESTARTCOLLISIONS]: error [{0}]
The specified error was ignored because RESTARTCOLLISIONS is being used. RESTARTCOLLISIONS applies HANDLECOLLISIONS logic for the first transaction after startup.
Action:
None
OGG-00497: Writing DDL operation to extract trail file
Extract is writing a DDL operation to the trail. Informational only.
Action:
None
OGG-00499: DDL RENAME found, old owner "{0}" object "{1}", new owner "{2}" object "{3}"
A RENAME operation was processed. Informational only.
Action:
None
OGG-00500: DDL RENAME found, old owner "{0}" object "{1}", new owner "{2}" object "{3}", RENAME converted to ALTER TABLE, new operation [{4}]
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-00501: Skipping DDL operation due to RESTARTSKIP, [{0,number,0}] more left to skip, DDL operation [{1}]
The Extract parameter file contains DDLERROR with the RESTARTSKIP option. Extract is skipping the specified number of DDL operations.
Action:
None
OGG-00502: DDL substitution [{0}] with [{1}] excluded [{2}]
Text substitution in the DDL was not performed because the DDL is listed in the EXCLUDE option in the DDLSUBST parameter.
Action:
None
OGG-00503: DDL substitution [{0}] with [{1}] excluded [no matching include]
Text substitution in the DDL was not performed because the DDL is not listed with an INCLUDE in the DDLSUBST parameter.
Action:
None
OGG-00504: DDL substitution [{0}] with [{1}] included [{2}], new operation [{3}]
Text substitution was performed according to the rules in the DDLSUBST parameter.
Action:
None
OGG-00505: DDL substitution [{0}] with [{1}] included [{2}], DDL operation remained the same after substitution
Text substitution was performed according to the rules of DDLSUBST, but the DDL text remained the same after the substitution.
Action:
None
OGG-00506: Both GETTRUNCATES and DDL replication are enabled
The parameter file contains the GETTRUNCATES parameter, but DDL replication is enabled.
Action:
Specify GETTRUNCATES (it is TABLE/MAP-specific) only for tables for which truncates must be replicated but are not part of the DDL configuration. GETTRUNCATES should not be used for tables that have DDL replication enabled, because truncates are supported by the DDL feature.
OGG-00507: Target table {0} is missing but ignored due to parameter {1}.
A DML operation on a non-existing table was ignored because the parameter file contains DDLOPTIONS with IGNOREMISSINGOBJECTS.
Action:
None
OGG-00508: Fragment number gap detected (faulty data) in DDL object versioning table, fragment #{1,number,0} for SCN {0}, query [{2}]
The data in the DDL history table is corrupted.
Action:
Contact Oracle Support.
OGG-00509: CREATE/ALTER USER with IDENTIFIED clause encountered, but no DDLOPTIONS DEFAULTUSERPASSWORD specified
A CREATE or ALTER USER with an IDENTIFIED BY clause was processed. The Extract parameter file contains DDLOPTIONS with the NOREPLICATEPASSWORD option to prevent the source password from being propagated, but the Replicat parameter file does not contain DDLOPTIONS with DEFAULTUSERPASSWORD to specify an alternate password for the target IDENTIFIED BY clause.
Action:
Add the DDLOPTIONS with DEFAULTUSERPASSWORD.
OGG-00510: Unexpected query selector in selecting DDL metadata
There was an internal error when querying the DDL history table.
Action:
Contact Oracle Support.
OGG-00511: Cannot access DDL history table. DDL schema owner is {0}. It must match schema used in DDL installation as well as GGSCHEMA parameter in GLOBALS file. Currently logged user {1} must have been given privileges to access DDL history table
The database user by which the process is running cannot read the GGS_DDL_HIST table (history table).
Action:
Make certain that the schema that is specified in the error text is the same one that is specified for the GGSCHEMA parameter in the GLOBALS file (and that this parameter exists there). If this parameter is correct, make certain that the specified user has full SELECT and DML privileges on the table. The privileges can be granted by running the role_setup.sql script to create the default GGS_GGSUSER_ROLE role, and then by granting the role to the Extract user. For more information, see the Oracle GoldenGate DDL installation and setup instructions.
OGG-00513: Table with SOURCEDEF cannot have DDL operations (table {0}). Either remove SOURCEDEF or filter out table from DDL operations
The table is configured for DDL replication, but also is configured to replicate to a dissimilar target. Oracle Supports DDL synchronization only in a like-to-like database environment, where source and target tables have identical definitions and are of the same database type.
Action:
Either map this table to an identical target, or remove it from the DDL INCLUDE or EXCLUDE options.
OGG-00514: Failed to substitute string in DDL operation [{0}], error [{1}]
The DDLSUBST parameter is being used, but the substitution failed.
Action:
Make sure that the DDL INCLUDE specification is compatible with the DDLSUBST INCLUDE specification (for example, that the targeted object is contained in both). Also make sure that REMOVECOMMENTS BEFORE is not specified. For more information, see the guidelines in the DDLSUBST reference documentation.
OGG-00515: Unknown operation code in DDLERROR structure
There is syntax in the INCLUDE or EXCLUDE statement, or in the error-handling syntax, of the DDLERROR parameter that cannot be parsed correctly.
Action:
Review the DDLERROR syntax and fix any errors. Consult the DDLERROR documentation for help with syntax.
OGG-00516: Fatal error executing DDL replication: error [{1}], due to explicit ABEND error handling and filter [{0}]
The DDLERROR statement is configured to cause the process to abend on the specified DDL error.
Action:
Fix the problem based on your data requirements. If ABEND is the error-handling rule, have a plan for manually fixing the problem, or contact Oracle Support.
OGG-00517: Fatal error executing DDL replication: error [{0}], because it's not included in error handling
There was an error processing a DDL operation, and the error was not handled because the filtering criteria in the DDLERROR statement excluded that operation from error handling.
Action:
Fix the problem based on the error text and then, if appropriate, include the operation type or object in the error handling.
OGG-00518: Fatal error executing DDL replication: error [{1}], due to exclusion from error handling because of filter [{0}]
There was an error processing a DDL operation, and the error was not handled because the filtering criteria in the DDLERROR statement excluded that operation from error handling.
Action:
Fix the problem based on the error text and then, if appropriate, include the operation type or object in the error handling.
OGG-00519: Fatal error executing DDL replication: error [{0}], no error handler present
There was an error processing a DDL operation, but because there is no error handling specified with the DDLERROR parameter, the process abended.
Action:
Fix the problem based on the error text in the message, and then add one or more DDLERROR parameters to handle future errors so that processing can continue.
OGG-00520: DDL replication is not supported for standby databases
Oracle GoldenGate does not support DDL replication to or from standby databases.
Action:
Remove the DDL configuration parameters and objects from the standby database.
OGG-00521: Object was resolved, however in the same resolution call both DDL history and database metadata resolution failed, cannot recover, {0} [{1}], object id {2}. Warning messages printed earlier may provide additional information.
The DDL object was not found in the database nor in in the DDL history record. Depending on the object, this message may or may not be ignored.
Action:
Check whether the object was dropped from the database. Also, make sure DDL history table did not get partially or fully truncated. If it did, restore the missing records. Make certain that the PURGEDDLHISTORY parameter does not delete DDL history records while they are still needed. Warning messages printed before this message may provide additional information about the cause of the error.
OGG-00523: Object ID in in marker data is not a number
The object metadata contains an object ID that is not in the form of a number.
Action:
Contact Oracle Support.
OGG-00524: Error in DDL trigger has been detected: {0}. Please investigate trace log file or contact Oracle Support
There was an error while processing DDL with the DDL trigger.
Action:
Examine the DDL trigger trace file and determine if the error is due to a system problem (such as a shut-down of the database or a lack of space for the DDL objects) or if it requires the attention of Oracle Support.
OGG-00525: Oracle GoldenGate DDL trigger is not installed correctly, details: {0}.
The DDL trigger was not installed correctly.
Action:
Install the DDL trigger again. For instructions, see the Oracle GoldenGate installation documentation for the Oracle database. If the problem persists, contact Oracle Support.
OGG-00526: Cannot find DDL statement in marker data
Extract could not find the text of the DDL operation in the DDL record.
Action:
Contact Oracle Support.
OGG-00528: The DDL parameter is not supported for this data source. Please remove this parameter and all DDL operations will be propagated in pass-through (PASSTHRU) mode.
The DDL parameter is specified in the parameter file of a data pump. DDL mapping or filtering is not supported for a data pump and must be passed through as-is.
Action:
Remove the DDL parameter from the data pump parameter file, and place the PASSTHRU parameter before all of the TABLE statements that contain tables that use DDL support. You can place the NOPASSTHRU parameter before any TABLE statements that contain tables that do not use DDL support, if you want data filtering, mapping, or transformation to be performed for them. For more information on configuring DDL support, see the Oracle GoldenGate administration documentation.
OGG-00530: Table DDL metadata changes are only changes supported at this time, type found [{0}]
Extract encountered an unsupported DDL operation. Oracle GoldenGate currently supports only table or sequence DDL operations.
Action:
Contact Oracle Support.
OGG-00534: Sequence update too large [{0}]
The update to the sequence value is greater than, or equal to, 100 million. Oracle GoldenGate does not support value updates that are greater than 100 million.
Action:
Use an update value of less than 100 million.
OGG-00535: Sequence cache value too large [{0}]
The sequence cache size is too large. Oracle GoldenGate does not support sequence CACHE values greater than 100 million.
Action:
Use a CACHE value of less than 100 million.
OGG-00536: Sequence increment by value [{0}] too large.
The sequence increment interval is too large. Oracle GoldenGate does not support INCREMENTBY values greater than 100 million.
Action:
Use an INCREMENTBY value of less than 100 million.
OGG-00537: Object type found [{0,number,0}] when resolving DDL object attributes unknown
The object type was not a table or sequence.
Action:
Contact Oracle Support.
OGG-00538: Metadata not invalidated for "{1}".{2} because of {0}
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-00539: Metadata not invalidated for "{1}".{2} because of {0} [{3}]
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-00540: Metadata not cleared for "{1}".{2} because of {0}
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-00541: Metadata not cleared for "{1}".{2} because of {0} [{3}]
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-00542: Unexpected threading library failure. Error code {0,number,0} ({1})
An internal error occurred while the process was executing a multi-threaded application.
Action:
Contact Oracle Support.
OGG-00543: Unexpected threading library failure. Error code {0,number,0} ({1})
An internal error occurred while executing a multi-threaded application. Oracle GoldenGate recovered from the error.
Action:
Contact Oracle Support for assistance if this warning continues to be issued.
OGG-00544: Invalid argument passed to threading function.
An unexpected programming logic error has occurred.
Action:
Contact Oracle Support.
OGG-00545: Threaded access not supported
Call Attachment Facility (CAF) does not permit a process to be threaded. There can be only one thread per Oracle GoldenGate process.
Action:
Either use the RRSAF (Recoverable Resource Manager Services Attachment Facility) attachment type or do not configure processes to be multi-threaded. For more information, see the Oracle GoldenGate installation and setup documentation for DB2 z/OS.
OGG-00546: Default thread stack size: {0,number,0}
Oracle GoldenGate determined the default number of Posix threads on the system.
Action:
None
OGG-00547: Increasing thread stack size from {0,number,0} to {1,number,0}
Oracle GoldenGate is increasing the number of Posix threads to support its processing requirements.
Action:
None
OGG-00549: Database operation failed: {0}. Unable to initialize using RRSAF - please check that RRS is available and functioning correctly. {1}
The MVSATTACHTYPE is set to RRSAF, but RRSAF could not be initialized.
Action:
Install RRSAF and make certain that is is configured properly.
OGG-00550: Database operation failed: {0}. Unable to initialize using RRSAF - please check that RRS is available and functioning correctly. {1}
The MVSATTACHTYPE is set to RRSAF, but RRSAF could not be initialized.
Action:
Install RRSAF and make certain that is is configured properly.
OGG-00551: Database operation failed: {0}. ODBC error: SQLSTATE {2} native database error {3,number,0}. {1}
The Oracle GoldenGate process could not complete its SQL operation because of the specified errors.
Action:
Correct the problem with the driver or database, and then restart the process.
OGG-00552: Database operation failed: {0}. ODBC error: SQLSTATE {2} native database error {3,number,0}. {1}
The Oracle GoldenGate process could not complete its SQL operation because of the specified errors.
Action:
Correct the problem with the driver or database, and then restart the process.
OGG-00554: Failed to execute SQL statement '{0}'
The specified SQL statement returned an error on execution.
Action:
Correct the problem that is related to the SQL statement and then restart the process.
OGG-00555: Executing fetch. ODBC error ({0,number,0}). {1}
A fetch failed.
Action:
Fix the problem based on the ODBC error message, and then restart the process.
OGG-00556: ODBC Driver for data source {0} does not provide ODBC level 1 conformance.
ODBC driver conformance level of at least level 1 is required.
Action:
Contact the database vendor and download the latest ODBC driver with conformance level of at least 1.
OGG-00557: ODBC Driver for {0} does not adequately support prepared statements
The ODBC driver for this database does not support prepared statements.
Action:
Upgrade to the latest ODBC driver for this database to correct the problem, and then restart the process.
OGG-00558: Failed to set implicit transactions off
An error occurred while disabling implicit transactions.
Action:
Determine whether the underlying database supports the SET IMPLICIT_TRANSACTIONS OFF command to return to autocommit mode. Correct the problem, and then restart the process.
OGG-00559: Failed to begin named transaction {0}
An error occurred while trying to start a named transaction command (such as BEGIN TRANSACTION tran_name).
Action:
Determine whether the underlying database supports named transactions. Correct the problem and then restart the process.
OGG-00560: Failed to change IDENTITY_INSERT state for table {0}
The execution of SET IDENTITY_INSERT failed with an error.
Action:
Make sure that the user that is used to connect to the database has sufficient privileges to use SET IDENTITY_INSERT. The user must either own the object in question, or be a member of the sysadmin fixed server role, or the db_owner and db_ddladmin fixed database roles.
OGG-00561: Failed to rollback to save-point {0}
There was an error when trying to roll back the transaction to a savepoint.
Action:
Note the name of the savepoint and then contact Oracle Support.
OGG-00562: Failed to save transaction {0}
The process failed to set a savepoint on the active transaction.
Action:
Note the name of the savepoint and then contact Oracle Support.
OGG-00563: Failed to retrieve IDENTITY information for table {0}
Replicat does not have the information that is required to process an IDENTITY column properly.
Action:
If the specified table does not contain an IDENTITY column, you can ignore this message. If the specified table does contain an IDENTITY column, make certain that you configured Oracle GoldenGate properly to handle these column types. For more information, see the Oracle GoldenGate documentation for SQL Server. If you cannot resolve the problem, contact Oracle Support.
OGG-00564: ODBC Driver for {0} does not support enough concurrent SQL statements. Need at least {1,number,0} and only {2,number,0} are available.
The ODBC driver does not support the number of concurrent SQL statements that are allowed by Oracle GoldenGate.
Action:
Set the MAXSQLSTATEMENTS parameter to a value that is supported by the driver.
OGG-00565: Cannot initialize ODBC operations
The system encountered an error while allocating an environment handle and the associated resources.
Action:
Contact the DBA of the underlying database, because this error probably relates to an unrecoverable system error.
OGG-00566: Table {0}.{1} does not exist in target database
The table is configured within Oracle GoldenGate for replication, but Replicat tried to get column information for the table on startup and was not able to find any metadata for it.
Action:
The table probably does not exist in the target database. Either add the table, or remove it from the Replicat configuration.
OGG-00567: Indexed value {2} not a column of table {0}.{1}
When the process tried to resolve a column name to its index, a column-not-found error occurred when cross-referencing the name with the current table metadata.
Action:
Stop and then restart the process to refresh the metadata record that the process keeps. If the problem persists, contact Oracle Support.
OGG-00568: The current ODBC session does not support multiple active transactions. Oracle Support recommends using multiple transactions to ensure transaction integrity and to enable releasing catalog locks as soon as possible. The ODBC initialization file should have both 'MVSATTACHTYPE=RRSAF' and 'MULTICONTEXT=1'.
The ODBC session does not support multiple active transactions.
Action:
Stop the Oracle GoldenGate process, then add the specified parameters to the ODBC initialization file, and then start the process again.
OGG-00570: Installed Teradata ODBC driver does not support batch SQL statement re-use. Upgrade driver to version {0,number,0}.{1,number,0}.{2,number,0}.{3,number,0} or greater.
The current ODBC driver does not support the BATCHSQL parameter.
Action:
Upgrade to the recommended driver.
OGG-00571: Outstanding SQL statements supported ({0,number,0}) less than maximum ({1,number,0})
The database does not support the number of prepared SQL statements that the current Oracle GoldenGate configuration allows.
Action:
Set the MAXSQLSTATEMENTS parameter to a value that is supported by the database. For more information about MAXSQLSTATEMENTS, see the Oracle GoldenGate reference documentation.
OGG-00572: Outstanding SQL statements limited to {0,number,0} by the Teradata ODBC driver.
The driver does not support the number of prepared SQL statements that the current Oracle GoldenGate configuration allows.
Action:
Set the MAXSQLSTATEMENTS parameter to a value that is supported by the database driver. For more information about MAXSQLSTATEMENTS, see the Oracle GoldenGate reference documentation.
OGG-00575: Driver for data source {0} does not support transactions.
The specified ODBC driver does not support transactions.
Action:
Upgrade the ODBC driver to one that supports transactions.
OGG-00576: Unexpected error ({0,number,0}) in fetch status array
The array fetch through ODBC resulted in an error for one or more rows in the array.
Action:
Attempt to resolve the problem based on the error code if possible. If you cannot resolve the problem, contact Oracle Support.
OGG-00577: Data length ({2,number,0}) exceeded maximum allowed value ({1,number,0}) for file {0}
This message is deprecated.
Action:
None
OGG-00578: Key length ({2,number,0}) exceeded maximum allowed value ({1,number,0}) for file {0}
This message is deprecated.
Action:
None
OGG-00579: Unexpected before image with key length ({0,number,0}) and record length ({1,number,0})
This message is deprecated.
Action:
None
OGG-00580: File {0} does not exist
This message is deprecated.
Action:
None
OGG-00581: C-tree error ({2,number,0}, {1}): {0}
This message is deprecated.
Action:
None
OGG-00582: C-tree error ({2,number,0}, {1}): {0}
This message is deprecated.
Action:
None
OGG-00583: Incorrect result type {1,number,0} describing table {0}
The describe request for the specified table or column definitions returned the specified unexpected result from the database.
Action:
Correct the problem based on the message. To help diagnose the problem, look for other Sybase-related messages in the report file for this Oracle GoldenGate process, and also check the Sybase error log.
OGG-00584: Incorrect result type {0,number,0} describing query definition
There was the specified unexpected result while describing a SQLEXEC query definition from the database. The SQLEXEC syntax probably contains an error.
Action:
View the SQLEXEC statement in the parameter file to find and correct the syntax error. For help with SQLEXEC syntax, see the Oracle GoldenGate reference documentation.
OGG-00585: Incorrect result type {0,number,0} describing table definition
While describing the SQLEXEC query definition from the database, the specified unexpected result type was received
Action:
View the SQLEXEC statement in the parameter file to find and correct the syntax error. For help with SQLEXEC syntax, see the Oracle GoldenGate reference documentation.
OGG-00586: Internal error opening data source for context
This is an internal error and should not be received in a production environment.
Action:
If you receive this error, contact Oracle Support.
OGG-00587: error executing sp while retrieving results
While executing a SQLEXEC stored procedure or query, an unexpected result was received.
Action:
View the SQLEXEC statement in the parameter file to find and fix syntax errors. For help with syntax, see SQLEXEC in the Oracle GoldenGate reference documentation. If the problem persists, check for other errors in the Oracle GoldenGate process report and the database error log before contacting Oracle Support. You might be able to determine the syntax error or other problem that is the cause.
OGG-00588: Unexpected error describing stored procedure
The SQLEXEC query execution failed because it failed to get syscolumn information.
Action:
Make certain that the Oracle GoldenGate user that executes SQLEXEC has permission to access the syscolumn table.
OGG-00593: SYBUTIL_convert_to_sybase_timestamp: Not one of the date/time datatypes: {0,number,0}
The specified data type is not supported by Oracle GoldenGate for this database version.
Action:
For supported data types, see the Oracle GoldenGate documentation that applies to the database.
OGG-00594: TIMECNV_convert_to_db_timestamp failed {0,number,0}
The conversion of a timestamp from the Oracle GoldenGate generic format to the Sybase timestamp data type failed. The timestamp is from a source database of a type other than that of the target.
Action:
Verify that the type of timestamp in the source can be converted to the format that is used by the target. For supported data types, see the Oracle GoldenGate documentation for the database.
OGG-00651: Failed to process SQL statement - error {0,number,0}
The query in the SQLEXEC statement failed due to the specified server error.
Action:
Check the SQLEXEC syntax in the parameter file for errors, and also make certain that the Oracle GoldenGate user that issues the SQLEXEC has the permission to execute the SQL that it contains. If these are not the cause of the problem, note the error number that is in the message text, and then look for possible causes or workarounds within the Sybase database.
OGG-00652: Failed to get results from server - error {0,number,0}
The query failed while fetching data for a SQLEXEC query or stored procedure.
Action:
Check the SQLEXEC syntax in the parameter file for errors, and also make certain that the Oracle GoldenGate user that issues the SQLEXEC has the permission to execute the SQL that it contains. If these are not the cause of the problem, note the error number that is in the message text, and then look for possible causes or workarounds within the Sybase database.
OGG-00653: Failed to send command for SQLEXEC - error {0,number,0}
The SQLEXEC query failed while sending data to the Sybase database.
Action:
Check the SQLEXEC syntax in the parameter file for errors, and also make certain that the Oracle GoldenGate user that issues the SQLEXEC has the permission to execute the SQL that it contains. If these are not the cause of the problem, note the error number that is in the message text, and then look for possible causes or workarounds within the Sybase database.
OGG-00654: Failed to prepare statement for SQLEXEC - error {0,number,0}
Sybase failed to prepare the SQLEXEC statement.
Action:
Fix the problem based on the error that is shown in the message text. Some possible causes are: The SQLEXEC syntax in the parameter file contains an error, or the Oracle GoldenGate user that issues the SQLEXEC does not have the permission for this particular query or stored procedure.
OGG-00655: Failed to allocate statement for SQLEXEC - error {0,number,0}
The SQLEXEC query failed because Sybase did not allocate space for a command structure for the query or stored procedure.
Action:
Check the SQLEXEC syntax in the parameter file for errors, and also make certain that the Oracle GoldenGate user that issues the SQLEXEC has the permission to execute the SQL that it contains. If these are not the cause of the problem, note the error number that is in the message text, and then look for possible causes or workarounds within the Sybase database.
OGG-00656: Server message ({0} Context): number({1,number,0}) severity({2,number,0}) state({3,number,0}) line({4,number,0}). Procedure({5}) Details ({6})
The specified error occurred in the Sybase server.
Action:
Resolve the problem with the server based on the Sybase error.
OGG-00660: Could not find unique key column within table definition, SQL <{0}>
The table only contains columns that are LONG, LOB or UDT. Oracle GoldenGate cannot construct a key from those column types.
Action:
Create a primary or unique key on the table, or remove it from the Oracle GoldenGate configuration. To remove a table when its name satisfies a wildcard definition, you can use the TABLEEXCLUDE parameter for Extract and the MAPEXCLUDE parameter for Replicat.
OGG-00661: Error selecting unique keys for table {0}. Detail: {1}, SQL: <{2}>.
The process could not select a unique key for the specified table.
Action:
Resolve the problem based on the error that is shown in the message.
OGG-00662: OCI Error {1} (status = {0,number,0})
An error occurred in the OCI.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-00663: OCI Error {1} (status = {0,number,0}), SQL <{2}>
An error occurred in the OCI.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-00664: OCI Error {2} (status = {0,number,0}-{1})
An error occurred in the OCI.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-00665: OCI Error {2} (status = {0,number,0}-{1}), SQL<{3}>
An error occurred in the OCI.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-00666: SQL operation failed: {2} SQL Error {0,number,0}: {1}
This is an internal error.
Action:
Contact Oracle Support.
OGG-00667: OCI error ({0,number,0}-{1}) retrieving length info of a ROWID/UROWID column (table: {2}, column: {3})
The specified column name does not exist in the specified table.
Action:
Make certain that the column is spelled correctly in any parameters where it is specified in the parameter file. Make certain that the column exists in the table.
OGG-00668: OCI error ({0,number,0}-{1}) initializing query to obtain ROWID/UROWID length (table: {2}, column: {3})
This is an internal error.
Action:
Contact Oracle Support.
OGG-00669: OCI error ({0,number,0}-{1}) retrieving precision info of a NUMBER column (table: {2}, column: {3})
The specified column does not exist in the specified table.
Action:
Make certain that the column is spelled correctly in any parameters where it is specified in the parameter file. Make certain that the column exists in the table.
OGG-00670: OCI error ({0,number,0}-{1}) initializing query to obtain NUMBER precision (table: {2}, column: {3})
This is an internal error.
Action:
Contact Oracle Support.
OGG-00671: Error selecting table_name from all_tables - SQL <{0}>
This is an internal error.
Action:
Contact Oracle Support.
OGG-00672: OCI error ({0,number,0}, {1}) fetching accessible schemas
An error occurred when retrieving all accessible tables for this user.
Action:
Contact Oracle Support.
OGG-00673: OCI error ({0,number,0}, {1}) executing select to get accessible schemas
This is an internal error.
Action:
Contact Oracle Support.
OGG-00674: OCI error ({0,number,0}, {1}) preparing query (sql {2})
This is an internal error.
Action:
Contact Oracle Support.
OGG-00675: OCI error ({2,number,0}, {3}) fetching unique keys for table {0}.{1}
The specified table probably lacks a primary key, unique constraint, or unique index.
Action:
Check to see if the table contains a primary key, unique constraint, or unique index, and create one of these objects if none exist. If you continue to get this error, contact Oracle Support.
OGG-00676: OCI error ({2,number,0}, {3}) executing select to get unique keys for table {0}.{1}
This is an internal error.
Action:
Contact Oracle Support.
OGG-00679: Could not determine instance state ({0}), SQL <{1}>
The instance number could be invalid.
Action:
Contact Oracle Support.
OGG-00680: Missing all_objects entry for {0}.{1}, SQL <{2}>
The object name does not exist in the database.
Action:
Add the object to the database if appropriate, or check for spelling errors in the parameter file. If the object does exist and is specified correctly in the parameter file, contact Oracle Support.
OGG-00681: Could not retrieve query on all_objects ({0}), SQL <{1}>
This is an internal error.
Action:
Contact Oracle Support.
OGG-00686: Could not retrieve row from table {0}
A call to the database to fetch table metadata failed.
Action:
Contact Oracle GoldenGate Support.
OGG-00687: Found inconsistent row in table {0}
A call to the database to fetch table metadata failed.
Action:
Contact Oracle GoldenGate Support.
OGG-00689: {0}.{1} {2}:Column data type is not ROWID nor UROWID.
A SQL statement that queries the Oracle system table failed.
Action:
Contact Oracle GoldenGate Support.
OGG-00690: {0} is not supported for this platform.
The specified function is not supported.
Action:
None
OGG-00699: OCI initialization error [{0,number,0}]
A SQL statement in Oracle that retrieves metadata for the target table failed.
Action:
Contact Oracle Support.
OGG-00700: Number of columns in table is set to zero
A SQL statement in Oracle that retrieves metadata for the target table failed.
Action:
Contact Oracle Support.
OGG-00701: No table name given
A SQL statement in Oracle that retrieves metadata for the target table failed.
Action:
Contact Oracle Support.
OGG-00702: OCI call failed
An OCI call to the Oracle database failed. This is a generic message that captures any type of OCI failure.
Action:
Contact Oracle Support.
OGG-00703: OCIHandleFree error in function {1} [type={0,number,0}].
The attempt to free a previously allocated Oracle OCI handle failed.
Action:
Contact Oracle Support.
OGG-00704: OCIHandleFree error in function {1} [type={0,number,0}].
The attempt to free a previously allocated Oracle OCI handle failed.
Action:
Contact Oracle Support.
OGG-00705: OCIDescriptorFree error in {1} [type={0,number,0}]
The attempt to free a previously allocated Oracle OCI descriptor failed.
Action:
Contact Oracle Support.
OGG-00706: Failed to add supplemental log group on table {0} due to {1} SQL {2}
ADD TRANDATA was issued for the specified table, but Oracle GoldenGate was not able to add a supplemental log group on the table.
Action:
Fix the problem based on the database error that is returned in the message.
OGG-00707: Table {0} has no valid key columns, no supplemental log group was added.
The table does not have any primary or unique key columns defined on it, so a supplemental log group cannot be created.
Action:
If the table contains any columns that always will be unique, you can specify them as a key by using a KEYCOLS clause. Otherwise, Oracle GoldenGate will use all of the columns as a key. For more information about KEYCOLS, see the Oracle GoldenGate reference documentation.
OGG-00708: Key column may exists after column {0}, may not be able to handle row chaining
There is a key column after a LONG, LOB, or UDT column. This message supports trigger-based extraction, which is no longer supported by Oracle GoldenGate.
Action:
None
OGG-00709: OCI error ({0,number,0}-{1}) building query to fetch codepoint info
The value for NLS_LANG might be invalid.
Action:
This warning is deprecated.
OGG-00710: OCI error ({0,number,0}-{1}) fetching codepoint info, use default codepoint value 1
This is an internal error that indicates the process could not fetch codepoint information.
Action:
This warning is deprecated.
OGG-00711: Cannot derive character set conversion ({0}), use default codepoint value 1
The process could not derive a character-conversion formula to convert the source data to the target data. This is a warning message.
Action:
This warning is deprecated.
OGG-00730: No minimum supplemental logging is enabled.
Minimal supplemental logging is not enabled. Supplemental logging must be enabled for Extract to successfully process records from the redo log.
Action:
Enable minimal supplemental logging.
OGG-00734: Failed to find LONG column index in table {0} to match up LONG data
The table is marked with a LONG column, but Extract could not find the LONG column when it resolved the table metadata.
Action:
Restart Extract to refresh the metadata in memory.
OGG-00735: Error converting Oracle numeric value to ASCII for column {0}
Extract failed to convert data in a numeric column from the native Oracle format to the Oracle GoldenGate internal format.
Action:
Restart Extract. If the problem persists, exclude this table from the Extract configuration so that processing continues, and then contact Oracle Support.
OGG-00737: Cannot support {0,number,0} byte integer boundary
Extract detected that the native data structure alignment on the specified word is higher than 4 bytes.
Action:
Move the Oracle GoldenGate installation to a platform with a lower data structure alignment. For assistance, contact Oracle Support.
OGG-00738: Object id [{0,number,0}], SCN [{1}], commit SCN [{2}] could not be resolved. Most likely this happens if DDL history for it was deleted. Please check purge parameters in manager parameter file (if it is too short). If that is ok, this was probably an object that was not filtered out and this can be ignored
Either this object ID represents something that Extract is not supposed to capture, or it is supposed to be captured but Oracle GoldenGate could not interpret the metadata, probably because the table was dropped after this record was generated.
Action:
If this record is an object that must be captured, restore the GGS_DDL_HIST (DDL history) table from backup to restore the metadata for the specified object ID and SCN. To prevent future loss, set PURGEDDLHISTORY so that the retained history exceeds Extract lag.
OGG-00739: invalid datetime ({1}) for obj attr ({0})
The specified date or timestamp value is invalid. The date format must be YYYY-MM-DD HH24:MI:SS and the timestamp format must be YYYY-MM-DD HH24:MI:SS.FF.
Action:
Use a value that conforms to the required format.
OGG-00740: invalid number ({1}) for obj attr ({0}), OCI Error {2}
The specified number value is not a valid Oracle number.
Action:
Use a valid Oracle number. For help, see the Oracle documentation.
OGG-00741: invalid string ({1}) for obj attr ({0})
An attempt to map an XML value attribute of type string to an attribute of an Oracle user-defined datatype failed.
Action:
Review the schema for the associated user-defined data type. Contact Oracle Support for additional assistance.
OGG-00742: invalid raw string ({1}) for obj attr ({0})
The field contains invalid characters. A RAW field can have only characters from 0123456789ABCDEF.
Action:
Remove any characters that are not from 0123456789ABCDEF.
OGG-00743: Error executing SELECT SQL query. Error code: {0,number,0}, Detail: {1}, Function: {2}.
Parse and binding on one of the internal queries failed.
Action:
Contact Oracle Support.
OGG-00744: Error ({0,number,0}, {1}) start select in {2}
Parse and binding on one of the internal queries failed.
Action:
Contact Oracle Support.
OGG-00745: Error ({0,number,0}, {1}) start cursor in {2}
Parse and binding on one of the internal queries failed.
Action:
Contact Oracle Support.
OGG-00746: Error ({0,number,0}, {1}) selecting data in {2}
An error occurred when fetching data from an internal cursor.
Action:
Contact Oracle Support.
OGG-00747: Error ({0,number,0}, {1}) selecting data in {2}
An error occurred when fetching data from an internal cursor.
Action:
Contact Oracle Support.
OGG-00748: Error ({2,number,0}, {3}) retrieving data in {4}() for table {0}.{1}
The process cannot find the specified table.
Action:
Ensure that the table exists in the database, and that it is specified correctly in the parameter file of the process. If these checks prove true, contact Oracle Support.
OGG-00749: Error ({1,number,0}, {2}) retrieving owner/object name for object id {0,number,0}
The process cannot find the object name by using the specified object ID.
Action:
Contact Oracle Support.
OGG-00750: Error ({3,number,0}, {4}) retrieving LOB object_id for col {2}, table {0}.{1}
The process cannot find the LOB object name by using the specified object ID.
Action:
Contact Oracle Support.
OGG-00751: Failed to validate table {0}. Likely due to existence of unused columns. It will cause data integrity issue if you are not using sourcedefs in downstream Replicat or the target table doesn't have the same unused columns due to ASSUMETARGETDEFS or DDL replication. Please use 'DBOPTIONS ALLOWUNUSEDCOLUMN' parameter to override this.
The specified table contains unused columns. Oracle Supports tables with unused columns, but the support is disabled by default. Extract abends on these columns unless you use the DBOPTIONS parameter with the ALLOWUNUSEDCOLUMN option to force Extract to generate a warning and continue processing.
Action:
Specify DBOPTIONS with ALLOWUNUSEDCOLUMN. When using this parameter, either the same unused column must exist in the target table, or a source definitions file must be created for Replicat with the DEFGEN utility. For more information about the source definitions file, see the Oracle GoldenGate administration documentation.
OGG-00752: Failed to validate table {0}. Likely due to existence of unused column. Please make sure you use sourcedefs in downstream Replicat, or the target table has exactly the same unused columns when using ASSUMETARGETDEFS or DDL replication.
The specified table contains unused columns. Oracle Supports tables with unused columns, but the support is disabled by default. Extract abends on these columns unless you use the DBOPTIONS parameter with the ALLOWUNUSEDCOLUMN option to force Extract to generate a warning and continue processing.
Action:
Specify DBOPTIONS with ALLOWUNUSEDCOLUMN. When using this parameter, either the same unused column must exist in the target table, or a source definitions file must be created for Replicat with the DEFGEN utility. For more information about the source definitions file, see the Oracle GoldenGate administration documentation.
OGG-00753: Error ({2,number,0}, {3}) retrieving partition count for table {0}.{1}
The process could not find the number of partitions in the specified table.
Action:
Contact Oracle Support.
OGG-00754: Error ({2,number,0}, {3}) retrieving subpartition count for table {0}.{1}
The process could not find the number of sub-partitions in the specified table.
Action:
Contact Oracle Support.
OGG-00755: Failed to lookup user ID for table {0}
The process could not find the owner of the specified table.
Action:
Ensure that the table is qualified with the correct owner in the parameter file and that the table exists in the schema to which the process is connected.
OGG-00756: Failed to lookup user ID for sequence {0}
The process could not find the owner of the specified sequence.
Action:
Ensure that the sequence is qualified with the correct owner in the parameter file and that the sequence exists in the schema to which the process is connected.
OGG-00757: Error ({2,number,0}, {3}) fetching alternate object IDs for table {0}.{1}
The process could not get the sub-partition IDs of the specified table.
Action:
Contact Oracle Support.
OGG-00758: Error ({0,number,0}, {1}) retrieving user name in {2}()
This is an internal error.
Action:
Contact Oracle Support.
OGG-00759: Error ({1,number,0}, {2}) retrieving user_id for username {0}
The process could not find the specified user name.
Action:
Ensure that the user exists in the database.
OGG-00760: Error ({3,number,0}, {4}) select data segcol# in {5}() for {0}.{1} column# {2,number,0}
This is an internal error.
Action:
Contact Oracle Support.
OGG-00761: Error ({3,number,0}, {4}) retrieving col# & seqcl# for col {2}, table {0}.{1}
The process could not find the specified column name in the table.
Action:
Add the column to the table, or remove it from any parameters that use it as the basis for filtering or other processing.
OGG-00762: Error ({2,number,0}, {3}) fetching table name {0}."{1}"
The process could not find the specified table name in the database.
Action:
Add the table to the database, or remove it from the Oracle GoldenGate configuration.
OGG-00763: Error ({0,number,0}, {1}) retrieving database block size
This is an internal error.
Action:
Contact Oracle Support.
OGG-00764: Error ({3,number,0}, {4}) checking log group on log {2} for table {0}.{1}
Supplemental logging is not enabled for the specified table.
Action:
Enable supplemental logging for the table.
OGG-00765: Error ({3,number,0}, {4}) checking log group on log {2} for table {0}.{1}
Supplemental logging is not enabled for the specified table.
Action:
Enable supplemental logging for the table.
OGG-00766: Error ({2,number,0}, {3}) retrieving total columns for user {0}, table {1}
This is an internal error.
Action:
Contact Oracle Support.
OGG-00767: Error ({3,number,0}, {4}) retrieving status in {5}() for trigger "{2}" table {0}.{1}
This error is deprecated.
Action:
None
OGG-00768: {0}. SQL error ({1,number,0}). {2}
This is a generic error message and there can be multiple reasons for it. One reason could be that a query to set the session timeout failed. Ignoring this message results in the session being disconnected after a default time period if the connection has been idle. This error message also is used when an operation against the database fails, such as a query.
Action:
To resolve this error, verify in the database why the query or other operation would fail. For example, verify that the user that executed the operation has the correct privileges to do so.
OGG-00769: {0}. SQL error ({1,number,0}). {2}
This is a generic error message and there can be multiple reasons for it. One reason could be that a query to set the session timeout failed. Ignoring this message results in the session being disconnected after a default time period if the connection has been idle. This error message also is used when an operation against the database fails, such as a query.
Action:
To resolve this error, verify in the database why the query or other operation would fail. For example, verify that the user that executed the operation has the correct privileges to do so.
OGG-00770: Failed to connect to MySQL database engine for HOST {0}, DATABASE {1}, USER {2}, PORT {3,number,0}
One of the Oracle GoldenGate parameters that specifies connection information is incorrect.
Action:
Verify the login credentials of the Oracle GoldenGate process (as a database user), the connection port, the database name, and the host name that are specified in the parameter file. In the case of the host name, the name might be incorrectly specified, or the MySQL server could not resolve it. It also is possible that the host name was not specified when the MySQL user was created, so the MySQL system table does not contain an entry for the user.
OGG-00771: Cannot initialize MySQL connection handler
The MySQL API failed to allocate, initialize, and return a new object that is used throughout the session to connect to the object. This error only occurs when there is not sufficient memory.
Action:
Add memory.
OGG-00772: Setting session isolation level to REPEATABLE READ
The query to set the session default isolation level to REPEATABLE READ in the MySQL database failed.
Action:
Make certain the user has the appropriate privilege to set the default isolation level.
OGG-00773: Disabling autocommit mode
The query to set the auto-commit variable (autocommit=0) failed.
Action:
Make certain the user has the appropriate privilege to perform this operation, and make certain that the MySQL server is running.
OGG-00774: Unrecognized field type ({1,number,0}) for column {0}
The specified column contains a data type that is not supported by Oracle GoldenGate.
Action:
Remove tables or columns that contain unsupported data types from the Oracle GoldenGate configuration. For supported data types, see the Oracle GoldenGate installation and setup guide for the MySQL database.
OGG-00775: Unable to determine database case sensitivity, setting to insensitive
Oracle Supports case sensitivity but cannot determine the case of the database.
Action:
Oracle GoldenGate checks the database collation to determine whether the database object names should be compared in case sensitive or case insensitive mode. View the collation of the database to make certain it is set correctly. Certain collation-dependent objects and duplicate names, for example, can cause a COLLATE definition to fail. For more information, see the Microsoft SQL Server documentation.
OGG-00776: 'SELECT INTO/BULKCOPY' option is enabled for database: {0}. SELECT INTO operations on permanent tables are not written to logs. These operations will therefore not get replicated.
Bulk copy is not supported.
Action:
To avoid this error, issue the following SQL Server command to avoid the select for the specified schema: exec sp_dboption 'owner/schema', 'select into/bulkcopy', false.
OGG-00777: Supplemental logging is disabled for database {0}. To enable logging, perform the following: 1) Set 'trunc. log on chkpt.' to false. 2) Create a full backup of the database. Refer to "Installing and Configuring Oracle GoldenGate for SQL Server" for details.
Undefined
Action:
Undefined
OGG-00778: Logging of supplemental log data is disabled for table {0}
Supplemental (extended) logging is not enabled for the specified table.
Action:
Issue the DBLOGIN command in GGSCI, and then issue the ADD TRANDATA command to enable the supplemental logging. For more information, see the Oracle GoldenGate for SQL Server documentation.
OGG-00779: Error in getting logging status for table: {0}
The process could not determine whether the specified table has supplemental logging enabled.
Action:
Check the database connection settings and whether SQL Server was configured according to the directions in the Oracle GoldenGate installation documentation for SQL Server.
OGG-00780: Error in getting logging status for table: {0} ({1})
The process could not determine whether the specified table has supplemental logging enabled.
Action:
Check the database connection settings and whether SQL Server was configured according to the directions in the Oracle GoldenGate installation documentation for SQL Server.
OGG-00781: Error in changing transaction logging for table: {0} ({1})
Oracle GoldenGate failed to enable or disable supplemental logging for the specified table.
Action:
Look for other warnings or error messages, because there are many possible causes for this error, such as insufficient privileges for the Oracle GoldenGate user and connectivity failures.
OGG-00782: Error in changing transaction logging for table: {0}
Oracle GoldenGate failed to enable or disable supplemental logging for the specified table.
Action:
Look for other warnings or error messages, because there are many possible causes for this error, such as insufficient privileges for the Oracle GoldenGate user and connectivity failures.
OGG-00783: Unable to enable replication on {0} ({1})
Oracle GoldenGate failed to enable or disable supplemental logging for the specified table.
Action:
Look for other warnings or error messages, because there are many possible causes for this error, such as insufficient privileges for the Oracle GoldenGate user and connectivity failures.
OGG-00784: Unable to determine if {0}.{1} is of computed column: {2}
Oracle GoldenGate failed to determine if the specified column is a computer column.
Action:
Look for other warnings or error messages, because there are many possible causes for this error, such as insufficient privileges for the Oracle GoldenGate user and connectivity failures.
OGG-00785: Before image with timestamp {0} does not match table definition for {1} at {2}.{3,number,0}. Sync of source and target to a later point in time is required before capture can resume. REORG is recommended.
The table was altered so that the current definition does not match the log record.
Action:
Synchronize source and target data to a point in time beyond that reported in the message. Then, restart Extract.
OGG-00786: Data corruption may result from use of the _NOMERGEMEMBERS option in a data sharing environment.
The undocumented option _NOMERGEMEMBERS is specified in the TRANLOGOPTIONS statement for Extract in a data sharing environment.
Action:
Contact Oracle Support.
OGG-00787: unexpected status {0} at {1}.{2,number,0}
This is a warning that the process is at the end of the log and waiting for more data.
Action:
None
OGG-00788: Check the DB2 maintenance for the presence of PQ78544 and the absence of PQ96356. Contact Oracle Support if PQ96356 has been applied.
Log record types 10, 11, 12, and 13 are either the result of a short-lived APAR PQ78544 (reversed by PQ96356) or changes subsequent to PQ96356.
Action:
Contact Oracle Support if any of these types appear without PQ78544.
OGG-00789: Table Space {0}.{1} is LOG NO - Table {2} Column # {3,number,0} will be captured via fetch
The specified LOB tablespace was created as LOG NO; therefore, the specified LOB column cannot be captured from the log and must be captured by means of a fetch.
Action:
None
OGG-00790: A resource was unavailable while attempting to read the log at {0}. Retry in {1,number,0} seconds.
The process is retrying a log read.
Action:
None
OGG-00791: Invalid log record
A processing check failed.
Action:
Save this message and other preceding messages that provide the context for it, and contact Oracle Support.
OGG-00794: A resource was unavailable while attempting to read the log at {0}. check SYSLOG for details.
The process is trying to read a log file that is no longer available.
Action:
Make certain that the BSDS name was specified correctly, and that the ADD EXTRACT or ALTER EXTRACT command was issued correctly. If a start time was used, instead of the NOW option, it is possible to specify a start point for which logs are no longer available. If Extract is configured properly, contact Oracle Support.
OGG-00795: DB2 Monitor Trace Class 1 must be active
DB2 Monitor Trace Class 1 is required to allow Extract to read the active log, but Monitor Trace Class 1 is not active.
Action:
See the Oracle GoldenGate installation and setup documentation for instructions on activating Monitor Trace Class 1.
OGG-00796: Unexpected IFI error, DB2 error message: {0}
A processing check failed.
Action:
Save this message and other messages that provide context for it, and contact Oracle Support. The IBM Messages and Codes documentation may provide additional information for this error.
OGG-00797: DB2 IFI abend - check the log record. DB2 error message: {0}
A processing check failed.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support. The IBM Messages and Codes documentation may provide additional information for this error.
OGG-00798: BUFSIZE too small for log record
The internal buffer that holds the results of each read of the transaction log is too small to hold the data returned.
Action:
Use the TRANLOGOPTIONS parameter with the BUFSIZE option to increase the buffer size.
OGG-00799: Error {4} diagnostic {5} retrieving log record for table {0} (dbid x'{1}' psid x'{2}' obid x'{3}')
The process could not retrieve the next log record for the specified table.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00800: Unable to decompress log record for table {0} Error {4} diagnostic {5} (dbid x'{1}' psid x'{2}' obid x'{3}'). The compression dictionary changed since the log record was written
DB2 z/OS was not able to decompress the log record. It is likely that a compression dictionary matching the record is not available.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00801: Unable to retrieve log record for table {0}. Error {4} diagnostic {5} (dbid x'{1}' psid x'{2}' obid x'{3}'). The buffer is too small to hold the log record.
The internal buffer that holds the results of each read of the transaction log is too small to hold the data returned.
Action:
Use the TRANLOGOPTIONS parameter with the BUFSIZE option to increase the buffer size.
OGG-00803: {0} Unable to find {1}
The initialization of the IFI interface failed.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00804: {0} Unable to initialize IFI
The initialization of the IFI interface failed.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00805: LOBCol {0} expected {1,number,0} bytes copied {2,number,0} bytes
The number of bytes that were moved from LOB storage to the base row did not match what the process expected.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00806: moving {1,number,0} bytes to base row for LOBcol {0}
The process failed to move data from LOB storage to the base row.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00808: Invalid log record sequence at line {5,number,0} - type {0,number,0} (before image) cannot be the first log record of an update pair. There must be a preceding update type {1} (after image) for the log record with LSN {2}, timestamp {3}, for the member {4}
An out-of-sequence log record was encountered.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00809: Variant mismatch at line {0,number,0}
An unknown type of log record was encountered.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00810: Validation error at line {0,number,0}
An out-of-sequence log record was encountered.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00811: Invalid sequence at line {0,number,0}
An out-of-sequence log record was encountered.
Action:
Save this message and other preceding messages that provide context for it, and contact Oracle Support.
OGG-00812: Extract is not APF authorized.
Extract is not APF authorized.
Action:
Determine why Extract is not APF authorized and correct the problem. Extract and all dll files must have the APF bit turned on and all load libraries in the execution concatenation must be APF authorized.
OGG-00813: Unexpected (non-URCTL) record type.
An unexpected log error was encountered.
Action:
Contact Oracle Support.
OGG-00814: SQL_NO_DATA_FOUND from SQLGetData for col {1} table {0} PTF UK34243 is required
A bug in DB2 z/OS occasionally causes no data to be found when Extract tries to fetch LOB data. Extract checks to see if the specified IBM fix was applied and, if not, generates this message.
Action:
Apply the required IBM fix shown in the message.
OGG-00815: db2ReadLog error [RC={0,number,0}:SQLCA structure may be corrupted]
The DB2ReadLog API has encountered an error reading the transaction log.
Action:
Contact Oracle Support.
OGG-00816: db2ReadLog error [{0}] [{1}]
An invalid parameter has been supplied to the DB2ReadLog API. This is an internal error.
Action:
Contact Oracle Support.
OGG-00817: db2ReadLog error [{0}]
The DB2ReadLog API encountered an error while trying to read the transaction log. This is an internal error.
Action:
Contact Oracle Support.
OGG-00818: Unknown Log Manager log record component ID encountered:{0,number,0}
An unrecognized component ID was encountered during the processing of a log record. This is an internal error.
Action:
Contact Oracle Support.
OGG-00820: Reposition to key {0,number,0} failed
Extract was not able to reposition to the specified timestamp. This is an internal error.
Action:
Contact Oracle Support.
OGG-00821: LSN requested ({0,number,0}) is no longer valid, positioning to the next LSN in the log files
Extract was positioned to start at the specified LSN, but it does not exist in the log files. Extract is positioned to the closest next LSN that exists in the log files.
Action:
None
OGG-00823: A key column on the after image was not present in the before image on table {0} column index {1,number,0} This is because column(s) were added to the table after it was originally created. This is a known issue with DB2 LUW that can only be addressed by IBM.
Columns were added to the specified table, so the after image contains a column that was not present in the before image that is used by Oracle GoldenGate for comparison purposes.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it with the target table. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-00824: Column index {1,number,0} in table {0} cannot be used as a key field
The table has a unique index that includes a column type that is not supported by Oracle GoldenGate as a key.
Action:
Use the KEYCOLS clause to specify unique columns that can be used as a key. You can use the existing index columns minus the nonsupported column in the KEYCOLS clause, if the remaining columns ensure uniqueness.
OGG-00825: Table {0} column {1,number,0} : Invalid LOB column value
The Extract process encountered an internal error while processing a log record containing a LOB column.
Action:
Contact Oracle Support.
OGG-00826: Table {0} column {1,number,0} : Invalid packed decimal column value
The Extract process encountered an internal error while processing a log record containing a PACKED DECIMAL column.
Action:
Contact Oracle Support.
OGG-00827: Insert of new hash item for tablespace:table:transID {0,number,0}:{1,number,0} failed
The Extract process encountered an internal storage allocation error.
Action:
Contact Oracle Support.
OGG-00828: Retrieval of hash item for tablespace:table:transID {0,number,0}:{1,number,0} failed
The Extract process encountered an internal storage access error.
Action:
Contact Oracle Support.
OGG-00829: Retrieval of hash item for tablespace:table:transID {0,number,0}:{1,number,0} succeeded unexpectedly
The Extract process encountered an internal storage access error.
Action:
Contact Oracle Support.
OGG-00830: Delete of hash item failed
The Extract process encountered an internal storage access error.
Action:
Contact Oracle Support.
OGG-00831: Neither a valid checkpoint start LSN nor a timestamp was passed to REDO_position
An internal error was encountered by Extract where the process could not determine the positioning mode at startup.
Action:
Contact Oracle Support.
OGG-00832: ASCII formatting not implemented
The FORMATASCII parameter is not supported for this database implementation.
Action:
Remove FORMATASCII from the Extract parameter file.
OGG-00833: Invalid component ID encountered {0,number,0}
The Extract process did not recognize the component identifier from the specified record.
Action:
Contact Oracle Support.
OGG-00834: Invalid row type {0,number,0} was received while creating a LOB row for an LOB record type: {1,number,0}.
The Extract process did not recognize the row type from the specified LOB record.
Action:
Contact Oracle Support.
OGG-00835: Invalid row type {0,number,0} was received while creating a LFM row for an LFM record type: {1,number,0}.
The Extract process did not recognize the LFM type from the specified LOB record.
Action:
Contact Oracle Support.
OGG-00836: No items were found in the transaction for tablespace:table:trans ID {0,number,0}:{1,number,0}:{2}
The Extract process unexpectedly encountered an empty transaction while trying to output the transaction.
Action:
Contact Oracle Support.
OGG-00837: db2CfgGet error [{0}]
An error occurred while processing a table truncate.
Action:
Contact Oracle Support.
OGG-00838: db2CfgGet error [RC={0,number,0}:SQLCA structure may be corrupted]
An error occurred while processing a table truncate.
Action:
Contact Oracle Support.
OGG-00839: Table {0} does not have DATA CAPTURE CHANGES turned on : Table will be ignored
The specified table does not have DATA CAPTURE CHANGES turned on, and Extract is ignoring it because TRANLOGOPTIONS includes IGNOREDATACAPTURECHANGES.
Action:
None
OGG-00840: Table {0} does not have DATA CAPTURE CHANGES turned on : Use the TRANLOGOPTIONS IGNOREDATACAPTURECHANGES parameter to override
The specified table does not have DATA CAPTURE CHANGES turned on. This is required by Extract.
Action:
Use the TRANLOGOPTIONS parameter with the IGNOREDATACAPTURECHANGES option to cause Extract to ignore tables for which DATA CAPTURE CHANGES is not set. This option enables you to use a wildcarded table specification for tables that have change capture enabled, while skipping tables with matching names that do not have it enabled.
OGG-00841: An update after image converted to an insert was not followed by its corresponding row ID update. An internal dms type of {0,number,0} was encountered in the following record
The after image of an update that was converted to an insert was not followed by its corresponding row ID update. This is an internal logic error.
Action:
Contact Oracle Support.
OGG-00842: No records left in transaction:An update after image converted to an insert with LRI {0,number,0}.(1,number,0} was not followed by its corresponding update.
Extract encountered an internal logic error while processing an update record at the specified LRI.
Action:
Contact Oracle Support.
OGG-00843: No tables were defined for extraction in the Extract parameter file
Extract was started but the parameter file contains no table specifications.
Action:
Specify tables for capture with the TABLE parameter.
OGG-00844: Source table entry not found in file array
A table that is specified for capture in the Extract parameter file does not exist in the specified database.
Action:
Add the table to the database or remove it from the TABLE parameter file.
OGG-00845: Rollback ID {1,number,0} does not match last record ID of {0,number,0} in FM transaction manager
An internal inconsistency was detected in the Extract process while processing a transaction rollback.
Action:
Contact Oracle Support.
OGG-00846: Row row: Expecting an update/delete/undo record after receiving an update converted to an insert in migrated row sequence: Received record type {0,number,0} instead
Extract encountered an unexpected sequence of records in the transaction log. This is an internal logic error.
Action:
Contact Oracle Support.
OGG-00847: Multi-dimensional clustered tables using formatted user data records with value compression are not supported in this release
The TABLE parameter includes a table that is defined with an unsupported database feature.
Action:
Remove the table that is not supported from the TABLE specification. If the table name is one of many that satisfy a wildcard, you can use TABLEEXCLUDE to exclude it.
OGG-00848: A log record with the previous LRI:{0,number,0}.{1,number,0} was not found in the DB2 log files: lookup failed
Extract failed to process backward in the LSN chain to find the first record of the transaction. This is an internal logic error.
Action:
Contact Oracle Support.
OGG-00849: Database name must be 8 characters or less
The database name that is specified in the parameter file is too long. The database name can be up to eight characters.
Action:
Check the parameter file for a typographical error.
OGG-00850: Database instance {0} has both USEREXIT and LOGRETAIN set to off
The database is not configured to retain the transaction logs.
Action:
Turn on the USEREXIT parameter, which automatically sets LOGRETAIN to RECOVERY and forces a user exit program to archive and retrieve the log files. Alternatively, you can set the LOGRETAIN parameter to RECOVERY, which retains the logs and enables them to be used for forward recovery.
OGG-00851: Invalid {1} record: row type {0,number,0} was received with an associated {1} record type: {2,number,0}
Extract failed an internal sanity check of the log record.
Action:
Contact Oracle Support.
OGG-00852: Invalid DMS record type received: {0,number,0}
Extract failed an internal sanity check of the log record.
Action:
Contact Oracle Support.
OGG-00853: Table {0} column {1,number,0} : invalid decimal digit in packed decimal field
The specified table contains invalid data in a packed decimal column.
Action:
Contact Oracle Support.
OGG-00854: Table {0} column {1,number,0} : maximum decimal precision exceeded
The specified table contains a decimal value that is larger than the maximum permitted value.
Action:
Contact Oracle Support.
OGG-00855: Table {0} column {1,number,0} : error {2,number,0} occurred
Extract encountered an error while converting the data in the specified column.
Action:
Contact Oracle Support.
OGG-00856: Table {0} does not have DATA CAPTURE CHANGES enabled for LONG columns. Use the TRANLOGOPTIONS NOREQUIRELONGDATACAPTURECHANGES parameter to override
DB2 LUW Data Capture Changes is not enabled for LONG columns on this table. The TRANLOGOPTIONS parameter is set to its default of REQUIRELONGDATACAPTURECHANGES, which forces Extract to abend when LONGs are not captured. When NOREQUIRELONGDATACAPTURECHANGES is used, Extract issues a warning and continues processing the record.
Action:
Change TRANLOGOPTIONS to NOREQUIRELONGDATACAPTURECHANGES to avoid an abend, or enable capture of LONG columns.
OGG-00857: Table {0} does not have DATA CAPTURE CHANGES enabled for LONG columns. Use the TRANLOGOPTIONS NOREQUIRELONGDATACAPTURECHANGES parameter to override
DB2 LUW Data Capture Changes is not enabled for LONG columns on this table. The TRANLOGOPTIONS parameter is set to its default of REQUIRELONGDATACAPTURECHANGES, which forces Extract to abend when LONGs are not captured. When NOREQUIRELONGDATACAPTURECHANGES is used, Extract issues a warning and continues processing the record.
Action:
Change TRANLOGOPTIONS to NOREQUIRELONGDATACAPTURECHANGES to avoid an abend, or enable capture of LONG columns.
OGG-00858: LONG columns are not supported for the NOCOMPRESSDELETES option for DB2 LUW. LONG columns from table {0} will not be included for delete operations
NOCOMPRESSDELETES writes all of the table columns to the trail, but LOBs are not supported for this feature. Because this is a DELETE, replication will not be affected by this limitation.
Action:
None
OGG-00862: Number of log records read: {0,number,0}. Number of log records dumped to file: {1,number,0}.
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-00863: DB2 Extract log dump stopped
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-00864: DB2 Extract log dump has reached the maximum number of log records it can process in a single run: {0,number,0}
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-00865: Reached RECORDCOUNT value requested of {0,number,0}
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-00866: Reached STOPATLSN value requested of {0,number,0}
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-00867: Only dumping propagated log records
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-00868: {0}
The specified database error occurred.
Action:
Follow the directions in the error message to resolve the problem, or contact Oracle Support.
OGG-00869: {0}
The specified database error occurred, but can be ignored.
Action:
Contact Oracle Support only if a problem persists.
OGG-00870: Database error {0,number,0} ({1})
The specified database error occurred.
Action:
Resolve the error. If the problem persists, contact Oracle Support.
OGG-00871: Could not find column {1} in table {0}
The XML input to the Veridata Agent (VERIAGT) refers to a column that does not exist in the specified table. This usually is caused by an internal error in Veridata Server, which is responsible for validating column references before putting them into the XML messages.
Action:
Contact Oracle Support.
OGG-00873: Could not find primary key column {1} in table {0}
The process encountered an internal error while retrieving primary key information from the database.
Action:
Contact Oracle Support.
OGG-00874: Expected number of output params (sqlexec id {0}) greater than actual ({1,number,0})
The SQLEXEC query or stored procedure contains fewer column parameters than the result of the fetch from the database.
Action:
Correct the SQLEXEC parameter specification. If the problem persists, contact Oracle Support.
OGG-00875: Unexpected error looking for col {0,number,0} in lobmem
The LOB column is missing from the database. Oracle GoldenGate fetches LOB values in certain cases. The table might have been updated to delete the LOB column between the time the transaction record was generated and the time that Extract processed it.
Action:
Contact Oracle Support.
OGG-00876: LOB data exceeds maximum size ({0,number,0}) for column {2,number,0} ({1})
The LOB exceeds the size that is supported by Oracle GoldenGate.
Action:
You can restart Replicat to skip this record with START options, or you can use a REPERROR rule to handle this type of record. Another option is to alter the target table definition to accept null values. For MySQL and Sybase, you can use TRANLOGOPTIONS with ALLOWLOBDATATRUNCATE to truncate LOBs that are too large for a target column.
OGG-00877: Could not map zero length BLOB from source column {0} into non-nullable target column {1}
The target column does not support null column values.
Action:
You can restart Replicat to skip this record with START options, or you can use a REPERROR rule to handle this type of record. Another option is to alter the target table definition to accept null values. You can use TRANLOGOPTIONS with EMPTYLOBSTRING to substitute a string value for empty (zero-length) LOB columns that are replicated to the target. By default, Oracle GoldenGate sets empty columns to NULL on the target and will abend if the target database does not permit LOB columns to be NULL. EMPTYLOBSTRING prevents Replicat from abending.
OGG-00878: Could not execute SQL, not logged onto database
The process could not execute the SQL operation because it did not log onto the database.
Action:
Check the parameter file for the USERID parameter and, if applicable, the SOURCEDB or TARGETDB parameter. These parameters provide the necessary login information. For more information, see the Oracle GoldenGate reference documentation.
OGG-00879: Owner is not specified in table {0}.
An owner is not included for this table in the TABLE and/or MAP specification.
Action:
Qualify all table names with an owner.
OGG-00880: Owner is not specified in table {0}.
The specified table is not qualified with an owner name in the parameter file.
Action:
Add the owner to the table specification, as in hq.sales.
OGG-00881: NODYNSQL cannot be used for columns > 4K
The NODYNSQL parameter is specified for Replicat, but a LOB column greater than 4K in size was encountered during replication.
Action:
Remove NODYNSQL or ensure that there are no LOB values greater than 4K.
OGG-00882: NODYNSQL option is not supported for the wide character types (SQL_WCHAR, SQL_WLONGVARCHAR and SQL_WVARCHAR)
NODYNSQL is being used in the Replicat parameter file, but a wide character type was encountered. In NODYNSQL mode, the process cannot expand the data into a static SQL statement.
Action:
Remove NODYNSQL, and then restart the process.
OGG-00883: failed to update entry in trace table {0}, group {1}. Number of rows updated is {2,number,0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-00884: Fetched fields ({1,number,0}) does not equal total columns ({0,number,0})
The number of fetched columns for the specified table does not match the number of columns for this table as shown in the metadata.
Action:
Find out whether this table was changed since the time that this transaction record was generated. Try restarting the process to see if the problem resolves. If the problem persists, contact Oracle Support.
OGG-00885: error encountered converting fetched column ({0}) from ascii val {1} ({2})
An error occurred when the process tried to convert a fetched column value to an internal format. More information can be obtained from the error message that is provided in the message.
Action:
If you cannot fix the problem based on the error message, contact Oracle Support.
OGG-00886: Unsuccessful execution on interval: {0}
An error occurred when the process tried to execute a SQL statement in a given interval.
Action:
Resolve the problem based on the error text, and then restart the process. If the problem persists, contact Oracle Support.
OGG-00887: Unsuccessful SQL execution on interval: {0}
An non-fatal error occurred when the process tried to execute a SQL statement in a given interval.
Action:
Resolve the problem based on the error text, and then restart the process. If the problem persists, contact Oracle Support.
OGG-00888: SQL statement executed successfully on interval.
The process successfully executed the SQL statement.
Action:
None
OGG-00889: Error performing SQL statement at end of transaction
A fatal error occurred when the process tried to execute a SQL statement at the end of a transaction.
Action:
Resolve the problem based on the SQL error. If the problem persists, contact Oracle Support.
OGG-00890: Error performing SQL statement at end of transaction
A non-fatal error occurred when the process tried to execute a SQL statement at the end of a transaction.
Action:
Resolve the problem based on the SQL error. If the problem persists, contact Oracle Support.
OGG-00891: Unsuccessful execution: {0}
A fatal error occurred when the process tried to execute a SQL statement.
Action:
Resolve the problem based on the SQL error. If the problem persists, contact Oracle Support.
OGG-00892: Unsuccessful SQL execution: {0}
The process was not able to execute the SQL statement because of a database error that is stated in the error text.
Action:
Correct the cause of the error, and then restart the process.
OGG-00893: SQL statement executed successfully.
The process successfully executed a SQL statement.
Action:
None
OGG-00894: SQL error {1,number,0} occurred when updating duplicate row in table {0}
The specified error occurred when the process issued an update on a duplicate row. There may be a constraint error.
Action:
Remove the duplicate row or change the constraint, and then restart the process.
OGG-00895: Unexpected error: could not add HASH for table {0}
An internal error occurred when the process tried to add a hash for the specified table.
Action:
Save this message and any related messages, and contact Oracle Support.
OGG-00896: Unexpected error: Delete of item known to be in hash table failed
An internal error occurred.
Action:
Save this message and any related messages, and contact Oracle Support.
OGG-00897: Unexpected error: could not find newly added table {0} by name
The specified table was resolved by the Extract producer thread but cannot be resolved by the Extract consumer thread.
Action:
Check to see if this table still exists. If not, restart Extract.
OGG-00898: Unexpected error: could not find newly added table {0} by Object ID ({1})
Extract could not find the specified table by its object ID.
Action:
Contact Oracle Support.
OGG-00899: Table {0} does not exist
The specified table does not exist in the database, but is specified in the Oracle GoldenGate configuration.
Action:
Remove the table from the TABLE and MAP statements.
OGG-00900: Table {0} object id {1} not found
An internal error occurred.
Action:
Contact Oracle Support.
OGG-00901: Failed to lookup object ID for table {0}
The DB2 catalog query for the specified table failed.
Action:
The table might have been dropped. If the table still exists, start the process again. If the error persists, contact Oracle Support.
OGG-00902: Total byte length of table {0} is too long (at column {1}, offset = {2,number,0})
The specified column is longer than the maximum length supported by Oracle GoldenGate for the Sybase database.
Action:
Decrease the length of the column.
OGG-00903: Error retrieving row count for last executed statement
The SQLRowCount() call returned an error.
Action:
Check the SQLRowCount() API page to see the possible issues associated with this call and correct the problem. If the problem persists, contact Oracle Support.
OGG-00904: Calling {0} when there is no active transaction (seqno: {1,number,0}, rba: {2,number,0}). Request ignored.
An internal error occurred because a ROLLBACK or COMMIT was called when there was no open transaction.
Action:
Save the trail files, and contact Oracle Support.
OGG-00905: Calling BEGIN when there is still an active transaction (seqno: {0,number,0}, rba: {1,number,0}). Request ignored.
An internal error occurred because a BEGIN TRANSACTION was issued for an open transaction.
Action:
Save the trail files, and contact Oracle Support.
OGG-00906: Unrecognized data type: {0,number,0}
An unexpected data type was encountered.
Action:
Contact Oracle Support.
OGG-00908: Table {0} column {1,number,0} : value truncated to {2,number,0}
The value of the specified column was truncated because the target database does not support the full length. The target data may not be an accurate reflection of the source.
Action:
Extend the target column length, or you can treat these cases as exceptions and apply the DML manually if you want to retain the full data length. For more information, see the error handling documentation in the Oracle GoldenGate Administration documentation.
OGG-00909: Table {0}, column {1}, unrecognized data type: {2,number,0}
The specified column contains an unsupported data type.
Action:
For supported data types, see the Oracle GoldenGate documentation for this database.
OGG-00910: Table {0}, column {1}, unrecognized data type: {2}
The specified column contains an unrecognized or unsupported data type.
Action:
For supported data types, see the Oracle GoldenGate documentation for this database.
OGG-00911: Table {0}, column {1}, unrecognized or unsupported data type: {2}
The specified column contains an unrecognized or unsupported data type.
Action:
For supported data types, see the Oracle GoldenGate documentation for this database.
OGG-00912: Could not find key column {1} within definition for table {0}
The key definition probably was changed. Oracle GoldenGate needs to know of the new definition.
Action:
Stop and then immediately start the process, so a new object cache can be built.
OGG-00913: Invalid datatype ({2,number,0}) processing column {0} ({1,number,0})
The specified column contains an unrecognized or unsupported data type.
Action:
For supported data types, see the Oracle GoldenGate documentation for this database.
OGG-00914: Table {0} contains too many columns. Max columns allowed is {1,number,0}
The number of columns in the table exceeds that which is supported by Oracle GoldenGate.
Action:
You can exclude columns, if permissible, by using the COLSEXCEPT clause of TABLE and MAP, or you can remove the table from the Oracle GoldenGate configuration.
OGG-00915: Column {1} in table {0} cannot be used as a key column.
The specified column is of a type that is not supported for use as a key by Oracle GoldenGate.
Action:
If the key cannot be altered to remove the column, you can specify a unique index or you can define a key with the KEYCOLS clause of TABLE and MAP. The index or KEYCOLS must match on the source and target tables.
OGG-00916: Column {1} cannot be used as a key column. Define a unique index for table {0} without this column or use the KEYCOLS parameter to correct this issue
The specified column in the table key is of a type that is not supported for use as a key by Oracle GoldenGate.
Action:
If the key cannot be altered to remove the column, you can specify a unique index or you can define a key with the KEYCOLS clause of TABLE and MAP. The index or KEYCOLS must match on the source and target tables.
OGG-00917: KEYCOLS parameter references column {1} which cannot be used as a key column. Remove this column from the KEYCOLS parameter for table {0} to correct this issue
The specified column is of a type that is not supported for use as a key by Oracle GoldenGate.
Action:
Remove the column from the KEYCOLS clause.
OGG-00918: Key column {0} is missing from map
Some, but not all, key columns are mapped in a COLMAP clause. If mapping key columns, all key columns must be mapped.
Action:
Add all key column(s) to the COLMAP clause.
OGG-00919: Error in {0} clause
There is a syntax error in the specified clause in the parameter file.
Action:
Fix the error. For help, see the Oracle GoldenGate reference documentation.
OGG-00920: Error ({1,number,0}) executing command {0}
The execution of an immediate SQL statement failed.
Action:
Contact Oracle Support.
OGG-00921: Unable to determine the database name
The process could not determine the name of the database in order to establish a connection.
Action:
Make certain that the Oracle GoldenGate user has privileges to query the database name. Also, make certain that the SOURCEDB or TARGETDB parameter is specified, if required for this database type.
OGG-00924: The wildcard specification length has a length of {1,number,0}. The maximum allowed in the return buffer is {0,number,0}
The wildcard specification has too many characters.
Action:
Reduce the length of the wildcard specification to the size specified in the message.
OGG-00925: Tables are out-of-sync. Source: {0}, Target: {1}, Rows {2,number,0}.
This message is deprecated.
Action:
None
OGG-00926: Tables are in sync. Source: {0}, Target: {1}.
This message is deprecated.
Action:
None
OGG-00927: Error in status file: missing {0} attribute
The specified attribute is missing from the XML message for the Oracle GoldenGate server or agent process. This indicates an internal error.
Action:
Contact Oracle Support.
OGG-00928: exceeded max_tables ({0,number,0})
Oracle GoldenGate Veridata Agent was asked to list all tables or views in a remote database or schema, and the number of tables exceeds the amount that can fit in the message.
Action:
File an enhancement request with Oracle Support to increase the maximum number of tables supported.
OGG-00929: exceeded max_schemas ({0,number,0})
Oracle GoldenGate Veridata Agent was asked to list all tables or views in a remote database or schema, and the number of tables exceeds the number of schemas that can fit in the message.
Action:
File an enhancement request with Oracle Support to increase the maximum number of schemas supported.
OGG-00930: Invalid XML in parameter file {0}
This message is deprecated.
Action:
None
OGG-00931: Invalid configuration file: {0}
This message is deprecated.
Action:
None
OGG-00932: File name resolution error {0,number,0} on file {1}.
This error occurs on a NonStop system when the agent cannot determine the Guardian file name for an Oracle GoldenGate sub-directory. The Guardian error code is displayed with the message.
Action:
Take the appropriate action based on the Guardian error code.
OGG-00933: could not find name for table entry {0,number,0}
The attribute for the table name is missing from the XML file.
Action:
Contact Oracle Support.
OGG-00934: could not find table-info node for {0}
The table-info element is missing from the XML file.
Action:
Contact Oracle Support.
OGG-00935: No keycols specified for table {0} that does not have a primary key
No defined primary key or user-defined key columns are defined for the specified comparison table.
Action:
Contact Oracle Support.
OGG-00936: Access denied (request from {0}, rule #{1,number,0})
Access to Manager was denied to the specified address based on rules set in the ACCESSRULE parameter.
Action:
Determine why the connection attempt was made. If it is legitimate, you can adjust the rules of ACCESSRULE.
OGG-00937: Error ({0,number,0}) decrypting password: {1}.
Manager on the target cannot decrypt the password that was specified with the ENCRYPT PASSWORD command on the source.
Action:
If you defined your own key, make certain the ENCKEYS files on the source and target exist, and that they contain the same key. If you used an Oracle GoldenGate-generated default key, make certain it was copied correctly into the USERID or TRANLOGOPTIONS ASMUSER parameters. You might need to retry the default encryption again.
OGG-00938: Manager is stopping at user request
The Manager process was stopped by a user.
Action:
None, if intentional. Note that when Manager is stopped, Oracle GoldenGate processes cannot continue to replicate data.
OGG-00939: Service Control Manager requested PAUSE
The Windows Service Control Manager issued a PAUSE command for the Manager service.
Action:
None, if intentional. Note that when Manager is paused, Oracle GoldenGate processes cannot continue to replicate data.
OGG-00940: Service Control Manager requested STOP
The Windows Service Control Manager issued a STOP command for the Manager service.
Action:
None, if intentional. Note that when Manager is stopped, Oracle GoldenGate processes cannot continue to replicate data.
OGG-00941: Service Control Manager requested CONTINUE
The Windows Service Control Manager issued a CONTINUE (Resume) command for the Manager service.
Action:
None
OGG-00942: Service Control Manager requested SHUTDOWN
The Windows Service Control Manager issued a SHUTDOWN command for the Manager service.
Action:
None, if intentional. Note that when Manager is stopped, Oracle GoldenGate processes cannot continue to replicate data.
OGG-00943: Error in service processing: Creating thread for batch tasks (error {0,number,0})
The process could not create a thread for batch tasks.
Action:
Verify that the system has the capacity for creating more threads. If you cannot resolve the problem, contact Oracle Support.
OGG-00944: Error in service processing: Calling {0} (error {1,number,0})
A call to the Windows SetServiceStatus or RegisterServiceCtrlHandler failed.
Action:
Check the Windows system error log and correct the problem. If you cannot resolve the problem, contact Oracle Support.
OGG-00945: Startup of Extract group {0} failed. Detail: {1}.
The specified Extract cannot start.
Action:
Look for additional error messages that indicate why the process cannot start, and then correct the problem.
OGG-00946: Application {0} abended.
The specified process abended.
Action:
Look for additional error messages that indicate why the process abended, and then correct the problem.
OGG-00950: Purge of old extract file {0} failed because the prev seqno exists. Purge rule: {1}
There is a MINKEEP rule in the PURGEOLDEXTRACTS parameter that requires a minimum number of files to be retained.
Action:
None
OGG-00951: Purging task Extract group {0}: could not delete file {1} ({2,number,0} {3}).
Manager could not purge the named remote task because it could not delete the specified file due to an operating system error.
Action:
Fix the operating system error.
OGG-00952: Purging log history from {0} older than {1}: {2}
Manager successfully purged rows in the log table that were older than the date shown. Informational only. This message appears in older Oracle GoldenGate versions that support trigger-based capture.
Action:
None
OGG-00953: Purging log history from {0} older than {1}: {2}
Manager is purging history from the log table. Informational only. This message appears in older Oracle GoldenGate versions that support trigger-based capture.
Action:
None
OGG-00954: Purging rows from {0} older than {1}: {2}
Manager failed to purge rows in the log table that are older than the date shown. Informational only. This message appears in older Oracle GoldenGate versions that support trigger-based capture.
Action:
Delete the rows manually.
OGG-00955: Purging rows from {0} older than {1}: {2}
Manager successfully purged rows in the log table that were older than the date shown. Informational only. This message appears in older Oracle GoldenGate versions that support trigger-based capture.
Action:
None
OGG-00956: hours_since_modified calculated as {1,number,0}, modtime is {2,number,0} for {0}
Manager determined that the specified file remained unmodified for the number of hours shown in this message, with the last modification being performed at the time shown.
Action:
None
OGG-00957: Purged old extract file '{0}'. Purge rule: {1}
The specified file was purged under the rules shown in the message text.
Action:
None
OGG-00958: {0} (MINKEEPFILES option not used; last MINKEEP time option entered will be used)
The PURGEOLDEXTRACTS parameter contains the option MINKEEPHOURS or MINKEEPDAYS with the option MINKEEPFILES. These are mutually exclusive. If either MINKEEPHOURS or MINKEEPDAYS is used with MINKEEPFILES, then MINKEEPHOURS or MINKEEPDAYS is accepted, and MINKEEPFILES is ignored.
Action:
Remove MINKEEPFILES or MINKEEP{HOURS│DAYS} depending on your requirements.
OGG-00959: MINKEEPFILES option not used for parameter {0}.
The PURGEOLDEXTRACTS parameter contains the option MINKEEPHOURS or MINKEEPDAYS with the option MINKEEPFILES. These are mutually exclusive. If either MINKEEPHOURS or MINKEEPDAYS is used with MINKEEPFILES, then MINKEEPHOURS or MINKEEPDAYS is accepted, and MINKEEPFILES is ignored.
Action:
Remove MINKEEPFILES or MINKEEP{HOURS│DAYS} depending on your requirements.
OGG-00960: Access granted (rule #{0,number,0})
Access to Oracle GoldenGate was granted based on the specified rule.
Action:
None
OGG-00961: DEBUG {0}: {1}
This is an informational message for debugging purposes.
Action:
None
OGG-00962: {1} did not recognize command {0}
Manager received an unrecognized command.
Action:
Check the syntax of the command for typographical errors or invalid options. For help, see the Oracle GoldenGate reference documentation or the online GGSCI help.
OGG-00963: Command received from application {0} on host {1}: {2}.
Manager received the specified command from the specified host.
Action:
None
OGG-00964: The application {0} started automatically.
The specified process was restarted automatically based on the AUTOSTART parameter.
Action:
None
OGG-00965: Extract group {0} restarted automatically.
The specified Extract was restarted automatically based on rules in the AUTORESTART parameter.
Action:
None
OGG-00966: Application {0} is already running.
A START command was issued for a process that is already running.
Action:
None
OGG-00967: Manager performing AUTOSTART processing.
Manager is automatically starting processes according to the AUTOSTART parameter(s) in the Manager parameter file.
Action:
None
OGG-00968: Error: can not send command to Manager.
The last command could not be sent to Manager.
Action:
Make certain that Manager is running and that the network connections to it are working properly.
OGG-00969: Error: Manager responded with {0}.
Manager could not start the passive Extract.
Action:
Check the process report and the error log for additional messages that provide context for this problem. If you cannot resolve the problem based on other messages, contact Oracle Support.
OGG-00970: Error: Bad reply message from Manager.
The Manager reply is not valid.
Action:
Contact Oracle Support. Save the process report and the error log for the support case.
OGG-00972: {0} {1} -> {2}@{3} started on port {4}.
The specified program started on the specified port number.
Action:
None
OGG-00973: Manager started replicat task process (Port {0,number,0}).
Manager started a Replicat task on the specified port number.
Action:
None
OGG-00974: Manager started collector process (Port {0,number,0}).
Manager started a Collector process on the specified port number.
Action:
None
OGG-00975: {0}
This is a generic informational message and does not indicate any problem.
Action:
None
OGG-00976: Manager started '{0}' process on port {1,number,0}.
Manager started the specified process on the specified port number.
Action:
None
OGG-00978: Application {0} group {1} is running.
The specified process is running.
Action:
None
OGG-00979: {0} {1} is down (gracefully).
The specified process stopped gracefully.
Action:
None
OGG-00980: Purged task Extract group {0}.
The specified task was purged according to the rules in the PURGEOLDTASKS parameter.
Action:
None
OGG-00981: Task Extract group {0} is running, cannot purge.
The specified task is still running.
Action:
Stop the task to enable purging.
OGG-00982: Rule {0,number,0}: {1}, seqno: {2,number,0}, hours_since_modified: {3,number,0}, modtime: {4,number,0}, oldest chkpt: {5,number,0}
Manager is purging old trail files based on the rules specified in PURGEOLDEXTRACTS.
Action:
None
OGG-00983: Manager started (port {0,number,0}).
The Manager process started on the specified port number.
Action:
None
OGG-00984: Delaying {0,number,0} minutes, {1,number,0} seconds before further processing.
The BOOTDELAYMINUTES parameter is being used for Manager, and Manager is waiting for the specified amount of time before performing its startup activities.
Action:
None
OGG-00985: Purged old veriagt report {0}
The Veridata Agent report was purged successfully.
Action:
None
OGG-00986: Error {1,number,0} Purging old veriagt report {0}
The Veridata Agent report could not be purged due to the specified error from the operating system.
Action:
Correct the operating system error.
OGG-00987: GGSCI command ({0}): {1}
The specified command from GGSCI was received.
Action:
None
OGG-00988: WARNING: Unsupported operation. This might cause transactional inconsistency. Modifying input checkpoint #{3,number,0}, Oracle thread #{4,number,0} of {2}: ioseq = {0,number,0} iorba = {1,number,0}
An ALTER EXTRACT command was issued to alter the read position of an Extract thread that reads one of the logs in a RAC configuration.
Action:
None. This is a warning but assumes the action is intentional. For help, contact Oracle Support.
OGG-00989: WARNING: Unsupported operation. This might cause transactional inconsistency. Modifying iocheckpoint: ioseq = {0,number,0} iorba = {1,number,0}
An unsupported ALTER operation was received.
Action:
None. This is a warning but assumes the action is intentional. For help, contact Oracle Support.
OGG-00990: Replicat group {0} stop forced by user.
The specified Extract process was stopped forcefully by a user.
Action:
None
OGG-00991: Extract group {0} stopped normally.
The specified Extract process stopped gracefully.
Action:
None
OGG-00992: Extract group {0} starting.
The specified Extract process is performing its startup.
Action:
None
OGG-00993: Extract group {0} started.
The specified Extract process started successfully.
Action:
None
OGG-00994: Replicat group {0} stopped normally.
The specified Replicat process stopped gracefully.
Action:
None
OGG-00995: Replicat group {0} starting.
The specified Replicat process is performing its startup.
Action:
None
OGG-00996: Replicat group {0} started.
The specified Replicat process started successfully.
Action:
None
OGG-00997: Purge of old extract file {0} failed (error {1,number,0}, {2})
The process tried to purge old trail files based on the rules in the PURGEOLDEXTRACTS parameter, but it encountered the specified operating-system error.
Action:
Correct the cause of the error or contact the system administrator.
OGG-00998: Purging old extract file {0}
The process is purging old trail files based on the rules in the PURGEOLDEXTRACTS parameter.
Action:
None
OGG-00999: Missing transaction begin, {0,number,0} records bypassed
The process skipped the specified number of records because the begin-transaction record is missing.
Action:
None
OGG-01000: Reperror {0} rule for error {1,number,0} found, Action {2}, Maxretries {3,number,0} exceeded
Replicat parsed a REPERROR rule statement with the specified error number and action, and retried the operation up to the maximum number of times that is specified with the MAXRETRIES option.
Action:
Correct the problem that caused the error, and then restart Replicat.
OGG-01001: Reperror {0} rule for error {1,number,0} found, Action {2}
Replicat parsed a REPERROR rule statement and will take the specified action for the operation that returned the specified error number.
Action:
None
OGG-01002: Reperror {0} rule for error {1,number,0} found, Action {2}, retries {3,number,0}
Replicat parsed a REPERROR rule statement that includes the RETRYOP option, and will retry the operation that returned the specified error number.
Action:
None
OGG-01003: Repositioning to rba {1,number,0}{0,choice,-1#│0# in seqno {0,number,0}}
The process is repositioning its read point to the specified location in the trail.
Action:
None
OGG-01004: Canceled grouped transaction on table {0}. Database error {1,number,0}, ({2}).
Replicat is not able to apply the GROUPTRANSOPS-controlled grouped transaction on the specified table, due to the SQL error that is reported in the message text.
Action:
Correct the problem that is reported in the error message. For more information on GROUPTRANSOPS, see the Oracle GoldenGate reference documentation.
OGG-01005: A value of zero for GROUPTRANSOPS is invalid. Using a value of one instead.
A value of zero is specified for the GROUPTRANSOPS parameter. A value of 1 executes the operations within the same transaction boundaries as the source transaction. Any value above 1 sets the minimum number of operations within a Replicat transaction.
Action:
Increase the value of GROUPTRANSOPS. See the Oracle GoldenGate reference documentation to determine an appropriate value.
OGG-01006: Maximum records exceeded in discard file ({0,number,0})
The maximum number of records allowed in the file specified with the DISCARDFILE parameter has been reached.
Action:
Increase the file size up to maximum permitted by the MAXBYTES or MEGABYTES option of DISCARDFILE.
OGG-01007: Maximum records exceeded in discard file ({0,number,0})
The maximum number of records allowed in the file specified with the DISCARDFILE parameter has been reached.
Action:
Increase the file size up to maximum permitted by the MAXBYTES or MEGABYTES option of DISCARDFILE.
OGG-01008: Discarding bad record (discard recs = {0,number,0})
The process is discarding a record that it cannot process, and it is reporting the current number of discarded records that are in the DISCARDFILE file.
Action:
None
OGG-01009: Error executing stored proc {0}: {1}
The process attempted to execute the specified stored procedure, but the specified database error was returned.
Action:
Fix the cause of the error that is shown in the message text.
OGG-01010: Error executing stored proc {0}: {1}
The process attempted to execute the specified stored procedure, but the specified database error was returned.
Action:
Fix the cause of the error that is shown in the message text.
OGG-01011: Skipped {0}.
The SEND EXTRACT command was issued with SKIPTRANS, and Extract skipped the specified long-running transaction.
Action:
None
OGG-01012: Failed to skip {0} due to error ({1}).
The SEND EXTRACT command was issued with SKIPTRANS, but Extract cannot skip the specified long-running transaction. Some possible causes are: the specified transaction is not the oldest one in the list of transactions shown with SHOWTRANS, or the THREAD option was not used if the database is Oracle RAC.
Action:
Fix the cause of the error that is shown in the message text.
OGG-01013: Cannot replace missing not-null column {1} of table {0}
The process encountered a not-null column for which no data existed, and it attempted to fetch a value from the database, but failed.
Action:
None
OGG-01014: Positioning with begin time: {0,date} {0,time}, starting record time: {1,date} {1,time} at {2,choice,-1#│0#extseqno {2,number,0}, }extrba {3,number,0}
The process is configured to start processing at the specified time, and it is starting with the specified record as the first one to be processed.
Action:
None
OGG-01015: Positioning with begin time: {0,date} {0,time}, waiting for data: at extseqno {1,number,0}, extrba {2,number,0}
The process is configured to start processing at the specified time. It is currently waiting for data at the specified position in the data source.
Action:
None
OGG-01016: Positioning with begin time: {0,date} {0,time}, skipping incomplete record - starting record time: {1,date} {1,time} at extseqno {2,number,0}, extrba {3,number,0}
The process is configured to start processing at the specified time. The first record with that timestamp is incomplete, so it is being skipped.
Action:
None
OGG-01017: Wildcard resolution set to IMMEDIATE because SOURCEISTABLE Extract is used.
The WILDCARDRESOLVE parameter is set to its default of DYNAMIC, but the process overrode the setting because SOURCEISTABLE is also used in the parameter file. IMMEDIATE is the forced default for SOURCEISTABLE. Source objects that satisfy a wildcard definition are processed at startup.
Action:
None
OGG-01018: Recovered from error at rba {1,number,0} in seqno {0,number,0}, replicat continuing
The recovery from the failed operation succeeded.
Action:
None
OGG-01020: Processed extract process {0} record at seq {2,number,0}, rba {3,number,0} (canceled {1,number,0} records)
Extract processed the specified record. Informational only.
Action:
None
OGG-01021: Command received from application {0}: {1}.
A command was received from the specified process. This is informational only.
Action:
None
OGG-01022: Unknown {1,number,0} bytes message received from {2}:{3,number,0} - {0}
An incomplete command was received from the specified process and cannot be executed.
Action:
If this message continues to appear, contact Oracle Support.
OGG-01023: Recovered from retryable error on table {0}
Replicat successfully applied a SQL operation that caused an error in a previous attempt. Informational only.
Action:
None
OGG-01024: Retrying SQL error {3,number,0} at rba {2,number,0} in seqno {1,number,0}, updating {0} in {4,number,0} seconds
Replicat is retrying a SQL operation that caused an error, based on REPERROR with the RETRYOP option. Informational only.
Action:
None
OGG-01025: REPLICAT task started by manager (port {0,number,0})
The Manager on the target started a remote-task Replicat. Informational only.
Action:
None
OGG-01026: Rolling over remote file {0}
Extract is closing the current remote file and starting a new one. Informational only.
Action:
None
OGG-01027: {0}
A non-recoverable error occurred in Extract or Replicat.
Action:
Contact Oracle Support and provide the details of this message.
OGG-01028: {0}
A non-recoverable error occurred in Extract or Replicat.
Action:
Contact Oracle Support and provide the details of this message.
OGG-01029: Extract reposition err - {0}
The process encountered an error while attempting to position to a specific point in the trail file.
Action:
Verify that the specified sequence number and RBA exist, and specify valid ones if necessary. Restart the process. Contact Oracle Support if this problem persists.
OGG-01030: Could not find checkpoint for output file {0}
During recovery, Extract encountered a trail file that is no longer assigned to it.
Action:
Specify the correct trail for this process, and delete the incorrect trail file with the DELETE EXTTRAIL or DELETE RMTTRAIL command.
OGG-01031: There is a problem in the communication with the Collector/Receiver Service. (Reply received is '{0}')
The Extract, Pump, or Distribution Service was not able to send data to the target.
Action:
Examine the network for an outage between the source and target system. Make certain that MGRPORT in RMTHOST matches the one in the parameter file of the remote Manager. Check for errors on the target system that indicate the Manager or Collector process is not running, or that Collector does not have privileges to write to the remote trail. Check for encryption errors if the ENCRYPT option is specified with the RMTHOST or RMTHOSTOPTIONS parameter: This might indicate that the encryption key that was sent from the source does not match the one in the ENCKEYS file on the target, or that the key or ENCKEYS file on the target is missing.
OGG-01032: There is a problem in the communication with the Collector. Length is {1,number,0} - {0}
Extract was not able to send data to the target.
Action:
Examine the network for an outage between the source and target system. Make certain that MGRPORT in RMTHOST matches the one in the parameter file of the remote Manager. Check for errors on the target system that indicate the Manager or Collector process is not running, or that Collector does not have privileges to write to the remote trail. Check for encryption errors if the ENCRYPT option is specified with the RMTHOST or RMTHOSTOPTIONS parameter: This might indicate that the encryption key that was sent from the source does not match the one in the ENCKEYS file on the target, or that the key or ENCKEYS file on the target is missing.
OGG-01033: There is a problem in the communication with the Collector. (Remote file used is {0}, reply received is {1})
Extract was not able to send data to the target.
Action:
Examine the network for an outage between the source and target system. Make certain that MGRPORT in RMTHOST matches the one in the parameter file of the remote Manager. Check for errors on the target system that indicate the Manager or Collector process is not running, or that Collector does not have privileges to write to the remote trail. Check for encryption errors if the ENCRYPT option is specified with the RMTHOST or RMTHOSTOPTIONS parameter: This might indicate that the encryption key that was sent from the source does not match the one in the ENCKEYS file on the target, or that the key or ENCKEYS file on the target is missing.
OGG-01034: There is a problem in the communication with the Collector. Remote trail file: {0}.
Extract was not able to send data to the target.
Action:
Examine the network for an outage between the source and target system. Make certain that MGRPORT in RMTHOST matches the one in the parameter file of the remote Manager. Check for errors on the target system that indicate the Manager or Collector process is not running, or that Collector does not have privileges to write to the remote trail. Check for encryption errors if the ENCRYPT option is specified with the RMTHOST or RMTHOSTOPTIONS parameter: This might indicate that the encryption key that was sent from the source does not match the one in the ENCKEYS file on the target, or that the key or ENCKEYS file on the target is missing.
OGG-01035: File {0} already exists and purge not specified
The process will not write to an existing file unless the PURGE option is used with the RMTFILE parameter.
Action:
Add the PURGE option, and then restart the process.
OGG-01038: Cannot fetch required data from table {0} due to missing key columns
Row data could not be fetched from the table because no key is defined on the table.
Action:
Define a key or specify unique columns with the KEYCOLS clause of the TABLE statement.
OGG-01039: mergeFetchedCols() failed to merge result fetched from table
Extract was not able to merge the fetched data with the row data that was obtained from the transaction log.
Action:
Contact Oracle Support.
OGG-01040: Failed to prepare fetch on table {0}.
This is an internal error.
Action:
Contact Oracle Support.
OGG-01041: Failed to prepare fetch on table {0} due to lack of defined key columns. Use KEYCOLS.
Row data could not be fetched from the table because no key is defined on the table.
Action:
Define a key or specify unique columns with the KEYCOLS clause of the TABLE statement.
OGG-01042: Invalid token length, expected: {0,number,0}, got: {1,number,0}
This is an internal error.
Action:
Contact Oracle Support.
OGG-01043: Terminate on fetch result = {1} ({2,number,0}) (table: {0})
The process failed to fetch column data, and the ABEND action is specified by the REPFETCHEDCOLOPTIONS parameter.
Action:
None. This is the expected result for ABEND.
OGG-01044: The trail '{0}' is not assigned to extract '{1}'. Assign the trail to the extract with the command "ADD EXTTRAIL/RMTTRAIL {0}, EXTRACT {1}"
The trail is specified in the Extract parameter file with an EXTTRAIL or RMTTRAIL parameter, but the required command to link the trail to the Extract process was not issued.
Action:
In GGSCI, issue the ADD EXTTRAIL or ADD RMTTRAIL command.
OGG-01045: Unrecognized response from server recovering target file {0}, at RBA {1,number,0}
Extract encountered a parsing error while reading values from a reply sent by the Server (Collector) process.
Action:
Contact Oracle Support.
OGG-01046: Target does not support append recovery mode. Reverting to overwrite recovery mode in file {0}, at RBA {1,number,0}
The version of the Server (Collector) is older than the version of Extract, and it does not support APPEND mode for trails or files. It is just a warning. Extract handles this situation automatically.
Action:
None
OGG-01048: Server error while recovering target file {0}, at RBA {1,number,0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01049: Invalid server return code ({0,number,0}) for target file {1}, at RBA {2,number,0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01051: Reverting to overwrite recovery mode at user's request...
The recovery method (controlled by the RECOVERYOPTIONS parameter) was changed to overwrite mode, from the default of append mode. Informational only.
Action:
None
OGG-01052: No recovery is required for target file {0}, at RBA {1,number,0} (file not opened)
No trail exists to recover.
Action:
None
OGG-01053: Recovery completed for target file {0}, at RBA {1,number,0}
Extract completed its recovery.
Action:
None
OGG-01054: Recovery completed for target file {0}, at RBA {1,number,0}, CSN {2}
Extract completed its recovery.
Action:
None
OGG-01055: Recovery initialization completed for target file {0}, at RBA {1,number,0}
The initialization phase of recovery completed. No transaction was found in the portion of the trail that was scanned, probably because Extract is inactive.
Action:
None
OGG-01056: Recovery initialization completed for target file {0}, at RBA {1,number,0}, CSN {2}
The initialization phase of recovery completed, and transaction were found in the portion of the trail that was scanned. This is informational only.
Action:
None
OGG-01057: Recovery completed for all targets
Extract recovered successfully for all of its targets.
Action:
None
OGG-01058: Empty commit sequence number (CSN) detected in target file {0}, at RBA {1,number,0}
An inconsistency occurred in the communication between Extract and Server (Collector).
Action:
Contact Oracle Support.
OGG-01059: Invalid commit sequence number (CSN) detected in target file {0}, at RBA {1,number,0}
An inconsistency occurred in the communication between Extract and Server (Collector).
Action:
Contact Oracle Support.
OGG-01060: Failed to retrieve CSN from data source during recovery
The current CSN read point from the transaction log could not be found during Extract recovery.
Action:
Contact Oracle Support.
OGG-01061: Invalid CSN value length({0,number,0}) from data source during recovery
The current CSN in the transaction record has an invalid length.
Action:
Contact Oracle Support.
OGG-01062: Invalid last CSN value length({1,number,0}) for trail {0} during recovery
The length of the CSN of the last completed transaction is invalid.
Action:
Contact Oracle Support.
OGG-01063: Current CSN value length({1,number,0}) differs from last CSN value length({2,number,0}), trail {0} during recovery
The length of the current CSN does not match the length of the CSN of the last completed transaction.
Action:
Contact Oracle Support.
OGG-01064: {5}: Buffer overflow, needed: {1,number,0}, allocated: {0,number,0} in trail {2}, Seqno {3,number,0}, RBA {4,number,0}
While updating the CSN, transaction ID, or transaction ID list in memory, the process determined that there is not enough space for this information in the buffer.
Action:
Contact Oracle Support.
OGG-01065: no CSN token found in record in trail {0}, Seqno {1,number,0}, RBA {2,number,0}
The CSN is missing from the trail record.
Action:
Contact Oracle Support.
OGG-01066: Input record from trail file {0}, Seqno {1,number,0}, RBA {2,number,0}, has CSN {3} but no Transaction ID
The transaction identifier is missing from the trail record.
Action:
Contact Oracle Support.
OGG-01067: Empty transaction ID detected in target file {0}, at RBA {1,number,0}
The transaction identifier in the trail record is empty.
Action:
Contact Oracle Support.
OGG-01068: Invalid transaction ID detected in target file {0}, at RBA {1,number,0}
The transaction identifier in the trail record is invalid.
Action:
Contact Oracle Support.
OGG-01069: Exceeded tran ID list size recovering target file {0}, at RBA {1,number,0}
While adding a transaction ID to the transaction ID list that is maintained for the current CSN, the process detected that there is no space left to add more transaction IDs.
Action:
Contact Oracle Support.
OGG-01070: Cannot translate threshold status word for target file {0}, at RBA {1,number,0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01071: {0} cannot be used with stored data
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01072: {2}: Buffer overflow, needed: {1,number,0}, allocated: {0,number,0}
A variable value did not fit into the internal buffer that was assigned to it at runtime. This is an internal error.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01073: {1}: Array overflow, {0,number,0} maximum entries
An array element in an XML message exceeded the defined limit.
Action:
Contact Oracle Support.
OGG-01074: Logical application error: invalid case statement, value {0,number,0} in function {1}.
Internal error.
Action:
Contact Oracle Support.
OGG-01075: The table object ID cannot be used to look up the table entry if the tables were added via a SOURCEDEFS file
The definitions file prevents correct table name resolution. DB2 LUW only gives the tablespace ID and the table object ID in the log records. To be able to resolve the actual owner and table name as they are given in the TABLE parameter, Extract looks up the tablespace and object IDs in the database catalog. The IDs are used in an ODBC query against the system catalog tables to retrieve the table name. This process is not possible if a SOURCEDEFS or TARGETDEFS file is used as input.
Action:
Remove the SOURCEDEFS or TARGETDEFS parameter.
OGG-01076: The table object ID cannot be used to look up the table entry if the table is a target table definition
This message is deprecated.
Action:
None
OGG-01077: Error closing file, handle: 0x{0}, err: {1,number,0} - {2}
An operating system error was returned when attempting to close a file.
Action:
Check the local file systems for errors.
OGG-01078: fcntl failure closing files after fork() {0,number,0} - {1,number,0}: {2}
Manager started a new Extract or Replicat process, but failed to close unused open file handles to reduce the number of open file handles.
Action:
Check the host system for a possible file handle shortage. Consider restarting Manager and all Extract and Replicat processes if this warning persists.
OGG-01079: Data for column {0,number,0} is {2,number,0} bytes which exceeds the maximum of {1,number,0} bytes. Column data truncated for user exit.
The data for the specified column exceeds the size allowed by the user exit. Informational only.
Action:
None
OGG-01080: SP {0} column {1} nearing buffer maximum of {2,number,0} bytes
The process is approaching the maximum buffer size that is set with the PARAMBUFSIZE of the SQLEXEC parameter. This buffer stores input and output parameters.
Action:
Stop the process, increase the buffer size, and then restart the process.
OGG-01081: SP {0} column {1} exceeded buffer maximum of {2,number,0} bytes
The SQLEXEC input/output parameters exceeded the maximum buffer size that is set with the PARAMBUFSIZE of the SQLEXEC parameter.
Action:
Stop the process, increase the buffer size, and then restart the process.
OGG-01082: The call to the function {0} from the function {2} failed with return code {1,number,0}.
An API error occurred.
Action:
Contact Oracle Support.
OGG-01083: The call to the function {0} from the function {1} failed with return code {2,number,0} ({3}).
A call to an operating system-provided API failed.
Action:
Check the operating system for related problems, and resolve them or contact your system administrator. If you cannot resolve the problem, contact Oracle Support.
OGG-01084: WIN32 API CALL {0} failed {1,number,0} ({2})
A call to an operating system-provided API failed.
Action:
Check the operating system for related problems, and resolve them or contact your system administrator. If you cannot resolve the problem, contact Oracle Support.
OGG-01085: Application {0} received window closed event.
A user terminated an interactive process by closing the console window instead of issuing a STOP command from GGSCI. This is informational only.
Action:
None
OGG-01086: Application {0} received system shutdown event.
An interactive process was terminated due to a system shutdown instead of a STOP command from GGSCI. This message is informational only.
Action:
None
OGG-01087: Application {0} received user log off event.
A logged-on user terminated the Windows desktop session. This message only occurs when Oracle GoldenGate is configured to run as a Windows service, and it is informational only.
Action:
None
OGG-01088: Out of memory condition encountered. {2} attempting to allocate {1,number} bytes with {0}.{3,choice,0#│1# Process using {3,number} KB physical memory.}{4,choice,0#│1# Process using {4,number} KB virtual memory.}
An attempt to allocate memory from the host system failed.
Action:
Check the system for a possible memory shortage. On some operating systems, this message is accompanied by a detailed memory-usage report that might assist with troubleshooting efforts.
OGG-01089: Directory {0} does not exist
The directory that is specified with TRANSMEMORY does not exist.
Action:
Specify a different directory, or check the file system for possible damage.
OGG-01090: Unable to create directory "{0}" (error {1,number,0}, {2})
The specified directory could not be created. The path does not exist or the disk is full.
Action:
Specify a valid directory name if the disk is not full.
OGG-01091: Unable to open file "{0}" (error {1,number,0}, {2})
The process could not open the specified file.
Action:
Verify that the Oracle GoldenGate user has the privilege to open and write to files.
OGG-01092: Unable to lock file "{0}" (error {1,number,0}, {2})
The process could not lock the specified file.
Action:
Determine whether this file is locked by another process and, if so, determine whether the other process is supposed to access this file or not. Check the Oracle GoldenGate configuration and fix any errors in the file specifications. If the problem persists, contact Oracle Support.
OGG-01093: Unable to delete file "{0}" (error {1,number,0}, {2})
The process could not remove the specified file.
Action:
Verify that the process has privileges to remove the file.
OGG-01094: Unable to delete file "{0}" (error {1,number,0}, {2})
The process could not remove the specified file.
Action:
Verify that the process has privileges to remove the file.
OGG-01095: Unable to redirect file "{0}" (error {1,number,0}, {2})
The process could not redirect to the output file.
Action:
Verify that the process had privilege to redirect.
OGG-01096: Unable to write to file "{0}" (error {1,number,0}, {2})
An error occurred while the process was writing to an open file.
Action:
Check for related errors in the error log of the operating system. If you cannot resolve the problem, contact Oracle Support.
OGG-01097: Could not sync "{0}" (error {1,number,0}, {2})
The process could not sync the specified file to disk.
Action:
Check for related errors in the error log of the operating system. If you cannot resolve the problem, contact Oracle Support.
OGG-01098: Could not flush "{0}" (error {1,number,0}, {2})
The specified operating system error occurred when the process tried to flush the file.
Action:
Contact Oracle Support.
OGG-01099: Function {1}, argument {0} cannot be NULL
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01100: Unrecoverable XML configuration error
A library error occurred while parsing the XML document.
Action:
Check for a message that was issued by the library. If you cannot resolve the problem based on other errors, contact Oracle Support.
OGG-01101: Unable to build IPC message from XML node.
A library error occurred while building an XML message.
Action:
Check for a message that was issued by the XML processor. If you cannot resolve the problem based on other errors, contact Oracle Support.
OGG-01102: Error {0,number,0} - ({1})
This message is deprecated.
Action:
Contact Oracle Support.
OGG-01103: missing err property in xml msg message
This message is deprecated.
Action:
None
OGG-01104: Unknown error starting remote program {0}
An internal error occurred when Oracle GoldenGate Veridata Server tried to start an agent process.
Action:
Contact Oracle Support.
OGG-01105: Error starting remote program {0} ({1} {2})
Oracle GoldenGate Veridata Server cannot start a remote agent.
Action:
Follow the directions provided in the message text. Look for additional troubleshooting information in the error log of the remote Oracle GoldenGate installation. If you cannot resolve the problem, contact Oracle Support.
OGG-01106: IPC_client_writeread failed starting program {0} ({1,number,0}, {2})
Oracle GoldenGate Veridata Server cannot start a remote agent.
Action:
Follow the directions provided in the message text. Look for additional troubleshooting information in the error log of the remote Oracle GoldenGate installation. If you cannot resolve the problem, contact Oracle Support.
OGG-01107: IPC_client_open failed opening port to Manager ({0,number,0}, {1})
Veridata server cannot connect to the remote Manager.
Action:
Make certain that the remote Manager is running, and that the remote Manager port and host are specified correctly in the Oracle GoldenGate Veridata configuration. Follow any directions provided in the message text to resolve the problem. Look for additional troubleshooting information in the error log of the remote Oracle GoldenGate installation. If you cannot resolve the problem, contact Oracle Support.
OGG-01108: error decompressing IPC message ({1}, complen={0,number,0})
The IPC message could not be decompressed.
Action:
Contact Oracle Support.
OGG-01109: error compressing IPC message ({1}, inlen={0,number,0})
The IPC message could not be compressed.
Action:
Contact Oracle Support.
OGG-01110: Definition mismatch: column {1,number,0} {0} defined length {2,number,0}, actual length {3,number,0}
The actual length of the data from the specified column is different from the length that is specified in the table definition.
Action:
None
OGG-01111: Column-level ASCII/EBCDIC conversion is not currently supported
This is an internal error.
Action:
Contact Oracle Support.
OGG-01112: Unexpected condition in function {0} at line {1,number,0}.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01113: Unexpected condition in function {0} at line {1,number,0}.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01114: invalid reply ({0})
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01115: Function {0} not implemented.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01116: Marker fragment and current fragment out of sync
This message is deprecated.
Action:
None
OGG-01117: Received signal: {1} ({0,number,0})
Oracle GoldenGate received a signal from the operating system indicating that processing cannot continue. The signal can be raised internally by an application error or externally by other means.
Action:
Contact Oracle Support.
OGG-01118: Unhandled exception 0x{0} at 0x{1}
Oracle GoldenGate encountered a non-recoverable processing exception.
Action:
Contact Oracle Support.
OGG-01119: XML error: {0}
An error occurred in the Oracle GoldenGate Veridata XML processor. The cause is reported in the message.
Action:
If you cannot resolve the problem based on the message, contact Oracle Support.
OGG-01120: XML parse error on line ({0,number,0}) ({1}), Reason: {2}
An error was returned by the Oracle GoldenGate Veridata XML processor.
Action:
If you cannot determine the cause and resolution from the message, contact Oracle Support.
OGG-01121: XML parse error
An error was returned by the Oracle GoldenGate Veridata XML processor.
Action:
If you cannot determine the cause and resolution from the message, contact Oracle Support.
OGG-01122: Error opening module {0} - {1}.
An error occurred when Extract tried to open a dynamically linked library module.
Action:
Make certain that the library exists and that its location is specified correctly. If the problem persists, contact Oracle Support.
OGG-01123: Error loading function {1} from {0} - {2}.
An error occurred when Extract tried to link to an exported function in a dynamically linked library module.
Action:
Contact Oracle Support.
OGG-01124: Unauthorized access to {0} (CMDSEC)
The program is not authorized to read the CMDSEC (command security) file.
Action:
You can grant read access as needed, but Oracle GoldenGate recommends denying write and delete access to everyone but Oracle GoldenGate Administrators.
OGG-01125: *ERROR* in CMDSEC: {0}
The CMDSEC (command security) file contains the specified error.
Action:
Fix the error, and then restart the process.
OGG-01126: Abending at user-exit request
The instructions in a user exit caused the process to abend. Informational only.
Action:
None
OGG-01127: cuserexit param PASSTHRU can not be used with {0}
The CUSEREXIT parameter contains the PASSTHRU option, which cannot be used with the specified parameter.
Action:
Either remove the PASSTHRU option, or do not use the specified parameter (depending on your replication requirements).
OGG-01128: cuserexit param PASSTHRU may only be used with an Extract pump
The parameter file for a primary Extract process or a Replicat process contains the CUSEREXIT parameter with the PASSTHRU option. PASSTHRU is only valid for a data-pump Extract.
Action:
Remove the PASSTHRU option, and then restart the process.
OGG-01129: NSort error {0,number,0} - {1}
The Nsort sorting function failed with the specified error.
Action:
Fix the problem according to the Nsort error message.
OGG-01130: NSort function {0} failed with {1,number,0} - {2}
The Nsort sorting function failed with the specified error.
Action:
Fix the problem according to the Nsort error message.
OGG-01131: error {2,number,0} reading queue file {0} at rba {1,number,0} ({3})
An operating system error occurred when the process tried to read the specified file.
Action:
Resolve the operating system error, and then restart the process.
OGG-01132: error {2,number,0} positioning queue file {0} to rba {1,number,0} ({3})
The process cannot position in the trail file.
Action:
Contact Oracle Support.
OGG-01134: Cannot find executable file '{0}'
An Oracle GoldenGate executable file is missing from the installation directory.
Action:
Make certain that no files were removed from the Oracle GoldenGate installation directory. Repair or reinstall the Oracle GoldenGate software. If this problem persists, contact Oracle Support.
OGG-01135: fork() failed creating new process
An Oracle GoldenGate process could not be started.
Action:
Check the operating system logs for a resource shortage.
OGG-01136: Child process is no longer alive
An Oracle GoldenGate process terminated immediately after starting successfully.
Action:
Check the operating system logs for a resource shortage.
OGG-01137: BATCHSQL suspended, continuing in normal mode
Replicat suspended batch mode and is trying to apply the exceptions in normal mode within the GROUPTRANSOPS transaction boundary. Informational only.
Action:
None
OGG-01139: BATCHSQL resumed, recovered from error
The Replicat parameter file contains the BATCHSQL parameter with the BATCHERRORMODE option. Replicat recovered from the error without leaving batch mode. Informational only.
Action:
None
OGG-01142: Invalid format type 0x{0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01144: Error mapping source hex-string data into a native floating-point format, col: {0}, input: [{1}]
An error occurred while converting the specified column from a hex string to a native floating-point number.
Action:
Contact Oracle Support.
OGG-01145: {0}
An internal error occurred during column mapping. The text of this message is generated by a lower-level function and is variable.
Action:
Contact Oracle Support.
OGG-01146: {0}
An internal error occurred during column mapping. The text of this message is generated by a lower-level function and is variable.
Action:
Contact Oracle Support.
OGG-01147: {0}
An internal error occurred during column mapping. The text of this message is generated by a lower-level function and is variable.
Action:
Contact Oracle Support.
OGG-01148: {0}
An internal error occurred during column mapping. The text of this message is generated by a lower-level function and is variable.
Action:
Contact Oracle Support.
OGG-01149: Invalid time format {0}
The mapping specification contains an invalid time format.
Action:
To determine the correct format, see the Oracle GoldenGate reference documentation for the parameter or function that contains the incorrect format.
OGG-01150: Invalid timestamp/datetime format {0}
The mapping specification contains an invalid timestamp or datetime format.
Action:
To determine the correct format, see the Oracle GoldenGate reference documentation for the parameter or function that contains the incorrect format.
OGG-01151: Error mapping from {0} to {1}
The mapping of the specified source and target tables failed.
Action:
Look for other, related messages that provide details on the failure and can help you resolve the problem on your own. If the problem persists, contact Oracle Support.
OGG-01152: {0} ({1}) not mapped
The mapping of the specified source and target tables failed.
Action:
Look for other, related messages that provide details on the failure and can help you resolve the problem on your own. If the problem persists, contact Oracle Support.
OGG-01154: SQL error {2,number,0} mapping source table {0} to target table{1}. Database error: {3}.
The specified SQL error occurred when mapping the specified source table to the specified target table.
Action:
Depending on other parameter options that are specified in the Replicat parameter file, Replicat may attempt, and succeed, to handle the error and then continue processing. If the error cannot be handled, expect the process to fail with an error message.
OGG-01155: Filter not passed: user error {2,number,0} mapping {0} to {1}
The specified error occurred on the syntax of the FILTER clause for the specified source-target table mapping.
Action:
Correct the syntax based on the error code, and then restart the process. For FILTER rules, see the TABLE and MAP parameters in the Oracle GoldenGate reference documentation.
OGG-01157: Error in WHERE clause for {0}
There was a syntax error in the WHERE clause of a TABLE or MAP statement.
Action:
Correct the syntax error. For help, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-01158: Timestamp out of range: {0,number,0}
There was an internal error converting a timestamp value.
Action:
Contact Oracle Support.
OGG-01159: Value ({0}) exceeds minimum value of column.
A numeric conversion failed because the resulting negative value cannot be represented in the space provided.
Action:
Correct the specified value.
OGG-01160: Value ({0}) exceeds maximum value of column.
A numeric conversion failed because the resulting positive value cannot be represented in the space provided.
Action:
Correct the specified value.
OGG-01161: Bad column index ({2,number,0}) specified for table {0}, max columns = {1,number,0}.
Oracle GoldenGate encountered a reference to a column ordinal that is not within an expected range.
Action:
Verify that the definitions for the specified table are correct, and verify the correctness of the MAP statement for the specified table. If the trail file is encrypted, the wallet file or key name may be incorrect. Verify the encryption configuration. This also happens if trail file is corrupted.
OGG-01162: Total data length ({2,number,0}) specified for table {0} exceeds record length ({1,number,0}).
There was an internal error converting trail file data. A buffer overflow was detected.
Action:
Contact Oracle Support.
OGG-01163: Bad column length ({3,number,0}) specified for column {1} in table {0}, maximum allowable length is {2,number,0}.
There was an internal error converting trail file data. A buffer overflow was detected.
Action:
Contact Oracle Support.
OGG-01164: Column index ({1,number,0}) out of sequence for table {0}, last column index = {2,number,0}.
There was an internal error converting trail file data. The columns are out of sequence.
Action:
Contact Oracle Support.
OGG-01165: Record length exceeds maximum record length permitted
An internal error occurred while constructing a trail record. The constructed record exceeds the maximum allowable record length.
Action:
Contact Oracle Support.
OGG-01166: Records larger than 32KB are not supported when using ETOLDFORMAT. Current record is {0,number,0} bytes.
The Extract parameter file contains the ETOLDFORMAT parameter. When this parameter is used, the trail file does not support records that are larger than 32KB.
Action:
To continue using the ETOLDFORMAT parameter, which should only be used if the target Replicat is older than Oracle GoldenGate version 6.0, remove tables that generate the larger record size. Otherwise, you can upgrade Replicat so that ETOLDFORMAT is not needed.
OGG-01167: Old format record headers are not supported in PASSTHRU mode
The primary Extract parameter file contains the ETOLDFORMAT parameter, but older trail header formats cannot be read by a pump Extract that is configured in PASSTHRU mode.
Action:
If possible, remove PASSTHRU from the data pump. As an alternative, you can use ETOLDFORMAT in the data pump parameter file instead of the primary Extract parameter file. This will write the trail to the old format to support the Replicat version for which this conversion is necessary.
OGG-01168: Encountered an update for target table {0}, which has no unique key defined. KEYCOLS can be used to define a key. Use ALLOWNOOPUPDATES to process the update without applying it to the target database. Use APPLYNOOPUPDATES to force the update to be applied using all columns in both the SET and WHERE clause.
Replicat tried to apply a record by using a unique key for row selection, but a matching key does not exist in the target table.
Action:
If the source and target tables do not have identical key columns, use an identical KEYCOLS clause in the source TABLE parameter and the target MAP parameter. For more information about KEYCOLS, see the Oracle GoldenGate reference documentation. To learn about ALLOWNOOPUPDATES and APPLYNOOPUPDATES, contact Oracle Support.
OGG-01169: Encountered an update where all key columns for target table {0} are not present
Replicat tried to apply a record by using a specific key from the source table, but some or all of the matching key columns do not exist in the target table.
Action:
If the source and target tables do not have identical key columns, use an identical KEYCOLS clause in the source TABLE parameter and the target MAP parameter. For more information about KEYCOLS, see the Oracle GoldenGate reference documentation. To learn about options that cause Replicat to skip such operations, or turn them into inserts by using whatever data is available in the trail record, contact Oracle Support.
OGG-01170: Exceeded maximum discard records, abending
The maximum number of discard records that is specified with the MAXDISCARDRECS parameter was exceeded.
Action:
You can use the PURGE option of the DISCARDFILE parameter to purge content when new content is written. As an alternative, you can specify a different discard file with the DISCARDFILE parameter, and then restart the process. This maintains the old discard file intact.
OGG-01172: Discard file ({0}) exceeded max bytes ({1,number,0})
The size of the discard file that is specified with the DISCARDFILE parameter exceeded the size that is allowed with the MAXBYTES option.
Action:
See the Oracle GoldenGate reference documentation for DISCARDFILE for default, minimum, and maximum size values, and for purge options.
OGG-01173: Error mapping a number for column {0}, (input value [{1}])
The specified value could not be converted for a numeric column.
Action:
Verify the MAP statement to make certain that the columns in the mapping are supported for conversion. For help, see the Oracle GoldenGate administration documentation.
OGG-01174: Unexpected non-numeric encountered for column {0}
The specified numeric column contains non-numeric data.
Action:
Verify that the source and target tables that are specified for the comparison have the same schema.
OGG-01175: Cannot Column map from an Enscribe auditcomp record
Enscribe auditcomp records are not supported by Oracle GoldenGate for Windows and UNIX.
Action:
Remove these record types from the Extract configuration on the NonStop system.
OGG-01176: Error converting data to ascii format
The data could not be converted to ASCII format.
Action:
Exclude the table or column from the Oracle GoldenGate configuration.
OGG-01177: Old record version encountered in trail file {0} at {1}.
This message is deprecated.
Action:
None
OGG-01178: New record version encountered (data may be missing) in trail file {0} at {1}.
This message is deprecated.
Action:
None
OGG-01179: Mismatched record version. Bad data found in trail file {0} at {1}.
The trail contains an incomplete record. A previously active Extract group probably was dropped and recreated to link to the same trail name as before. The new Extract started to write to the beginning of the first file in the trail, which caused it to overlay new data over the data that was written by the old group. Because record lengths vary, the new data overwrote record headers, causing one or more incomplete records. Replicat expects a record to start with a header; otherwise it abends.
Action:
Examine the parameter files to determine if the parameter file for one Extract group was copied as the basis for the second group, but trail names were not changed for the second group. If this is the case, the best solution is to start over due to lost or corrupted data. To do this, back up the old trail files, drop and recreate the Extract groups and trails, and create new Replicat groups. Then, resynchronize the data. Save any "debug509" files that are generated in case you need to open a support case. For Oracle GoldenGate versions 10.0 and later, there is a RECOVERYOPTIONS parameter that also might be influencing the way that a recovering Extract writes to the trail. See the Oracle GoldenGate reference documentation for more information.
OGG-01180: LOB chunk too short ({0,number,0} bytes), minimum length: {1,number,0} bytes
The size of the LOB chunk in the trail file is too small. The trail file may be corrupted.
Action:
Contact Oracle Support.
OGG-01181: LOB chunk header size must be {0,number,0} bytes
The size of the LOB chunk in the trail file is invalid. The trail file may be corrupted.
Action:
Contact Oracle Support.
OGG-01182: Cannot retrieve io_type property from the record header in extract file {0}, rba {1,number,0}
The trail record header does not contain the I/O type. The trail file may be corrupted.
Action:
Contact Oracle Support.
OGG-01183: Total length of record is {1,number,0}, maximum length allowed is {0,number,0}
The length of the trail record is too long. The trail file may be corrupted.
Action:
Contact Oracle Support.
OGG-01184: Expected {3,number,0} bytes, but got {4,number,0} bytes, in trail {0}, seqno {1,number,0}, reading record trailer token at RBA {2,number,0}
The actual length of the trail record is different from the length field.
Action:
Contact Oracle Support. The trail file may be corrupted.
OGG-01185: Bad trailer token in trail {0}, seqno {1,number,0}, at RBA {2,number,0}
A bad trail token was found. The trail file may be corrupted.
Action:
Contact Oracle Support.
OGG-01186: Indicated beginning of record occurs before beginning of file after reading record trailer token at RBA {2,number,0} in trail {0}, seqno {1,number,0}
The trail file contains an invalid record position. The trail file may be corrupted.
Action:
Contact Oracle Support.
OGG-01187: Duplicate entry encountered for {0}, Reloading definition...
A duplicate entry was found in the definitions file.
Action:
Edit the definitions file to remove the duplicate entry.
OGG-01188: Short redefine encountered in {0}, Continuing...
An Enscribe short redefine was found in the definitions file.
Action:
Edit the definitions file to remove the short redefine entry.
OGG-01189: Sequence number ({0,number,0}) received : Expecting ({1,number,0})
The initial load Replicat encountered an unexpected sequence number. The trail file might be corrupted.
Action:
Contact Oracle Support.
OGG-01190: Non-numeric data sequence number [{0}]
The initial load Replicat encountered a non-numeric sequence number field. The trail file might be corrupted.
Action:
Contact Oracle Support.
OGG-01191: Bad/unrecognized block format converting timestamps
The initial load Replicat cannot convert commit timestamp data. The trail file might be corrupted.
Action:
Contact Oracle Support.
OGG-01192: Trying to use RMTTASK on data types which may be written as LOB chunks (Table: {0}).
The Oracle GoldenGate direct load method (performed as a remote-task) does not support tables that have columns that contain LOBs, LONGs, user-defined types (UDT), or any other large data type that is greater than 4k in size.
Action:
Exclude these tables from the load.
OGG-01193: Remote tasks cannot be used when other targets files or trails are specified
The Extract parameter file specifies RMTTASK to configure a remote task for an Oracle GoldenGate direct load, but it is possible that an ADD command to add a trail or file was issued to link a trail or file with the remote-task Extract, or that a local or remote trail or file was specified in the remote-task Extract parameter file. Disk storage is not used for a remote task, and there can be only one target Replicat for the task. A remote task cannot be run from the same Extract that also writes to a trail.
Action:
Remove the trail or file specification from the parameter file of the remote-task Extract, and/or delete the trail that is linked with that Extract. Also make certain that the remote-task Replicat was added as a SPECIALRUN, and that its parameter file does not contain any trail or file specifications. To configure an Oracle GoldenGate direct load, see the Oracle GoldenGate administration documentation.
OGG-01194: Extract task {0} abended : {1}
The initial load Extract task abended due to the specified error.
Action:
Refer to the associated error message for the cause and action to take.
OGG-01195: Invalid response code received <0x{0} {1}>
The initial load Extract received an invalid TCP/IP response code.
Action:
Make certain that the network connections are open and working. If this problem persists, contact Oracle Support.
OGG-01196: Did not recognize command <0x{0}>
The initial load Extract received an unrecognized TCP/IP command.
Action:
Make certain that the network connections are open and working. If this problem persists, contact Oracle Support.
OGG-01197: Did not recognize command <0x{0} {1}>
The initial load Extract received an unrecognized TCP/IP command.
Action:
Make certain that the network connections are open and working. If this problem persists, contact Oracle Support.
OGG-01198: Unknown data type received <0x{0} {1}>
The initial load Extract received an unrecognized data type.
Action:
Make certain that the network connections are open and working. If this problem persists, contact Oracle Support.
OGG-01199: Replicat (initial data load task) stopped by Extract.
Extract stopped the initial-load Replicat after the load completed successfully. Informational only.
Action:
None
OGG-01201: Error reported by Manager: {0}
The specified error was returned by Manager.
Action:
Resolve the problem based on the reported error message.
OGG-01202: TCP/IP link with manager was unexpectedly terminated
The connection that Extract had with the remote Manager terminated.
Action:
Verify that the remote host and Manager are still running. Use network diagnostic tools to resolve the error if it is network related, or consult the network administrator.
OGG-01203: Extract abending
The initial load Replicat failed.
Action:
Check the process report file for related errors, and take action based on that error.
OGG-01204: Command sent was not recognized by receiving process
The initial load Replicat did not recognize a command that was sent to it. There could be a TCP/IP network problem.
Action:
Check the Replicat report file for related error messages, and take action based on them.
OGG-01205: The transaction to be deleted is not the current transaction on the list. Current: 0x{0}, Given: 0x{1}
The transaction to be deleted is not the current one.
Action:
Contact Oracle Support.
OGG-01206: Error [A fatal error was previously returned by FMLARGEROW, check error log and report file for details]
This message is deprecated.
Action:
None
OGG-01207: The length given for the unique row identifier required for LOBROW is zero
The length of the LOB that is being processed is zero.
Action:
Contact Oracle Support.
OGG-01208: The {0} function failed with return code {1,number,0}: {2}
This is a generic message about file memory.
Action:
Check for lower-level error messages, and then try to resolve the problem based on those messages. For example, they may report a disk problem. If you cannot determine or resolve the problem, contact Oracle Support.
OGG-01209: Error [A block with a length of zero has been added for column index ({0,number,0}) without indicating that this is the last block in the LOB being added]
The block that was being added to column data has a zero length, and this is not the last block to be added.
Action:
Contact Oracle Support.
OGG-01210: Error [Column index ({0,number,0}) does not have an entry in the column mapping for the LOB map entry]
While trying to add a block to column data, the process determined that the specified column is not mapped.
Action:
Contact Oracle Support.
OGG-01211: Invalid LOB row to put chunk into
An internal error occurred while processing a LOB row.
Action:
Contact Oracle Support.
OGG-01212: Programming error - LOB chunk size ({0,number,0}) exceeds maximum allowed ({1,number,0})
The size of the LOB chunk exceeds the maximum allowed limit.
Action:
Contact Oracle Support.
OGG-01213: Unexpected error allocating LOB column memory structure
While storing a LOB chunk in memory, the process detected that the transaction information is missing.
Action:
Contact Oracle Support.
OGG-01214: oldest uncommitted transaction has no tran_hdr data
The transaction does not contain a header.
Action:
Contact Oracle Support.
OGG-01216: Cannot allocate more memory for a new transaction without violating memory settings (INITTRANSRAM = {0,number,0} bytes)
An internal memory allocation error occurred while initializing the Cache Object Manager.
Action:
Contact Oracle Support.
OGG-01217: TCP/IP process name exceeds maximum length allowed ({0})
This message is not used by Oracle GoldenGate for Windows and UNIX.
Action:
Contact Oracle Support if you receive this message on Windows, Linux, or UNIX.
OGG-01218: Error in {2}: {0,number,0} ({1})
A TCP/IP system call failed.
Action:
Check for a duplicate process that is running, such as another Manager. Make certain that the remote process is still running. Check for any firewalls that forbid the connection, such as blocking certain ports or processes.
OGG-01219: TCP/IP message header is not numeric ({0})
This message is deprecated.
Action:
None
OGG-01220: Could not establish host TCP/IP address
The RMTHOST parameter specifies a host name, and Oracle GoldenGate was unable to resolve that host name to an IP address.
Action:
Consult your network administrator to make certain that the remote host is listed correctly in the domain name server.
OGG-01221: Connect failed to {0}:{1,number,0}, error {2,number,0}:{3}
The process attempted to connect to the specified IP address and port number, but failed with the TCP error that is shown. Typical connection problems are that the target Manager or Collector process is not running, or that Extract is pointing to the wrong IP address or Manager port number.
Action:
Verify that the Manager port in the target Manager parameter file is the same as that in the RMTHOST parameter in the source Extract parameter file, and verify the IP address in RMTHOST. Connection errors also can indicate Collector security violations, a full file system, or errors relating to the system or to the Oracle GoldenGate configuration. If the error condition does not resolve itself in a reasonable amount of time (depending on the error type) consult the network administrator.
OGG-01222: Connect failed to {0}:{1,number,0}, error {2,number,0}:{3} - retries exceeded
The process failed to establish a TCP/IP link and retried the link for the maximum number of times allowed by the system or the tcperrs file.
Action:
Make certain that the remote process is still running. Check for any firewalls that forbid the connection, such as blocking certain ports or processes.
OGG-01223: {0}
A TCP/IP error occurred. The process will retry based on the tcperrs file setting for retries.
Action:
Make certain that the remote process is still running. Check for any firewalls that forbid the connection, such as blocking certain ports or processes. Make certain that the RMTHOST parameter is configured correctly. Consult your network administrator if you cannot resolve the problem, before contacting Oracle Support, to rule out any other network issues.
OGG-01224: {0}
A TCP/IP error occurred. The process will retry based on the tcperrs file setting for retries.
Action:
Make certain that the remote process is still running. Check for any firewalls that forbid the connection, such as blocking certain ports or processes. Make certain that the RMTHOST parameter is configured correctly. Consult your network administrator if you cannot resolve the problem, before contacting Oracle Support, to rule out any other network issues.
OGG-01226: Socket buffer size set to {0,number,0} (flush size {1,number,0})
The TCP socket buffer size is set to the specified size, which is either the default size or the size specified with the TCPBUFSIZE setting in the RMTHOST or RMTHOSTOPTIONS parameter. The buffer that collects data that is ready to be sent across the network is set to the specified size, which is either the default size or the size specified with the TCPFLUSHBYTES option. Informational only.
Action:
None
OGG-01227: Waiting for connection on port {0,number,0} ...
The process is waiting to connect to the specified listening port. Informational only.
Action:
None
OGG-01228: Timeout in {0,number,0} seconds
The process connection will timeout in the specified time frame.
Action:
None
OGG-01229: Connected to {0}:{1,number,0}
Informational message showing the host name and port number that the process is connected to.
Action:
None
OGG-01230: Recovered from TCP error, host {0}, port {1,number,0}
Oracle GoldenGate recovered from a TCP error. Informational only.
Action:
None
OGG-01231: Remote host TCP params error: {0}
A TCP/IP error occurred. The process will retry based on the tcperrs file setting for retries.
Action:
Make certain that the remote process is still running. Check for any firewalls that forbid the connection, such as blocking certain ports or processes. Make certain that the RMTHOST parameter is configured correctly. Consult your network administrator if you cannot resolve the problem, before contacting Oracle Support, to rule out any other network issues.
OGG-01232: Receive TCP params error: {0}
An error in the TCP/IP layer prevented the process from receiving a full message, probably because of a network error. This message is generated when all retries that are permitted by the tcperrs file fail.
Action:
Make certain that the sending process is still running, and that the network is still available. If you or the network administrator cannot resolve the problem, contact Oracle Support.
OGG-01233: Send TCP params error: {0}
An error in the TCP/IP layer prevented the process from sending a full message, probably because of a network error. This message is generated when all retries that are permitted by the tcperrs file fail.
Action:
Make certain that the receiving process is still running, and that the network is still available. If you or the network administrator cannot resolve the problem, contact Oracle Support.
OGG-01234: Command sent was not recognized by receiving process
The command received from the TCP/IP packet is not recognizable. The TCP packet itself is correct, but the enclosed message is unrecognizable.
Action:
Make certain that the Oracle GoldenGate versions on the source and target are the same. If the problem persists, contact Oracle Support.
OGG-01235: Command not allowed by receiving manager process
A TCP command was not permitted by the receiving Manager process.
Action:
Contact Oracle Support.
OGG-01236: Trace file {0} opened
The specified trace file was opened by the process. Informational only.
Action:
None
OGG-01237: Trace file {0} closed
The specified trace file was closed by the process. Informational only.
Action:
None
OGG-01239: {0}
There was an internal error parsing the binary Activity Logging file.
Action:
Verify that the target file was generated by the Activity Logging subsystem and contact Product Development for additional assistance.
OGG-01242: Invalid key field: {0}
The column that is specified in KEYCOLS is not specified in the COBOLDEFSFILE.
Action:
Correct the KEYCOLS specification to be a valid column.
OGG-01243: No key fields specified
This message is deprecated.
Action:
None
OGG-01244: {0}
This is a generic message for an error that occurred while parsing the COBOLDEFSFILE.
Action:
Attempt to correct the problem based on the error that is returned. If it persists, contact Oracle Support.
OGG-01245: Missing source file DEFINITION for target {0}
The DEF parameter is missing the record name detail.
Action:
Add the record name to be used in the DEF file output.
OGG-01247: Error processing {0} params: {1}
An invalid EXPANDDDL option was used in the parameter file.
Action:
For valid EXPANDDDL options, see the Oracle GoldenGate reference documentation.
OGG-01248: Could not retrieve definition for table {0}
The table was not found in the database.
Action:
Add the table to the database or remove it from the DDLGEN configuration.
OGG-01249: Invalid template file, missing one or more required sections
The template file is missing an expected section.
Action:
Get or create a valid copy of the template (TMPL) file.
OGG-01250: Invalid line (no section yet designated): {0}
The template file is missing an expected section.
Action:
Get or create a valid copy of the template (TMPL) file.
OGG-01251: Invalid param in template: {0}
There is an invalid parameter in the template file.
Action:
Get or create a valid copy of the template (TMPL) file.
OGG-01252: Invalid column name mapping line: {0}
The template file is missing the precision or scale for the data type.
Action:
Add the precision and scale to the template (TMPL) file.
OGG-01253: Invalid column type mapping line: {0}
The template file is missing the precision or scale for the data type.
Action:
Add the precision and scale to the template (TMPL) file.
OGG-01254: Unable to replace '*' with ' ' in "{0}"
This message is deprecated.
Action:
None
OGG-01255: Missing entry for data type {0}
The template file does not contain the source column type to map to a target column type.
Action:
Add the missing type to the template (TMPL) file.
OGG-01256: {1}: FM_cache_pool_init: {0}
The process failed to create a memory pool to store the captured transactional data.
Action:
Make certain the system allocated enough resources to create the memory pool.
OGG-01257: File cache directory: {0}, does not exist or is write protected.
The paging directory that is specified with the CACHEDIRECTORY option of the CACHEMGR parameter, or the default dirtmp directory in the Oracle GoldenGate installation directory, is write protected or cannot be found.
Action:
If the directory exists, assign Oracle GoldenGate full control of that directory. If the directory does not exist, create it or specify an existing directory for CACHEDIRECTORY.
OGG-01258: Invalid cache memory values.
The CACHESIZE, CACHEBUFFERSIZE, or CACHEPAGEOUTSIZE specifications of the CACHEMGR parameter contain invalid value specifications. See the Oracle GoldenGate reference documentation for correct value ranges and syntax.
Action:
None
OGG-01259: Duplicate directory: {1}, for VM parameter: {0}.
A CACHEDIRECTORY option of the CACHEMGR parameter contains duplicate directory entries, or there are duplicate CACHEDIRECTORY entries that specify the same directory.
Action:
Correct the syntax and then restart the process. Only one directory can be specified per CACHEDIRECTORY entry. For syntax and usage of CACHEMGR, see the Oracle GoldenGate reference documentation.
OGG-01260: No sufficient space on directories : de: {0}, bytes: 0x{1}, co_uid: 0x{2}, mb_uid: 0x{3}, co: 0x{4}, mb: 0x{5}, mf: 0x{6}
There is an error finding sufficient space in the directories defined to be used by CACHEMGR.
Action:
Check the space available for the CACHEMGR directory entries defined.
OGG-01261: CACHEMGR: Cannot allocate virtual memory len: 0x{0}, prot: 0x{1}, flags: 0x{2}, file: {3}, offset: 0x{4}, co_uid: {5}, mh: 0x{6}, co: 0x{7}, mf: 0x{8}
An attempt to allocate virtual memory failed.
Action:
Contact Oracle Support.
OGG-01262: The call to the {0}() function from line {2,number,0} in {3}() failed with reason '{1}'
An internal error occurred. Usually this message is logged along with other messages that provide more specific information. In some cases, the message text will indicate a cause and possible action.
Action:
If you cannot resolve the problem based on the related messages, contact Oracle Support.
OGG-01263: CACHEMGR: filecaching disk out of space error: 0x{0}, path: {1}, co_uid: 0x{2}, mf: 0x{3}, co: 0x{4}
The disk or directory used during file caching for the temporary files has no space.
Action:
Make space available in the specified directory in the error message.
OGG-01264: The call to the {0}() function from line {1,number,0} in {2}() returned an unexpected value
There is a problem with the function that was called. Usually this message is preceded by other messages that provide more specific information.
Action:
If the related messages do not help you resolve the problem, contact Oracle Support.
OGG-01265: CACHEMGR: Insufficient vm for co: 0x{0}, co_uid: 0x{1}, co_vm: 0x{2}, mbuf_vmsz: 0x{3}
Insufficient cache object virtual memory for buffer usage.
Action:
Contact Oracle Support.
OGG-01266: {0}
The cache object manager (COM) returned an internal error. Usually this message is preceded by other messages that provide more specific information.
Action:
If the related messages do not help you resolve the problem, contact Oracle Support.
OGG-01267: CACHEMGR: filecaching cursor object position mismatch for co: 0x{0}, mb: 0x{1}, file_pos: 0x{2}, obj_pos: 0x{3}, co_uid: 0x{4}, mb_uid: 0x{5}, mb_used: 0x{6}, mb_tpos: 0x{7}, mb_csr_pos: 0x{8}, obj_pos_mb_uid: 0x{9}, obj_pos_mb_used: 0x{10}, obj_pos_mb_tpos: 0x{11}
CACHEMGR cursor position in object is wrong.
Action:
Contact Oracle Support.
OGG-01268: CACHEMGR: filecaching mismatched cached object uid co: 0x{0}, mb: 0x{1}, co_uid: 0x{2}, mb_co_uid: 0x{3}
CACHEMGR found a wrong cached object uid.
Action:
Contact Oracle Support.
OGG-01269: CACHEMGR: Cannot deallocate virtual memory type: 0x{0}, mb_uid: 0x{1}, mb_flags: 0x{2}, mb_vmsz: 0x{3}, co_uid: {4}, co: 0x{5}, addr: 0x{6}, size: 0x{7}
An attempt to unmap virtual memory failed.
Action:
Examine any preceding error messages for a possible cause and resolution; otherwise, contact Oracle Support.
OGG-01270: CACHEMGR: filecaching temporary file details missing for co: 0x{0}, co_uid: 0x{1}
CACHEMGR temporary cache file details are not found in memory.
Action:
Contact Oracle Support.
OGG-01271: {1}: Bad Parameter Argument: {0}
The CACHEMGR parameter contains invalid syntax or an illegal value.
Action:
Correct the syntax or value, and then restart the process. For syntax and usage of CACHEMGR, see the Reference for Oracle GoldenGate for Windows and UNIX.
OGG-01272: CACHEMGR: filecaching disk write error: 0x{0}, path: {1}, co_uid: 0x{2}, mf: 0x{3}, co: 0x{4}
There was a disk write error during a file caching operation.
Action:
Verify and correct the access permission on the specified path in the error message.
OGG-01273: CACHEMGR: filecaching sync error 0x{0} on file {1}, addr: 0x{2}, len: 0x{3}
An error during CACHEMGR file caching has occurred while trying to sync the file to disk.
Action:
Contact Oracle Support.
OGG-01274: CACHEMGR: {0}, file {1}
An error during CACHEMGR file caching copy has occurred.
Action:
Contact Oracle Support.
OGG-01275: CACHEMGR: No more items in object uid: 0x{0}, items: 0x{1}, size: 0x{2}, co: 0x{3}
There are no more items found in the cached object at the requested position.
Action:
Contact Oracle Support.
OGG-01276: CACHEMGR: empty object uid: 0x{0}, items: 0x{1}, size: 0x{2}, co: 0x{3}
The cached object size is zero.
Action:
Contact Oracle Support.
OGG-01277: CACHEMGR: Invalid directory size specification for CACHEDIRECTORY: {1} ({0})
The directory size for the CACHEDIRECTORY option of the CACHEMGR parameter is incorrect.
Action:
Specify a value that is between the maximum size imposed by the file system and the minimum size of 2 GB.
OGG-01278: CACHEMGR: directory {0} does not have write access
There is no write access for directory specified in the error message.
Action:
Enable write access for directory.
OGG-01279: CACHEMGR: maximum number of directories allocated: {0,number,0}
The maximum number of paging directories that are specified for the CACHEDIRECTORY option of the CACHEMGR parameter was exceeded.
Action:
Reduce the number of directories.
OGG-01280: CACHEMGR: Duplicate CACHEDIRECTORY: {0}
The CACHEDIRECTORY option of the CACHEMGR parameter contains one or more duplicate entries.
Action:
Remove the duplicate entries.
OGG-01281: {0}
This is a generic Event Marker Infrastructure informational message. It may be useful for operational, performance, or diagnostic purposes.
Action:
None
OGG-01282: {0}
This is a generic Event Marker Infrastructure warning message that may indicate a potential problem. The data provided may be useful for operational, performance, or diagnostic purposes.
Action:
Take action based on the message that is returned. If you cannot resolve the problem, contact Oracle Support.
OGG-01283: Stopping process due to {0} event {1}{2} {3}
The parameter file contains the EVENTACTIONS parameter with the STOP option. The process stopped gracefully after completing open transactions and any grouped transactions. Informational only.
Action:
None
OGG-01284: Stopping process due to {0} event {1}{2}. STOP request will be executed immediately (current transaction canceled)
The parameter file contains the EVENTACTIONS parameter with the STOP option. The process stopped immediately and canceled the current transaction, because it was still open when the event record was processed. Informational only.
Action:
None
OGG-01285: Processed {0} event {1}{2}
The parameter file contains the EVENTACTIONS parameter with the specified option, and the action was performed successfully. Informational only.
Action:
None
OGG-01286: Executing shell command '{0}' due to SHELL event {1}{2}
The parameter file contains EVENTACTIONS with the SHELL option, and the shell command is being executed because the event was triggered. Informational only.
Action:
None
OGG-01287: Successfully executed shell command '{0}'
The parameter file contains EVENTACTIONS with the SHELL option, and the shell command succeeded when the event was triggered. In the UNIX shell language, a zero exit status equals success. Informational only.
Action:
None
OGG-01288: Failed to execute shell command '{0}', exit status = {1,number,0}
The parameter file contains EVENTACTIONS with the SHELL option, but the shell command failed when the event was triggered. In the UNIX shell language, a non-zero exit status equals failure.
Action:
Check the syntax of the command that is specified in the EVENTACTIONS parameter, and fix it if it is wrong. If the syntax is correct, find out if there is a problem with the file system or operating system that prevents the command from succeeding.
OGG-01289: Canceling process due to {0} event {1}{2}
EVENTACTIONS with the ABORT option is specified in the parameter file, and the event record triggered the ABORT. If DISCARD was also specified, the event record is in the discard file. This is informational to alert you that the event occurred.
Action:
None, unless manual procedures are required outside Oracle GoldenGate as a result of the event. The process will undergo recovery on startup.
OGG-01290: Event action ABORT cannot be combined with any of the following actions: STOP, FORCESTOP, IGNORE, LOG, ROLLOVER, TRACE, CHECKPOINT AFTER, CHECKPOINT BOTH or SYNC
The EVENTACTIONS parameter includes an ABORT option and at least one of the other specified options. These options are mutually exclusive.
Action:
Remove mutually exclusive options. For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-01291: Event action FORCESTOP cannot be combined with STOP, CHECKPOINT AFTER, CHECKPOINT BOTH, or SYNC
The EVENTACTIONS parameter includes a FORCESTOP option and at least one of the other specified options. These options are mutually exclusive.
Action:
Remove mutually exclusive options. For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-01292: Event action IGNORE cannot be combined with DISCARD
The EVENTACTIONS parameter includes an IGNORE option and a DISCARD option. These options are mutually exclusive.
Action:
Remove one of the options. For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-01293: TABLE specification without TARGET must include either IGNORE or DISCARD event action
A TABLE specification does not declare a TARGET. Without a TARGET clause, the EVENTACTIONS specification requires the action to be either IGNORE or DISCARD.
Action:
Add a TARGET clause to the TABLE statement or use IGNORE or DISCARD for the EVENTACTIONS clause.
OGG-01294: Cannot process {0} event {1}{2} because the event record is not the first record in the transaction
EVENTACTIONS is being used in the parameter file. Certain EVENTACTIONS options require the event record to be the first record in a transaction. The event record is a record in the TABLE or MAP statement, typically specified with filtering criteria, that triggers the specified EVENTACTIONS action.
Action:
Specify an event record that is the beginning of a transaction. For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-01296: Error mapping from {0} to {1}
The mapping of the specified source and target tables failed.
Action:
Examine the accompanying messages that provide details about the mapping failure, and resolve the problem based on those messages. If the problem persists, contact Oracle Support.
OGG-01297: Column function diagnostic message: could not find resource {0}
The GETVAL column-conversion function contains an invalid specification.
Action:
Correct the syntax. Make certain the procedure or query name is correct and that the parameter portion contains a valid parameter name or return value. For help, see the Oracle GoldenGate reference documentation.
OGG-01298: Column function diagnostic message: could not find column {0}
The specified column could not be found when the column-conversion function executed.
Action:
Specify the correct column name.
OGG-01299: Column function diagnostic message: DAT_{0} Bad value for century {1,number,0}
Column conversion failed. Century data from the source database or trail file may be corrupted, or a century value was specified for non-century data.
Action:
Make certain that the source column contains valid century data. If it does not contain century data, remove the century specification from the column-conversion function and specify an appropriate data type.
OGG-01300: Column function diagnostic message: DAT_{0} Bad value for year {1,number,0}
Column conversion failed. Year data from the source database or trail file may be corrupted, or a year value was specified for non-year data.
Action:
Make certain that the source column contains valid year data. If it does not contain year data, remove the year specification from the column-conversion function and specify an appropriate data type.
OGG-01301: Column function diagnostic message: DAT_{0} Bad value for month {1,number,0}
Column conversion failed. Month data from the source database or trail file may be corrupted, or a month value was specified for non-month data.
Action:
Make certain that the source column contains valid month data. If it does not contain month data, remove the month specification from the column-conversion function and specify an appropriate data type.
OGG-01302: Column function diagnostic message: DAT_{0} Bad value for day {1,number,0}
Column conversion failed. Day data from the source database or trail file may be corrupted, or a day value was specified for non-day data.
Action:
Make certain that the source column contains valid day data. If it does not contain day data, remove the day specification from the column-conversion function and specify an appropriate data type.
OGG-01303: Column function diagnostic message: DAT_{0} Bad value for day of year {1,number,0}
Column conversion failed. Day-of-year data from the source database or trail file may be corrupted, or a day-of-year value was specified for data that is not day-of-year.
Action:
Make certain that the source column contains valid day-of-year data. If it does not contain day-of-year data, remove the day-of-year specification from the column-conversion function and specify an appropriate data type.
OGG-01304: Column function diagnostic message: DAT_{0} Bad value for day of week {1,number,0}
Column conversion failed. Day-of-week data from the source database or trail file may be corrupted, or a day-of-week value was specified for data that is not day-of-week.
Action:
Make certain that the source column contains valid day-of-week data. If it does not contain day-of-week data, remove the day-of-week specification from the column-conversion function and specify an appropriate data type.
OGG-01305: Column function diagnostic message: DAT_{0} Bad value for day of paramType, week
Column conversion failed on a bad value for a day-of- data type (such as day-of-year). The data in the source column or trail file may be corrupted, or a day-of- value was specified for data that is not day-of- data.
Action:
Make certain that the source column is supposed to contain this kind of data. If not, remove the day-of- specification from the column-conversion function and specify an appropriate data type.
OGG-01306: Column function diagnostic message: DAT_{0} Bad value for hour {1,number,0}
Column conversion failed. Hour data from the source database or trail file may be corrupted, or an hour value was specified for non-hour data.
Action:
Make certain that the source column contains valid hour data. If it does not contain hour data, remove the hour specification from the column-conversion function and specify an appropriate data type.
OGG-01307: Column function diagnostic message: DAT_{0} Bad value for minute {1,number,0}
Column conversion failed. Minute data from the source database or trail file may be corrupted, or a minute value was specified for non-minute data.
Action:
Make certain that the source column contains valid minute data. If it does not contain minute data, remove the minute specification from the column-conversion function and specify an appropriate data type.
OGG-01308: Column function diagnostic message: DAT_{0} Bad value for second {1,number,0}
Column conversion failed. Second data from the source database or trail file may be corrupted, or a second value was specified for non-second data.
Action:
Make certain that the source column contains valid second data. If it does not contain second data, remove the second specification from the column-conversion function and specify an appropriate data type.
OGG-01309: Column function diagnostic message: DAT_{0} Bad value for julian day
Column conversion failed on a bad value for a Julian day data type. The data in the source column or trail file may be corrupted, or a Julian day value was specified for data that is not Julian day.
Action:
Make certain that the source column is supposed to contain Julian day data. If not, remove the Julian day specification from the column-conversion function and specify an appropriate data type.
OGG-01310: Column function diagnostic message: DAT_{0} Bad value for julian time
Column conversion failed on a bad value for a Julian time data type. The data in the source column or trail file may be corrupted, or a Julian time value was specified for data that is not Julian time data.
Action:
Make certain that the source column is supposed to contain Julian time data. If not, remove the Julian time specification from the column-conversion function and specify an appropriate data type.
OGG-01311: Column function diagnostic message: DAT_{0} Bad value for C date
Column conversion failed on a bad value for a C date. The data in the source column or trail file may be corrupted, or a C date value was specified for data that is not a C date.
Action:
Make certain that the source column is supposed to contain C date data. If not, remove the C date specification from the column-conversion function and specify an appropriate data type.
OGG-01312: Column function diagnostic message: DAT_{0} Bad value for TTS date
Column conversion failed on a bad value for a TTS date. The data in the source column or trail file may be corrupted, or a TTS date value was specified for data that is not a TTS date.
Action:
Make certain that the source column is supposed to contain TTS date data. If not, remove the TTS date specification from the column-conversion function and specify an appropriate data type.
OGG-01313: Column function diagnostic message: DAT_{0} Bad value for stratus date
Column conversion failed on a bad value for a Stratus date. The data in the source column or trail file may be corrupted, or a Stratus date value was specified for data that is not a Stratus date.
Action:
Make certain that the source column is supposed to contain a Stratus date. If not, remove the Stratus date specification from the column-conversion function and specify an appropriate data type.
OGG-01314: Column function diagnostic message: Output needs full year
The timestamp data in the column does not contain the full year, but a full year (CC and YY) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove one or both of the CC and YY specifications, depending on what the column contains.
OGG-01315: Column function diagnostic message: Output needs year
The timestamp data in the column does not contain a year, but a year (YY) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the YY specification.
OGG-01316: Column function diagnostic message: Output needs month
The timestamp data in the column does not contain a month, but a month (MMM or MM) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the month specification.
OGG-01317: Column function diagnostic message: Output needs day
The timestamp data in the column does not contain a day, but a day (DD) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the day specification.
OGG-01318: Column function diagnostic message: Output needs day or DOY
The timestamp data in the column does not contain a day-of-year, but a day-of-year (DOY) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the day-of-year specification.
OGG-01319: Column function diagnostic message: Output needs day or DOW
The timestamp data in the column does not contain a day-of-week, but a day-of-week (DOW) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the day-of-week specification.
OGG-01320: Column function diagnostic message: Output needs hour
The timestamp data in the column does not contain an hour, but an hour (HH) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the hour specification.
OGG-01321: Column function diagnostic message: Output needs minute
The timestamp data in the column does not contain a minute, but a minute (MI) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the minute specification.
OGG-01322: Column function diagnostic message: Output needs second
The timestamp data in the column does not contain a second, but a second (SS) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the second specification.
OGG-01323: Column function diagnostic message: Output needs timestamp
The timestamp data in the column does not contain a year, month, or day, but these timestamp components are specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the erroneous specification, which can be one of the following: JTSGMT, JTSLCT, JTS, PHAMIS, STRATUS, CDATE, TTS.
OGG-01324: Column function diagnostic message: Output needs timestamp fraction
The timestamp data in the column does not contain a fraction, but a fraction (FFFFFF) is specified by the output date and time descriptor of the @DATE column-conversion function.
Action:
Remove the fraction specification.
OGG-01325: Column function diagnostic message: Unknown output requirement
An invalid date and time format descriptor is specified by the @DATE column-conversion function.
Action:
Specify a valid date and time format descriptor. For help with syntax and supported values, see the Oracle GoldenGate reference documentation.
OGG-01326: Column function diagnostic message: Start offset is greater than end offset
The begin position in the @STREXT function syntax is later in the string than the end position that is specified.
Action:
Correct the begin and end positions in the syntax.
OGG-01327: Column function diagnostic message: Invalid range arguments, must be @RANGE(<this range>, <tot ranges> [, <column>...])
The syntax for @RANGE is incorrect.
Action:
The syntax should be in the format shown in the error message, where the input is the number of the range partition, the total number of ranges, and the name of the column on which to base the range. See the Oracle GoldenGate reference documentation for more information.
OGG-01328: Column function diagnostic message: Could not find expected key column ({0})
The @RANGE function cannot create the ranges because a column on which to base the range is not defined.
Action:
Add a primary key to the table definition, or specify a column on which to base the range allocation to the third position of the syntax as follows: @RANGE ( range_number , total_number_of_ranges , base_column ). See the Oracle GoldenGate reference documentation for more information.
OGG-01329: Column function diagnostic message: No key columns for @RANGE clause
The @RANGE function cannot create the ranges because a column on which to base the range is not defined.
Action:
Add a primary key to the table definition, or specify a column on which to base the range allocation to the third position of the syntax as follows: @RANGE ( range_number , total_number_of_ranges , base_column ). See the Oracle GoldenGate reference documentation for more information.
OGG-01331: File {0} does not have a valid Oracle GoldenGate signature.
The specified trail is not a valid Oracle GoldenGate trail.
Action:
Contact Oracle Support.
OGG-01334: Error mapping data from source table {0} to target table {1}, column {2} in function {3}.
The specified source table could not be mapped to the specified target table in the specified column-conversion function.
Action:
Make certain that the mapping syntax is correct and that names are spelled correctly. For help, see the Oracle GoldenGate reference documentation.
OGG-01335: Error mapping data from {0} to {1}.{2} in function {3}
The specified source table could not be mapped to the specified target table in the specified column-conversion function.
Action:
Make certain that the mapping syntax is correct and that names are spelled correctly. For help, see the Oracle GoldenGate reference documentation.
OGG-01336: Switching to next trail file {0} at {1}{3} with current RBA {2,number,0}
The process is rolling over the trail to the next file in the sequence. Informational only.
Action:
None
OGG-01337: Trail file {0}, IO error {1,number,0} ({2})
The process cannot open the trail file because there was an operating system error.
Action:
Resolve the operating system error. Consult the system documentation or the system administrator if you cannot determine the cause of the problem.
OGG-01338: {1}: The {0} service was started successfully.
The specified service started successfully. Informational only.
Action:
None
OGG-01339: {1}: Failed to start the {0} service, error code {2,number,0} ({3}).
Manager could not start the specified service.
Action:
Make certain that Oracle GoldenGate is installed properly and that Manager has permission on the system to start the process. Make certain that the parameter file is in the right place and that database is running. Check the related message that is specified in this text for additional troubleshooting details.
OGG-01342: DDL found, SQL operation [{0}], start CSN {1} [{2}], DDL seqno [{3}].
A DDL operation with the specified identifier is being processed. Informational only.
Action:
None
OGG-01343: Restart Timer failed. status = {0} waitState: {1,number,0}
A restart failed.
Action:
Contact Oracle Support.
OGG-01344: Restart notification failure. status = {0}.
A restart notification failed.
Action:
Contact Oracle Support.
OGG-01348: Invalid CHARSET and A2E character set configuration
The value specified for the CHARSET global option does not match the CHARSET value specified in the A2E parameter.
Action:
Correct the A2E parameter or GLOBALS file so that the character sets match.
OGG-01349: Could not convert ASCII data to EBCDIC. Error occurred at or about byte {0} in the {1} byte string beginning: {2}
A conversion of character data from ASCII to EBCDIC failed.
Action:
Verify that the column definitions are correct.
OGG-01350: Could not convert EBCDIC data to ASCII. Error occurred at or about byte {0} in the {1} byte string beginning: {2}
A conversion of character data from EBCDIC to ASCII failed.
Action:
Verify that the column definitions are correct.
OGG-01351: Could not convert CHAR/VARCHAR to NCHAR/NVARCHAR
Invalid character data was found during mapping from a CHAR/VARCHAR column to a target NCHAR/NVARCHAR column.
Action:
Fix the source column data, or use the REPLACEBADCHAR parameter in the Extract and Replicat parameter files.
OGG-01352: Could not convert NCHAR/NVARCHAR to CHAR/VARCHAR
Invalid character data was found during mapping from a NCHAR/NVARCHAR column to a target CHAR/VARCHAR column.
Action:
Fix the source column data, or use the REPLACEBADCHAR parameter in the Extract and Replicat parameter files.
OGG-01353: Could not convert CLOB/TEXT to NCLOB/NTEXT
An error occurred while converting single-byte character data to multi-byte character data.
Action:
Check the column mapping for incorrect specifications, especially if it contains textual LOB data, and determine whether the character sets involved are compatible.
OGG-01354: Could not convert NCLOB/NTEXT to CLOB/TEXT
An error occurred while converting multi-byte character data to single-byte character data.
Action:
Check the column mapping for incorrect specifications, especially if it contains textual LOB data, and determine whether the character sets involved are compatible.
OGG-01355: Following CHAR/NCHAR conversion is being used
Oracle GoldenGate is converting character data. Informational only.
Action:
None
OGG-01356: CHAR/VARCHAR: {0}
Character data is in the format of the specified character set. Informational only.
Action:
None
OGG-01357: CHAR/VARCHAR: Default
Character data is in the format of the default character set. Informational only.
Action:
None
OGG-01358: NCHAR/NVARCHAR: UTF-16/UTF-8
The multibyte data is in the format of UTF-16/UTF-8. Informational only.
Action:
None
OGG-01359: The WILDCARDRESOLVE and (NO)DYNAMICRESOLUTION parameters are deprecated. Defaulting to WILDCARDRESOLVE DYNAMIC.
The WILDCARDRESOLVE parameter is deprecated and was specified.
Action:
Remove the WILDCARDRESOLVE parameter. If immediate resolution is necessary for Replicat or data pump, specify ASSUMETARGETDEFS or SOURCEDEFS with the OVERRIDE option.
OGG-01360: {0} is running in {1} mode.
This is an informational message to indicate the mode of a group.
Action:
None
OGG-01361:
Undefined
Action:
Undefined
OGG-01362: Unsupported object ({0}) encountered at Sequence {1}, RBA {2}
The specified object is of a type not supported in integrated or parallel Replicat modes.
Action:
Replicat will fall back to standard mode for transactions with unsupported objects. To retain integrated or parallel apply mode, remove the table from the Replicat configuration or change the object to a type that is supported.
OGG-01363: Unsupported operation (type {0}) for table {1} encountered at Sequence {2}, RBA {3}
The specified operation type is not supported in integrated or parallel Replicat modes.
Action:
Replicat will fall back to standard mode for transactions with unsupported objects. To retain integrated or parallel apply mode, remove the table from the Replicat configuration or change the operation to a type that is supported.
OGG-01364: No opening parenthesis was found for the {0} {1} parameter.
An opening parenthesis is missing from the beginning of the specified parameter option.
Action:
Add the parenthesis. See the Oracle GoldenGate reference documentation for correct syntax. To test for correct syntax in a parameter file, add the CHECKPARAMS parameter to the first line of the parameter file, save the file, and then start the process. The process stops automatically after the test is finished. To determine if there were syntax errors, view the process report file. Correct the syntax errors in the parameter file. To test again, repeat these steps. Remove CHECKPARAMS when you are finished testing syntax.
OGG-01365: No closing parenthesis was found for the {0} {1} parameter.
A closing parenthesis is missing from the end of the specified parameter option.
Action:
Add the parenthesis. See the Oracle GoldenGate reference documentation for correct syntax. To test for correct syntax in a parameter file, add the CHECKPARAMS parameter to the first line of the parameter file, save the file, and then start the process. The process stops automatically after the test is finished. To determine if there were syntax errors, view the process report file. Correct the syntax errors in the parameter file. To test again, repeat these steps. Remove CHECKPARAMS when you are finished testing syntax.
OGG-01366: Text was found before the opening parenthesis for the {0} {1} parameter.
There is a syntax error for the specified parameter option.
Action:
Look for characters that precede the opening parenthesis without a space between them, and make certain that the characters that precede the opening parenthesis are also valid syntax. See the Oracle GoldenGate reference documentation for correct syntax. To test for correct syntax in a parameter file, add the CHECKPARAMS parameter to the first line of the parameter file, save the file, and then start the process. The process stops automatically after the test is finished. To determine if there were syntax errors, view the process report file. Correct the syntax errors in the parameter file. To test again, repeat these steps. Remove CHECKPARAMS when you are finished testing syntax.
OGG-01367: Length of CSN {0}, {1,number,0}, from input data source not equal to that of previous CSN, {2,number,0}
There is a possible memory corruption or invalid data in the trail.
Action:
Contact Oracle Support.
OGG-01368: Could not truncate file "{0}" at RBA {1,number,0} (error {2,number,0}, {3})
The process could not truncate the trail during recovery.
Action:
Check for a full disk, disk failure, network failure, or other system-related problem.
OGG-01369: DDL operation mapped to target database {0}, new DDL operation [{1}]
Replicat successfully applied the DDL operation to the specified target. Informational only.
Action:
None
OGG-01370: User requested START SKIPTRANSACTION. The current transaction will be skipped. Transaction ID {0}, position Seqno {1,number,0}, RBA {2,number,0}.
The START REPLICAT command was issued with the SKIPTRANSACTION option. Replicat will skip the specified transaction in the trail, which is the first one after its expected startup point. All operations from the first transaction are excluded. If the MAXTRANSOPS parameter is also being used for this Replicat, it is possible that the process will start to read the trail file from somewhere in the middle of a transaction. In that case, the remainder of the partial transaction is skipped, and Replicat resumes normal processing from the next begin-transaction record in the file.
Action:
None
OGG-01371: No discard file specified. Records discarded due to SKIPTRANSACTION will not be logged.
The START REPLICAT command was issued with the SKIPTRANSACTION option, but because a discard file is not specified in the parameter file, the skipped operations cannot be persisted to a file.
Action:
None, unless you want future SKIPTRANSACTION transactions to be logged. In that case, stop Replicat and specify a discard file with DISCARDFILE, then restart the process.
OGG-01372: User requested start at CSN {0}
A START REPLICAT command was issued with the ATCSN option to start processing beginning with the transaction that has the specified CSN (Commit Sequence Number). All transactions before this one are skipped.
Action:
None
OGG-01373: User requested start after CSN {0}
A START REPLICAT command was issued with the AFTERCSN option to start processing at the transaction immediately after the one that has the specified SCN (Commit Sequence Number). All transactions in the trail up to, and including the one with the specified SCN, are skipped.
Action:
None
OGG-01374: Transaction delivery commencing at position Seqno {0,number,0}, RBA {1,number,0}, Transaction ID {2}, CSN {3}, {4,number,0} transaction(s) skipped.
A START REPLICAT command was issued with the ATCSN or AFTERCSN option. Replicat is starting processing from the specified sequence number and RBA of the input trail, with the specified transaction in the trail. The number of transactions that were skipped is stated in the message. This message can also apply to START EXTRACT for Data Pump.
Action:
None
OGG-01375: Trail format does not support starting at a specific CSN. File header not found.
A START REPLICAT command was issued with the ATCSN or the AFTERCSN option, but the format of the trail does not support these options. A trail file must have a version that is equal to, or lower than, that of the process that reads it, in this case Replicat. This indicates that the Oracle GoldenGate version of Replicat is older than the version of Extract.
Action:
Upgrade the Replicat version to use these options.
OGG-01376: Trail format does not support starting at a specific CSN. CSN token not found at position Seqno {0,number,0}, RBA {1,number,0}.
A START REPLICAT command was issued with the ATCSN or AFTERCSN option, but the format of the trail does not support these options. A trail file must have a version that is equal to, or lower than, that of the process that reads it, in this case Replicat. This indicates that the Oracle GoldenGate version of Replicat is older than the version of Extract.
Action:
Upgrade the Replicat version to use these options.
OGG-01377: CSN format supplied does not match the CSN format in the trail. CSN supplied {0}. Expecting {1} format CSN.
A START EXTRACT command was issued with the ATCSN or AFTERCSN option, but an invalid format was supplied for the CSN value. The CSN format that you supply must match the CSN format of the trail records, which is based on the CSN format of the source database.
Action:
See the Oracle GoldenGate administration documentation for a list of CSN formats per database, and then re-issue the command with the correct CSN format.
OGG-01378: Unrecoverable DDL execution error encountered [{0}]
The process could not execute a DDL statement.
Action:
If you cannot resolve the problem based on the error that is returned in the message, contact Oracle Support.
OGG-01379: Error {0,number,0} creating CSN instance. CSN {1}, DBID {2,number,0}.
The CSN could not be resolved from the trail record. The trail file may be corrupted because of a disk or network failure.
Action:
Contact Oracle Support.
OGG-01380: Start parameters SKIPTRANSACTION, ATCSN, AFTERCSN and FORCECURRENTPOSITION are mutually exclusive. Only one may be specified.
Only one of the specified parameters can be used in the START REPLICAT command. Note that FORCECURRENTPOSITION is not currently a valid parameter and should not be used.
Action:
Re-issue the command with only one of the options.
OGG-01381: The VAM compatibility level must be set via the TRANLOGOPTIONS VAMCOMPATIBILITY <level> parameter, where <level> is a number starting at 1
A new Oracle GoldenGate Extract has been paired with an older TAM module, but TRANLOGOPTIONS VAMCOMPATIBILITY is not set in the Extract parameter file to support backward compatibility.
Action:
Add the TRANLOGOPTIONS parameter with the VAMCOMPATIBILITY option set to 1. As an alternative, you can set the VAM compatibility to 1 with VAMInitialize, and then you can omit TRANLOGOPTIONS with VAMCOMPATIBILITY. To avoid the need to set the VAM compatibility, upgrade the TAM module to that of the Extract version.
OGG-01382: The number of alternate online logs being retrieved exceeds the number returned by the GG_ATTR_SESS_NUM_ALT_ONLINE_LOGS session object attribute of {0,number,0}.
Too many alternate online logs are specified.
Action:
Edit the Extract parameter file and remove some of the log specifications so that the value is within the specified range, and then restart Extract.
OGG-01383: The number of alternate log files must be retrieved via the GG_ATTR_SESS_NUM_ALT_ONLINE_LOGS session object attribute before attempting to retrieve the individual log files.
The VAM module tried to retrieve the alternate online log file names directly without initiating the required VAM API protocol. This is an internal programming error.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01384: The maximum number of alternate online log file values allowed for the TRANLOGOPTIONS ALTONLINELOGS parameter is {0,number,0}.
Too many alternate online logs are specified.
Action:
Edit the Extract parameter file and remove some of the log specifications so that the value is within the specified range, and then restart Extract.
OGG-01386: Value for {0} must be between {1} and {2}.
The specified value is not within the range of valid values for the specified parameter.
Action:
Edit the parameter file to specify a valid value, and then restart the process. See the Oracle GoldenGate reference documentation for usage guidelines, if needed.
OGG-01387: Table {0} has no valid key columns, added unconditional supplemental log group for all table columns.
Informational only. The table does not have a primary key or a unique key, and no KEYCOLS clause is defined for it. Oracle GoldenGate is using all of the columns as a key to ensure uniqueness, except for columns that cannot be used as part of a key. For column types that are excluded, see the Oracle GoldenGate installation documentation for your database type.
Action:
None
OGG-01388: File header failed to construct tokens. File {0}, last offset {1,number,0}, data: {2}
The trail file header is corrupted.
Action:
First, restart the process. If the problem still exists, contact Oracle Support.
OGG-01389: File header failed to parse tokens. File {0}, last offset {1,number,0}, data: {2}
There was an error while parsing the trail header.
Action:
Contact Oracle Support.
OGG-01391: Trail file {0} has been previously recovered in overwrite mode, and the current checkpoint is not quiescent. To change to append-mode recovery, perform a quiet checkpoint and restart
Extract is configured to write to the trail in overwrite mode, and the last commit position was not found. The process will continue to try to recover.
Action:
None, if overwrite mode is to be retained; however, further errors may occur. Switch to append mode, if possible, which provides a more reliable recovery history. To change to append mode, see the RECOVERYOPTIONS parameter in the Oracle GoldenGate reference documentation.
OGG-01392: No position tokens found in trail {0}, RBA {1,number,0}
The process could not find the last commit position in the trail.
Action:
Contact Oracle Support.
OGG-01394: Using _ALLOWPKMISSINGROWCOLLISIONS may cause data corruption under certain conditions.
This parameter is being used with HANDLECOLLISIONS to skip key UPDATEs if the corresponding target row does not exist. This can compromise target data integrity and should not be done without guidance from an Oracle support analyst. _ALLOWPKMISSINGROWCOLLISIONS is an unpublished parameter and typically is only used with the guidance of Oracle technical-support personnel.
Action:
None
OGG-01395: Using _ALLOWPKMISSINGROWCOLLISIONS may cause data corruption under certain conditions while mapping from {0} to {1}.
This parameter is being used with HANDLECOLLISIONS to skip key UPDATEs if the corresponding target row does not exist. This can compromise target data integrity and should not be done without guidance from an Oracle support analyst. _ALLOWPKMISSINGROWCOLLISIONS is an unpublished parameter and typically is only used with the guidance of Oracle technical-support personnel.
Action:
None
OGG-01396: A complete after image is not available in {0} at rba {1,number,0} in file {2}, while inserting a row into {3} due to missing target row for a key update operation. NOCOMPRESSUPDATES or FETCHOPTIONS FETCHPKUPDATECOLS may be specified in the Extract parameter file to include a complete image for key update operations.
HANDLECOLLISIONS is enabled for Replicat. (For details, see the HANDLECOLLISIONS reference documentation.) This error indicates that a primary key was updated, but the record cannot be found on the target. Replicat attempted to populate the missing row, instead of performing the update, but it failed to do so because not all of the column values were available in the trail.
Action:
Manually apply the row values to the target, and then skip the record that errored by restarting Replicat with the ATCSN, AFTERCSN, or SKIPTRANSACTION option. If primary keys will continue to be updated, you can stop Extract, and then add either the NOCOMPRESSUPDATES parameter or the FETCHOPTIONS parameter with the FETCHPKUPDATECOLS option.
OGG-01397: {1}: The Token Buffer has exceeded the maximum size of {0,number,0} bytes.
The TOKENS clause is too large. TOKENS supports a maximum character string of up to 2000 bytes. The data can be either a constant that is enclosed within double quotes or the result of an Oracle GoldenGate column-conversion function.
Action:
Edit the TOKENS clause to reduce the character string, if possible. If using the result of a column-conversion function, you might need to select alternate input criteria that does not produce output that is too long.
OGG-01398: Failed to open target trail file {0}, at RBA {1,number,0}; ALTER EXTRACT assumed. Trail file will be created
The process could not find a remote trail.
Action:
Contact Oracle Support.
OGG-01399: DDL of size {0,number,0} cannot be used with this trail format, please use newer trail format
The version of the trail is older than the version of Extract, and the current trail version does not support the maximum DDL size that Extract does.
Action:
To upgrade the trail to the correct format, issue the ALTER EXTRACT command with the ETROLLOVER option to start a new trail file that is of the correct format, and then restart Extract. Note that the version of the process that reads this trail must be at least the same version as the trail, so you might need to upgrade that process and any downstream processes.
OGG-01400: Database operation failed: {0}. ODBC error: SQLCODE {2,number,0}. ODBC error detail is not available - please check that the ODBC configuration is complete, including the DB2 BIND for ODBC plans & packages. {1}
This indicates a possible invalid or incomplete DB2 ODBC configuration. This situation is seen as error -805 and there is no additional detail available.
Action:
Check the DB2 ODBC configuration, plans, and packages to ensure they are valid and complete. Restart the process after fixing these issues.
OGG-01401: Database operation failed: {0}. ODBC error: SQLCODE {2,number,0}. ODBC error detail is not available - please check that the ODBC configuration is complete, including the DB2 BIND for ODBC plans & packages. {1}
This indicates a possible invalid or incomplete DB2 ODBC configuration. This situation is seen as error -805 and there is no additional detail available.
Action:
Check the DB2 ODBC configuration, plans, and packages to ensure they are valid and complete. Restart the process after fixing these issues.
OGG-01402: CACHEMGR: item allocation too large: {0,number,0} > {1,number,0} (max single allocation)
The size of the row data or LOB exceeded the allowed maximum.
Action:
Double the value specified with the CACHESIZE option of the CACHEMGR parameter. If the problem persists, contact Oracle Support.
OGG-01403: Error constructing IPC message {0}. Last offset is {1,number,0}
There was an error getting the last CSN from the currently active remote trail.
Action:
Contact Oracle Support
OGG-01404: Error parsing IPC message {0}. Message length is {1,number,0}, last offset {2,number,0}
There was an error getting the CSN and other information about the last transaction from the currently active remote trail.
Action:
Contact Oracle Support
OGG-01405: Empty commit sequence number (CSN) timestamp detected in target file {0}, at RBA {1,number,0}
The process could not find the timestamp of the CSN for the last transaction.
Action:
Contact Oracle Support
OGG-01406: Invalid commit sequence number (CSN) timestamp detected in target file {0}, at RBA {1,number,0}
The process could not convert the timestamp (in string form) of the CSN of the last transaction to a numeric value.
Action:
Contact Oracle Support
OGG-01407: Setting current schema for DDL operation to schema {0}.
The process is setting the schema for the DDL operation. This is an informational message.
Action:
None
OGG-01408: Restoring current schema for DDL operation to schema {0}.
Replicat is setting the schema for DDL operations to the one that is specified. This is informational only.
Action:
None
OGG-01409: Unable to detect missing target row for update for table {0} because there are no modifiable columns, at RBA {1,number,0}, in file {2}. NOCOMPRESSUPDATES may be specified in the EXTRACT parameter file to include a complete image for update operations.
Replicat could not perform the update, probably because the source and target tables do not have a primary or unique key (or a KEYCOLS clause) and, therefore, Replicat could not locate the target row. By default, Extract only writes the primary key, unique key, or KEYCOLS columns to the trail (plus the changed columns), which provides enough information for the Replicat SQL operation for updates. However, without a key, Replicat only has the change data, which is not enough.
Action:
You can do one of the following: Use the Extract NOCOMPRESSUPDATES parameter to send all of the columns to the trail, so that when a table definition does not include a primary key or unique index, Replicat can use all of the columns as a key. Alternatively, you can define a substitute key for the table by using a KEYCOLS clause in the TABLE parameter.
OGG-01410: Unable to apply a non operational (NOOP) update for table {0} because there are no modifiable columns, at RBA {1,number,0}, in file {2}. NOCOMPRESSUPDATES may be specified in the Extract parameter file to include a complete image for update operations.
Replicat could not perform the update, probably because the source and target tables do not have a primary or unique key (or a KEYCOLS clause) and, therefore, Replicat could not locate the target row. By default, Extract only writes the primary key, unique key, or KEYCOLS columns to the trail (plus the changed columns), which provides enough information for the Replicat SQL operation for updates. However, without a key, Replicat only has the change data, which is not enough.
Action:
You can do one of the following: Use the Extract NOCOMPRESSUPDATES parameter to send all of the columns to the trail, so that when a table definition does not include a primary key or unique index, Replicat can use all of the columns as a key. Alternatively, you can define a substitute key for the table by using a KEYCOLS clause in the TABLE parameter.
OGG-01411: Cannot convert input file {0} with format {1} to output file {2} with format {3}
The output trail of the data pump has a different format (version) than the input trail of the data pump. The input and output trail formats must be identical for a data pump.
Action:
The FORMAT RELEASE option of EXTFILE or EXTTRAIL and RMTFILE or RMTTRAIL must be the same when associated with a data pump. For more information, see the Oracle GoldenGate reference documentation.
OGG-01412: Invalid query specified: Large objects cannot be tokenized with the getval function in SQLEXEC statements.
Large object types (LOBs) are not supported by GETVAL or SQLEXEC for this database system.
Action:
Use a supported data type for the SQLEXEC query. See the SQLEXEC reference documentation for supported data types.
OGG-01413: Missing argument for the shell command.
The SHELL action of EVENTACTIONS does not include a valid argument to execute.
Action:
For the SHELL command, specify a valid command or script.
OGG-01414: CACHEMGR: no primary key for id: 0x{0}, len: 0x{1}
The Oracle GoldenGate memory manager cannot ascertain a unique identifier for the transaction or object that Extract processed.
Action:
Open a support case with Oracle.
OGG-01415: CACHEMGR: no secondary key for id: 0x{0}, len: 0x{1}, primary key: {2}
The length of a secondary key was provided in the transaction record, but no secondary key could be found by the memory manager.
Action:
Open a support case with Oracle.
OGG-01416: File {0}, with format {1}, does not match current format specification of {2}. Modify the parameter file to specify format {1} or issue ETROLLOVER prior to restart.
The version of Extract and the version of the output file or trail do not match. Extract may have been upgraded to a newer version. By default, Extract expects the trail version to be the same as its own version; otherwise a different version must be specified in the parameter file if you want to retain backward compatibility for an older Replicat.
Action:
You have two choices, depending on whether the Replicat process is the same version as the Extract process, or whether it is older: To continue using an older Replicat process, you must specify the FORMAT option in the RMTTRAIL, EXTTRAIL, RMTFILE, or EXTFILE parameter, depending on which is being used. If you are upgrading Replicat to the same version of Extract, issue the ALTER EXTRACT command with the ETROLLOVER option in GGSCI before you start Extract. The rollover sets the trail format to the same as that of the new Extract. For more information, see the Oracle GoldenGate reference documentation for these parameters.
OGG-01417: CACHEMGR: duplicate transaction secondary key: {0}, primary key: {1}, co_uid: 0x{2}, co_items: 0x{3}, co_size: 0x{4}, co: 0x{5}
The Oracle GoldenGate object pool in memory already contains an object with the same secondary identifier.
Action:
Determine whether old (already processed) transaction data was processed by Extract. If you are certain that the transaction logs are not corrupted, open a support case with Oracle.
OGG-01418: Unsupported datatype {0} ({1,number,0}) found in UDT attribute {2}.
An NCLOB, NCHAR, or NVARCHAR2 datatype is defined in the object table. These data types are not supported.
Action:
Exclude the UDT from the Oracle GoldenGate configuration.
OGG-01419: Source table {0} is mapped to multiple targets. Combination of EBCDIC and non EBCDIC targets is not supported.
The source table is mapped to multiple targets, but the encoding is specified differently for each target. One is specified as EBCDIC but the other is not.
Action:
Change the encoding so that it is the same for all targets (either EBCDIC or ASCII). To keep the existing configuration, use different Extract groups for each encoding scheme.
OGG-01420: CACHEMGR: duplicate transaction primary key: {0}, co_uid: 0x{1}, co_items: 0x{2}, co_size: 0x{3}, co: 0x{4}
The Oracle GoldenGate object pool in memory already contains an object with the same unique identifier, typically a transaction identifier.
Action:
Determine whether old (already processed) transaction data was processed by Extract. If you are certain that the transaction logs are not corrupted, open a support case with Oracle.
OGG-01421: CACHEMGR: no primary key for id: 0x{0}, len: 0x{1}
The Oracle GoldenGate memory manager cannot ascertain a unique identifier for the transaction or object that Extract processed.
Action:
Open a support case with Oracle.
OGG-01422: CACHEMGR: invalid buffer mb: 0x{0} for co: 0x{1}, item_len: {2}, mb_used: 0x{3}, mb_uid: 0x{4}, co_uid: 0x{5}
Invalid buffer detected during CACHEMGR operations.
Action:
Contact Oracle Support.
OGG-01424: Event processing not supported for Teradata maximum performance mode.
This message is deprecated.
Action:
None
OGG-01425: Missing context item number {0,number,0}, '{1}', for message issued from line {3,number,0} of '{2}'
Internal error: An expected message token is missing.
Action:
Contact Oracle Support.
OGG-01426: DDL operation excluded by user exit [{0}], optype [{1}], objtype [{2}], objowner "{3}", objname "{4}"
The specified user exit excluded the specified DDL. This is informational only.
Action:
None
OGG-01427: {1} ignored when {0} is used
The specified parameter is incompatible with another parameter in the process configuration and was ignored.
Action:
Remove the parameter.
OGG-01428: Reached maximum number of retries ({0,number,0}) on Oracle error {1,number,0}
The number of retries that is specified with the MAXRETRIES option of the REPERROR parameter has been reached.
Action:
Try to fix the problem with the data that is causing the error. If the problem cannot be resolved, you can change the REPERROR options to discard the operation so that you can examine it and apply it manually, if possible. You can also START REPLICAT with the SKIPTRANSACTION, ATCSN, or AFTERCSN option to skip the transaction.
OGG-01431: Canceled grouped transaction on {0}, Mapping error
There was an error mapping the source table to the target table while applying a grouped transaction.
Action:
Resolve the mapping error and restart the process.
OGG-01432: Canceled grouped transaction on {0}, Filter not passed
There was an error in the filter logic.
Action:
Fix the filter specification in the parameter file, and then restart the process.
OGG-01434: {0}
The specified error occurred when the process tried to map memory.
Action:
If you cannot resolve the error based on the content of the message, such as add system memory resources, contact Oracle Support.
OGG-01435: mmap: len: 0x{0} prot: 0x{1} flags: 0x{2} fd: {3,number,0} off: 0x{4} errno: {5,number,0} ({6})
Internal warning. A memory mapping operation failed.
Action:
Verify that the installation directory is on a file system that supports memory mapped files.
OGG-01437: Failed to modify trail record image prior to write to trail file {0}
The in-memory trail record could be corrupted, causing an update to its fields or other properties to fail.
Action:
Save the checkpoint file and the trail files, and then contact Oracle Support.
OGG-01438: Checkpoint marked as from graceful shutdown, but records found after checkpoint in trail {0}. Expected EOF Seqno {1,number,0}, RBA {2,number,0}. Found Seqno {3,number,0}, RBA {4,number,0}
The process found records that were generated after the checkpoint in the trail. This is just a warning. A correction will be attempted.
Action:
None
OGG-01443: The key columns available in the table {0} may not guarantee uniqueness due to exclusion of virtual, nullable, or other unusable column(s).
A key column contains one or more of the specified column types. Oracle GoldenGate accepts nullable columns in a key definition if no other key exists, but does not accept the other specified column types in a key definition. If one or more columns of these types helps to provide uniqueness to the key, the exclusion of them leaves open the possibility for data inaccuracies on the target. Nullable columns by virtue of their definition cannot be considered unique.
Action:
None, if you know that excluding these columns does not compromise uniqueness. To view the rules of Oracle GoldenGate key selection, see the installation and setup guide for the database type.
OGG-01444: Error in replicating sequence value [{0}]
The specified database error occurred while the process was replicating a sequence value.
Action:
Resolve the database error that is indicated in the error message and then restart the process.
OGG-01445: Buffer overflow (max buffer size {0,number,0}), no xmltype data extracted
The length of the embedded XML data exceeds the size of the memory buffer that is specified with the XMLBUFSIZE option of DBOPTIONS.
Action:
Increase the value of this parameter, and then restart Extract.
OGG-01446: Object table {0} is not supported for this database version.
An object table was specified in an Oracle GoldenGate parameter file or command, and the Oracle version is prior to release 10.2.0.2. Object tables are not supported for those database versions.
Action:
Remove the object table from the Oracle GoldenGate configuration.
OGG-01447: Unsupported opaque type ({0}) found
An XMLTYPE is part of the UDT that is being processed. XMLTYPE is not supported.
Action:
Remove the XMLTYPE from the UDT or do not replicate the UDT.
OGG-01448: XmlLoadDom error uploading XML data ({0}) for col:{1} attr:{2} type:{3}
Extract could not process the specified XML data.
Action:
Contact Oracle Support.
OGG-01449: Scan failed in trail file {0}, with scan start seqno {1,number,0}, rba {2,number,0}
While trying to find the last commit position in a remote trail, the process encountered an internal scan error.
Action:
Contact Oracle Support.
OGG-01450: Unrecognized return value '{0,number,0}' from scan of trail file {1}, with scan start seqno {2,number,0}, rba {3,number,0}
While trying to find the last commit position in a remote trail, the process encountered an unexpected return value.
Action:
Contact Oracle Support.
OGG-01451: {0}
This is a generic informational message that is used to report various different conditions.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-01453: Database login information not specified in parameter file.
The USERID parameter is missing from the parameter file.
Action:
Add the USERID parameter according to the directions in the Oracle GoldenGate reference documentation.
OGG-01454: Unable to lock file "{0}" (error {2,number,0}, {3}).{1,choice,0#│1# Lock currently held by process id (PID) {1,number,0}.}
An attempt by the process to use the operating system to lock a file failed because the file is in use by another process. If possible, the identifier of the offending process is shown.
Action:
Make certain that the file is supposed to be in the Oracle GoldenGate configuration, and that a typo did not cause a different file to be used. Verify that the file system that is being used is supported by Oracle GoldenGate.
OGG-01455: Object table {0} is not supported for this database version.
An object table was specified in an Oracle GoldenGate parameter file or command, and the Oracle version is prior to release 10.2.0.2. Object tables are not supported for those database releases.
Action:
Remove the object table from the Oracle GoldenGate configuration.
OGG-01456: Limit of maximum LOB columns ({0,number,0}) exceeded.
The number of columns with LOBs exceeds the limit that the system can handle.
Action:
Contact Oracle Support.
OGG-01457: {1} cannot be called with the VAM compatibility level set to {0,number,0}
The VAM module and the VAM API kernel in Extract have different compatibility levels and cannot be used together.
Action:
Add the TRANLOGOPTIONS parameter with the VAMCOMPATIBILITY option to the Extract parameter file to set the compatibility level for the VAM module. If the problem persists, contact Oracle Support.
OGG-01458: The VAM compatibility level of {0,number,0} set via the TRANLOGOPTIONS VAMCOMPATIBILITY parameter was overridden by the VAM client module in VAMInitialize and set to {1,number,0}
VAMInitialize overrides the TRANLOGOPTIONS VAMCOMPATIBILITY setting.
Action:
None if the VAMInitialize version is correct. Otherwise, make the necessary changes to reflect the correct version. To support backward compatibility with an older TAM module, set TRANLOGOPTIONS with VAMCOMPATIBILITY to a value of 1, or set the value with VAMInitialize.
OGG-01459: The VAM compatibility level must be set via the TRANLOGOPTIONS VAMCOMPATIBILITY <level> parameter, where <level> is a number starting at 1
A new Oracle GoldenGate for Teradata Extract has been paired with an older TAM module.
Action:
To support backward compatibility with the older module, set TRANLOGOPTIONS with VAMCOMPATIBILITY to a value of 1. If you set the VAM compatibility with VAMInitialize, it does not have to be set with TRANLOGOPTIONS. This parameter is not needed if the Extract and the TAM module are the same version.
OGG-01462: Requested TDS packet size of {0,number,0} bytes changed to {1,number,0} by SQL Server
The request for the TDS packet size was returned successfully, but the value was changed by the database server to the value specified in the warning.
Action:
This is a warning message, so no immediate action is needed. If the problem persists, contact Oracle Support.
OGG-01464: mmap: len: 0x{0} prot: 0x{1} flags: 0x{2} fd: {3,number,0} off: 0x{4} errno: {5,number,0} ({6})
The operating system could not create or allocate a shared memory region of the given size and operation flags. The error value indicates the specific error mode. This operation can fail due to exhausted disk space, the Oracle GoldenGate installation being on a shared (NFS) virtual device, or the associated backing file being in use by another process.
Action:
Contact Oracle Support.
OGG-01465: Exceeded transaction timeout threshold ({2,number,0} seconds) waiting for source transaction with XID {3} and CSN {4} at RBA {1,number,0}, in file {0}.
Replicat has been at the same position for a period of time that is equal to, or greater than, the value that is specified with the TRANSACTIONTIMEOUT parameter. Informational to indicate the beginning of the transaction timeout recovery process.
Action:
None
OGG-01466: Exceeded transaction timeout threshold ({2,number,0} seconds) waiting for source transaction at RBA {1,number,0}, in file {0}.
Replicat has been at the same position for a period of time that is equal to, or greater than, the value that is specified with the TRANSACTIONTIMEOUT parameter. Informational to indicate the beginning of the transaction timeout recovery process.
Action:
None
OGG-01467: Recovered to start of partial source transaction with XID {2} and CSN {3} at RBA {1,number,0}, in file {0}. Waiting for more data.
The value that is specified with the TRANSACTIONTIMEOUT parameter in the Replicat parameter file was reached, and Replicat did not receive the end-of-transaction record. The transaction timeout recovery process successfully backed out the open transaction and recovered to the logical end-of-file, and is now waiting for more data.
Action:
None
OGG-01468: Recovered to start of partial source transaction at RBA {1,number,0}, in file {0}. Waiting for more data.
The value that is specified with the TRANSACTIONTIMEOUT parameter in the Replicat parameter file was reached, and Replicat did not receive the end-of-transaction record. The transaction timeout recovery process successfully backed out the open transaction and recovered to the logical end-of-file, and is now waiting for more data.
Action:
None
OGG-01469: New data detected after RBA {1,number,0}, in file {0}. Resuming delivery for transaction with XID {2} and CSN {3}.
Applies to TRANSACTIONTIMEOUT processing. Additional data has been received while the transaction timeout recovery process was waiting at the logical end-of-file. This message marks the transition from transaction timeout recovery back to normal processing.
Action:
None
OGG-01470: New data detected after RBA {1,number,0}, in file {0}. Resuming delivery.
Applies to TRANSACTIONTIMEOUT processing. Additional data has been received while the transaction timeout recovery process was waiting at the logical end-of-file. This message marks the transition from transaction timeout recovery back to normal processing.
Action:
None
OGG-01471: TRANSACTIONTIMEOUT cannot be less than EOFDELAY.
The value that is specified for TRANSACTIONTIMEOUT is less than the value of the EOFDELAY parameter. It must be greater than the EOFDELAY parameter.
Action:
Edit the Replicat parameter file to set TRANSACTIONTIMEOUT to a value that is greater than that of EOFDELAY, and then restart Replicat.
OGG-01472: TRANSACTIONTIMEOUT cannot be greater than 1 week.
The TRANSACTIONTIMEOUT parameter is being used in the Replicat parameter file, but the value that was specified is greater than the maximum allowed value of one week (seven days).
Action:
Change the TRANSACTIONTIMEOUT value to something between one second and one week, and then restart Replicat.
OGG-01473: DDL is too large and is ignored. Details: DDL statement with marker sequence [{0}], ddl sequence [{1}] for {2}.{3}/{4} will be ignored. The length of [{5}] bytes exceeds the supported maximum size.
The DDL statement exceeds the size that is supported by Oracle GoldenGate and will be ignored.
Action:
Depends on whether the discarding of the DDL has an effect on any subsequent DML. Future DML may cause an error if discarding the DDL causes metadata inconsistencies. In any case, you can apply the DDL on the target manually. You might need to restart processes if the condition caused an error.
OGG-01475: Cannot automatically restart {0} {1}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump EXTRACT, or REPLICAT, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Manager cannot start the specified process. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action:
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-01476: The previous run abended due to an out of order transaction. Issue ALTER ETROLLOVER to advance the output trail sequence past the current trail sequence number, then restart. Then, use ALTER EXTSEQNO on the subsequent pump EXTRACT, or REPLICAT, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Somehow, the transactions in the current trail file are out of order. A different Extract might have been configured to write to this trail, and old data was overlaid with the new data. You will need to skip this record, and then reposition Replicat to start at the next one.
Action:
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-01477: Target does not support format {1} for file {0}. Reverting to format {2}
The process that reads this file is of an older version than that of the process that wrote the file. A trail or extract file must have a version that is equal to, or lower than, that of the process that reads it. In addition, the input file and output file of a data pump must be the same version. This message is informational only.
Action:
None
OGG-01478: Output file {0} is using format {1}.
The trail or file that this process is writing to is using the specified trail format. Trail formats can vary from version to version of Oracle GoldenGate. This message is informational only.
Action:
None
OGG-01479: {0}
This message is deprecated.
Action:
None
OGG-01482: DDL object type is not supported, type {0}
The specified database object is not supported by the Oracle GoldenGate DDL replication feature.
Action:
Remove the object from the DDL parameter in the parameter file, and then restart the process.
OGG-01483: The key for table {0}.{1}.{2} contains one or more variable length columns. These columns may not have their pre-images written to the transaction log during updates. Please use KEYCOLS to specify a key for Oracle GoldenGate to use on this table.
The specified table does not have a clustered index and has variable length columns. Oracle GoldenGate will use the entire row as the key, so there is the potential for some before images to be lost if data gets stored off page.
Action:
Specify columns that contain unique values as key columns by using a KEYCOLS clause in the TABLE and MAP statements, or alternatively define a clustered index on the table. Note that if you define a clustered index, it is a DDL operation. DDL operations are not supported by Oracle GoldenGate for this database, so follow the instructions in the Oracle GoldenGate administration documentation for performing DDL on objects that are in an active replication configuration.
OGG-01485: Error adding item to transaction {0,number,0}:{1,number,0}:{2,number,0}, op={3,number,0}, record LRI={4,number,0}.{5,number,0}, length={6,number,0}.
An internal error occurred.
Action:
Report the full message content to Oracle Support.
OGG-01487: DDL found, operation [{0}], start {1} [{2}], commit {1} [{3}] instance [{4} ({5})], DDL seqno [{6}], marker seqno [{7}]
A DDL operation was processed. Informational only.
Action:
None
OGG-01489: Could not add TRAN DATA for table, error [{1}], error code [{0,number,0}], operation [{2}]
The DDLOPTIONS parameter with the ADDTRANDATA option is specified in the Extract parameter file, and the ALTER TABLE command that adds the supplemental logging did not succeed because of an error.
Action:
Correct the problem based on the database error that is returned. If you cannot resolve the problem, contact Oracle Support.
OGG-01495: Error action for ADDTRANDATA already specified (ABEND, RETRYOP) [{0}]
Both ABEND and RETRY are specified for ADDTRANDATA.
Action:
Remove one of these options. They are mutually exclusive.
OGG-01496: Failed to open target trail file {0}, at RBA {1,number,0}
The process could not find a valid trail during the initial phase of recovery.
Action:
Contact Oracle Support.
OGG-01498: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}. Database error {1,number,0} ({2}).
BATCHERRORMODE processing was not able to apply the transaction successfully due to the specified database error, and is rolling back the transaction. Replicat will process the transaction in normal mode.
Action:
None
OGG-01500: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}. Detected inconsistent result: executed {1,number,0} operations in batch, resulting in {2,number,0} affected rows.
The batched operation resulted in possible data integrity issues based on the number of operations in the batch, versus the number of affected rows returned by the database response. The transaction is being rolled back, and Replicat will re-process the transaction in normal mode.
Action:
None
OGG-01501: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}. Database error {1,number,0} ({2}). Temporarily disabling batch mode due to transient key update.
The batched transaction is being rolled back because the BATCHERRORMODE conversion processing resulted in a transient primary key update. (See the HANDLETPKUPDATE parameter documentation for more information on Transient Primary Key Update - TPKU.) Replicat will revert to normal processing to apply this transaction.
Action:
None
OGG-01502: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}. Database error {1,number,0} ({2}). Override of duplicate failed.
BATCHSQL is operating in BATCHERRORMODE, but there was a collision converting an insert to an update.
Action:
To use BATCHERRORMODE, you must use the HANDLECOLLISIONS parameter in the Replicat parameter file to handle collisions caused by the conversions.
OGG-01503: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}. Mapping error.
The batched transaction is being canceled, and Replicat will revert to normal processing.
Action:
None
OGG-01504: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}. Filter not passed.
The batched transaction is being canceled due to a filter error. Replicat will revert to normal processing.
Action:
None
OGG-01505: OCI Error ({0,number,0}, {1}) maximum cursors exceeded, unable to prepare new statement for table {2}, query = {3}
The maximum number of cursors allowed by the MAXSQLSTATEMENTS parameter has been reached.
Action:
If the database cursor limit permits, and there will be enough cursors for other applications, you can increase the value of MAXSQLSTATEMENTS. However, see the Oracle GoldenGate reference documentation before changing this parameter.
OGG-01506: Value ({0}) exceeds minimum value of column. Table {1}, column {2}.
A numeric conversion failed because the resulting negative value cannot be represented in the space provided, based on the catalog definition for the specified column.
Action:
Examine any recent changes to the table. The catalog definition for the specified table may not match the data in the archive logs.
OGG-01507: Value ({0}) exceeds maximum value of column. Table {1}, column {2}.
A numeric conversion failed because the resulting positive value cannot be represented in the space provided, based on the catalog definition for the specified column.
Action:
Examine any recent changes to the table. The catalog definition for the specified table may not match the data in the archive logs.
OGG-01508: Failed to initialize monitoring point service for process group {0} (error {1,number,0}). Monitoring point publishing will be disabled.
An Oracle GoldenGate process failed to initialize the shared memory for its monitoring point registry and service. This failure typically occurs if: there is not enough disk space to host the backing file (Linux); there is not enough memory to host the shared region; the backing file is being stored on an NFS mounted directory (Linux); or the system exhausted its allocation of available handles.
Action:
For issues that relate to system resources, such as disk space and handles, increase the available resource by allocating more disk storage, by allocating more handles, or by reducing the consumption of those resources by other processes (as the case may be). For an NFS issue, either install Oracle GoldenGate on a local physical device or set the internal GLOBALS parameter _TMPSTOREDIR to a directory on a local physical device.
OGG-01509: Failed to publish monitoring point value for "{0}" (error {1,number,0}). Monitoring point publishing will be disabled.
An Oracle GoldenGate process could not establish a shared memory region to hold monitoring point statistics. This inability indicates corruption of the region.
Action:
Check for a related message or messages (such as error OGG-01508) to determine how to resolve the problem. If there are no related messages, restart the process. If the error persists, contact Oracle Support.
OGG-01510: Failed to set monitoring point registry ID to "{0}" (error {1,number,0})
An Oracle GoldenGate process could not establish a shared memory region to hold monitoring point statistics. This inability indicates corruption of the region.
Action:
Check for a related message or messages (such as error OGG-01508) to determine how to resolve the problem. If there are no related messages, restart the process. If the error persists, contact Oracle Support.
OGG-01511: Failed to set process status to {0} (error {1,number,0})
An Oracle GoldenGate process could not establish a shared memory region to hold monitoring point statistics. This inability indicates corruption of the region.
Action:
Check for a related message or messages (such as error OGG-01508) to determine how to resolve the problem. If there are no related messages, restart the process. If the error persists, contact Oracle Support.
OGG-01512: WILDCARDRESOLVE DYNAMIC parameter is mandatory for the generic database implementation of the VAM
In the VAM implementation, tables can only be looked up as they are encountered dynamically. The table metadata cannot be exchanged statically in the VAMInitialize function
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01513: Positioning to {0}
Extract is positioning to the specified sequence number.
Action:
None
OGG-01514: Positioning to start
Extract is positioning to the start of the data source on startup, rather than to a specific sequence or time.
Action:
None
OGG-01515: Positioning to begin time {0,date} {0,time}
The process is being positioned to start at the specified timestamp.
Action:
None
OGG-01516: Positioned to {0}, {1,date} {1,time}
The process is now positioned to start at the specified timestamp.
Action:
None
OGG-01517: Position of first record processed {0}, {1,date} {1,time}
The processing began with the first record that has the specified timestamp.
Action:
None
OGG-01519: Waiting at EOF on input trail file {0}, which is not marked as complete; but succeeding trail file {1} exists. If ALTER ETROLLOVER has been performed on source extract, ALTER EXTSEQNO must be performed on each corresponding downstream reader.
Extract was upgraded, and an ALTER EXTRACT command with ETROLLOVER was issued to roll over the existing trail to a new file that is of the correct format for the new version. The process that reads the trail (data pump or Replicat) must be altered to start reading at the beginning of the new trail.
Action:
Issue the ALTER EXTRACT or ALTER REPLICAT command (depending on the process) with the EXTSEQNO option, and specify the sequence number of the new trail.
OGG-01520: Rollover performed. For each affected output trail of Version 10 or higher format, after starting the source extract, issue ALTER EXTSEQNO for that trail's reader (either pump EXTRACT or REPLICAT) to move the reader's scan to the new trail file; it will not happen automatically.
Extract was upgraded, and an ALTER EXTRACT command with ETROLLOVER was issued to roll over the existing trail to a new file that is of the correct format for the new version. The process that reads the trail (data pump or Replicat) must be altered to start reading at the beginning of the new trail.
Action:
Issue the ALTER EXTRACT or ALTER REPLICAT command (depending on the process) with the EXTSEQNO option, and specify the sequence number of the new trail.
OGG-01521: Scan resumed.
A trail was rolled over, and the reading process was altered to begin reading at the beginning of the new trail.
Action:
None
OGG-01522: Non-zero value for delay required when calling {0}
This is an internal error and should not occur in production. A polling error occurred. Configuration of the Oracle GoldenGate error logging subsystem via the Activity Logging class can be set up so that a specific file is polled for every N milliseconds. If N is zero, it is considered a programming error and this message is issued.
Action:
Contact Oracle Support.
OGG-01523: Failed to initialize DTD for Activity Logging
The gglog.dtd XML definition file is invalid in the installation folder.
Action:
Fix this file, or contact Oracle Support.
OGG-01525: Failed to open trace output file, '{0}', error {1,number,0} ({2})
The specified output file could not be opened.
Action:
Verify that the file permissions are adequate.
OGG-01526: Unknown appender, '{1}', for logger, '{0}', ignored in configuration file, '{2}'
The appender named by the 'appender-ref' element is not defined in the XML file.
Action:
Specify one of the valid appender class names defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01527: Problem validating configuration file, '{1}', {0}. Problem ignored.
Undefined
Action:
Undefined
OGG-01528: Cannot access configuration file '{0}', error {1,number,0} ({2})
The specified XML configuration file cannot be accessed.
Action:
Verify that the file permissions are adequate. If you cannot resolve the problem, contact Oracle Support.
OGG-01529: Failure validating configuration file, '{1}', {0}. Configuration unchanged.
Undefined
Action:
Undefined
OGG-01530: MaxFileSize of '{0}' in configuration file, '{1}', must be between zero and 4GB
The Activity Logging XML file contains a MaxFileSize parameter for a RollingFileAppender that is not between 0 and 4GB (exclusive).
Action:
Change the parameter value to be within the specified size range. If you cannot resolve the problem, contact Oracle Support.
OGG-01531: MaxFileSize of '{0}' in configuration file, '{1}', has an invalid multiplier. Expected 'KB', 'MB', or 'GB'.
The Activity Logging XML file contains a MaxFileSize parameter for a RollingFileAppender that has a suffix with a value other than 'KB', 'MB', or 'GB' in either upper or lower case.
Action:
Change the suffix value to a valid size unit. If you cannot resolve the problem, contact Oracle Support.
OGG-01532: Cannot locate XML configuration file, '{0}'
The Activity Logging XML file that is specified could not be located in the file system. Both the current directory and the application directory were searched.
Action:
Find the configuration file, or create a new one. If you cannot resolve the problem, contact Oracle Support.
OGG-01533: Cannot use XML configuration file, '{0}', validation failed
Undefined
Action:
Undefined
OGG-01534: Error parsing XML configuration file, '{2}', at line {0,number,0}: {1}
The XML file that is used by Activity Logging is not well-formed. The specific reason is provided by the third-party XML library.
Action:
Fix the XML error that is reported by the XML checker. If you cannot resolve the problem, contact Oracle Support.
OGG-01535: Cannot use XML configuration file, '{0}', document root inaccessible
The XML file was well-formed, valid, and successfully loaded, but the root of the document could not be determined.
Action:
Correct the XML file. If you cannot resolve the problem, contact Oracle Support.
OGG-01536: Unknown appender class name, '{1}', for appender '{0}' in configuration file '{2}'
An invalid class name was specified for an appender element in a Activity Logging XML configuration file.
Action:
Specify one of the valid appender class names defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01537: Unknown parameter, '{2}', for '{1}' appender class in appender '{0}' in configuration file '{3}'
An invalid or misspelled parameter name was encountered for an appender element in a Activity Logging XML configuration file.
Action:
Specify one of the valid appender class parameters defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01538: Unknown layout class name, '{1}', for appender '{0}' in configuration file '{2}'
An invalid class name was specified for a layout element in a Activity Logging XML configuration file.
Action:
Specify one of the valid layout class names defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01539: Unknown parameter, '{2}', for '{1}' layout class in appender '{0}' in configuration file '{3}'
An invalid or misspelled parameter name was encountered for a layout element in a Activity Logging XML configuration file.
Action:
Specify one of the valid layout class parameters defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01540: Unknown filter class name, '{1}', for appender '{0}' in configuration file '{2}'
An invalid class name was specified for a filter element in a Activity Logging XML configuration file.
Action:
Specify one of the valid filter class names defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01541: Unknown parameter, '{2}', for '{1}' filter class in appender '{0}' in configuration file '{3}'
An invalid or misspelled parameter name was encountered for a filter element in a Activity Logging XML configuration file.
Action:
Specify one of the valid parameters for the filter class defined in gglog.dtd. If you cannot resolve the problem, contact Oracle Support.
OGG-01560: Positioned to {0}
Extract positioned to the specified sequence number.
Action:
None
OGG-01562: Source schema {0} is mapped to target schema {1} to set the current schema for DDL execution.
The specified source session schema is now mapped to the target session schema specified in the TARGET clause of DDLOPTIONS MAPSESSIONSCHEMA. Any DDL executed from this source session schema will be replicated under the TARGET session schema.
Action:
None
OGG-01563: Transaction {0} contains {1,number,0} orphaned LOB buffers. These must be deleted before the transaction is completed.
An internal error occurred while storing a LOB column in the Cache Object Manager (COM).
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01564: LOB handle {0,number,0} is invalid.
An internal error occurred while storing a LOB column in the Cache Object Manager.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01565: LOB handle {0,number,0} has already been associated with another base row column.
An internal error occurred while storing a LOB column in the Cache Object Manager.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01566: LOB handle {0,number,0} has already been associated with a base row column and cannot be deleted explicitly.
An internal error occurred while storing a LOB column in the Cache Object Manager.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-01567: Cannot find first oldest persisted object file. File: {0}, Function: {1}.
The oldest persisted-object file cannot be found. These files contain the persisted transaction data and other information that is needed for Extract to recover from the bounded-recovery checkpoint.
Action:
None, unless the log files are not available. Extract will revert to normal recovery for this recovery, and then turn on Bounded Recovery again. If Extract stops because the log file that contains the oldest open transaction is not online, restore that log and any subsequent logs before restarting Extract.
OGG-01568: {3}: unsupported BR version: {0}: version expected: {1,number,0} version found: {2,number,0}
The persisted-object files were created by a version of Bounded Recovery that is different from the one that currently is running. An Extract upgrade was probably performed and the new version contains a newer Bounded Recovery version.
Action:
Restart Extract from the command line with the BRRESET option. BRRESET starts the process as if this is the first run, and the process will use normal recovery. For syntax help, see the BRRESET option of the BR command in the Oracle GoldenGate reference documentation. If you cannot resolve the problem this way, manually remove all of the files that have the group name in the BRDIR directory. If the problem persists, contact Oracle Support.
OGG-01569: {1}: POF crc64 mismatch: POF: {0}
The recovery file did not pass the integrity check that the Bounded Recovery feature performs.
Action:
None. Extract will revert to normal recovery for this recovery, and then turn on Bounded Recovery again.
OGG-01570: {3}: magic number mismatch: {0} expected: 0x{1} found: 0x{2}
The recovery file did not pass the integrity check that the Bounded Recovery feature performs.
Action:
None. Extract will revert to normal recovery for this recovery, and then turn on Bounded Recovery again.
OGG-01571: {3}: footer magic number mismatch: filename: {0}: expected: 0x{1} found: 0x{2}
The recovery file did not pass the integrity check that the Bounded Recovery feature performs.
Action:
None. Extract will revert to normal recovery for this recovery, and then turn on Bounded Recovery again.
OGG-01572: {2}: filename mismatch: POF: {0} mt_filename: {1}
The name of the persisted-object file is not what is expected based on the Extract Bounded Recovery checkpoint file.
Action:
None. Extract will revert to normal recovery for this recovery, and then turn on Bounded Recovery again.
OGG-01573: {1}: failed in call to: {0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01574: {1}: failed in call to: {0}: error code: {2,number,0} ({3})
Bounded Recovery failed in the specified function invocation.
Action:
If the error pertains to the Bounded Recovery storage directory, try to resolve the problem. If you cannot resolve the problem, contact Oracle Support.
OGG-01575: {2}: file operation failed in call to: {0}: filename {1}
Extract was unable to open the specified file. Extract will revert to normal recovery.
Action:
None
OGG-01576: {0}: error code: {1,number,0} ({2})
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01577: {0}: NULL persisted objected pointer
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01578: {1}: unexpected flag in PO (CO): 0x{0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01579: Validated the Bounded Recovery checkpoint: {0}.
Bounded Recovery validated the specified checkpoint.
Action:
None
OGG-01580: Invalid crc64 value. Checkpoint File: {0} crc value: 0x{1}, Function: {2}.
The recovery file did not pass the integrity check that the Bounded Recovery feature performs.
Action:
None. Extract will revert to normal recovery for this recovery, and then turn on Bounded Recovery again.
OGG-01582: {2}: extract group mismatch: group expected: {0} group found: {1}
The Extract group in the Bounded Recovery checkpoint file is not the one that is currently running.
Action:
Restart Extract from the command line with the BRRESET option. BRRESET starts the process as if this is the first run, and the process will use normal recovery. For syntax help, see the BRRESET option of the BR command in the Oracle GoldenGate reference documentation. If you cannot resolve the problem this way, contact Oracle Support.
OGG-01584: {0}: extract group not supplied
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01585: {1}: unique bounded recovery instance already exists: requested extract group: {0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01586: {4}: file operation failed in call to {0} file {1}, error code: {2,number,0} ({3})
While Extract was in Bounded Recovery mode, a request to the file system failed with the specified error.
Action:
Fix the problem based on the error, if possible. If you cannot resolve the problem, contact Oracle Support.
OGG-01587: {4}: file operation failed in call to: {0} file {1}, error code: {2,number,0} ({3})
While Extract was in Bounded Recovery mode, a file system operation by the Cache Object Manager (COM) failed.
Action:
Try to resolve the problem based on the error message that is returned. If you cannot resolve the problem, contact Oracle Support.
OGG-01588: {0}: failed
An internal message occurred in the Cache Object Manager.
Action:
Contact Oracle Support.
OGG-01589: {1}: failed in call to: {0}
An internal message occurred in the Cache Object Manager.
Action:
Contact Oracle Support.
OGG-01590: {1}: failed in call to: {0} error code: {2,number,0} ({3})
The calling internal function failed with the specified system error code. Examine the message text for the specific function and error code.
Action:
This message can occur in many contexts. If it indicates a file system error, you might be able to resolve it yourself. If not, contact Oracle Support.
OGG-01591: {2}: failed in call to: {0} pool instance: {1,number,0}
An internal function failed.
Action:
Contact Oracle Support.
OGG-01593: {0}: error code: {1,number,0} ({2})
The specified function failed with the given system error code.
Action:
Contact Oracle Support.
OGG-01596: {2}: mmapc instance address: 0x{0} differs from base address: 0x{1}
An internal mapping error occurred.
Action:
Contact Oracle Support.
OGG-01597: {1}: failed in call to: {0}
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01598: {1}: failed in call to: {0} error code: {2,number,0} ({3})
A library function call failed in the given function. This low-level error returns an exception to be handled at a higher level of code.
Action:
Examine the error text, the error code, and any preceding related error messages. If a file system error occurred, determine if corrective action can be taken. If you cannot resolve the problem, contact GoldenGate Support.
OGG-01599: {2}: type: {0,number,0} subtype: {1,number,0}
An internal function failed.
Action:
Contact Oracle Support.
OGG-01600: {1}: invalid mode: 0x{0}
The specified function has an invalid mode.
Action:
Contact Oracle Support.
OGG-01601: {2}: memory map length: {0,number,0} differs from registered length: {1,number,0}
The specified length of the virtual memory map is not equal to its registered length.
Action:
Contact Oracle Support.
OGG-01602: {0}: memory map out of space and extend operation failed
The virtual memory map could not be extended.
Action:
Check the free swap size, and increase it if possible. If this message persists, contact Oracle Support.
OGG-01603: {0}: NULL data source pointer
The address of the internal virtual memory map is missing.
Action:
Contact Oracle Support.
OGG-01604: {0}: cannot extend memory map: not marked for extend
An attempt has been made to extend a non-extendable virtual memory map. This low-level error returns an exception to be handled at a higher level of code.
Action:
Contact Oracle Support.
OGG-01610: {0}: NULL dhv pointer found
An invalid bounded recovery redo state occurred.
Action:
Contact Oracle Support.
OGG-01611: {0}: NULL object pointer found
An object necessary for Bounded Recovery is not present.
Action:
Contact Oracle Support.
OGG-01612: {0}: NULL tag pointer found
A parameter necessary for Bounded Recovery is not present.
Action:
Contact Oracle Support.
OGG-01613: {4}: NULL cache object pointer found: rc_co0: 0x{0} rc_co0->rst_co: 0x{1} rc_co1: 0x{2} rc_co1->rst_co: 0x{3},
A pointer to an object necessary for Bounded Recovery data persistence is not present.
Action:
Contact Oracle Support.
OGG-01614: {5}: {0}: <{1,number,0}, {2,number,0}> <{3,number,0}, {4,number,0}>
A virtual memory map integrity error occurred.
Action:
Contact Oracle Support.
OGG-01615: {7}: dhnode_map_traverse: {0} <{1,number,0}, {2,number,0}> (children: {3,number,0}, <{4,number,0}, {5,number,0}> (children: {6,number,0})
A virtual memory map integrity error occurred.
Action:
Contact Oracle Support.
OGG-01616: {7}: {0} dn: <{1,number,0}, {2,number,0}> (children: {3,number,0}, <{4,number,0}, {5,number,0}> (children: {6,number,0})
An internal virtual memory map error occurred with a mismatch on node properties.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01617: {7}: {0} <{1,number,0}, {2,number,0}> (len: {3,number,0}), <{4,number,0}, {5,number,0}> (len: {6,number,0})
The found length of child nodes in the virtual memory map does not match the expected length.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01618: {4}: {0} <{1,number,0}, {2,number,0}> index: {3,number,0}
The virtual memory map node is invalid for the specified reason.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01619: {7}: {0} <{1,number,0}, {2,number,0}>, <{3,number,0}, {4,number,0}> indexes: {5,number,0}, {6,number,0}
A virtual memory map integrity error occurred.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01620: {3}: {0} <{1,number,0}, {2,number,0}>
An internal virtual memory map has an invalid type or subtype due to the condition specified in the error text.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01621: {3}: {0} group type: {1,number,0} type found: {2,number,0}
An internal virtual memory map definition has an unterminated group entry.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01622: Count mismatch in the header {0,number,0} found value {1,number,0}, in the leafs {2,number,0} found value {3,number,0}, in terminator {4,number,0} found value {5,number,0} in function {6}.
The recovery file did not pass the integrity check that the Bounded Recovery feature performs.
Action:
None. Extract will revert to normal recovery for this recovery and then return to Bounded Recovery.
OGG-01623: {5}: count mismatch: processed_nodes: {0,number,0} found nodes: {1,number,0} (headers: {2,number,0} leafs: {3,number,0} terminators: {4,number,0}
The recovery file did not pass the integrity check that the Bounded Recovery feature performs.
Action:
None. Extract will revert to normal recovery for this recovery and then return to Bounded Recovery.
OGG-01624: {1}: failed in call to: {0}
A library function call failed in the given function.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01625: {2}: {0}: {1}
An attempt to compile an internal virtual memory map failed. A preceding error message should indicate the cause.
Action:
Restart Extract. If the problem persists, contact Oracle Support.
OGG-01626: Bounded Recovery restore failed. Function: {1}, Source function: {0}, Error code: {2,number,0} ({3}).
A Bounded Recovery file operation failed. The cause is indicated in the message text.
Action:
Examine the file and directory to see if corrective action can be taken. If you cannot determine any file problems, restart Extract from the command line by using the BRRESET option of the BR parameter. For more information, see the BR parameter in the Oracle GoldenGate reference documentation. If the problem persists, contact Oracle Support.
OGG-01627: {2}: invalid file mode for: {0} mode: 0x{1}.
The specified directory has an invalid permission mode.
Action:
Change the directory permissions. If the problem persists, contact Oracle Support.
OGG-01628: {2}: rename({0}, {1}) error code: {3,number,0} ({4}).
The rename of a stale Bounded Recovery file failed with the specified error.
Action:
Try to resolve the file problem based on the error, and determine if it will occur for other Bounded Recovery files. If you cannot correct this problem, contact Oracle Support.
OGG-01629: Bounded Recovery successfully recovered the persisted objects. {0} (Total persisted cached files: {1}).
Extract successfully recovered the transaction data that was persisted to disk.
Action:
None
OGG-01630: {4}: invalid object count on OP list. {0,number,0} OP active count: {1,number,0} pool instance: {2,number,0} ({3}).
The number of persisted objects expected for recovery differs from the actual number of long-running transactions that are detected. Bounded Recovery will resolve the difference or else revert to normal recovery.
Action:
None
OGG-01631: Bounded Recovery completed successfully. Bounded Recovery checkpoint file: {0}.
Extract created a new Bounded Recovery checkpoint, concluding another Bounded Recovery interval (as determined by the BRINTERVAL option of the BR parameter.)
Action:
None
OGG-01632: {4}: Active object count differs from count from previous instance BCP: OP active count: {1,number,0} recovered count from previous BCP: {0,number,0} pool instance: {2,number,0} ({3}).
Bounded Recovery detected an anomaly in the checkpoint and is using the previous Bounded Recovery checkpoint for recovery.
Action:
None
OGG-01633: No valid Bounded Recovery checkpoint found. Last file examined: {0}.
Extract could not find a valid Bounded Recovery checkpoint, and will revert to normal recovery.
Action:
None
OGG-01634: {2}: file operation failed in call to: {0}: filename {1}
Extract could not open the specified file, and will revert to normal recovery.
Action:
None
OGG-01635: Bounded Recovery is not used. Normal recovery is only used due to altered checkpoint.
User altered checkpoint by executing ADD or ALTER Extract commands. Extract will use Normal Recovery for the current run and then turn on Bounded Recovery after the recovery is complete.
Action:
None
OGG-01636: Bounded Recovery is disabled. Error during its initialization.
Extract was unable to initiate a Bounded Recovery checkpoint, and is disabling Bounded Recovery. Extract will revert to normal recovery.
Action:
None
OGG-01637: Bounded Recovery is canceled and disabled. Error creating the checkpoint.
Extract was unable to create a Bounded Recovery checkpoint, and is disabling Bounded Recovery. Extract will revert to normal recovery.
Action:
None
OGG-01638: Bounded Recovery is disabled. Error restoring its checkpoint.
Extract was unable to recover from the expected checkpoint, and is disabling Bounded Recovery. Extract will revert to normal recovery.
Action:
None
OGG-01639: Bounded Recovery is active for the object pool {0,number,0}, pool ID {1}.
Extract is reporting that Bounded Recovery is currently active.
Action:
None
OGG-01640: Bounded Recovery starts recovery from the transaction ID {0}.
Extract is reporting the ID of the transaction with which it will start Bounded Recovery.
Action:
None
OGG-01641: Bounded Recovery recovery start position: {0}.
Extract is reporting the position in the transaction log where it will start Bounded Recovery.
Action:
None
OGG-01642: Bounded Recovery recovery end position: {0}.
Extract is reporting the position in the transaction log where it finished its Bounded Recovery.
Action:
None
OGG-01643: Bounded Recovery is canceled for the object pool {0,number,0}, pool ID {1}.
The Bounded Recovery was abandoned, and Extract will revert to normal recovery.
Action:
None
OGG-01644: Bounded Recovery is completed for the object pool {0,number,0}, pool ID {1} at position {2}.
Extract has completed the Bounded Recovery.
Action:
None
OGG-01645: For an initial load EXTRACT, the SOURCEDB parameter must specify a single APPLID
This message is deprecated.
Action:
None
OGG-01646: Unexpected record type {1,number,0} encountered in file {0}
This message is deprecated.
Action:
None
OGG-01647: File {0} column {1,number,0}, name length {2,number,0} exceeds maximum supported length {3,number,0}
This message is deprecated.
Action:
None
OGG-01648: File {0} column {1}, will be set to data type character, sub data type binary. SYSADATA values: {2,number,0}, {3,number,0}, {4,number,0}
This message is deprecated.
Action:
None
OGG-01649: Data set name {0} length {1,number,0} exceeds maximum length {2,number,0}
This message is deprecated.
Action:
None
OGG-01650: FLDATA failed for file {0}
This message is deprecated.
Action:
None
OGG-01651: Open failed: {0}, error {1,number,0}: {2}
This message is deprecated.
Action:
None
OGG-01652: Open File Read Only failed: {0}, file may be empty
This message is deprecated.
Action:
None
OGG-01653: Unexpected EOF encountered on {0}
This message is deprecated.
Action:
None
OGG-01654: File {0} has no columns
This message is deprecated.
Action:
None
OGG-01655: File {0} key start or end is not on a field boundary. The specified SYSADATA member does not match the specified file
This message is deprecated.
Action:
None
OGG-01656: File {0} type {1} is not supported
This message is deprecated.
Action:
None
OGG-01657: Data set name {0} was not found in the criteria definition contained in the SOURCEDEFS file
This message is deprecated.
Action:
None
OGG-01658: Criteria specification {0} {1} contains an unrecognized type {0}. Valid criteria types are FOR, USE and WHERE.
This message is deprecated.
Action:
None
OGG-01659: Criteria specification {0} {1} type is out of sequence. Expecting USE type
This message is deprecated.
Action:
None
OGG-01660: Criteria specification {0} {1} type is out of sequence. Expecting FOR or WHERE type
This message is deprecated.
Action:
None
OGG-01661: An error occurred trying to position to the last criteria information record in the SOURCEDEFS file. The file may be empty.
This message is deprecated.
Action:
None
OGG-01662: An invalid WHERE clause {0} was encountered. Expecting <column name>=<value>
Incorrect syntax was used to define a WHERE clause in a TABLE or MAP statement.
Action:
See the permissible WHERE operators that are listed in the TABLE and MAP reference documentation, and then fix the syntax in the parameter file.
OGG-01663: An invalid quoted string was encountered in a criteria specification {0} {1}. Quoted strings are only valid for the value component of a WHERE clause. An embedded quote must be represented by a pair of quotes.
This message is deprecated.
Action:
None
OGG-01664: Criteria value {0} is a duplicate for type {1}
This message is deprecated.
Action:
None
OGG-01665: {0}
This message is deprecated.
Action:
None
OGG-01667: {1}: process ID {0,number,0} waiting in sleep loop for diagnostician to attach debugger
When the _HANGATPROGRAMSTART internal option is specified, or the _HANGONFATALERROR internal option is used and a fatal error is encountered, Oracle GoldenGate will pause in order to allow point-in-time diagnosis.
Action:
Remove the parameter from the parameter file and contact Oracle Support for additional assistance.
OGG-01668: PROCESS ABENDING
An unrecoverable error occurred and processing cannot continue.
Action:
Examine previously issued error messages for possible causes and actions.
OGG-01669: Opening {0} (byte {1,number,0}, current EOF {2,number,0})
The Collector process is opening the specified file. Informational only.
Action:
None
OGG-01670: Closing {0}
The Collector process is closing the specified file. Informational only.
Action:
None
OGG-01671: Closing batch file {0} ({1})
The Collector process is closing the specified batch file. Informational only.
Action:
None
OGG-01672: Opening batch file {0}
The Collector process is opening the specified batch file. Informational only.
Action:
None
OGG-01673: Truncated {0}
The Collector process truncated the specified file. Informational only.
Action:
None
OGG-01674: Executed system command "{0}" with status ({1,number,0})
The Collector process executed the specified system command. The return status is indicated. Informational only.
Action:
None
OGG-01675: Terminating because extract is stopped
The Collector process terminated because its associated Extract terminated.
Action:
If the Extract process abended (did not stop normally), look at the Extract report file for errors that may need to be resolved, and resolve them based on their message content.
OGG-01676: Terminating after client disconnect
The Collector process terminated because the associated Extract client disconnected.
Action:
Look for problems with network connectivity between the source system that hosts Extract and the local system. Check the Extract report file for more errors that might help you diagnose and resolve the problem.
OGG-01677: Waiting for connection (started dynamically)
The Collector process was started by Manager and will find a free listening port dynamically. Informational only.
Action:
None
OGG-01678: Listening for requests
The Collector process was started from the command line on a designated listening port. Informational only.
Action:
None
OGG-01679: Connecting to {0}
The Collector process is verifying the connection to the remote system where a passive Extract or data pump is running. Informational only.
Action:
None
OGG-01680: {0}
The specified number of bytes was received. This message appears when Oracle GoldenGate is in debug mode, as specified with the tcpstats parameter when Collector was started.
Action:
Unless you need tcpstats on for debugging purposes, turn it off to improve performance.
OGG-01688: Thread: {0}, Message: {1}
This is a generic error that forwards another message that contains errors from the Java Agent component of Oracle GoldenGate Monitor.
Action:
If you cannot resolve the error that is returned based on the context, contact Oracle Support.
OGG-01689: Thread: {0}, Message: {1}
This is a generic error that forwards another message that contains errors from the Java Agent component of Oracle GoldenGate Monitor.
Action:
If you cannot resolve the error that is returned based on the context, contact Oracle Support.
OGG-01690: Thread: {0}, Message: {1}
This is a generic error that forwards another message that contains errors from the Java Agent component of Oracle GoldenGate Monitor.
Action:
If you cannot resolve the error that is returned based on the context, contact Oracle Support.
OGG-01693: Canceling BATCHSQL transaction{0,choice,0#│1# in batch error mode}.
The batched SQL transaction encountered exceptions. Replicat will revert to normal processing (one operation at a time). For more information, see the BATCHSQL reference documentation.
Action:
None
OGG-01702: Cannot get file status for '{0}'. Error {1,number,0} ({2})
While repairing a partial record at the end of a trail, the process could not get the status of the file.
Action:
Contact Oracle Support.
OGG-01705: Input checkpoint position {2,number,0} for input trail file '{0}' is greater than the size of the file ({1,number,0}). Please consult Oracle Knowledge Management Doc ID 1138409.1. for instructions.
This inconsistency is caused by a disk or system failure during which data that was still in cache gets lost. The result is that the reader process (a data pump or Replicat) appears stalled waiting for more data. The writer process (Extract or data pump), when it performs its recovery, creates a new trail file and may write some of the data that has already been processed by the reader process.
Action:
To avoid duplicate records, you need to perform a manual recovery, find the duplicate records, and alter the reader process to start processing after those records. See Oracle Knowledge Base solution 1138409.1 for instructions.
OGG-01706: Table {0} is an Index Organized Table (IOT) and only supported for Oracle 10gR2 and above.
This table type is not supported.
Action:
Stop Extract. Edit the parameter file to remove the table and others of this type from the TABLE statements, and then restart Extract. (If TABLE uses a wildcard, you can exclude those tables with TABLEEXCLUDE.)
OGG-01707: Failed to retrieve the singleton instance of {0}
The metadata cache of the Oracle GoldenGate Monitor C-agent was not initialized properly.
Action:
Contact Oracle Support.
OGG-01708: Failed to create an instance of {0}
The Oracle GoldenGate Monitor Java Agent was not installed properly, or the Java VM ran out of memory.
Action:
Reinstall the Oracle GoldenGate Monitor Java Agent according to the instructions in the Oracle GoldenGate Monitor administration documentation.
OGG-01709: Failed to create an array of instances of {0}
The Oracle GoldenGate Monitor Java Agent was not installed properly, or the Java VM ran out of memory.
Action:
Reinstall the Oracle GoldenGate Monitor Java Agent according to the instructions in the Oracle GoldenGate Monitor administration documentation.
OGG-01710: Failed to retrieve {0} from {1}
The metadata cache of the Oracle GoldenGate Monitor C-agent was not initialized properly.
Action:
Contact Oracle Support.
OGG-01711: Failed to find the Java class ID of {0}
The Oracle GoldenGate Monitor Java Agent was not installed properly.
Action:
Reinstall the Oracle GoldenGate Monitor Java Agent according to the instructions in the Oracle GoldenGate Monitor administration documentation. Make certain that the jagent.jar file exists in the dirjar directory.
OGG-01712: Failed to find the ID of method {1} in Java class {0}
The Oracle GoldenGate Monitor Java Agent was not installed properly.
Action:
Reinstall the Oracle GoldenGate Monitor Java Agent according to the instructions in the Oracle GoldenGate Monitor administration documentation. Make certain that the jagent.jar file exists in the dirjar directory.
OGG-01713: Failed to retrieve the Java VM object
The Oracle GoldenGate Monitor Manager failed to load the Java VM or the Java VM that is loaded is invalid.
Action:
Make certain that a supported version of Java is installed on the local system. For the supported Java versions, see the Oracle GoldenGate Monitor administration documentation.
OGG-01714: Failed to allocate memory for {0}
The Oracle GoldenGate Monitor C-agent failed to create a new Java object because the Java VM ran out of memory.
Action:
Contact Oracle Support.
OGG-01715: Failed to call class {0} method {1}
The Oracle GoldenGate Monitor C-agent failed to call the Java Agent.
Action:
Reinstall the Oracle GoldenGate Monitor Java Agent according to the instructions in the Oracle GoldenGate Monitor administration documentation. Make certain that the jagent.jar file exists in the dirjar directory.
OGG-01716: Failed to find the process {0} in the given process list
The specified Extract or Replicat process could not be found by Oracle GoldenGate Monitor.
Action:
None. The process list will be refreshed in the next update interval.
OGG-01717: Failed to create a wrapper object {0} with the given object ID {1}
The Oracle GoldenGate Monitor C-agent detected an invalid monitoring point.
Action:
Contact Oracle Support.
OGG-01718: Failed to retrieve {0} MpObjectInfo from loaded MP metadata
The Oracle GoldenGate Monitor C-agent detected an invalid monitoring point.
Action:
Contact Oracle Support.
OGG-01719: Failed to load Metadata during initialization
Monitoring point metadata was not properly initialized in the Oracle GoldenGate Monitor C-agent.
Action:
Contact Oracle Support.
OGG-01720: Failed to retrieve corresponding JNI type for {0}
The data type of a monitoring point in the Java agent is not consistent with the data type in the C-agent.
Action:
Make certain that the version of the Java Agent is compatible with that of the C-agent, or contact Oracle Support.
OGG-01721: Failed to retrieve PseudoObjectProcAssociation object for object {0}.
A trail or database object that is maintained in the cache of the Oracle GoldenGate Monitor C-agent is invalid.
Action:
Contact Oracle Support.
OGG-01722: Failed to retrieve input parameter {0} in {1} JNI invocation
An error occurred between the Java Agent and the C-agent because the JNI call parameter is not valid.
Action:
Contact Oracle Support.
OGG-01723: Zero MPs returned for pseudo object {0}
The number of retrieved monitoring points for a trail or database object is not valid.
Action:
Contact Oracle Support.
OGG-01724: Pseudo object {0} with associated process name {1} is not found
The metadata for the monitoring points that are maintained by the Oracle GoldenGate Monitor C-agent is inconsistent with the monitoring points that were captured by the Extract or Replicat process.
Action:
Contact Oracle Support.
OGG-01725: Number of MPs {2,number,0} in Pseudo object list does not match the number of MPs {1,number,0} returned from the process {0}
The metadata for the monitoring points that are maintained by the Oracle GoldenGate Monitor C-agent is inconsistent with the monitoring points that were captured by the Extract or Replicat process.
Action:
Contact Oracle Support.
OGG-01726: Failed to retrieve the singleton CprocessManager instance
An internal error occurred in the Oracle GoldenGate Monitor C-agent.
Action:
Contact Oracle Support.
OGG-01727: Failed to retrieve the manager process from collectProcess call
An internal error occurred in the Oracle GoldenGate Monitor C-agent.
Action:
Contact Oracle Support.
OGG-01728: MP id {0} should be in the form of objid:mpid
The monitoring point passed by the Java agent to the C-agent has an invalid format.
Action:
Contact Oracle Support.
OGG-01729: Invalid In-Out type {0,number,0} for getMappedMpid call
The specified monitoring point is invalid.
Action:
Contact Oracle Support.
OGG-01730: Appender '{0}' in configuration file '{3}' uses 'BinaryLayout' in a 'RollingFileAppender' with 'MaxFileSize' of {1}, which is smaller than the minimum of {2}.
The value for 'MaxFileSize' for a RollingFileAppender when BinaryLayout is used must be larger than the specified size.
Action:
Correct the appender definition in the XML file.
OGG-01731: Appender '{0}' in configuration file '{1}' uses 'BinaryLayout' with filters, which is not supported
Filters are not supported with the BinaryLayout layout.
Action:
Remove the Filter element.
OGG-01733: Trail file header file size value {2,number,0} for trail file '{0}' differs from the actual size of the file ({1,number,0}).
There is a discrepancy between the expected size of the trail file, as stated in the file header, and the actual size of the file. The file was truncated because there is a shortage of disk space or a corruption in the file system.
Action:
Contact Oracle Support. Extensive recovery is needed to prevent data loss.
OGG-01735: Synchronizing {0} to disk
The specified trail file on the target was opened, closed, or rolled over. Informational only.
Action:
None
OGG-01736: {2}: Buffer overflow, needed: {1,number,0}, allocated: {0,number,0}. Table {3}, column {4}.
A numeric conversion failed because the value in the archive logs has more digits that the specified column can contain.
Action:
Verify that the column definitions are correct.
OGG-01738: Bounded Recovery started checkpoint for the object pool {0}, pool ID {1}.
A Bounded Recovery checkpoint was issued. Informational only.
Action:
None
OGG-01739: {0} must be used with the {1} parameter in order to function correctly.
A required option or parameter is missing in the parameter file.
Action:
Add the specified option or parameter to the parameter file. Stop the process, and then restart it again for the new configuration to take effect.
OGG-01740: Invalid numeric data detected and replaced by _CONVERTBADNUMBER. Column {0}, table {1}, rowid {2}, row length {3,number,0}, rowdata: {4}
The redo data is corrupted. Either Extract assigned a zero value or a conversion was made (Oracle GoldenGate version 8 and later). This is a warning to alert you that data was converted.
Action:
None
OGG-01741: Unexpected Log Sequence encountered at LSN {0}, previous LSN {1}.
The transaction records appear to be out of sequence.
Action:
Contact Oracle Support with details of this message.
OGG-01742: Command sent to {0} {1} returned with {2,choice,-1#an ERROR│0#an empty│1#an invalid} response.
A command sent to Manager resulted in the specified error response. The expected response is either invalid data or an error indicator.
Action:
Retry the command that caused the error. If it fails again, look at the process report file and the error log (and the Windows event browser if Manager is a Windows service) for errors generated before this message. These errors could indicate the cause and possible resolution. If you cannot resolve the error based on these logs, contact Oracle Support.
OGG-01745: Additional columns detected for table {0}. Change data processing may be less efficient until the table is reorganized.
An ALTER TABLE...ADD COLUMN command was issued to add one or more columns to the specified table.
Action:
Reorganize the table to avoid the extra overhead in processing log data for this table. This will ensure that the before image for any future updates match the table definition.
OGG-01746: Support for parameter {0} is not available in the RDBMS version you are using.
The parameter is not supported for the database or database version (or both) that the associated Oracle GoldenGate process is connected to.
Action:
Remove the parameter from the parameter file. See the Oracle GoldenGate documentation to find out if there is a similar parameter that is supported for the database or a specific release of the database.
OGG-01747: Error resetting AES cipher at trail file {0}, RBA {1,number,0} (error {2,number,0}, {3})
An error occurred while attempting to reset the AES cipher. This message is deprecated.
Action:
None
OGG-01748: Error encrypting data record with AES cipher at trail file {0}, RBA {1,number,0} (error {2,number,0}, {3})
An error occurred while encrypting a data record with an AES cipher. This message is deprecated.
Action:
None
OGG-01750: Successfully unregistered Extract group {0} from database.
A DELETE EXTRACT or UNREGISTER EXTRACT command was issued to unregister the Extract group from the database.
Action:
None
OGG-01751: Cannot register or unregister Extract group {0} because no database login was provided. Use DBLOGIN to establish a connection.
A REGISTER EXTRACT or UNREGISTER EXTRACT command was issued without first issuing a DBLOGIN command.
Action:
Issue the DBLOGIN command, and then issue REGISTER EXTRACT or UNREGISTER EXTRACT again.
OGG-01754: Cannot register or unregister Extract group {0} because the Extract is currently running. Stop the Extract and retry the command.
A REGISTER EXTRACT or UNREGISTER EXTRACT command was issued without first stopping the process.
Action:
Stop the Extract process, then issue a DBLOGIN command, and then the REGISTER EXTRACT or UNREGISTER EXTRACT command.
OGG-01762: The Oracle GoldenGate Monitor service could not be started. Monitoring might not be supported on this platform or the agent might not be installed correctly.
Oracle GoldenGate failed to load the required Java VM, or failed to start the Java Agent or C Agent module, or failed to start the service that publishes information on the monitoring points. Monitoring services will not be available.
Action:
Make certain that Oracle GoldenGate Monitor is installed on a supported platform, and if so, reinstall the agent. See the administration documentation for instructions.
OGG-01777: Extract abended as it ran out of sequence numbers used to create TRAIL files. The maximum number of TRAIL files allowed is 999999.
Extract ran out of sequence numbers that it uses to create trail files.
Action:
Contact Oracle Support
OGG-01778: Feature {0} unsupported on the current database version. Upgrade database version to {1} or higher.
The specified feature is not supported by Oracle GoldenGate for the current database version.
Action:
Upgrade to at least the specified database version.
OGG-01779: Invalid specification on {0} command.
The specified command contains invalid input.
Action:
Fix the invalid input. For help, see the Oracle GoldenGate reference documentation.
OGG-01780: Missing/Invalid argument(s) on {0} command.
Arguments that were provided for the specified command are either incomplete or invalid.
Action:
Fix the invalid input. For help, see the Oracle GoldenGate reference documentation.
OGG-01781: Wildcard is not allowed on {0} command.
The specified command does not allow wildcards as input.
Action:
Replace the wildcard with an explicit name specification. For help, see the Oracle GoldenGate reference documentation.
OGG-01782: Unknown command on {0}.
The specified command is invalid.
Action:
Verify the syntax and then issue the command again. For help, see the Oracle GoldenGate reference documentation.
OGG-01783: Cannot verify existence of table function that is required to enable schema level supplemental logging, {0}.
The function that is used to enable schema level supplemental logging (ADD SCHEMATRANDATA command) is missing from the database.
Action:
Apply Oracle Patch 10423000 to the source database.
OGG-01784: INFO SCHEMATRANDATA failed due to error during select start.
The SELECT statement that underlies the INFO SCHEMATRANDATA command failed.
Action:
Try the command again. If the problem persists, contact Oracle Support.
OGG-01785: Schema level supplemental logging is enabled on schema "{0}".
Schema-level supplemental logging is enabled for all objects in the specified schema, as the result of the ADD SCHEMATRANDATA command. Informational only.
Action:
None
OGG-01786: Schema level supplemental logging is disabled on schema "{0}".
Schema-level supplemental logging is disabled for the specified schema, as the result of the DELETE SCHEMATRANDATA command. Informational only.
Action:
None
OGG-01787: INFO SCHEMATRANDATA failed on schema "{0}" because of the following OCI error: {1}-{2}
A OCI error prevented Oracle GoldenGate from getting information about schema-level supplemental logging through the INFO SCHEMATRANDATA command.
Action:
Fix the OCI error and retry the INFO SCHEMATRANDATA command. If the OCI error cannot be resolved, contact Oracle Support.
OGG-01788: SCHEMATRANDATA has been added on schema "{0}".
The ADD SCHEMATRANDATA command enabled supplemental logging for all objects in the specified schema. Informational only.
Action:
None
OGG-01789: Failed to ADD SCHEMATRANDATA on schema "{0}", because schema does not exist.
The schema that is specified in the ADD SCHEMATRANDATA command does not exist.
Action:
Fix any typographical errors or create the schema, and then retry the command.
OGG-01790: Failed to ADD SCHEMATRANDATA on schema "{0}" because of the following SQL error: {1}
The specified SQL error prevented the ADD SCHEMATRANDATA command from enabling supplemental logging for the specified schema.
Action:
Fix the SQL error and then retry ADD SCHEMATRANDATA.
OGG-01791: Failed to ADD SCHEMATRANDATA on schema "{0}" because of an internal error: {1}.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01792: SCHEMATRANDATA has been deleted on schema "{0}".
Schema-level supplemental logging is disabled for the specified schema, as the result of the DELETE SCHEMATRANDATA command. Informational only.
Action:
None
OGG-01793: Failed to DELETE SCHEMATRANDATA on schema "{0}", because schema does not exist.
The DELETE SCHEMATRANDATA command failed because the specified schema does not exist.
Action:
Verify that the correct schema is specified in the command input, and try the command again.
OGG-01794: Failed to DELETE SCHEMATRANDATA on schema "{0}" because of the following SQL error: {1}
DELETE SCHEMATRANDATA failed because of the specified SQL error.
Action:
Fix the SQL error and retry the command.
OGG-01795: Failed to DELETE SCHEMATRANDATA on schema "{0}" because of an internal error: {1}.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-01796: Schema: "{0}", does not exist.
The specified schema does not exist.
Action:
Verify that the schema name is spelled correctly in the command or parameter input. Make certain that the schema still exists in the database.
OGG-01797: Table {0} column values will also be captured in native format: {1}
ADDNATIVE is used for the specified table in a TABLE statement. In this mode, Extract will also capture supported data values in their native format.
Action:
None
OGG-01799: Unable to rename file "{0}" to "{1}" (error {2,number,0}, {3})
The process could not rename the specified file on the local file system. Oracle GoldenGate cannot continue.
Action:
Correct the problem based on the operating system error message that is returned. If you cannot resolve the problem, contact Oracle Support.
OGG-01800: Unable to rename file "{0}" to "{1}" (error {2,number,0}, {3})
The process could not rename the specified file on the local file system. Oracle GoldenGate will continue processing.
Action:
To avoid future warnings or possible failures related to this condition, correct the problem based on the operating system error message that is returned. If you cannot resolve the problem, contact Oracle Support.
OGG-01801: Failed to determine discard file name
An internal error occurred when trying to determine the name of the discard file.
Action:
Contact Oracle Support.
OGG-01802: Discard file path name "{0}" is too long. Specify a name that is no more than 250 characters.
The fully qualified name of the discard file is longer than the 250 characters allowed.
Action:
Change the DISCARDFILE parameter to specify a file name that is no more than 250 characters.
OGG-01803: {0} SCHEMATRANDATA option "{1}" is invalid. Valid options are: {2}.
An invalid option was specified for the ADD SCHEMATRANDATA or DELETE SCHEMATRANDATA command.
Action:
See the Oracle GoldenGate Reference Guide for correct syntax.
OGG-01804: Option "{0}" is invalid. INFO SCHEMATRANDATA does not have options.
The INFO SCHEMATRANDATA command was issued with invalid options. This command takes no options.
Action:
See the Oracle GoldenGate Reference Guide for correct syntax.
OGG-01805: Virtual memory allocation error: {0,number,0})
An attempt to allocate virtual memory failed.
Action:
Contact Oracle Support.
OGG-01806: Virtual memory mmap allocation error: {0} (error: {1,number,0})
An attempt to allocate virtual memory failed.
Action:
Contact Oracle Support.
OGG-01807: Virtual memory custom allocation error
An attempt to allocate virtual memory failed.
Action:
Contact Oracle Support.
OGG-01808: Virtual memory file read error
An attempt to read a file failed.
Action:
Contact Oracle Support.
OGG-01809: Virtual memory unmap error: {0} (error: {1,number,0})
An attempt to unmap virtual memory failed.
Action:
Contact Oracle Support.
OGG-01810: Virtual memory custom deallocation error
An attempt to deallocate virtual memory failed.
Action:
Contact Oracle Support.
OGG-01811: Virtual memory file write error
An attempt to write to a file failed.
Action:
Contact Oracle Support.
OGG-01812: Virtual memory probe error: {0}
An attempt to probe virtual memory failed.
Action:
Contact Oracle Support.
OGG-01813: invalid parameter
An invalid parameter was passed to the VMF constructor.
Action:
Contact Oracle Support.
OGG-01814: file utility error: {0}: file: {1}: {2} (error: {3,number,0})
The specified file utility function failed.
Action:
Contact Oracle Support.
OGG-01815: Virtual Memory Facilities for: {0} anon alloc: {1} anon free: {2} file alloc: {3} file free: {4} target directories: {5}
The virtual memory facilities for the specified module and directories have been determined. Informational only.
Action:
None
OGG-01818: XMLDiff data is missing, can not continue: table {0}.
XMLDiff data for a column was read from trail but did not get processed.
Action:
It is an internal error. Contact support.
OGG-01819: Operation on table {0} with a deferrable constraint is not supported because a workspace is active.
A table with a deferrable constraint was modified in a transaction that has an open workspace for handling transient duplicates.
Action:
Remove the deferrable constraint, and then restart the process.
OGG-01820: Could not enable workspace
An attempt to handle transient duplicates in an update statement failed.
Action:
Restart Replicat. If the problem persists, grant privileges to the Replicat user by running the dbms_goldengate_auth.grant_admin_privilege procedure. Also resolve any associated errors, such as OCI session errors.
OGG-01821: DYNAMICPORTREASSIGNDELAY parameter has been deprecated. Value will be ignored.
The DYNAMICPORTREASSIGNDELAY parameter is not valid for the current Oracle GoldenGate version.
Action:
Remove the DYNAMICPORTREASSIGNDELAY parameter from the parameter file.
OGG-01822: Invalid trail FORMAT RELEASE {0} is specified.
Invalid trail FORMAT RELEASE is specified.
Action:
Specify the correct FORMAT RELEASE release, such as 10.4, 11.1, 11.2, 12.1, 12.2, 12.3, and 18.1.
OGG-01823: Invalid SHELL syntax: {0}. Shell command must be enclosed in parentheses or double quotes.
The command in EVENTACTIONS SHELL is not enclosed within parentheses or double quotes.
Action:
Enclose the command within parentheses or double quotes.
OGG-01824: Resume processing from SUSPEND state for process {0}.
The process is resuming after an EVENTACTIONS SUSPEND state.
Action:
None required.
OGG-01825: DDL operation ignored due to EMI [{0}], optype [{1}], objtype [{2}], objowner "{3}", objname "{4}"
The specified DDL operation was ignored according to the rule specified in EVENTACTIONS.
Action:
None required.
OGG-01826: SPECIALRUN task type is no longer supported for Extract (capture).
SPECIALRUN as a task type has been removed from Extract processes.
Action:
Remove SPECIALRUN task type as a declaring attribute for Extract processes.
OGG-01827: SPECIALRUN task type is no longer supported for Extract (capture).
SPECIALRUN as a task type has been removed from Extract processes.
Action:
Remove SPECIALRUN task type as a declaring attribute for Extract.
OGG-01828: Trail file FORMAT RELEASE {0} or higher is required for operation {1}.
The EXTFILE, EXTTRAIL, RMTFILE, or RMTTRAIL parameter contains the FORMAT option, but the given RELEASE value does not support the specified operation.
Action:
To support the specified operation type, set FORMAT RELEASE to at least the version shown in the error message. Note that the reader process (data pump or Replicat) must be at least the specified version.
OGG-01832: Failed to determine if the table is XMLType: table {0}.
An internal error occurred when trying to verify a table as XMLType.
Action:
Contact Oracle Support.
OGG-01833: Missing OID value for table {0}.
An internal error occurred when processing an object table.
Action:
Contact Oracle Support.
OGG-01835: No schema is specified for table {0} in statement '{1}'. Using default schema {2}.
A schema was not explicitly given in the specification for this table in the parameter file. The default login schema of the process is being used.
Action:
To specify a schema other than the default login schema, edit the parameter file to specify the correct schema.
OGG-01836: No schema is specified for table {0} in statement '{1}'. No mapping will be applied.
A schema was not explicitly given in the specification for this table in the parameter file. No mapping will be applied.
Action:
Specify a schema or add DBLOGIN parameter to use default schema. Edit the parameter file to specify the correct schema or add DBLOGIN parameter.
OGG-01837: Fetch requires database redo compatible version {0} or higher.
The specified database redo-compatible version does not support fetch.
Action:
To support fetch, set the database redo-compatible version to at least the version shown in the error message.
OGG-01838: The internal token encountered, 0x{0}, in the trail is unknown.
The internal token in the trail record is unknown.
Action:
Verify that the version of Extract and Replicat are compatible.
OGG-01839: RDBMS OCI Library does not support PARTIAL XML: table {0}.
RDBMS OCI Library does not support PARTIAL XML.
Action:
A workaround is to use FETCHPARTIALXML option in Extract so that Replicat does not encounter PARTIAL XML.
OGG-01840: Internal error in forming SQL from PARTIAL XML: table {0}.
An internal error occurred while forming SQL from PARTIAL XML read from trail.
Action:
A workaround is to use FETCHPARTIALXML option in Extract so that Replicat does not encounter PARTIAL XML. Contact Oracle support.
OGG-01841: {0}
CACHESIZE is below the valid minimum.
Action:
Check the parameter file for an invalid CACHEMGR CACHESIZE setting. Check available swap space on the system. See CACHEMGR in the Oracle GoldenGate reference documentation for setting swap size.
OGG-01842: {0}
The virtual memory is below the recommended minimum.
Action:
Check the swap space available on the system. See the CACHEMGR parameter in the Oracle GoldenGate reference documentation for the recommended swap size.
OGG-01843: {0}
An internal error occurred. Usually this message is logged along with other messages that provide more specific information. In some cases, the message text will indicate a cause and possible action.
Action:
Contact Oracle Support.
OGG-01844: CACHEMGR: filecaching, error 0x{0} deleting file: name {1}, co_uid 0x{2}, mf 0x{3}, co 0x{4}
An error occurred deleting a CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-01845: {0}
A fatal mmap/MapViewOfFile error has occurred.
Action:
Contact Oracle Support.
OGG-01846: {0}
A VMF (Virtual Memory Facilites) error occurred. See the message body for more details.
Action:
Contact Oracle Support.
OGG-01847: {0}
A VMF (Virtual Memory Facilites) error occurred. See the message body for more details.
Action:
Contact Oracle Support.
OGG-01848: CACHEMGR: oldest cached object 0x{0}, co_uid: 0x{1} has no aux data
Oldest cached object found does not have auxiliary data.
Action:
Contact Oracle Support.
OGG-01849: CACHEMGR: filecaching error 0x{0} setting position in file: {1}, co_uid: {2}, mf: 0x{3}, co: 0x{4}
An error during CACHEMGR file caching has occurred while trying to position within a file.
Action:
Contact Oracle Support.
OGG-01850: CACHEMGR: invalid parameter: {0}
The CACHEMGR parameter is invalid.
Action:
Refer to Oracle GoldenGate documentation for specification of the CACHEMGR parameter.
OGG-01851: filecaching started: thread ID: {0,number,0}
The filecaching thread was started.
Action:
None
OGG-01852: CACHEMGR: filecaching queue is in an invalid state
The CACHEMGR filecaching queue is in an invalid state.
Action:
Contact Oracle Support.
OGG-01853: CACHEMGR: filecaching: error {0,number,0}
An error occurred accessing the CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-01854: CACHEMGR: filecaching: {0}
An error occurred accessing CACHEMGR mbuf VM.
Action:
Contact Oracle Support.
OGG-01855: CACHEMGR: filecaching virtual memory is in invalid state. vm_freed: 0x{0}, vm_freed_from_writes: 0x{1}, vm_released: 0x{2}
The CACHEMGR VM accounting is in an invalid state.
Action:
Contact Oracle Support.
OGG-01856: CACHEMGR: filecaching: {0}
A threading error has occurred in the CACHEMGR filecaching.
Action:
Contact Oracle Support.
OGG-01857: CACHEMGR: filecaching: {0}
An error occurred accessing the CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-01858: CACHEMGR: filecaching error closing file handle: 0x{0}, name: {1}, co_uid: 0x{2}, mf: 0x{3}, co: 0x{4}
An error occurred closing a CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-01859: CACHEMGR: filecaching error: 0x{0} opening file: name {1}, co_uid: 0x{2}, mf: 0x{3}, co: 0x{4}
An error occurred opening a CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-01860: CACHEMGR: directory does not exist: {0}
The directory in question does not exist.
Action:
Contact Oracle Support.
OGG-01861: CACHEMGR from client: process name: {0}, ID:{1}, instance: {2,number,0}.
CACHEMGR general information
Action:
Contact Oracle Support.
OGG-01862: BR RESTORE error. Standard Recovery will be used instead. Please contact Oracle Support. Please keep the rpt file if possible
There was an error during BR RESTORE processing.
Action:
Contact Oracle Support.
OGG-01863: BR RESTORE error
There was an error during BR RESTORE processing.
Action:
Contact Oracle Support.
OGG-01864: CACHEMGR: No items in object uid: 0x{0}, items: 0x{1}, size: 0x{2}, co: 0x{3}
There are no items found in the cached object at the requested position.
Action:
Contact Oracle Support.
OGG-01865: MMAP: madvise error 0x{0}, addr: 0x{1}, len: 0x{2}, advise: 0x{3}
System call madvise failed.
Action:
Contact Oracle Support.
OGG-01866: CACHEMGR: Out of limit value {2,number,0} {1} set for parameter: {0}. Range values between: min {3,number,0} - max {4,number,0} {1}
The CACHEMGR parameter reported in the error message contains an out of limit value.
Action:
Adjust the value to be in the limits reported in the error message and then restart the process.
OGG-01867: BR: Cannot deallocate virtual memory: size 0x{0}, file: {1}, code: {2,number,0} ({3})
An attempt to unmap virtual memory failed.
Action:
Contact Oracle Support.
OGG-01868: BR: error closing file handle: 0x{0}, name: {1}, code: {2,number,0} ({3})
An error occurred while closing a BR file.
Action:
Contact Oracle Support.
OGG-01870: The Operating System does not support IPv6 dual stack mode (error: {0,number,0}, {1}).
The system only has the IPv6 stack enabled or installed, or the IPv6 stack does not support dual stack mode.
Action:
None
OGG-01871: Unexpected error fetching from table {0} - {1,number,0}
This is an internal error.
Action:
Contact Oracle Support.
OGG-01872: Transaction delivery commencing with Transaction ID {0}, CSN {1}, {2,number,0} transaction(s) skipped.
A START EXTRACT command for a Primary Extract was issued with the ATCSN or AFTERCSN option. Extract is starting processing with the specified transaction in the trail. The number of transactions that were skipped is stated in the message.
Action:
None
OGG-01874: Unsupported trail FORMAT RELEASE {0} is specified.
Format release 9.0/9.5 or 10.0 is specified. These format releases are no longer supported.
Action:
Specify the correct FORMAT RELEASE release, such as 10.4, 11.1, 11.2, 12.1, 12.2, 12.3, and 18.1.
OGG-01876: Access to MGR is denied (request from {0}, rule #{1,number,0})
Access to Manager was denied to the specified address based on rules set in the ACCESSRULE parameter.
Action:
Determine why the connection attempt was made. If it is legitimate, adjust the rules of ACCESSRULE.
OGG-01877: Missing explicit accessrule for server collector.
There was no explicit ACCESSRULE specified for SERVER.
Action:
Only allow accessing SERVER from hosts where data pump(s) might send trail files to this host.
OGG-01878: Failed resolving ALLOWOUTPUTDIR {0} (error: {1,number,0}, {2})
Unable to locate the canonical path of the given directory.
Action:
Resolve the reported error.
OGG-01879: ALLOWOUTPUTDIR {0} conflicts with reserved GoldenGate directory {1}
Specified ALLOWOUTPUTDIR entry is or is within a reserved path.
Action:
Pick another directory.
OGG-01880: ALLOWOUTPUTDIR {0} is the same directory where this GoldenGate instance is installed.
Specified ALLOWOUTPUTDIR entry is the same directory as this Oracle GoldenGate installation. Note that no output files are allowed in GoldenGate home directory.
Action:
None
OGG-01881: Output file {0} in the GoldenGate installation directory is not allowed.
The remote party requested to open an output file in the Oracle GoldenGate home directory.
Action:
Specify a different output file directory in the remote data pump parameter file.
OGG-01882: Output file {0} is not in any allowed output directories.
The remote party requests to open an output file in some directory that is not specified by ALLOWOUTPUTDIR
Action:
Specify a different output file directory in the remote data pump parameter file, or add that directory in GLOBALS by ALLOWOUTPUTDIR statement.
OGG-01883: Failed resolving output file {0} (error: {1,number,0}, {2})
Not able to locate the canonical path of the given file name.
Action:
Resolve the reported error.
OGG-01884: Output file {0} is in a reserved GoldenGate directory {1}
Specified RMTTRAIL in data pump is or is within a reserved path.
Action:
Specify another RMTTRAIL location.
OGG-01885: Starting a VERIDATA or VERIAGT process remotely through MGR is not allowed.
Starting a VERIDATA or VERIAGT process remotely through MGR is not allowed.
Action:
None
OGG-01886: Error tuning TCP network parameters, error {0,number,0} - {1}.
Failed to tune the network parameters.
Action:
Contact Oracle Support.
OGG-01887: Legacy parameter TCPBUFSIZE is overridden by option SNDBUF of INETOPT.
The new INETOPT.SNDBUF option overrides legacy TCPBUFSIZE option, if they are both specified at the same time.
Action:
None
OGG-01888: TCP network is configured as {0}.
Undefined
Action:
None
OGG-01889: Flush size (max message size) is set to {0}.
Undefined
Action:
None
OGG-01890: Compression level is set to {0}.
Undefined
Action:
None
OGG-01891: Extract group {0} must first be deleted before it can be registered.
A REGISTER EXTRACT command was issued for an Extract group that was unregistered, but not deleted.
Action:
Delete then re-add the Extract group, and then retry the command.
OGG-01892: Distribution path network is configured as {0}.
Undefined
Action:
None
OGG-01893: Error tuning UDT network parameters, error {0} - {1}.
Failed to tune the network parameters.
Action:
Contact Oracle Support.
OGG-01894: Trail record length {0} bytes exceeds the processing buffer size.
The process tried to process a trail record that is bigger than the maximum allowed size.
Action:
Contact Oracle Support.
OGG-01896: Table {0}.{1} has an identity column which is not supported. This table will be ignored by Extract.
Extract found a table with an identity column that is not supported. This table will be ignored by Extract.
Action:
Remove the table with the identity column from the Oracle GoldenGate configuration.
OGG-01897: Table {0}.{1} has a temporal validity column which is not supported. This table will be ignored by extract.
Extract found a table with a temporal validity column that is not supported. This table will be ignored by Extract.
Action:
Remove the table with the temporal validity column from the Oracle GoldenGate configuration.
OGG-01898: Error ({0,number,0}, {1}) releasing stmt in {2}
An error occurred when releasing an internal cursor.
Action:
Contact Oracle Support.
OGG-01899: Unable to set UDP send or receive buffer size {0}, because it exceeds the OS buffer size limit. Try with a smaller value or increase OS UDP send or receive buffer size limit.
Preferred UDP send or receive buffer size specified exceeds the limit set for the OS.
Action:
Reduce the preferred send or receive buffer size for UDP or adjust the max UDP buffer size kernel limit for your OS.
OGG-01900: Key column {2} cannot be specified in {1} clause of {0}
A key column is specified in the ALLEXCLUDING clause of the MAP statement.
Action:
Remove any key columns from the ALLEXCLUDING clause.
OGG-01901: Incompatible resolution {2} specified for {0}: {1}
An incompatible resolution was given for the specified conflict.
Action:
Specify a valid resolution for this conflict. For valid resolutions per conflict type, see RESOLVECONFLICT Oracle GoldenGate reference documentation.
OGG-01902: Unsupported datatype for column {1} specified in {0} clause
An unsupported data type is specified in the COMPARECOLS clause of the MAP statement or the GETBEFORECOLS of a TABLE statement.
Action:
Specify a column that has a supported data type. For supported data types, see the Oracle GoldenGate reference documentation.
OGG-01903: Column {2} for {0}:{1} previously used in prior conflict resolution
The same column is specified in more than one conflict resolution type.
Action:
Select a different column or column group for each resolution type.
OGG-01904: Missing COLS clause for non-default conflict resolution {0}:{1}
The RESOLVECONFLICT parameter specifies a non-DEFAULT resolution, but does not contain a COLS clause.
Action:
Specify a COLS clause for a non-default resolution. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-01905: Missing apply col list for non-default conflict resolution {0}:{1}
The RESOLVECONFLICT parameter specifies a non-DEFAULT resolution, but does not list columns in the COLS clause. For help with syntax, see the Oracle GoldenGate reference documentation.
Action:
Specify one or more columns in a COLS clause for a non-default resolution. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-01906: Missing resolution column for conflict resolution {0}:{1}
The RESOLVECONFLICT parameter specifies a USEMIN or USEMAX resolution, but no resolution columns are specified. For help with syntax, see the Oracle GoldenGate reference documentation.
Action:
Supply a resolution column for USEMIN or USEMAX resolution. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-01907: Null column {0} cannot be used in delta resolution
A null column was specified in the USEDELTA resolution in the RESOLVECONFLICT parameter.
Action:
Replace USEDELTA with an appropriate resolution for null columns.
OGG-01908: Duplicate specification found for {0} conflict
A conflict type was specified more than once in a MAP statement.
Action:
Remove duplicate conflict specification.
OGG-01909: Invalid ({2}) columns specified in {1} resolution of conflict {0}
An invalid number of resolution columns was specified for the chosen conflict type.
Action:
Specify only one resolution column per conflict type.
OGG-01910: Missing apply columns in non-default conflict resolution {0}:{1}
A non-default resolution was specified in RESOLVECONFLICT, but the apply (target) columns are not specified.
Action:
Specify at least one apply column in a non-default conflict resolution.
OGG-01911: Missing column specification in {1} option of {0}
Missing column in COMPARECOLS/GETBEFORECOLS option.
Action:
Specify at least one column in the COMPARECOLS/GETBEFORECOLS option.
OGG-01912: Duplicate specification of {1} {2} clause in {0} parameter
Duplicate specification of a COMPARECOLS/GETBEFORECOLS clause in a MAP statement.
Action:
Remove duplicate COMPARECOLS/GETBEFORECOLS clause.
OGG-01913: Duplicate {0} parameter found
Duplicate specification of a conflict resolution parameter in a MAP statement.
Action:
Remove the duplicate parameter specification.
OGG-01914: Duplicate {1} resolution found for conflict {0}
A duplicate resolution name is specified for this conflict.
Action:
Specify a unique name for each resolution.
OGG-01915: Missing DEFAULT resolution for conflict {0}
The specified conflict does not contain a DEFAULT resolution.
Action:
Specify a DEFAULT resolution for this conflict in the RESOLVECONFLICT parameter.
OGG-01916: Missing or incomplete specification of resolution {1} for conflict {0}
The resolution for the specified conflict is missing or incomplete.
Action:
Specify a valid resolution for this conflict. For valid resolutions per conflict type, see RESOLVECONFLICT Oracle GoldenGate reference documentation.
OGG-01917: Incorrect or incomplete specification of RESOLVECONFLICT {0}
The conflict clause of the RESOLVECONFLICT statement is incomplete.
Action:
Specify a valid conflict for this RESOLVECONFLICT parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-01918: Missing option {1} or incomplete specification of {0}
Missing or incomplete specification in COMPARECOLS/GETBEFORECOLS parameter.
Action:
Specify valid COMPARECOLS and GETBEFORECOLS options. For help, see the Oracle GoldenGate reference documentation.
OGG-01919: Missing RESOLVECONFLICT for SQL error {0}
An apply conflict was detected, but the Replicat parameter file does not contain a RESOLVECONFLICT parameter to resolve it.
Action:
Specify a matching RESOLVECONFLICT to enable conflict resolution.
OGG-01920: Missing COMPARECOLS column "{0}" in before image, while mapping to target table "{1}". Add the column to GETBEFORECOLS.
The specified column is in a COMPARECOLS parameter, but is not specified with a GETBEFORECOLS parameter.
Action:
Specify the column in a GETBEFORECOLS parameter in the Extract parameter file, so that before images are available for comparison.
OGG-01921: Missing GETBEFORECOLS with conflict detection enabled in target table {0}
The specified table has a RESOLVECONFLICT parameter, but the before columns required by COMPARECOLS are not specified with GETBEFORECOLS.
Action:
Specify GETBEFORECOLS in the Extract parameter file so that before images are captured for COMPARECOLS.
OGG-01922: Missing RESOLUTION COLUMN "{0}" while mapping to target table "{1}"
The before image of the specified column is not available for the conflict resolution.
Action:
Specify this column in a GETBEFORECOLS parameter in the Extract parameter file.
OGG-01923: Conflict resolution failed with SQL error {0} on original conflict with SQL error {1}
A conflict resolution failed with the specified SQL error.
Action:
Identify the cause of the SQL error, and then restart Replicat.
OGG-01924: Missing parenthesis for {0}
The GETBEFORECOLS or COMPARECOLS parameter contains an invalid specification.
Action:
Specify valid COMPARECOLS or GETBEFORECOLS options. For help, see the Oracle GoldenGate reference documentation.
OGG-01925: Ignoring redundant string {2} in {0} clause: {1}
A redundant string was found in the specified parameter.
Action:
Remove the redundant string from the parameter.
OGG-01926: Cannot flush sequence {0}. Refer to the Oracle GoldenGate for Oracle documentation for instructions on how to set up and run the sequence.sql script. Error {1}
The sequence.sql script was not run properly to install the required Oracle database procedures that support FLUSH SEQUENCE.
Action:
You must create a DDL user, configure Oracle GoldenGate to recognize this schema, create the procedures with the sequence.sql script, and assign privileges. Refer to Oracle GoldenGate for Oracle installation instructions.
OGG-01927: Child process started, process ID {0,number,0}, command line '{1}'
The specified Oracle GoldenGate child process was started.
Action:
None
OGG-01928: Child process terminated {0,choice,0#successfully│1#with exit code {0,number,0}}.
The specified Oracle GoldenGate child process was terminated.
Action:
None
OGG-01929: Child process terminated with signal {0,number,0}
The specified Oracle GoldenGate child process was terminated with a signal.
Action:
None
OGG-01931: Datastore '{0}' cannot be opened. Error {1,number,0} ({2})
The datastore environment cannot be opened.
Action:
Verify the datastore is created with the GGSCI command INFO DATASTORE. To add the datastore use the GGSCI command CREATE DATASTORE. To repair an existing datastore stop all GoldenGate processes, including Manager, and issue the GGSCI command REPAIR DATASTORE. Contact Oracle Support if assistance is needed.
OGG-01932: Datastore already exists.
The datastore environment cannot be created because it already exists.
Action:
None
OGG-01933: Datastore create failed.
The datastore environment cannot be created.
Action:
Examine the accompanying warnings and contact Oracle Support if assistance is needed.
OGG-01934: Datastore repair failed.
The datastore environment cannot be repaired.
Action:
To repair an existing datastore stop all GoldenGate processes, including Manager, and issue the GGSCI command REPAIR DATASTORE. If the issue persists contact Oracle Support.
OGG-01935: Error flushing file, handle: 0x{0}, err: {1,number,0} - {2}
The specified operating system error was returned when attempting to flush a file. This could be something you can resolve yourself, such as a disk failure, insufficient quota or a OS internal error. Otherwise, it probably is an internal Oracle GoldenGate error.
Action:
If possible fix the operating system error, and then restart the process. If you cannot resolve the error, contact Oracle Support.
OGG-01938: OBEY or INCLUDE file is not supported in parameter file {0}.
The parameter file specifies one or more OBEY or INCLUDE files. OBEY and INCLUDE are not supported.
Action:
Remove the OBEY/INCLUDE statement from the parameter file or merge the contents.
OGG-01939: Invalid table name "{0}" specified by parameter {1} in parameter file {2}.
The specified table name is not valid.
Action:
Correct the table name.
OGG-01940: Invalid schema name "{0}" specified by parameter {1} in parameter file {2}.
The specified schema name is not valid.
Action:
Correct the schema name.
OGG-01948: Invalid or unsupported character set {0} specified in parameter file {1}.
An invalid or unsupported character set is specified with the CHARSET parameter.
Action:
Specify a valid character set.
OGG-01949: CHARSET parameter is only supported on the first line of parameter file {0}.
The CHARSET parameter is not specified on the first line of the parameter file.
Action:
Move the CHARSET parameter to the first line of the parameter file or remove it from the file.
OGG-01950: Invalid MACRO definition in the MACRO {0}. The END keyword is not specified.
The MACRO definition does not end with the END keyword.
Action:
Add the END keyword.
OGG-01951: Invalid MACRO definition in the MACRO {0}. The macro body is not specified.
The MACRO definition does not contain a macro body.
Action:
Add the macro body.
OGG-01952: Missing open parentheses in MACRO {0} definition.
A macro is defined in the parameter file, but an open parentheses is missing in PARAMS clause.
Action:
Add the open parentheses.
OGG-01953: Missing close parentheses in MACRO {0} definition.
A macro is defined in the parameter file, but a close parentheses is missing in PARAMS clause.
Action:
Add the close parentheses.
OGG-01954: Invalid macro name ({0} - must begin with {1})
The name of the macro is not preceded by the macro character.
Action:
Add the macro character that is shown in this error message. This character must precede all macro names.
OGG-01955: Unused parameter {1} in the MACRO {0} definition.
A macro is defined in the parameter file, but there is an unused parameter in the macro body text.
Action:
Add the parameter to the macro body text or remove it from the macro body.
OGG-01956: Missing close parentheses in MACRO {0} invocation.
A macro is invoked in the parameter file, but a close parentheses is missing.
Action:
Add the close parentheses.
OGG-01957: Missing open parentheses in parameter {0}.
An open parentheses is missing from the specified parameter.
Action:
Add the open parentheses.
OGG-01958: Missing close parentheses in parameter {0}.
A close parentheses is missing from the specified parameter.
Action:
Add the close parentheses.
OGG-01962: OCI Error {1} (status = {0,number,0}). {2}
An error occurred in the OCI.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-01963: Network address and service translation call {0} failed with error (return code = {1,number,0}, errno = {2,number,0}, {3})
A call to an operating system-provided API regarding network address and service translation failed.
Action:
Check the operating system and network configuration for related problems, and resolve them or contact your system administrator. If you cannot resolve the problem, contact Oracle Support.
OGG-01964: No available socket on port {0}.
Failed to create a socket on the given port.
Action:
Check the operating system and network configuration for related problems, and resolve them or contact your system administrator. If you cannot resolve the problem, contact Oracle Support.
OGG-01965: Failed to write checkpoint file {0}
The process could not write to the checkpoint file.
Action:
Check the operating system privileges on the file, and make certain that the process has read and write privileges on it. Make certain the file is not corrupted. If the file remains unwritable, contact Oracle Support.
OGG-01966: AUTOSTART or AUTORESTART group type of '{0}' is invalid.
The group type for an AUTOSTART or AUTORESTART parameter must be one of ER, EXTRACT, REPLICAT, or JAGENT.
Action:
Correct the group type. For more information, see the Oracle GoldenGate reference documentation.
OGG-01967: A supplemental logging group cannot be found for table {0}. Issue the ADD TRANDATA command or enable logging of all columns.
Extract could not find a supplemental log group for the specified table. Supplemental logging is required so that the values of key columns are available to Extract.
Action:
Add a supplemental log group with the ADD TRANDATA command in ggsci or enable supplemental logging of all columns through the database. For more information about logging requirements, see the Oracle GoldenGate for Oracle documentation.
OGG-01968: The supplemental log group for table {0} does not contain all of the columns that Oracle GoldenGate expects to use as the key.
The supplemental log group for the specified table does not contain all of the key columns that are required by Oracle GoldenGate.
Action:
Add a supplemental log group with the ADD TRANDATA command, or enable logging for all of the columns.
OGG-01969: Cannot find metadata property {0}. DDL metadata [{1}]
A metadata property that Oracle GoldenGate needs to resolve is not present.
Action:
Upgrade the DDL trigger to the current version by running the ddl_setup script. For help, see the Oracle GoldenGate documentation for the Oracle database.
OGG-01971: The previous message, '{0} {1}', repeated {2,number,0} times.
The previous message repeated the specified number of times but was suppressed from logging.
Action:
None
OGG-01974: Synchronizing file data to disk failed due to system error. (func 0x{0}, err_cnt {1,number,0}, error: {2,number,0}, {3}).
A system call to synchronize the data of a file to disk failed.
Action:
None
OGG-01975: Failed to synchronize input trail {0} to disk. (error: {1,number,0}, {2}).
A system call to synchronize the input trail to disk failed.
Action:
Disable this feature by setting the internal parameter _NOSYNCSOURCETRAILONCHKPT. Contact Oracle Support for usage.
OGG-01976: SCHEMATRANDATA for scheduling columns has been added on schema "{0}".
The ADD SCHEMATRANDATA command enabled supplemental logging for scheduling columns in all the objects in the specified schema. Informational only.
Action:
None
OGG-01977: SCHEMATRANDATA for all columns has been added on schema "{0}".
The ADD SCHEMATRANDATA command enabled supplemental logging for all columns in all the objects in the specified schema. Informational only.
Action:
None
OGG-01978: SCHEMATRANDATA for all columns has been deleted on schema "{0}".
The DELETE SCHEMATRANDATA command disabled supplemental logging for all columns in all the objects in the specified schema. Informational only.
Action:
None
OGG-01979: SCHEMATRANDATA for scheduling columns has been deleted on schema "{0}".
The DELETE SCHEMATRANDATA command disabled supplemental logging for scheduling columns in all the objects in the specified schema. Informational only.
Action:
None
OGG-01980: Schema level supplemental logging is enabled on schema "{0}" for all scheduling columns.
Schema-level supplemental logging is enabled on all scheduling columns for the specified schema, as the result of the ADD SCHEMATRANDATA command. Informational only.
Action:
None
OGG-01981: Schema level supplemental logging is enabled on schema "{0}" for all columns.
Schema-level supplemental logging is enabled on all columns for the specified schema, as the result of the ADD SCHEMATRANDATA command. Informational only.
Action:
None
OGG-01982: Schema level supplemental logging is disabled on schema "{0}" for all columns.
Schema-level supplemental logging is disabled on all columns for the specified schema, as the result of the DELETE SCHEMATRANDATA command. Informational only.
Action:
None
OGG-01983: COMPRESSDELETES parameter is ignored since LOGALLSUPCOLS has been specified.
LOGALLSUPCOLS parameter takes precedence over the parameter COMPRESSDELETES.
Action:
None
OGG-01984: IGNOREUPDATEBEFORES parameter is ignored since LOGALLSUPCOLS has been specified.
LOGALLSUPCOLS parameter takes precedence over the parameter IGNOREUPDATEBEFORES.
Action:
None
OGG-01985: Legacy Teradata session character set {0} is not 100% compatible with {2}. Use the new Teradata session character set {1} when possible.
The legacy Teradata session character set may not support the characters that are defined in the corresponding Windows code page.
Action:
Use the new Teradata session character set.
OGG-01986: ODBC session character set of {0} does not match application code page of {1}.
The ODBC session character set is different from the application code page.
Action:
Change ODBC session character set to match the Windows code page.
OGG-01987: Could not retrieve trandata information for table "{0}" because of the following OCI error: {1}-{2}.
An OCI error prevented Oracle GoldenGate from getting information about table-level supplemental logging.
Action:
Fix the OCI error and retry the operation. If the OCI error cannot be resolved, contact Oracle Support.
OGG-01988: Could not find schematrandata function in source database: {0}.
There was a problem verifying the existence of the internal Oracle function used to retrieve information for schema supplemental logging.
Action:
Contact Oracle Support.
OGG-01989: Failed to lookup object ID for table {0}. {1}.
There was a problem finding the Oracle object id associated with the given table name. This may have been produced by an error while querying the database.
Action:
Try to resolve the problem based on the error description and/or contact Oracle Support.
OGG-01990: Cannot process table or schema supplemental logging operation because verification of database login failed. {0}.
A request for information about trandata or schematrandata 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-01991: Start Replicat from the command shell of the operating system without writing results into the report file when using the SHOWSYNTAX parameter.
The parameter file contains the SHOWSYNTAX parameter, but Replicat was started from GGSCI or from the command shell using reportfile. To use SHOWSYNTAX, Replicat must be started from the command shell of the operating system without writing the results into the report file.
Action:
Remove SHOWSYNTAX or start Replicat from the command shell of the operating system without using reportfile.
OGG-01992: SHOWSYNTAX cannot be used with BATCHSQL. BATCHSQL is disabled.
The parameter file contains the SHOWSYNTAX parameter, which is not compatible with the BATCHSQL parameter. BATCHSQL is disabled.
Action:
Remove SHOWSYNTAX to use BATCHSQL or specify the NOBATCHSQL parameter to use SHOWSYNTAX.
OGG-01993: Invalid maximum LOB size {0} specified for SHOWSYNTAX INCLUDELOB parameter.
An invalid number is specified for SHOWSYNTAX with the INCLUDELOB option.
Action:
Specify a valid maximum LOB size or remove SHOWSYNTAX with INCLUDELOB and allow the use of a default maximum LOB size. For valid values, see the Oracle GoldenGate reference documentation for SHOWSYNTAX.
OGG-01994: Replicat is stopping because Stop was specified at the SHOWSYNTAX prompt and the NOAPPLY option is specified.
Stop was specified at the SHOWSYNTAX prompt. Because NOAPPLY is specified for SHOWSYNTAX, Replicat abends instead of applying the SQL.
Action:
None
OGG-01995: Could not create a SQL statement for display, continuing replication. Error detail: {0}.
Check the error message for error detail.
Action:
Resolve the error that is displayed in the error detail, and then restart Replicat.
OGG-01996: The parameter {0} is no longer supported. Contact Oracle Support for assistance with a possible migration procedure.
The specified parameter option is no longer valid for the current release of Oracle GoldenGate.
Action:
Remove the option from the parameter file. Consult the current release notes and documentation for any newer options or enhanced functionality that is related to this feature, and for any required migration steps, or contact Oracle Support.
OGG-01997: Failure processing command {0}. Error response: {1} cannot be sent to client in streaming mode.
There was a failure when processing a command received from network. The error message cannot be sent back to the requester in streaming mode, except during checkpoint time.
Action:
Contact Oracle Support.
OGG-01998: Oracle GoldenGate received an external signal: {0,number,0}. Process shutting down gracefully.
A system signal to terminate a program was delivered to Oracle GoldenGate. The receiving process will shutdown gracefully.
Action:
None
OGG-01999: Unknown error sending data over TCP. Ensure that the intended receiver program is running; for example, server or manager. Also, ensure that an adequate number of ports is defined with the DYNAMICPORTLIST parameter if one is being used.
A TCP/IP error occurred. The process will retry based on the tcperrs file setting for retries.
Action:
Ensure that the remote process is still running and that the number of ports requested do not exceed the number of ports defined in DYNAMICPORTLIST parameter. Check for any firewalls that forbid the connection, such as blocking certain ports or processes. Make certain that the RMTHOST parameter is configured correctly. Contact your Network Administrator if you cannot resolve the problem to rule out any other network issues before contacting Oracle Support.
OGG-02000: Ignoring option {0} because it is incompatible with an integrated capture configuration.
The specified option is not valid in an integrated capture configuration.
Action:
Remove the incompatible option from the Extract parameter file.
OGG-02001: Ignoring integrated capture option {0} because it is incompatible with a classic capture configuration.
The specified integrated capture option is not valid in a classic capture configuration.
Action:
Remove the incompatible option from the Extract parameter file.
OGG-02003: Extract group {0} successfully registered with database at SCN {1}.
The specified Extract is now registered with the database to support integrated capture.
Action:
Use ADD EXTRACT with INTEGRATED TRANLOG or ALTER EXTRACT with UPGRADE TO INTEGRATED TRANLOG to add or upgrade an Extract by the same name.
OGG-02004: This database lacks the required PL/SQL packages to support integrated capture
The database does not contain the PL/SQL packages that support integrated capture.
Action:
Upgrade the Oracle database to a newer version.
OGG-02007: Error retrieving current Extract checkpoint value
Extract failed to obtain the current checkpoint from the checkpoint file.
Action:
Make certain the checkpoint file is available.
OGG-02020: Unable to initialize connection to MININGDB because of error {0}
Logon to the database specified by MININGDB was successful, but the connection could not be initialized because of the reported error.
Action:
Correct the error, and then restart the process.
OGG-02021: This database lacks the required libraries to support integrated capture
The database does not contain the libraries that support integrated capture.
Action:
Upgrade the Oracle database to a newer version which supports integrated capture or check if environment variables LD_LIBRARY_PATH/LIBPATH are pointing to the location containing the right version of oracle libraries. For instructions, see the Oracle GoldenGate installation and setup guide for Oracle database.
OGG-02022: Logmining server does not exist on this Oracle database.
An logmining server cannot be found on this database.
Action:
Make certain that you logged into the correct database from GGSCI.
OGG-02023: The attempt to stop logmining server failed
The logmining server could not be stopped because of the reported error.
Action:
Correct the error, and then retry the operation.
OGG-02024: An attempt to gather information about the logmining server configuration from the Oracle database failed.
The specified error occurred when Extract tried to get information about the logmining server from the database.
Action:
Correct the error and then retry the operation.
OGG-02025: Attempt to write rule checksum failed
The process failed to write a checksum for a filter rule.
Action:
Make certain storage space is available on disk.
OGG-02026: Attempt to set checkpoint retention to value {0} failed
Extract failed to set checkpoint retention for the logmining server.
Action:
Correct the error and then retry the operation.
OGG-02027: Attempt to start logmining server on Oracle database failed
The specified error occurred when Extract tried to start the logmining server.
Action:
Fix the error, and then retry the operation.
OGG-02028: Failed to attach to logmining server {0} error {1} - {2}.
The specified error occurred when Extract tried to attach to a logmining server.
Action:
Fix the error, and then retry the operation.
OGG-02029: Failed to obtain global database name from source database because of the reported error.
The specified error occurred when Extract tried to query the global database name.
Action:
Fix the error, and then retry the operation.
OGG-02030: Failed to set logmining server parameters back to default values
The specified error occurred when Extract tried to set logmining server parameters to the default values.
Action:
Fix the error, and then retry the operation.
OGG-02031: Missing value for TRANLOGOPTIONS INTEGRATEDPARAMS ({0})
A TRANLOGOPTIONS INTEGRATEDPARAMS parameter was specified without a value.
Action:
Specify a value. For help, see the Oracle GoldenGate reference documentation.
OGG-02032: Failed to set TRANLOGOPTIONS INTEGRATEDPARAMS ({0}, {1})
A TRANLOGOPTIONS INTEGRATEDPARAMS parameter or value is invalid.
Action:
Correct the parameter name or value. For help, see the Oracle GoldenGate reference documentation.
OGG-02033: Failed to clear filter rules
An error occurred when Extract tried to clear the filter rules for the logmining server.
Action:
Fix the error, and then retry the operation.
OGG-02036: Integrated capture successfully attached to logmining server {0}.
Extract successfully attached to logmining server.
Action:
None
OGG-02037: Failed to retrieve the name of a missing Oracle redo log.
An error occurred when Extract tried to retrieve the name of a missing Oracle redo log.
Action:
Fix the error, and then retry the operation.
OGG-02038: Failed to create a logmining server ruleset
An error occurred when Extract tried to create a logmining server ruleset.
Action:
Fix the error, and then retry the operation.
OGG-02039: Failed to set logmining server parameter {0} to value {1}.
An error occurred when Extract tried to set a logmining server parameter.
Action:
Fix the error, and then retry the operation.
OGG-02040: Extract USERID or TRANLOGOPTIONS MININGUSER {0} does not match the logmining server connect user {1}
The Extract USERID or TRANLOGOPTIONS MININGUSER parameter does not match the user that issued DBLOGIN or MININGDBLOGIN and REGISTER EXTRACT.
Action:
Make certain that the user shown in this message is the value given for USERID or TRANLOGOPTIONS MININGUSER.
OGG-02041: Failed to receive LCR record from logmining server.
An error occurred when Extract tried to get an LCR from logmining server.
Action:
Fix the error, and then retry the operation.
OGG-02042: OCI Error {0}
An unexpected OCI error was returned.
Action:
Fix the error, and then retry the operation.
OGG-02043: ID missing from SQLEXEC EXEC clause, id {0}. If an EXEC clause includes a schema name with the stored procedure name, ID is required due to bug 12989433. See the Oracle GoldenGate reference documentation for details.
Although ID is optional when SPNAME is present, a known issue documented in Bug 12989433 makes it required if SPNAME takes the form of schema.spname.
Action:
To work around this issue, add a logical name with the ID option to the SQLEXEC statement. For syntax, see the Oracle GoldenGate reference documentation.
OGG-02044: Grouped transaction was canceled, most likely to use an Oracle workspace to handle a transient primary-key duplicate. Check for additional messages.
On encountering an ORA 00001 (unique constraint) error, Replicat disables its grouped transaction and then tries to handle transient primary-key duplicates to resolve the error. These are duplicates that occur temporarily during the execution of a transaction, but are resolved by transaction commit time. To do this, Replicat opens an Oracle workspace. See Bug 13105877 for more details.
Action:
None
OGG-02045: Database does not have streams_pool_size initialization parameter configured.
The database initialization parameter streams_pool_size is not set correctly to support integrated capture.
Action:
Set database initialization parameter streams_pool_size. For sizing recommendations, see the Oracle GoldenGate reference documentation.
OGG-02046: Not enough database memory to service current number of Extracts in integrated capture mode: {0}.
Not enough database memory configured for proper functioning of Extract in integrated capture mode.
Action:
Increase database initialization parameter streams_pool_size. For sizing recommendations, see the Oracle GoldenGate reference documentation.
OGG-02047: Extract group {0} can not be positioned to SCN {1,number,0}.
Extract could not be positioned to the requested SCN.
Action:
Issue the command again with a valid SCN.
OGG-02049: Extract in integrated capture mode failed to create or allocate an environment or error handle for the OCI session
There was an error when Extract made an OCI call to create or allocate handles.
Action:
Restart Extract. If the problem persists, make sure there is enough system memory. If you cannot resolve the problem, contact Oracle Support.
OGG-02050: Not enough database memory to honor requested MAX_SGA_SIZE of {0}.
Not enough database memory configured for the MAX_SGA_SIZE specification in TRANLOGOPTIONS INTEGRATEDPARAMS.
Action:
Increase the database initialization parameter streams_pool_size or allocate less memory to Extract. For sizing recommendations, see the Oracle GoldenGate reference documentation.
OGG-02051: Not enough database memory to service Extract in integrated capture mode.
There is not enough database memory to support the recommended amount for Extract in integrated capture mode.
Action:
Increase the database initialization parameter streams_pool_size or allocate less memory to Extract by reducing the value of MAX_SGA_SIZE within the INTEGRATEDPARAMS option of the TRANLOGOPTIONS parameter. For sizing recommendations, see the Oracle GoldenGate reference documentation.
OGG-02052: This database lacks the required libraries to support integrated capture.
The database does not contain the libraries that support integrated capture.
Action:
Contact Oracle Support.
OGG-02053: Extract group {0} failed to archive the current redo log file on the source database because of the following SQL error: {1}. See Extract user privileges in the Oracle GoldenGate for Oracle Installation and Setup Guide.
A request for a redo log file archive required for integrated capture configured in downstream mode failed, probably because of insufficient privileges.
Action:
Manually archive the current redo log file on the source database with the command 'alter system archive log current'. Check the Oracle GoldenGate for Oracle documentation to make certain the Extract privileges are set correctly.
OGG-02054: Extract group {0} failed to switch the current redo log file on the source database because of the following SQL error: {1}. See Extract user privileges in the Oracle GoldenGate for Oracle Installation and Setup Guide.
A switch of the current redo log file required for integrated capture in downstream mode failed, probably due to insufficient Extract privileges.
Action:
Manually switch the current redo log file on the source database with the command 'alter system switch logfile'. Check the Oracle GoldenGate for Oracle documentation to make certain the Extract privileges are set correctly.
OGG-02055: ARCHIVELOG mode must be enabled on this Oracle database
Integrated capture is not supported for this Oracle database because ARCHIVELOG mode is not enabled on this database.
Action:
Enable ARCHIVELOG mode on this database, or do not use integrated capture.
OGG-02056: Oracle compatibility version {0} is not supported for integrated capture. Version {1} required.
Integrated capture can not be supported with the current Oracle compatible parameter setting for this database.
Action:
See the Oracle GoldenGate reference documentation for help with required Oracle database compatible parameter setting requirements.
OGG-02057: The Oracle source database is not configured properly to support integrated capture.
Integrated capture can not be used with this Oracle database because it is not configured properly.
Action:
Correct the specified error. Refer to the Oracle GoldenGate reference documentation for help with configuring the Oracle database.
OGG-02058: The Oracle source database is not configured properly to support integrated capture. The following configuration error must be fixed: {0}
Integrated capture can not be used with this Oracle database because it is not configured properly.
Action:
Correct the specified error. Refer to the Oracle GoldenGate reference documentation for help with configuring the Oracle database.
OGG-02059: The Oracle mining database is not configured properly to support integrated capture.
Integrated capture can not be used with this Oracle database because it is not configured properly.
Action:
Correct the specified error. Refer to the Oracle GoldenGate reference documentation for help with configuring the Oracle database.
OGG-02060: The Oracle mining database is not configured properly to support integrated capture. The following configuration error must be fixed: {0}
Integrated capture can not be used with this Oracle database because it is not configured properly.
Action:
Correct the specified error. Refer to the Oracle GoldenGate reference documentation for help with configuring the Oracle database.
OGG-02061: User {0} does not have the required privileges to use integrated capture.
A user associated with this operation does not have enough Oracle database privileges.
Action:
See the Oracle GoldenGate for Oracle Installation and Setup Guide for help with required user privileges.
OGG-02062: User {0} does not have the required privileges to use integrated capture
A user associated with this operation does not have enough Oracle database privileges.
Action:
See the Oracle GoldenGate for Oracle Installation and Setup Guide for help with required user privileges.
OGG-02063: Oracle database version {0} is not supported for integrated capture. Version {1} required.
Integrated capture is not supported with this version of the Oracle database.
Action:
See the Oracle GoldenGate for Oracle Installation and Setup Guide for help with supported Oracle database versions.
OGG-02064: Oracle compatibility version {0} has limited datatype support for integrated capture. Version {1} required for full support.
Integrated capture has limited datatype support with the current Oracle compatible parameter setting for this database.
Action:
See the Oracle GoldenGate reference documentation for help with required Oracle database compatible parameter setting requirements.
OGG-02065: Integrated capture dictionary initialization in progress. State of logmining server: {0}.
Integrated capture is waiting for the logmining server to start.
Action:
None
OGG-02066: Integrated capture cannot find the redo logs that contain the dictionary build. State of logmining server: {0}
The logmining server cannot scan the redo logs because the redo files that contain the dictionary build cannot be found.
Action:
Check the redo transport setting at the source database. For details, see the Oracle GoldenGate documentation for the Oracle database.
OGG-02067: This version of the Oracle library does not support the {0} option.
This version of Oracle library does not support the specified option.
Action:
Specify a valid option for the Oracle library. For help, see the Oracle GoldenGate reference documentation.
OGG-02068: Integrated capture successfully attached to logmining server {0} using OGGCapture API.
Extract successfully attached to logmining server using OGGCapture API.
Action:
None
OGG-02070: Invalid syntax for REGISTER command
Invalid syntax was specified for the REGISTER command.
Action:
For help with syntax, see the Oracle GoldenGate reference documentation or the GGSCI online help.
OGG-02071: Invalid syntax for UNREGISTER command
Invalid syntax was specified for the UNREGISTER command.
Action:
For help with syntax, see the Oracle GoldenGate reference documentation or the GGSCI online help.
OGG-02072: The container list for REGISTER EXTRACT cannot be empty
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. For help, see the GGSCI help or the Oracle GoldenGate reference documentation.
OGG-02073: WARNING: Parameter {0} is deprecated for Extract.
The specified parameter is deprecated for Extract.
Action:
Remove the deprecated parameter.
OGG-02074: This database lacks the required patch to support V2 LCRCAPTUREPROTOCOL.
The function that is used to enable V2 LCRCAPTUREPROTOCOL is missing from the database.
Action:
Refer to article 1411356.1 at the My Oracle Support website (https://support.oracle.com) to get the required Oracle patch.
OGG-02075: This database lacks the required PL/SQL package {0} to support switching LCRCAPTUREPROTOCOL.
The PL/SQL package that is used to switch the LCRCAPTUREPROTOCOL is missing from the database.
Action:
Refer to the post-install steps of the patch readme file to get the required PL/SQL package.
OGG-02076: The Extract parameter value {0} cannot contain a wildcard character.
The parameter value contains a wildcard character. Wildcards are not supported for this parameter.
Action:
Do not use wildcard characters for this parameter value.
OGG-02077: Extract encountered a read error in the asynchronous reader thread and is abending: {0}
An error occurred while reading the input data stream from the Logmining server.
Action:
Contact Oracle Support.
OGG-02078: Extract encountered a fatal error in a processing thread and is abending
An error was reported in one of the subsidiary threads in Extract.
Action:
Contact Oracle Support.
OGG-02079: Extract failed to login to the database as user {0} specified in the MININGUSER parameter because of error {1}
Logon to the database specified by MININGUSER failed because of the reported error.
Action:
Correct the error, and then restart Extract.
OGG-02080: This database lacks the required PL/SQL procedure {0} to support switching LCRCAPTUREPROTOCOL.
The PL/SQL procedure that is used to switch the LCRCAPTUREPROTOCOL is missing from the database.
Action:
Refer to the post-install steps of the patch readme file to get the required PL/SQL procedure.
OGG-02081: Detected duplicate TABLE/MAP entry for source table {0} and target table {1}. Using prior TABLE/MAP specification.
A duplicate target table mapping was detected. The source table is mapped to the target table twice or more.
Action:
Correct the duplicate target table mapping or specify the ALLOWDUPTARGETMAP parameter in the Replicat parameter file to allow duplicate target table mapping.
OGG-02082: Unable to use {0} as input for the EXCLUDETAG parameter. A valid hex value is expected.
An invalid value was used as input for the EXCLUDETAG parameter.
Action:
Specify a valid hex value as input for the EXCLUDETAG parameter, for example FF.
OGG-02083: DDLOPTIONS with ADDTRANDATA is no longer supported.
The parameter file contains the DDLOPTIONS parameter with the ADDTRANDATA option. This option is deprecated.
Action:
Make certain that the ADD SCHEMATRANDATA command was used for each schema in the Extract configuration.
OGG-02084: Oracle database version {0} is not supported for integrated capture upgrade/downgrade. Version {1} required.
Integrated capture upgrade/downgrade is not supported with this version of the Oracle database.
Action:
Upgrade the Oracle database to at least the specified database version.
OGG-02085: The logmining server failed to locate a dictionary at scn {0}.
The logmining server failed to locate a dictionary at this scn number.
Action:
Specify a valid scn number. For help, see the Oracle GoldenGate reference documentation. Contact Oracle Support.
OGG-02086: Integrated Dictionary will be used.
Extract is in integrated mode and is using the logmining server integrated dictionary.
Action:
None
OGG-02087: TRANLOGOPTIONS BUFSIZE is too small. It must be greater than {0} bytes.
The internal buffer that holds the results of each read of the transaction log is too small to hold the data returned.
Action:
Use the TRANLOGOPTIONS parameter with the BUFSIZE option to increase the buffer size.
OGG-02088: Drop container {0} failed: {1}
Failed to drop a container from xout server filter rule.
Action:
Contact Oracle Support.
OGG-02089: Source redo compatibility version is: {0}.
The compatibility of the database is set to {0}.
Action:
None
OGG-02090: An invisible column named "{0}" was encountered in table "{1}"."{2}". Invisible columns are not supported in Oracle GoldenGate.
Invisible columns in tables are not supported by Oracle GoldenGate.
Action:
Exclude the table from the Integrated Capture parameter file using the TABLEEXCLUDE parameter.
OGG-02091: Operation not supported because enable_goldengate_replication is not set to true
The enable_goldengate_replication system parameter is not set to true in the database. This parameter is required to support the attempted operation.
Action:
Set the enable_goldengate_replication system parameter to true by executing the following command: alter system set enable_goldengate_replication=true;
OGG-02092: Unexpected condition in function {0} at line {1,number,0}. Index {2} out of range. Number of elements: {3}.
An internal error occurred. Index specified is out of range.
Action:
Contact Oracle Support.
OGG-02093: Unexpected condition in function {0} at line {1,number,0}. Missing catalog name.
An internal error occurred. Missing catalog name.
Action:
Contact Oracle Support.
OGG-02094: Failed to set environment variable {0}.
The process could not set the environment variable that is specified with the SETENV parameter.
Action:
Allocate enough memory space for operating system environment or contact Oracle Support.
OGG-02095: Successfully set environment variable {0}.
The process set the environment variable that is specified with the SETENV parameter.
Action:
None
OGG-02096: {0}
This is a generic informational message that is used to report various different conditions with GGSCI commands.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-02097: LOB write size {0} is specified by the LOBWRITESIZE parameter, but the SKIPTEMPLOB parameter requires a minimum value of {1}. LOBWRITESIZE will be ignored.
The parameter file includes the LOBWRITESIZE parameter, but the specified value does not meet the minimum required size for the SKIPTEMPLOB parameter.
Action:
Remove the LOBWRITESIZE parameter or specify a value that is equal to, or greater than, the minimum required size of SKIPTEMPLOB.
OGG-02098: {0} is not supported for integrated capture with Oracle version {1}. Version {2} required.
The requested parameter for integrated capture can not be supported with the current Oracle version for this database.
Action:
See the Oracle GoldenGate reference documentation for help with required Oracle database version setting requirements.
OGG-02099: The DBLOGIN and MININGDBLOGIN commands are both connected to the same database (database id: {0}).
The MININGDBLOGIN command was used and connects to the same database as the DBLOGIN command.
Action:
If you are configuring Integrated Extract in downstream capture mode, the DBLOGIN command must connect to a different database than the MININGDBLOGIN command. Otherwise, the source and mining connections may connect to the same database.
OGG-02100: Unexpected condition in function {0} at line {1,number,0}. NULL session context is returned. User may not have sufficient privileges.
The Oracle GoldenGate process may not have the privileges that are required to perform the operation.
Action:
If this is an Oracle multitenant container database, make certain the Oracle GoldenGate user has sufficient privileges to perform the operation. Consult the Oracle GoldenGate documentation for Oracle Database. If the problem persists, contact Oracle Support.
OGG-02101: OCILobGetChunkSize() returned with invalid handle or zero length: status {0}, chunk_size {1}, column {2} query {3}.
The Oracle Call Interface returned an unexpected error to Replicat when it queried for the LOB chunk size.
Action:
Contact Oracle support.
OGG-02102: {0} option is not compatible with integrated capture.
The specified option is not valid in an integrated capture configuration.
Action:
Remove the incompatible option from the Extract parameter file.
OGG-02103: Invalid COLCHARSET clause {0}.
The COLCHARSET clause syntax is invalid.
Action:
Use valid syntax for the COLCHARSET clause.
OGG-02104: Missing character set in COLCHARSET clause {0}.
The character set parameter is missing from the COLCHARSET clause.
Action:
Specify a character set for the COLCHARSET clause.
OGG-02105: Invalid character set {1} in COLCHARSET clause {0}.
The character set parameter in the COLCHARSET clause is invalid.
Action:
Specify a valid character set for the COLCHARSET clause.
OGG-02106: Invalid column name {1} for table {2} in COLCHARSET clause {0}.
The column name parameter in the COLCHARSET clause is invalid.
Action:
Specify a valid column name for the COLCHARSET clause.
OGG-02107: COLCHARSET PASSTHRU is specified. Ignoring the source database character set for the table {0}, column {1}.
COLCHARSET PASSTHRU parameter is specified, which directs the process to pass the data as it exists in the trail record, without performing character set conversion for the specified columns.
Action:
None
OGG-02108: The source column character set {0} is specified with the COLCHARSET parameter for the table {1}, column {2}.
The COLCHARSET parameter is specified and assumed as the column character set.
Action:
None
OGG-02109: Invalid CHARSET clause {0}.
The CHARSET clause syntax is invalid.
Action:
Use valid syntax for the CHARSET clause.
OGG-02110: Missing character set in CHARSET clause {0}.
The character set parameter is missing from the CHARSET clause.
Action:
Specify a character set for the CHARSET clause.
OGG-02111: Invalid character set {1} in CHARSET clause {0}.
The character set parameter in the CHARSET clause is invalid.
Action:
Specify a valid character set for the CHARSET clause.
OGG-02112: CHARSET PASSTHRU is specified. Ignoring the source database character set for the table {0}, column {1}.
CHARSET PASSTHRU parameter is specified, which directs the process to pass the data as it exists in the trail record, without performing character set conversion for the character type columns of the specified table.
Action:
None
OGG-02113: The source table character set {0} is specified with the CHARSET parameter for the table {1}, column {2}.
The CHARSET parameter is specified and assumed as the character type column character set of the specified table.
Action:
None
OGG-02114: Ignoring COLCHARSET parameter for the table definition file format.
The COLCHARSET parameter is specified for the incompatible table definition file format.
Action:
Specify the table definition file format release 12.1 or later, or remove the COLCHARSET parameter from TABLE clause.
OGG-02115: Ignoring CHARSET parameter for the table definition file format.
The CHARSET parameter is specified for the incompatible table definition file format.
Action:
Specify the table definition file format release 12.1 or later, or remove the CHARSET parameter from TABLE clause.
OGG-02116: Both USEIPV4 and USEIPV6 have been set, but only one should be set. Ignoring USEIPV6 and using USEIPV4, which means only IPv4 will be used.
In the parameter file both USEIPV4 and USEIPV6 have been set, but only one of them should be set. The USEIPV6 parameter will be ignored and IPv4 will be used.
Action:
None
OGG-02117: Parsing error, unexpected token {2} at line {0} column {1}. Expecting token {3}.
Parser encountered unexpected token.
Action:
Contact Oracle Support.
OGG-02118: Parsing error, no viable alternative token {2} at line {0} column {1}.
Parser encountered no viable alternative token.
Action:
Contact Oracle Support.
OGG-02119: Parsing error, missing token {2} element at line {0} column {1}.
Parser encountered missing token element.
Action:
Contact Oracle Support.
OGG-02120: Parsing error, unquoted token {2} at line {0} column {1}.
Parser encountered unquoted token.
Action:
Contact Oracle Support.
OGG-02121: Parsing error, token {2} syntax error at line {0} column {1}.
Parser encountered syntax error.
Action:
Contact Oracle Support.
OGG-02122: Invalid object name {0}.
The object name is in invalid format.
Action:
Specify the object name in correct format.
OGG-02123: The CHARMAP clause does not contain the name of a character mapping file.
The parameter file contains a CHARMAP clause that does not contain the name of a character mapping file.
Action:
Specify a name for the character mapping file in the CHARMAP clause.
OGG-02124: The CHARMAP clause contains an unsupported parameter {0}.
The CHARMAP clause contains a parameter that is not supported.
Action:
Correct the syntax and then restart the process. For syntax help, see the Oracle GoldenGate reference documentation.
OGG-02125: Could not open the character mapping file {0} specified in the CHARMAP clause.
The character mapping file could not be opened.
Action:
Make certain that the name of the character mapping file is correct, that the file exists, and that Oracle GoldenGate has permission to open it in the operating system. Make corrections based on your findings.
OGG-02126: No valid parameter or command found in the parameter {0} in the character mapping file {1}.
An invalid command or parameter was found in the character mapping file.
Action:
Review and fix the specified parameter in the character mapping file.
OGG-02127: The parameter {0} is specified two or more times in the character mapping file {1}. Remove all but one instance of it.
The specified parameter is specified multiple times. Only one character set can be specified for this parameter.
Action:
Edit the parameter so that only one character set is specified.
OGG-02128: No character set is specified for the parameter {0} in the character mapping file {1}.
The character set is missing from the character set parameter of the character mapping file.
Action:
Specify a character set.
OGG-02129: No character set is specified for the {0} parameter in the character mapping file {1}.
The parameter that specifies the character set is missing from the character mapping file.
Action:
Specify a character set parameter. For help, see the Oracle GoldenGate reference documentation for CHARMAP.
OGG-02130: Invalid or unknown character set {0} for the character set parameter {1} in the character mapping file {2}.
An invalid or unknown character set is specified for the character set parameter in the character mapping file.
Action:
Specify a correct character set.
OGG-02131: The character mapping file {0} does not contain a character mapping definition and will be ignored.
A CHARMAP parameter exists in the parameter file, but the character mapping file does not contain a character mapping definition.
Action:
Remove the CHARMAP parameter or define a character mapping in the character mapping file.
OGG-02132: Invalid character mapping definition {0} in the character mapping file {1}.
The format of the character mapping definition is invalid.
Action:
Specify a valid character mapping definition. For help with syntax, see the Oracle GoldenGate reference documentation.
OGG-02133: Invalid code point range specified for the character mapping definition {0} in the character mapping file {1}.
The code point range in the character mapping specification is invalid. The start code point is larger than the end code point.
Action:
Specify a valid character code point range.
OGG-02134: The source code point does not match the target code point for the character mapping definition {0} in character mapping file {1}.
The numbers specified for the source and target code points do not match.
Action:
Specify a valid character code point range.
OGG-02135: Could not map the source character set {0} code point {1} to the target character set {2} code point {3} specified by the character mapping definition {4} in the character mapping file {5}.
The source or target code point of the character mapping definition is incompatible with the character set.
Action:
Specify the correct character mapping definition.
OGG-02136: The character mapping override is not supported for the source character set {0} and the target character set {1}.
The character mapping override is not available for the source or target character set.
Action:
Remove the CHARMAP clause from the parameter file.
OGG-02137: The data pump requires a DDL history table. None found.
A data pump that makes a database connection must have access to a DDL history table if DDL replication is enabled. No history table was found.
Action:
You can either convert the primary Extract to classic capture mode, also known as trigger-based capture, or you can add the PASSTHRU parameter to the parameter file of the data pump. For more information about PASSTHRU, see the Oracle GoldenGate reference documentation.
OGG-02138: Extract has encountered an unsupported LCR. This LCR will not be replicated. origop:{0} reason:{1} scn:{2} obj_id:{3} rba:{4} xid:{5,number,0}.{6,number,0}.{7,number,0}
Redo logs do not contain required data to support replication of this LCR.
Action:
Check that nologging keyword is not used in the query and/or force logging is enabled in the database.
OGG-02139: Extract has encountered an unsupported LCR: opcode:{0} reason:{1} scn:{2} rba:{3} thread_id:{4} object_id:{4} xid:{6,number,0}.{7,number,0}.{8,number,0}
Redo logs do not contain required data to support replication of this LCR.
Action:
Check that nologging keyword is not used in the query and/or force logging is enabled in the database and restart Extract.
OGG-02140: The ETOLDFORMAT trail is no longer supported.
The trail format is in Oracle GoldenGate version 7.0 or earlier version format and is no longer supported.
Action:
Upgrade the extract or use the newer trail file format.
OGG-02141: Unable to initialize fetch database connection specified by the FETCHUSERID parameter because of error {0}.
Logon to the fetch database specified by the FETCHUSERID parameter was successful, but the connection could not be initialized because of the reported error.
Action:
Correct the error, and then restart the process.
OGG-02143: Unable to obtain fetch database information specified by the FETCHUSERID parameter because of error {0}.
Logon to the fetch database specified by the FETCHUSERID parameter was successful, but the connection could not be used to obtain database information.
Action:
Correct the error, and then restart the process.
OGG-02144: The fetch database specified by the FETCHUSERID parameter must be to an Active Data Guard database.
The connection information supplied by the FETCHUSERID parameter does not point to an Active Data Guard database.
Action:
Remove the FETCHUSERID parameter or correct the login information.
OGG-02145: Failed to obtain global database name from the fetch database specified by the FETCHUSERID parameter because of the reported error.
The specified error occurred when Extract queried the global database name from the fetch database.
Action:
Fix the error, and then restart Extract.
OGG-02146: The fetch database specified by the FETCHUSERID parameter must be to an Active Data Guard of the source database.
The connection specified by the FETCHUSERID parameter is an Active Data Guard database, but not for the source database connection specified by the USERID parameter.
Action:
Correct the FETCHUSERID parameter connection options.
OGG-02147: Waiting for fetch database to process beyond SCN {1}. Current SCN is {0}.
Extract is waiting to fetch from the fetch database because it has not processed far enough.
Action:
None
OGG-02148: Extract failed to login to the fetch database as user {0} specified in the FETCHUSERID parameter because of error {1}.
Logon to the database specified by FETCHUSERID parameter failed because of the reported error.
Action:
Correct the error, and then restart Extract.
OGG-02149: Standby database has made no progress for more than {0} seconds.
Extract is abending because the Active Standby Database has not been applying redo changes from the source database and has reached its timeout threshold.
Action:
Correct the problem on the Active Data Guard standby database or increase the Extract timeout threshold by setting parameter DBOPTIONS FETCHTIMEOUT if using Integrated Capture or TRANLOGOPTIONS ADGTIMEOUT if using Classic Extract.
OGG-02150: Standby database has made no progress for more than {0} seconds because the Oracle Managed Redo Process(MRP) is not running on the Standby database.
Extract is abending because the Active Standby Database has not been applying redo changes from the source database and has reached its timeout threshold.
Action:
Start the Oracle Managed Redo Process (MRP) or increase the Extract timeout threshold by setting parameter DBOPTIONS FETCHTIMEOUT if using Integrated Capture or TRANLOGOPTIONS ADGTIMEOUT if using Classic Extract.
OGG-02151: Oracle Managed Redo Process(MRP) is not running on the Standby database.
Oracle Managed Redo Process(MRP) is not running.
Action:
Start the Oracle Managed Redo Process (MRP).
OGG-02152: Oracle Managed Redo Process(MRP) has been restarted on the Standby database.
Oracle Managed Redo Process(MRP) was down, but is now running.
Action:
None
OGG-02153: Fetch database has processed beyond required SCN {1}. Current SCN is {0}. Extract processing resumed.
Extract has finished waiting to fetch from the fetch database because it has processed far enough.
Action:
None
OGG-02154: Skipping conflict detection resolution for partial lob data.
A table has a partial lob data, which cannot be processed by CDR.
Action:
None
OGG-02155: Skipping conflict detection resolution for xmldiff data.
A table has an xmldiff_data, which cannot be processed by CDR.
Action:
None
OGG-02156: Unexpected data source function call without data source initialization.
An internal error occurred. The data source is not initialized properly.
Action:
Contact Oracle Support.
OGG-02157: Could not retrieve the logtrail next checkpoint.
Could not retrieve or find the logtrail checkpoint.
Action:
Ensure that the checkpoint file exists with accessible permissions. Contact Oracle Support.
OGG-02158: The mining database character set {0} is not compatible with the source database character set {1}
The mining database character set is not AL32UTF8 or a superset of the source database character set.
Action:
Connect to the mining database and alter its database character set to AL32UTF8.
OGG-02159: The mining database character set {0} is not compatible with the source database character set {1}
Extract registration completed successfully but the combination of mining and source database character sets is not recommended.
Action:
Connect to the mining database and alter its database character set to AL32UTF8.
OGG-02160: Could not find the definition of target table {0}. Assuming the table structure is exactly the same as the source table {1}.
The definition of the target table is not present in a target definitions file.
Action:
If the source and target table definitions are different, create a target definitions file with the DEFGEN utility, and specify the file with the TARGETDEFS parameter. For more information about specifying table definitions, see Administering Oracle GoldenGate for Windows and UNIX.
OGG-02161: Failed to retrieve the trail file begin checkpoint position.
Could not retrieve the trail file begin checkpoint position.
Action:
Ensure that the valid checkpoint and trail file are present on the system. Contact Oracle Support if both exist.
OGG-02162: Failed to retrieve the trail file next checkpoint position.
Could not retrieve the trail file next checkpoint position.
Action:
Ensure that the valid checkpoint and trail file are present on the system. Contact Oracle Support if both exist.
OGG-02163: Trail file {0} not found or no records beyond begin time {1}.
Trail file does not exist or no records beyond begin time.
Action:
Ensure that the valid checkpoint and trail file are present on the system. Contact Oracle support if both exist.
OGG-02164: Could not position in trail file {0}, status {1}.
The trail file or checkpoint file may be corrupted.
Action:
Ensure that the valid checkpoint and trail file are present on the system. Contact Oracle support if both exist.
OGG-02165: Failed to retrieving VAM two phase commit I/O checkpoint.
Could not retrieve the trail file begin checkpoint position.
Action:
Ensure that the valid checkpoint and trail file are present on the system. Contact Oracle support if both exist.
OGG-02166: Buffer overrun while reading extractor initial data load TCP/IP message, status {0}.
Network buffer overflow was detected while receiving initial data load TCP/IP message.
Action:
Check your network connection then contact Oracle Support.
OGG-02167: Invalid or unrecognized record format found when parsing incoming record data, status ({1}).
Invalid or unrecognized record format found during incoming record data parsing for initial data load apply.
Action:
Check your network connection then contact Oracle Support.
OGG-02168: Incompatible record format found when getting record header for initial data load, status ({1}).
Incompatible record format found while waiting for the record header for the initial data load apply.
Action:
Check your network connection then contact Oracle Support.
OGG-02169: Error resetting AES cipher (error {0,number,0}, {1})
An error occurred while attempting to reset the AES cipher while processing incoming initial load data.
Action:
None
OGG-02170: Error encrypting data record with AES cipher (error {0,number,0}, {1})
An error occurred while encrypting a data record with an AES cipher while processing incoming initial load data.
Action:
None
OGG-02171: Error reading LCR from data source. Status {0}, data source type {1}.
An error occurred while reading the Logical Change Record from the data source.
Action:
Check for any additional message detail then fix the issue described. Contact Oracle Support with the status code if no other additional detail was provided.
OGG-02173: The SHARDING parameter is not supported with this version of the Oracle Database.
The SHARDING parameter was specified in the Extract parameter file, but the Oracle Database does not support it.
Action:
Remove the SHARDING parameter from the Extract parameter file or connect to a version of the Oracle Database that supports it.
OGG-02174: The SHARDING parameter is only supported when using OGGCAPTURE API protocol.
The SHARDING parameter was specified in the Extract parameter file, but Extract is not configured to use the OGGCapture API.
Action:
Remove the SHARDING parameter from the Extract parameter file or configure Extract to use the OGGCapture API.
OGG-02175: The SHARDING parameter requires OGGCAPTURE API protocol version {0}. The Oracle Database supports up to version {1}.
The SHARDING parameter was specified in the Extract parameter file, but Extract is not connected to a database that supports it.
Action:
Remove the SHARDING parameter from the Extract parameter file or configure Extract to connect to a database that supports it.
OGG-02176: Trail file FORMAT RELEASE {0} or higher is required for SHARDING configuration.
The EXTFILE, EXTTRAIL, RMTFILE, or RMTTRAIL parameter contains the FORMAT option, but the given RELEASE value does not support the SHARDING configuration.
Action:
To support the SHARDING configuration, set FORMAT RELEASE to at least the version shown in the error message. Note that the reader process (data pump or Replicat) must be at least the specified version.
OGG-02177: The SHARDING parameter is not supported with this version of the Oracle mining database.
The SHARDING parameter was specified in the Extract parameter file, but the Oracle mining database does not support it.
Action:
Remove the SHARDING parameter from the Extract parameter file or connect to a version of the Oracle Database that supports it.
OGG-02178: The SHARDING parameter is not supported when Extract is configured with multiple trail files.
The SHARDING parameter as well as multiple trail files were specified in the Extract parameter file.
Action:
Remove the SHARDING parameter from the Extract parameter file or configure Extract to use only one trail file.
OGG-02180: Table {0} will use legacy trail format to support parameter {1}.
The indicated parameter provides uncompressed after image data by default so Extract will use legacy format to preserve that data.
Action:
If your configuration does not require the presence of uncompressed after image data, then you may specify UPDATERECORDFORMAT COMPACT to eliminate the uncompressed after image data and improve performance.
OGG-02181: Root container timezone information will be used for all containers.
Container specific timezone information can not be obtained. Specification of parameter USE_ROOT_CONTAINER_TIMEZONE has allowed Extract to proceed with the guarantee that all containers have the same timezone information as the root container.
Action:
Ensure all containers have the same timezone information as the root container.
OGG-02182: Container specific timezone can not be obtained. Mining database patch 20631846 or parameter TRANLOGOPTIONS USE_ROOT_CONTAINER_TIMEZONE is required.
Container specific timezone information can not be obtained because Extract is running in a sourceLess Extract configuration.
Action:
Install the required patch on the mining database. Alternatively, a fetch database can be configured. Alternatively, if all containers have the same timezone as the root container then parameter TRANLOGOPTIONS USE_ROOT_CONTAINER_TIMEZONE can be specified.
OGG-02183: Trail file {0} was partially transferred, retransmission is required.
An error occurred while waiting the trail file transmission completion. Only part of the trail file was transferred.
Action:
Check for network and file system problems; resolve any problems found. Contact Oracle Support if no problem was found.
OGG-02184: Invalid trail file name {0}.
Invalid trail file name found when opening the input trail file.
Action:
Check the input trail file configuration. The checkpoint file may be corrupted.
OGG-02185: Buffer overflow while reading trail file {0}. (RBA {1}).
Buffer overflow happened while reading the trail file. The trail file may be corrupted.
Action:
Ensure that the trail file is valid. Contact Oracle Support if the trail file is valid.
OGG-02186: Bad reposition RBA {0} where file header size is {1}.
Bad trail position was specified when repositioning trail file.
Action:
Ensure that the trail file and checkpoint files are valid. Contact Oracle Support if the trail files are valid.
OGG-02187: Could not reposition. Trail file {0} missing.
Could not find the trail file when attempting to reposition it.
Action:
Check the disk space and the network connection for problems. Contact Oracle Support if no problem was found.
OGG-02188: Unexpected LOB or DDL record or record fragment in {0}, rba {1}.
LOB or DDL record, or record fragment was found without base record in the trail file.
Action:
Wrong start RBA was specified or the trail file is corrupted.
OGG-02189: Unexpected RestartOK record in {0}, rba {1}.
RestartOK record was found in the middle of record.
Action:
Trail file may be corrupted. Check the trail file and contact Oracle Support.
OGG-02190: The data length of {0} exceeds the maximum allowed record length of {1}.
The length of the specified record exceeds the maximum length that is allowed for the trail file.
Action:
Contact Oracle Support.
OGG-02191: Incompatible record {0} in {1}, rba {2} when getting trail header.
Trail file format is not compatible with Oracle GoldenGate.
Action:
Trail file may be corrupted or the trail file version is no longer supported. Contact Oracle Support.
OGG-02192: Unrecognized response from trail file parsing {0} in {1}.
Trail file format is invalid.
Action:
Trail file may be corrupted. Contact Oracle Support.
OGG-02193: Invalid transaction ID {0} from trail file {1}, record RBA {2}.
The transaction ID read from the trail file has an invalid format.
Action:
The trail file may be corrupted. Contact Oracle Support.
OGG-02194: Error {0} ({1}) while reading trail file {2} (rba {3}).
Encounter unrecoverable file read error, which can be caused by file system or network issue.
Action:
Check additional message detail and try resolve the issue. Contact Oracle Support if you cannot resolve the issue.
OGG-02195: Error {0} ({1}) opening trail file {2} in EOF check.
Encountered trail file open error when checking logical EOF.
Action:
Check additional message detail and try resolve the issue. Contact Oracle Support if you cannot resolve the issue.
OGG-02196: Error {0} ({1}) positioning trail file {2} in EOF check.
Encountered trail file positioning (seek) error when checking logical EOF.
Action:
Check additional message detail and try resolve the issue. Contact Oracle Support if you cannot resolve the issue.
OGG-02197: Error {0} ({1}) reading trail file {2} in EOF check.
Encountered trail file reading error when checking logical EOF.
Action:
Check additional message detail and try resolve the issue. Contact Oracle Support if you cannot resolve the issue.
OGG-02198: Incompatible record (logical EOF) in trail file {0}, rba {1}.
Incompatible record found in the trail file after logical EOF marker.
Action:
Trail file may be corrupted. Check for file system and network issues. Contact Oracle Support if no issue was found.
OGG-02199: Incomplete record in trail file {0}, rba {1} at EOF.
Incomplete record found in the trail file at EOF.
Action:
Trail file may be corrupted. Check for file system and network issues. Contact Oracle Support if no issue was found.
OGG-02200: Unexpected condition in function {0} at line {1,number,0}. LCR parameter error.
An internal error occurred. LCR parameter error.
Action:
Contact Oracle Support.
OGG-02201: Unexpected condition in function {0} at line {1,number,0}. Duplicate LCR column {2}.
An internal error occurred. Duplicate LCR column.
Action:
Contact Oracle Support.
OGG-02202: Unexpected condition in function {0} at line {1,number,0}. Invalid flag {3} for LCR column {2}.
An internal error occurred. Invalid LCR column flag.
Action:
Contact Oracle Support.
OGG-02203: Unexpected condition in function {0} at line {1,number,0}. Invalid data chunk offset {3} for column {2}, previous chunk offset {4}, length {5}.
An internal error occurred. Invalid out of row data chunk offset.
Action:
Contact Oracle Support.
OGG-02204: Unexpected condition in function {0} at line {1,number,0}. LCR column {2} not found.
An internal error occurred. LCR column does not exist in the LCR column list.
Action:
Contact Oracle Support.
OGG-02205: Unexpected condition in function {0} at line {1,number,0}. Table metadata not found. Database ID: {2}, Object ID: {3}, Object Version: {4}, Map ID: {5}.
An internal error occurred. Table metadata not found for the object ID.
Action:
Contact Oracle Support.
OGG-02206: Unexpected condition in function {0} at line {1,number,0}. Could not allocate pool buffer.
An internal error occurred. Could not allocate pool buffer item.
Action:
Contact Oracle Support.
OGG-02207: Unexpected condition in function {0} at line {1,number, 0}. Invalid data state {2}.
An internal error occurred. Invalid data state found.
Action:
Contact Oracle Support.
OGG-02208: Operator {0} is not available for {1} data type.
Operator is not available for the data type.
Action:
Update parameter file to exclude the operator for the column or other data.
OGG-02209: Data type conversion from {0} data type to {1} data type is not supported.
Unsupported data type conversion is specified by mapping parameter.
Action:
Update the TABLE/MAP parameter and remove the mapping between the two data types.
OGG-02210: Comparison operation {1} is not supported between data type {0} and data type {2}.
Unsupported data type comparison is specified by mapping parameter.
Action:
Update the TABLE/MAP parameter and remove the comparison between the two data types.
OGG-02211: Operation {0} is not available for {1} data type.
Operation is not available for the data type.
Action:
Update parameter file to exclude the operation for the column or other data.
OGG-02212: Invalid data found for comparison of {0} data type.
Invalid data was found when attempting comparison of the data type.
Action:
Update parameter file to handle invalid data before the comparison may be using @COLTEST().
OGG-02213: Missing data found for comparison of {0} data type.
Data is missing and can not compare.
Action:
Update parameter file to handle missing data before the comparison may be using @COLTEST().
OGG-02214: Operation {0} is not supported for NULL {1} data type.
NULL data is not supported for the operation.
Action:
Update parameter file to handle NULL data before the operation may be using @COLTEST().
OGG-02215: Operation {0} is not supported for invalid {1} data type.
Invalid data is not supported for the operation.
Action:
Update parameter file to handle invalid data before the operation may be using @COLTEST().
OGG-02216: Operation {0} is not supported for missing {1} data type.
Missing data is not supported for the operation.
Action:
Update parameter file to handle missing data before the operation may be using @COLTEST().
OGG-02217: The character set {0} is not supported for data type conversion.
The character set is not supported for the data type conversion.
Action:
Contact Oracle Support.
OGG-02218: Numeric operation overflow occurred.
Number overflow occurred.
Action:
None
OGG-02219: Numeric operation underflow occurred.
Number underflow occurred.
Action:
None
OGG-02220: Invalid number format {0}.
Invalid number format found during conversion from numeric string to numeric value.
Action:
Provide correct numeric string if numeric string value is given by parameter.
OGG-02221: Invalid argument found. Module: {0}, Function {1}, Line {2}, Argnum {3}.
Invalid function argument.
Action:
Contact Oracle Support.
OGG-02222: Zero division error.
Zero division occurred.
Action:
None
OGG-02223: Floating point number value is not a number.
NaN detected.
Action:
None
OGG-02224: Floating point number value is infinite.
Infinite value or negative infinite value is detected.
Action:
None
OGG-02225: Data mapping buffer overflow from {1} to {0}.
Buffer overflow occurred while mapping the source data to the target data container.
Action:
None
OGG-02226: Data type conversion is not supported for NULL {0} data type.
Data type conversion is not supported for the NULL data.
Action:
Update parameter file to handle NULL data before the operation may be using @COLTEST().
OGG-02227: Data type conversion is not supported for invalid {0} data type.
Data type conversion is not supported for the invalid data.
Action:
Update parameter file to handle invalid data before the operation may be using @COLTEST().
OGG-02228: Conversion is not supported for missing {0} data type.
Data type conversion is not supported for the missing data.
Action:
Update parameter file to handle missing data before the operation may be using @COLTEST().
OGG-02229: Compression failed with error code {0}. Switch to non-compression mode for the data block.
Data compression failed. Typically, the compressed data size exceeds the original data size, which rarely happens when the data is encrypted.
Action:
None
OGG-02230: Decompression failed with error code {0}.
Data decompression failed. Possible data loss during network operation.
Action:
Check network connection. Contact Oracle Support if this happens often.
OGG-02231: Switching to next trail file {0} at {1}. with current RBA {2}.
Switch to the next trail file sequence.
Action:
None
OGG-02232: Switching to next trail file {0} at {1} due to EOF. with current RBA {2}.
Switch to the next trail file sequence due to current trail file reached to EOF.
Action:
None
OGG-02233: Switching to next trail file {0} at {1} due to logical EOF. with current RBA {2}.
Switch to the next trail file sequence because the current trail file reached to logical EOF.
Action:
None
OGG-02234: Invalid ATTRCHARSET clause {0}.
The ATTRCHARSET clause syntax is invalid.
Action:
Use valid syntax for the ATTRCHARSET clause.
OGG-02235: Missing character set in ATTRCHARSET clause {0}.
The character set parameter is missing from the ATTRCHARSET clause.
Action:
Specify a character set for the ATTRCHARSET clause.
OGG-02236: Invalid character set {1} in ATTRCHARSET clause {0}.
The character set parameter in the ATTRCHARSET clause is invalid.
Action:
Specify a valid character set for the ATTRCHARSET clause.
OGG-02237: Invalid UDT attribute name {1} for table {2} in ATTRCHARSET clause {0}.
The attribute name parameter in the ATTRCHARSET clause is invalid.
Action:
Specify a valid attribute name for the ATTRCHARSET clause.
OGG-02238: The source attribute character set {0} is specified with the ATTRCHARSET parameter for the table {1}, attribute {2}.
The ATTRCHARSET parameter is specified and assumed as the attribute character set.
Action:
None
OGG-02239: Upgrading to OGGCapture API.
Automatically upgrading to OGGCapture API.
Action:
None
OGG-02241: LCR column iterator is not supported for record or operation type {0}.
Internal error. LCR column iterator is not supported for internal record type or SQL operation type.
Action:
Contact Oracle Support.
OGG-02242: Invalid operation call was made on invalid LCR record.
Internal error. LCR column iterator cannot be created for invalid LCR.
Action:
Contact Oracle Support.
OGG-02243: Opened trail file {0} at {1}.
Trail file has been opened.
Action:
None
OGG-02244: Error reading LCR from Transaction Log data source. {0}
An error occurred while reading the Logical Change Record from the Transaction Log data source.
Action:
Check for message detail then fix the issue described. Contact Oracle Support with the status code if no other additional detail was provided.
OGG-02245: Repositioning was attempted as REPERROR action, but is not supported by RMTTASK.
Repositioning is not supported by initial load RMTTASK, because it does not use trail file.
Action:
Check whether the ALTER REPLICAT was meant for a change-synchronization Replicat instead of the task Replicat, or specify IGNORE/DISCARD for the REPERROR action.
OGG-02246: Source redo compatibility level {0} requires trail FORMAT {1} or higher.
Source database redo compatibility level can not be supported with the current trail file format.
Action:
Specify a trail file format supported for the source redo compatibility.
OGG-02247: Failed to read {0} file {1}: {2}.
Failed to read the table definition file specified by SOURCEDEFS or TARGETDEFS parameters.
Action:
Check for message detail then fix the issue described.
OGG-02248: Logmining server DDL filtering enabled.
The Extract configuration allows the Logmining server to filter unneeded DDLs.
Action:
None
OGG-02249: The Extract configuration does not support a physical standby as the source database.
The source database role is PHYSICAL STANDBY, which is not supported with the current Extract configuration.
Action:
Correct the source database connection information.
OGG-02250: Duplicate specification of parameter {0}.
The parameter is specified more than once.
Action:
Remove all but one specification of the parameter.
OGG-02251: Fetch requires a connection to the source or fetch database.
Extract attempted a fetch operation that requires a connection to the source or fetch database.
Action:
Specify a USERID parameter, FETCHUSERID parameter, or exclude the table.
OGG-02252: WILDCARDRESOLVE parameter must be set to DYNAMIC when NOUSERID parameter is specified.
The NOUSERID parameter is specified and the WILDCARDRESOLVE parameter is not set to DYNAMIC.
Action:
Set WILDCARDRESOLVE to DYNAMIC and restart the process.
OGG-02253: Integrated capture option {0} is incompatible with a classic capture configuration.
The specified integrated capture option is not valid in a classic capture configuration.
Action:
Remove the incompatible option from the Extract parameter file or upgrade to integrated capture.
OGG-02255: The MININGDBLOGIN is connected to the source database {0}.
The MININGDBLOGIN command was used and connects to the same database as the DBLOGIN command.
Action:
If you are configuring Integrated Extract in downstream capture mode, the DBLOGIN command must connect to a different database than the MININGDBLOGIN command. Otherwise, the source and mining connections may connect to the same database.
OGG-02256: Source redo initial compatibility version is: {0}.
The redo compatibility version of the source database at the time of the GGSCI register command.
Action:
None
OGG-02257: Using the parameter supplied redo compatibility version: {0}.
The redo compatibility version of the source database supplied by the Extract parameter file.
Action:
None
OGG-02258: The supplied value of _SOURCE_REDO_COMPATIBLE is invalid: {0}.
The value specified for the parameter _SOURCE_REDO_COMPATIBLE is invalid.
Action:
Specify a valid parameter value. Example: 11.2.0.4.
OGG-02259: Extract failed to gather source database metadata from the mining database because of the following error: {0}.
Extract received a failure while obtaining source database metadata information from the mining database.
Action:
Correct the error, and then restart the process.
OGG-02260: Incompatible or invalid RMTTASK format {0}.
Metadata format from extract is incompatible or invalid for the RMTTASK replicat version.
Action:
Check for extract RMTTASK parameter, remove or specify compatible FORMAT RELEASE option.
OGG-02261: Incompatible or invalid trail format {0}.
Metadata format from extract is incompatible or invalid for the replicat version.
Action:
Check for extract EXTTRAIL/RMTTRAIL parameter, remove or specify compatible FORMAT RELEASE option.
OGG-02264: Trail file is encrypted but no decryption key was found that is required for MAP (entry {0}).
The map entry is not passthru and requires trail file decryption in order to access to record data. The trail file header indicates that its content is encrypted, but the reading process could not find the key in the trail metadata. The Oracle GoldenGate source configuration might be using an ENCKEYS file to store an encryption key, but the reading process is not configured to use this method.
Action:
Make the map entry to passthru that has no TARGET, FILTER, WHERE, SQLEXEC, and COLMAP. Alternatively, make certain that the source and the target configuration for the trail encryption matches. If using ENCKEYS in source, target needs this method as well. Contact Oracle Support if assistance is needed.
OGG-02265: Missing source trail table definition after switching trail sequence.
Previous sequence trail had table definition, but the new trail file does not have table definition. Requires restarting the pump to reset the table mapping.
Action:
Restart extract pump.
OGG-02266: Table definition found in source trail after switching trail sequence.
Previous sequence trail had no table definition, but the new trail file has table definition. Requires restarting the pump to reset the table mapping.
Action:
Restart extract pump.
OGG-02267: Missing source trail decryption key after switching trail sequence.
Previous sequence trail had trail file decryption key, but the new trail file does not have the decryption key. Requires restarting the pump to reset the table mapping.
Action:
Restart extract pump.
OGG-02268: Decryption key found in source trail after switching trail sequence.
Previous sequence trail had no trail file decryption key, but the new trail file has the trail file decryption key. Requires restarting the pump to reset the table mapping.
Action:
Restart extract pump.
OGG-02269: Processing heartbeat table {0} in passthru mode.
Source trail file is encrypted, but no decryption key was found to update heartbeat table record.
Action:
None
OGG-02270: Timezone can not be obtained for container {0}. Either make the container available or install mining database patch 20631846 or set parameter TRANLOGOPTIONS USE_ROOT_CONTAINER_TIMEZONE.
Container specific timezone information can not be obtained because the container is unavailable.
Action:
Ensure the container is open or install required patch 20631846 on the mining database. Alternatively, If all containers have the same timezone as the root container then parameter TRANLOGOPTIONS USE_ROOT_CONTAINER_TIMEZONE can be specified.
OGG-02271: Decryption key is missing and record can not be filtered out.
Record is filtered out by parameter specification while pump/distribution require decryption key when any record is filtered out from encrypted trail for recovery.
Action:
Pass through all records including table, sequence, DDL, and procedure using add or modify TABLE, SEQUENCE, DDL or PROCEDURE parameter. Alternatively, you can the provide decryption key for Oracle GoldenGate to process records.
OGG-02272: Extract is using mining database timezone for processing source database redo: {0}.
Extract could not obtain source database timezone information. TIMESTAMP WITH LOCAL TIMEZONE column type will be processed with mining database timezone information.
Action:
No action necessary if source and mining databases have the same timezone or if no TIMESTAMP WITH LOCAL TIMEZONE redo will be captured and written to the trail file. Full support can be obtained by installing a RDBMS patch containing the fix for bug number 20631846.
OGG-02273: Extract is using mining database NLS_NCHAR_CHARACTERSET for processing source database redo: {0}.
Extract could not obtain source database NLS_NCHAR_CHARACTERSET information. NCHAR/NVARCHAR/NCLOB column types will be processed with mining databaseNLS_NCHAR_CHARACTERSET information.
Action:
No action necessary if source and mining databases have the same NLS_NCHAR_CHARACTERSET or if no NCHAR/NVARCHAR/NCLOB redo will be captured and written to the trail file. Full support can be obtained by installing a RDBMS patch containing the fix for bug number 20631846.
OGG-02274: TRANLOGOPTIONS INCLUDEEXTENDEDSESSIONINFO is not supported until database version 12.2
The parameter file contains the TRANLOGOPTIONS parameter with the INCLUDEEXTENDEDSESSIONINFO option. This option is not supported for database versions less than 12.2.
Action:
Do not expect any extended session information to appear in the trail file.
OGG-02275: The NOALLOWNULLABLEKEYS parameter is only supported when the Integrated Dictionary is in use.
The NOALLOWNULLABLEKEYS parameter is specified, but Extract is not configured to use the Integrated Dictionary.
Action:
Remove the NOALLOWNULLABLEKEYS parameter from the GLOBALS file or configure Extract to use the Integrated Dictionary.
OGG-02276: Invalid LCR encoder {0} is specified.
Invalid LCR encoder is specified.
Action:
Contact Oracle Support.
OGG-02277: Invalid XML encoding {0} specified.
Invalid XML encoding is specified for OUTPUTFORMAT XML option.
Action:
Specify correct XML encoding.
OGG-02278: Output format parameter {0} is a deprecated parameter.
The specified parameter is deprecated and is not be valid for later releases of Oracle GoldenGate.
Action:
Remove the parameter from the parameter file. Consult the current release notes and documentation for OUTPUTFORMAT parameter.
OGG-02279: Column {0} has missing or invalid date format data and unable to encode the column.
The date or timestamp column data is missing or has invalid date format data.
Action:
Check the column data of the source database.
OGG-02280: LCR operation type {0} encoding is not supported by LCR encoder {1}.
LCR operation type encoding is not supported by LCR encoder that is specified by OUTPUTFORMAT parameter.
Action:
None
OGG-02281: This database lacks the required PL/SQL procedure {0} to support integrated capture
The database does not contain the required PL/SQL procedures that support integrated capture.
Action:
Upgrade the Oracle database to a newer version.
OGG-02282: Invalid or unsupported TEXT format encoding {0} specified.
Invalid or unsupported text encoding is specified for OUTPUTFORMAT TEXT option.
Action:
Specify correct text encoding.
OGG-02283: Invalid SQL format encoding {0} specified.
Invalid SQL format encoding is specified for OUTPUTFORMAT SQL option.
Action:
Specify correct SQL format encoding.
OGG-02284: The source column data character set int the trail file format {0} may not be compatible with the ASSUMETARGETDEFS OVERRIDE parameter.
Trail file format release 12.3 and later can be optimized to capture source column data efficiently especially CLOB data by skipping character set conversion performed by previous version of extract. ASSUMETARGETDEFS OVERRIDE may be expecting converted character set data depending on source database and column data type.
Action:
Remove the ASSUMETARGETDEFS OVERRIDE Replicat parameter.
OGG-02285: Object type column {0} of table {1} is mapped twice or more to the target table {2} columns.
Duplicate object type column mapping is specified by TABLE/MAP clause COLMAP option.
Action:
Update TABLE/MAP COLMAP option to remove duplicate mapping of the object type column.
OGG-02286: Parameter {0} is incorrectly specified multiple times.
The parameter scope is global and second or more occurrences overwrite the previous option value or are ignored.
Action:
Specify the parameter only once.
OGG-02287: Parameter {0} option {1} is incorrectly specified multiple times.
The parameter option scope is global and second or more occurrences overwrite the previous option value or are ignored.
Action:
Specify the parameter option only once.
OGG-02288: Group name [{0}] in parameter file does not match with specified PROCESSID [{1}].
The Extract or Replicat group name does not match with PROCESSID option given by GGSCI or command line.
Action:
Correct the group name of parameter file.
OGG-02289: XML DOM documentation error: {0}
Caught XML DOM documentation exception.
Action:
Contact Oracle Support with error detail.
OGG-02290: XML DOM documentation internal error.
XML DOM document internal logic error.
Action:
Contact Oracle Support.
OGG-02291: XML DOM parsing error: {0}
XML parsing error.
Action:
Check the error detail and correct XML problem.
OGG-02292: Column data comparison is not supported on column {0} data type.
Column data comparison is attempted, but the column data type is not supported. This happens when compares column data with different data types such as compare TIMESTAMP column with number.
Action:
Check the column level filtering configuration and resolve the rule issue.
OGG-02293: Column {0} is NULL, unable to compare.
Column data comparison is attempted, but the column is NULL.
Action:
Check the column level filtering configuration and resolve the rule by excluding NULL column comparison.
OGG-02294: Unknown column data type and unable to compare the column data.
Column data comparison is attempted, but the column is not associated with metadata so is unable to fetch column data type.
Action:
Internal error, contact Oracle support.
OGG-02295: Invalid timestamp format {0}.
Invalid timestamp format found during conversion from timestamp string to numeric data and time value.
Action:
Provide correct timestamp string if timestamp string value is given by parameter.
OGG-02296: Timestamp value {0} out of range.
Timestamp value out of range found, such as month of 13, minute of 61.
Action:
Provide correct timestamp string if timestamp string value is given by parameter.
OGG-02297: This is an unsupported ALTER TABLE statement for table {0}.
The ALTER TABLE DDL statement is an unsupported command for replication.
Action:
Filter the DDL out of the Oracle GoldenGate configuration.
OGG-02298: Load library {0} failed with error {1}.
Loading OCI shared library failed.
Action:
Contact Oracle Support.
OGG-02299: Load library {0} failed with error: [{1}].
Loading OCI shared library failed.
Action:
Contact Oracle Support.
OGG-02300: Loading function {0} from library {1} failed with error {2}, a database patch is required.
A function required for XML UDT processing is missing from the OCI shared library. A database patch is required to resolve this issue.
Action:
Contact Oracle Support.
OGG-02301: Loading function {0} from library {1} failed with error: [{2}], a database patch is required.
A function required for XML UDT processing is missing from the OCI shared library. A database patch is required to resolve this issue.
Action:
Contact Oracle Support.
OGG-02302: Ignoring TABLE clause ATTRCHARSET option, incompatible with redo log based UDT and ANYDATA replication.
The ATTRCHARSET option to override the UDT attribute character set is incompatible with the redo log based UDT and the ANYDATA replication mode.
Action:
Remove the ATTRCHARSET option from your TABLE clause, or specify TRANLOGOPTIONS NOUSENATIVEOBJSUPPORT.
OGG-02303: MAPALLCOLUMNS option is specified but following source columns are not mapped: {0}.
MAPALLCOLUMNS option is specified but an unmapped source column was found.
Action:
Map all source columns to target columns or remove the MAPALLCOLUMNS option.
OGG-02304: Failed to create XDK XML context: {0}
Could not create Oracle XDK XML context. This is an internal error.
Action:
Contact Oracle Support with the error detail.
OGG-02305: XDK DOM error: {0} error code {1}.
Detected an Oracle XDK DOM error. This is an internal error.
Action:
Contact Oracle Support with the error detail.
OGG-02306: Encryption type name {0} is too long.
An invalid encryption type name is specified from the command line.
Action:
Specify a correct encryption type name. Contact Oracle Support if Extract or Replicat was launched from GGSCI.
OGG-02307: Encryption digest type name {0} is invalid or too long.
An invalid encryption digest type name is specified from the command line.
Action:
Specify a correct encryption digest type name. Contact Oracle Support if Extract or Replicat was launched from GGSCI.
OGG-02308: Encryption key name {0} is too long.
An invalid encryption key name is specified from the command line.
Action:
Specify a correct encryption key name. Contact Oracle Support if Extract or Replicat was launched from GGSCI.
OGG-02309: Encryption key name is missing.
Encryption key name is not specified.
Action:
Specify an encryption key name.
OGG-02310: Encryption type name is missing.
Encryption type name is not specified.
Action:
Specify an encryption type name.
OGG-02311: Encryption digest type name is missing.
Encryption digest type name is not specified.
Action:
Specify an encryption digest type name.
OGG-02312: Encryption IV value is missing.
Encryption IV value is not specified.
Action:
Specify an encryption IV value.
OGG-02313: Encryption IV value is invalid, too long or too short.
An invalid encryption IV value is specified.
Action:
Specify the correct encryption IV value.
OGG-02314: Remote host IP address is missing.
Remote host IP address is not specified.
Action:
Specify the remote host IP address.
OGG-02315: MGR TCP/IP port number is missing.
MGR TCP/IP port is not specified.
Action:
Specify the MGR TCP/IP port.
OGG-02316: MGR TCP/IP port number {0} is invalid.
An invalid MGR TCP/IP port is specified.
Action:
Specify a valid MGR TCP/IP port.
OGG-02317: Server TCP/IP port number is missing.
Server TCP/IP port is not specified.
Action:
Specify the server TCP/IP port.
OGG-02318: Server TCP/IP port number {0} is invalid.
An invalid server TCP/IP port is specified.
Action:
Specify a valid server TCP/IP port.
OGG-02319: Parameter incompatible with encryption digest type.
RMTHOST encryption digest type parameter is specified with MGRPORT, KEYNAME or an encryption type other than AES.
Action:
The encryption digest type is only valid for static Server Collector and AES encryption using Oracle Wallet. You must specify this with PORT, AES encryption type without KEYNAME.
OGG-02320: The EXCLUDEUSER option of the TRANLOGOPTIONS parameter cannot be specified when the NOUSERID parameter is specified.
The EXCLUDEUSER option of the TRANLOGOPTIONS parameter cannot be specified when the NOUSERID parameter is specified.
Action:
Specify a USERID parameter or remove the EXCLUDEUSER parameter or replace with the EXCLUDEUSERID parameter.
OGG-02321: The EXCLUDEUSER and EXCLUDEUSERID options of the TRANLOGOPTIONS parameter cannot be specified when capturing changes from a container database.
The EXCLUDEUSER or EXCLUDEUSERID option of the TRANLOGOPTIONS parameter was specified when attempting to capture changes from a container database.
Action:
Remove the EXCLUDEUSER or EXCLUDEUSERID option and consider using TRANLOGOPTIONS EXCLUDETAG for a bidirectional configuration.
OGG-02322: Invalid column mapping function or argument found in the {0} clause.
Invalid column mapping function or a function argument was found in the clause.
Action:
Check the clause and correct the syntax of the column mapping function or argument.
OGG-02323: Missing open parenthesis in the {0} clause.
The clause must begin with an open parenthesis.
Action:
Add an open parenthesis to the beginning of the clause.
OGG-02324: Expecting a target column name in the {0} clause.
Could not find the target column name in the clause.
Action:
Check the clause and specify the target column name for the left-hand side.
OGG-02325: Expecting an equal sign in the {0} clause.
Could not find equal (=) in the clause.
Action:
Check the clause and specify the equal sign between the target column and the source column, value, function or resource name.
OGG-02326: Mismatched data types in the {0} clause. (source {1} [{2}], target {3} [{4}])
The source and target data types are incompatible to the map in the clause.
Action:
Check the source and target data types. Convert the source data type using a function if necessary or choose different target column.
OGG-02327: Mismatched target column {0} and assigned value data types in the {0} clause
Source and target data types are incompatible to the map in the clause.
Action:
Check the source and target data types. Convert the source data type using a function if necessary or choose different target column.
OGG-02328: Failed to deserialize trail file metadata record header.
Encountered an invalid trail file metadata record header. Trail file may be corrupted if trail file is not encrypted. If trail file is encrypted, wrong wallet file is placed or wrong key name is specified.
Action:
If the trail file is encrypted, ensure that the wallet file and key name are properly configured. If trail file is not encrypted, check the trail file using logdump. Contact Oracle support if trail file is not corrupted and encryption configuration is correct.
OGG-02329: LCR has invalid length ({0} bytes) of key column record.
Encountered an invalid key column record length. Trail file may be corrupted if trail file is not encrypted. If trail file is encrypted, wrong wallet file is placed or wrong key name is specified.
Action:
If the trail file is encrypted, ensure that the wallet file and key name are properly configured. If trail file is not encrypted, check the trail file using logdump. Contact Oracle support if trail file is not corrupted and encryption configuration is correct.
OGG-02330: Requires to write the table definition to the trail file to exclude hidden column capture.
The EXCLUDEHIDDENCOLUMNS parameter with the NO_OBJECTDEF trail file option are specified together.
Action:
Remove the NO_OBJECTDEF option to exclude the hidden columns capture.
OGG-02336: TRANLOGOPTIONS EXCLUDEUSER / EXCLUDEUSERID requires catalog specification.
TRANLOGOPTIONS EXCLUDEUSER was specified for a multitenant container database configuration without specifying a preceding catalog name.
Action:
Specify the catalog for which the user belongs by specifying a catalog portion. Example: tranlogoptions excludeuser pdb1.username
OGG-02337: Could not find USER_ID corresponding to USERNAME '{0}'
The username specified by the EXCLUDEUSER parameter does not exist.
Action:
Specify a valid username for the EXCLUDEUSER parameter.
OGG-02338: TRANLOGOPTIONS EXCLUDEUSER / EXCLUDEUSERID invalid specification.
The value specified for TRANLOGOPTIONS EXCLUDEUSER is invalid.
Action:
Specify a username or userid in a valid format. For help, see the Oracle GoldenGate reference documentation.
OGG-02339: Integrated capture successfully attached to logmining server {0} using {1} second streaming duration.
Extract successfully attached to logmining server using streaming mode with the specified duration per database round trip.
Action:
None
OGG-02340: TRANLOGOPTIONS EXCLUDEUSER / EXCLUDEUSERID non-existing catalog '{0}'.
The catalog specified for TRANLOGOPTIONS EXCLUDEUSER does not exist.
Action:
Specify a valid catalog name for the EXCLUDEUSER parameter.
OGG-02400: Load library {0} failed with error {1}.
Loading CRS/XAG shared library failed.
Action:
Contact Oracle Support.
OGG-02401: CRS/XAG function call {0} failed with error status {1}.
CRS function call failed.
Action:
Contact Oracle Support.
OGG-02402: Transparent Integration with XAG is enabled but CRS/XAG is not available.
CRS/XAG is not available.
Action:
Contact Oracle Support.
OGG-02403: GGSCI failed to retrieve environment variable OGG_HOME.
The environment variable OGG_HOME is not set.
Action:
Contact Oracle Support.
OGG-02404: No Oracle GoldenGate instance is found in XAG resource list.
Oracle GoldenGate instance may not be registered with XAG.
Action:
Register the Oracle GoldenGate instance with XAG using XAG tool AGCTL and try again. If the problem persists, contact Oracle Support.
OGG-02405: No Oracle GoldenGate instance is registered with XAG.
Oracle GoldenGate instance is not registered with XAG.
Action:
Register the Oracle GoldenGate instance with XAG using XAG tool AGCTL and try again. If the problem persists, contact Oracle Support.
OGG-02406: Command {0} manager failed with error status {1}.
XAG failed to start/stop manager.
Action:
Contact Oracle Support.
OGG-02407: CRS/XAG status: {0}
CRS/XAG status message is captured in callback function.
Action:
None
OGG-02408: More than one GoldenGate instance was found.
More than one Oracle GoldenGate instance, with the same GoldenGate home directory, exists.
Action:
Remove the extraneous Oracle GoldenGate instances and try again. If the problem persists, contact Oracle Support.
OGG-02409: Oracle GoldenGate instance is already running on node {0}.
Oracle GoldenGate instance is already running.
Action:
None
OGG-02410: XAG Integration mode global setting of {0,choice,0#false│1#true} does not match command line setting of {1,choice,0#false│1#true}.
The setting for XAG integration established at installation time must match the command line arguments.
Action:
Review installation settings and command line arguments.
OGG-02411: Altering Extract to an SCN less than the current First SCN. Current First SCN is {0}. Altered Start SCN is {1}.
Altering Extract to an SCN less than the current first SCN.
Action:
None
OGG-02413: Extract {0} successfully registered to mine redo at SCN {1}.
The specified Extract is now registered to mine redo with integrated capture.
Action:
None
OGG-02414: Extract {0} successfully added containers with database to mine redo
The specified Extract successfully added a new container to mine redo with integrated capture.
Action:
None
OGG-02415: Cannot create Extract group {0} because no mining database login was provided. Use MININGDBLOGIN to establish a connection
Create Extract requires a connection to mining database.
Action:
None
OGG-02417: Could not retrieve Oracle REDO log I/O checkpoint.
Internal error.
Action:
Contact Oracle Support.
OGG-02419: Missing checkpoint file name.
Internal error. Missing checkpoint file name.
Action:
Contact Oracle Support.
OGG-02420: Invalid mode {0} specified for opening checkpoint file {1}.
Internal error. Invalid file open mode specified.
Action:
Contact Oracle Support.
OGG-02421: Could not create checkpoint file {0}, mode {1} (error {2}, {3}).
Could not create checkpoint file.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02422: Could not open checkpoint file {0} (error {1}, {2}).
Could not open the checkpoint file.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02423: Could not read from checkpoint file {0}, (error {1}, {2}).
Could not read from checkpoint file.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02424: Could not read full block ({0} bytes) from checkpoint file {1}.
Could not read the full checkpoint block. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02425: Could not read full record ({0} bytes) from checkpoint file {1}.
Could not read the full checkpoint record. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02426: Invalid header token ({0}) found in checkpoint file {1}.
Checkpoint file header is invalid. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02427: Could not construct backup file name for {0} (error {1}, {2}).
Failed to construct the backup file name.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02428: Could not to copy backup file {0}. (error {1}).
Failed to copy to backup file.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02429: Exceeded checkpoint buffer ({0}/{1}) in checkpoint file {2}.
Internal error.
Action:
Contact Oracle Support.
OGG-02430: Exceeded checkpoint record size ({0}/{1}) in checkpoint file {2}.
Internal error.
Action:
Contact Oracle Support.
OGG-02431: Invalid record header found in checkpoint file {0}.
Invalid checkpoint record header found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02432: Invalid configuration record found in checkpoint file {0}.
Invalid checkpoint configuration record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02433: Invalid alias record found in checkpoint file {0}.
Invalid checkpoint alias record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02434: Invalid status record found in checkpoint file {0}.
Invalid checkpoint status record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02435: Invalid Integrated Replicat record found in checkpoint file {0}.
Invalid Integrated Replicat record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02436: Invalid mining DB record found in checkpoint file {0}.
Invalid mining DB record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02437: Invalid logretention timestamp record found in checkpoint file {0}.
Invalid mining logretention timestamp record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02438: Unexpected input checkpoint found in checkpoint file {0}.
Unexpected input checkpoint record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02439: Unexpected output checkpoint found in checkpoint file {0}.
Unexpected output checkpoint record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02440: Invalid input subtoken ({0}) found in checkpoint file {1}.
Invalid input checkpoint subtoken found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02441: Invalid output subtoken ({0}) found in checkpoint file {1}.
Invalid output checkpoint subtoken found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02442: Invalid trailer record found in checkpoint file {0}.
Invalid checkpoint trailer record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02443: Invalid token ({0}) found in checkpoint file {1}.
Invalid checkpoint token found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02444: Missing trailer token ({0}) found in checkpoint file {1}.
Missing checkpoint trailer token. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02445: Checkpoint file {0} is not opened.
Internal error.
Action:
Contact Oracle Support.
OGG-02446: Checkpoint record smaller than block ({0}/{1}) in file {2}.
Checkpoint record is smaller than checkpoint block size. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02447: Could not rewrite to checkpoint file {0} ({1} of {2} bytes).
Internal error. Failed to rewrite checkpoint file.
Action:
Contact Oracle Support.
OGG-02448: Could not rewrite to checkpoint file {0} (error {1}, {2}).
Error rewriting checkpoint file.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02449: Could not write to checkpoint file {0} ({1} of {2} bytes).
Internal error. Failed to write checkpoint file.
Action:
Contact Oracle Support.
OGG-02450: Could not write to checkpoint file {0} (error {1}, {2}).
Error writing checkpoint file.
Action:
See the error detail to resolve the issue. If you cannot resolve this issue, contact Oracle Support.
OGG-02451: Could not retrieve Oracle REDO log begin checkpoint.
Internal error.
Action:
Contact Oracle Support.
OGG-02452: THREAD option is not supported for the checkpoint type {0}.
The THREAD option is only supported by Oracle Classic Extract mode.
Action:
Don't specify the THREAD option or change the Extract type to Oracle Classic Extract.
OGG-02453: Error opening locked checkpoint file {0}.
Extract or Replicat is running and the checkpoint file is locked.
Action:
Stop extract or replicat.
OGG-02454: Trail {0} not found in checkpoint file {1}.
The trail file is not associated with Extract or Replicat.
Action:
Associates the trail file with an Extract or Replicat, or specify correct trail file in parameter file.
OGG-02455: Invalid pointer retrieving GGS logtrail timestamp in {0}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02456: Invalid pointer retrieving initial load capture timestamp in {0}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02457: Invalid pointer retrieving Oracle redo log timestamp in {0}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02458: Invalid pointer retrieving DB2 redo log timestamp in {0}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02459: Invalid pointer retrieving sybase redo log timestamp in {0}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02460: Invalid pointer retrieving VAM timestamp in {0}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02461: Invalid type ({0}) retrieving timestamp in {1}.
Internal checkpoint error.
Action:
Contact Oracle Support.
OGG-02462: Received no metadata LCR with objID: {0}. objName: {1}. opType: {2} due to altering Extract to an SCN less than the current First SCN.
No metadata LCR was received because you attempted to alter Extract to an SCN less than the current first SCN.
Action:
None
OGG-02463: Trying to replace string {0} considered as an annotation with a comment {1} at position {2} and length {3} as a result of DDLSUBSTR operation.
When trying to replace existing text in a DDL with a comment using DDLSUBSTR when the existing text is treated as an annotation.
Action:
Abend
OGG-02464: Unlike for a heterogeneous Database, COMPRESSUPDATES is not supported for Oracle Database but generates trail records in non-unified trail format.
COMPRESSUPDATES trail format was specified in the Extract parameter file for Oracle database.
Action:
Unlike for a heterogeneous Database, COMPRESSUPDATES is not supported for Oracle Database but generates trail records in non-unified trail format.
OGG-02465: Invalid operation call was made for non-op checkpoint.
Internal error.
Action:
Contact Oracle Support.
OGG-02466: Invalid application name {0} is specified for the checkpoint operation.
Internal error.
Action:
Contact Oracle Support.
OGG-02467: Could not delete the checkpoint file {0}. Error code {1}, {2}.
Could not delete the checkpoint file. Refer to the error detail.
Action:
Review the error and resolve the issue.
OGG-02468: The checkpoint file {0} does not exist for the group {1}.
The checkpoint file for the group does not exist and may be removed.
Action:
Check to see if the Extract or Replicat group was properly created.
OGG-02471: Could not access checkpoint Oracle PDB list record.
Internal error.
Action:
Contact Oracle Support.
OGG-02472: Could not cleanup checkpoint for Replicat coordinator {0} (Error {1}, detail {2}).
Could not cleanup Replicat coordinator checkpoint.
Action:
Check the error detail and resolve the issue.
OGG-02473: Could not cleanup checkpoint for Replicat group {0} (Error {1}, detail {2}).
Could not cleanup the Replicat checkpoint.
Action:
Check the error detail and resolve the issue.
OGG-02474: Could not cleanup checkpoint for Extract group {0} (Error {1}, detail {2}).
Could not cleanup Extract checkpoint.
Action:
Check the error detail and resolve the issue.
OGG-02475: Could not set current output checkpoint for Extract {0} trail index {1}.
Could not set the current output checkpoint for Extract.
Action:
Internal error. Contact Oracle Support.
OGG-02476: Could not set current input checkpoint for Replicat {0} trail index {1}.
Could not set the current input checkpoint for Replicat.
Action:
Internal error. Contact Oracle Support.
OGG-02477: Could not set start input checkpoint for Replicat {0} trail index {1}.
Could not set the start input checkpoint for Replicat.
Action:
Internal error. Contact Oracle Support.
OGG-02478: No extract trails exist for Extract {0} to rollover.
ETROLLOVER command was requested, but no Extract trail is associated with the Extract.
Action:
Add the trail file to the Extract before issuing ETROLLOVER command.
OGG-02479: ETROLLOVER Failed for trail file {1} for the Extract {0} as the seqno exceeds limit.
Failed to rollover the trail file.
Action:
Internal error. Contact Oracle Support.
OGG-02480: DB2 checkpoint file is obsolete and no longer supported.
The existing checkpoint file was created by obsolete Oracle GoldenGate application and is no longer supported.
Action:
Reinstantiate the Extract with a newer Oracle GoldenGate.
OGG-02482: VAMTRAIL data source is no longer supported.
The VAMTRAIL data source is no longer supported.
Action:
None
OGG-02483: Invalid database checkpoint record found in checkpoint file {0}.
Invalid database checkpoint record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02484: Source LCR operation type {0} for the object '{1}' is not supported by this version of Replicat.
The source LCR operation type is generated by newer version of Extract and is not supported by the current Replicat version.
Action:
Upgrade the Replicat to same or newer version with the Extract that generated the source operation type.
OGG-02485: Source LCR operation type UPSERT is not supported by the trail format version or output format type.
The source LCR operation type UPSERT is not supported by older version of the trail file or the format such as XML, SQL, and TEXT output format.
Action:
Specify INSERTUPSERTS or remove NOINSERTUPSERTS option from the Extract parameter file to treat UPSERT operation as INSERT, or use trail file format release 19.1 or later.
OGG-02486: Source LCR operation type UPSERT is not supported by the UserExit module.
The source LCR operation type UPSERT is not supported by the version of UserExit module. At least callback version 6 is required.
Action:
Specify INSERTUPSERTS or remove NOINSERTUPSERTS option from the Extract/Replicat parameter file to treat UPSERT operation as INSERT, or upgrade the UserExit module.
OGG-02487: Source LCR operation type UPSERT is not supported by the Replicat version or by the Database.
The source LCR operation type UPSERT is not supported by the Replicat version or by the Replicat database type.
Action:
Specify INSERTUPSERTS or remove NOINSERTUPSERTS option from the Replicat parameter file to treat UPSERT operation as INSERT. OVERRIDEDUPS option is automatically turned on when the UPSERT record is applied as INSERT record.
OGG-02488: Checkpoint was not selected during initialization.
Internal error.
Action:
Contact Oracle Support.
OGG-02489: Data source is not initialized during startup.
Internal error.
Action:
Contact Oracle Support.
OGG-02490: Unsupported checkpoint type is specified. {0}
Unsupported checkpoint type is specified from the source Extract or Distribution Service.
Action:
If the source Extract or Distribution Service is newer version, upgrade the installed Oracle GoldenGate.
OGG-02491: Could not retrieve checkpoint table {0} for startup checkpoint position writing.
Checkpoint table may not exist in the target Database.
Action:
Check if the checkpoint table exist and accessible by the Replicat.
OGG-02492: Could not retrieve checkpoint position to update Database checkpoint position.
Checkpoint may be missing or corrupted.
Action:
Check if the checkpoint exists and accessible by Replicat.
OGG-02493: Inconsistent condition: no valid last update checkpoint position.
Internal error.
Action:
Contact Oracle Support.
OGG-02494: Failed to restart Replicat {0} in non-Integrated mode.
Failed to restart Integrated Replicat in non-Integrated Replicat mode.
Action:
Check and resolve the error detail and restart the Replicat.
OGG-02495: Failed to start Replicat thread {0}.
Failed to start Replicat thread.
Action:
Check and resolve the error detail and start the Replicat.
OGG-02496: Failed to start Replicat {0}, because it is already running.
Replicat thread may not be stopped properly previously.
Action:
Contact Oracle Support.
OGG-02497: Error retrieving GGS logtrail last checkpoint
The process could not open the last checkpoint.
Action:
Make certain that the process has read and write privileges on the checkpoint. Make certain that the file that caused the error is not corrupted. If the process cannot open the next checkpoint, contact Oracle Support.
OGG-02498: Invalid Oracle PDB checkpoint record found in checkpoint file {0}.
Invalid Oracle Database PDB checkpoint record found. The checkpoint file may be corrupted.
Action:
Check the file system. If you cannot resolve this issue, contact Oracle Support.
OGG-02499: Could not delete the process status file {0}. Error code {1}, {2}.
Could not delete the process status file. Refer to the error detail.
Action:
Review the error and resolve the issue.
OGG-02501: Unsupported data type code {0} encountered for table {1}, column {2} at Sequence {3}, RBA {4}
The specified data type is not supported in integrated or parallel apply modes.
Action:
Replicat will fall back to standard mode for transactions with unsupported data types. To retain integrated or parallel apply mode, remove the table from the Replicat configuration or change the incompatible data type to one that is supported.
OGG-02502: Invalid parameter specified for integrated apply mode
The integrated apply parameter specification is invalid.
Action:
Use valid syntax for the INTEGRATEDPARAMS parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-02503: Integrated apply mode not supported by this database version
Integrated apply was specified, but it is not supported by this database version.
Action:
Run Replicat in non-integrated apply mode, or upgrade the database to a version that supports integrated apply.
OGG-02504: Integrated apply '{0}' had a position length of {1} when {2} was expected
A mismatch in position length was detected.
Action:
Contact Oracle Support.
OGG-02505: Integrated apply mode does not support operation code {0}
An unsupported operation code was encountered while in integrated apply mode.
Action:
Contact Oracle Support.
OGG-02506: Cannot register Replicat group {0} because no database login was provided. Use DBLOGIN to establish a connection.
A REGISTER REPLICAT command was issued without first issuing a DBLOGIN command.
Action:
Issue the DBLOGIN command, and then issue REGISTER REPLICAT again.
OGG-02507: Cannot register Replicat group {0} because the specified Replicat is running. Stop Replicat and then retry the command.
A REGISTER REPLICAT command was issued without first stopping the process.
Action:
Stop the Replicat process, then issue a DBLOGIN command, and then the REGISTER REPLICAT command.
OGG-02508: Cannot register Replicat group {0} because of the following SQL error: {1}. See Replicat user privileges in the Oracle GoldenGate for Oracle Installation and Setup Guide.
A REGISTER REPLICAT command was issued and an error occurred either while querying the database or when calling a PL/SQL procedure.
Action:
Issue DBLOGIN with the appropriate privileges that are required for REGISTER REPLICAT. See the Oracle GoldenGate reference documentation.
OGG-02509: Replicat group {0} is already registered with the database.
A REGISTER REPLICAT command was issued for a Replicat group that is already registered with the database.
Action:
None
OGG-02510: Invalid syntax for REGISTER REPLICAT command. Expecting 'DATABASE', but received '{0}'
Invalid syntax was specified for the REGISTER REPLICAT command.
Action:
The correct syntax is REGISTER REPLICAT groupname DATABASE, where groupname is the name of the group. For additional information, see the Oracle GoldenGate reference documentation or the GGSCI online help.
OGG-02511: Invalid syntax for UNREGISTER REPLICAT command. Expecting 'DATABASE', but received '{0}'
Invalid syntax was specified for the UNREGISTER REPLICAT command.
Action:
The correct syntax is UNREGISTER REPLICAT groupname DATABASE, where groupname is the name of the group. For additional information, see the Oracle GoldenGate reference documentation or the GGSCI online help.
OGG-02512: Replicat group {0} is not registered with the database.
An UNREGISTER REPLICAT command was issued for a Replicat group that is not registered with the database.
Action:
None
OGG-02513: Replicat group {0} is not registered with the database.
An integrated Replicat was started before it was registered with the database.
Action:
Register the Replicat before starting it.
OGG-02514: The Replicat {0} is already in integrated mode.
The specified Replicat is already in integrated apply mode.
Action:
None
OGG-02515: The Replicat {0} is already in non-integrated mode.
The specified Replicat is already in non-integrated apply mode.
Action:
None
OGG-02516: Integrated replicat requires a trail source
Cannot switch to integrated apply mode because the specified Replicat does not have a trail to read.
Action:
None
OGG-02517: REGISTER REPLICAT {0} DATABASE must be performed before switching to integrated apply.
The REGISTER REPLICAT command was not issued.
Action:
Issue the command as REGISTER REPLICAT groupname DATABASE, where groupname is the name of the Replicat group. Then switch Replicat to integrated apply.
OGG-02518: Cannot convert data for for table {0} column {1} because the client character set {2} is not supported.
The client character set is not supported.
Action:
Set the client character set to a supported character set.
OGG-02519: Cannot convert data for table {0} column {1} because the server character set {2} is not supported.
The server character set is not supported.
Action:
Set the server character set to a supported character set.
OGG-02520: Character set conversion failure occurred for table {0} column {1} when converting from source character set {2} to target character set {3}. Error code: {4,number,0}
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-02521: Integrated Replicat flush of an OCI call failed
The OCI flush failed. This could be due to a problem communicating with the database.
Action:
Restart Replicat.
OGG-02522: Integrated Replicat failed to get the processed low watermark
Internal error getting the cached processed low watermark.
Action:
Restart Replicat.
OGG-02523: Integrated Replicat query of the error queue failed
A query of the error queue failed.
Action:
Check the connection to the database.
OGG-02524: Integrated Replicat APT-based filtering suppressed an already applied record at SEQNO {0,number,0}, RBA {1,number,0}, with transaction ID {2}.
APT-based filtering identified an already applied record and filtered it out.
Action:
None
OGG-02525: Integrated Replicat has been unregistered
The integrated Replicat has been switched to non-integrated mode.
Action:
None
OGG-02526: Parameter {0} is ignored by Integrated Replicat
The specified parameter is ignored by Integrated Replicat.
Action:
None
OGG-02527: Integrated Replicat does not populate a trace table
Integrated Replicat does not populate a trace table and ignores any TRACETABLE setting in the parameter file.
Action:
Use the NOTRACETABLE parameter in the Integrated Replicat parameter file.
OGG-02528: Replicat group {0} successfully registered with database as inbound server {1}
The specified Replicat is now registered with the database to support integrated apply.
Action:
None
OGG-02529: Successfully unregistered Replicat group {0} inbound server OGG${0} from database
A DELETE REPLICAT or UNREGISTER REPLICAT command was issued to unregister the Replicat group from the database.
Action:
None
OGG-02530: Integrated replicat successfully attached to inbound server {0}
Replicat successfully attached to the inbound server.
Action:
None
OGG-02531: Inbound server {0} error status ORA-{1}:{2}
The inbound server recorded an error code.
Action:
Resolve the error and restart Replicat.
OGG-02532: Checkpoint table required to switch to non-integrated mode
Replicat was switched to non-integrated mode. This mode requires the use of a checkpoint table.
Action:
Issue the ALTER REPLICAT command to associate a checkpoint table with this Replicat group. For help, see the online GGSCI help or the Oracle GoldenGate reference documentation.
OGG-02533: Cannot unregister Replicat group {0} from database because DBLOGIN command was not issued first. Issue DBLOGIN, then UNREGISTER REPLICAT {group_name} DATABASE.
A DELETE REPLICAT command was issued without first issuing a DBLOGIN command. Integrated Replicat requires DBLOGIN before deleting Replicat groups.
Action:
Manually unregister the replicat using the UNREGISTER REPLICAT DATABASE command.
OGG-02534: SHOWSYNTAX is not interactive in integrated mode. Refer to the Oracle RDBMS trace files for the SQL trace output.
SHOWSYNTAX enables SQL trace on the server.
Action:
None
OGG-02535: CSN filtering is always active for Integrated and Parallel modes.
_CSNFILTERING OFF was specified for an Integrated or Parallel Replicat.
Action:
Remove the _CSNFILTERING parameter.
OGG-02536: The inbound server ID for Replicat {0} does not match the registered ID.
The inbound server that was registered was dropped and recreated.
Action:
The Integrated Replicat may be in an inconsistent state. Delete the integrated Replicat with the DELETE REPLICAT command and then add it again with the ADD REPLICAT command. For help, see the online GGSCI help or the Oracle GoldenGate reference documentation.
OGG-02537: Cannot unregister Replicat group {0} because no database login was provided. Use DBLOGIN to establish a connection.
An UNREGISTER REPLICAT command was issued without first issuing a DBLOGIN command.
Action:
Issue the DBLOGIN command, and then issue UNREGISTER REPLICAT again.
OGG-02538: Cannot unregister Replicat group {0} because of the following SQL error: {1}. See Replicat user privileges in the Oracle GoldenGate for Oracle Installation and Setup Guide.
An UNREGISTER REPLICAT command was issued and an error occurred either while querying the database or when calling a PL/SQL procedure.
Action:
Issue DBLOGIN with the appropriate privileges that are required for UNREGISTER REPLICAT. See the Oracle GoldenGate reference documentation.
OGG-02539: Cannot unregister Replicat group {0} because the specified Replicat is running. Stop Replicat and then retry the command.
An UNREGISTER REPLICAT command was issued without first stopping the process.
Action:
Stop the Replicat process, then issue a DBLOGIN command, and then the UNREGISTER REPLICAT command.
OGG-02540: Parameter {0} is not supported by Integrated Replicat
The specified parameter is incompatible with Integrated Replicat.
Action:
Remove the parameter and restart Replicat.
OGG-02541: Replicat could not process some SQL errors before being dropped or unregistered. This may cause the data to be out of sync.
In integrated mode, Replicat can be shut down and dropped before it is finished processing any SQL errors that accumulated in the error queue. This warning indicates that Replicat was dropped before it could resolve the errors, and this may cause the source and target data to be out of synchronization.
Action:
Before adding a new Replicat (in any mode), verify the state of the data and perform an initial synchronization for any target objects that are out-of-sync.
OGG-02542: Cannot unregister Replicat group {0} because the specified Replicat is still in Integrated mode. Please DELETE REPLICAT or ALTER to NONINTEGRATED mode then retry the command.
An UNREGISTER REPLICAT command was issued without first switching Replicat to non-integrated mode or deleting the Replicat group.
Action:
Either issue the ALTER REPLICAT command with the NONINTEGRATED option to switch the Replicat in non-integrated mode, or issue the DELETE REPLICAT command to delete the Replicat group, which automatically unregisters Replicat from the database.
OGG-02543: The UNREGISTER REPLICAT {0} command was forced by a user
An UNREGISTER REPLICAT command was forcefully issued. This command bypassed the requirement to first issue the ALTER REPLICAT command with the NONINTEGRATED option or the DELETE REPLICAT command.
Action:
None
OGG-02544: Unhandled error ({0}) while processing the record at SEQNO {1,number,0}, RBA {2,number,0} in Integrated mode. REPLICAT will retry in Direct mode
An error occurred in the database server while processing a trail record in Integrated mode. Replicat will retry in direct mode.
Action:
You can use the REPERROR parameter and/or Conflict Detection Resolution rules to control how Replicat should handle a specific error or conflict.
OGG-02545: Parameter {0} is ignored by Integrated Replicat when parallelism is greater than 1
Parallelism is greater than 1 for this Integrated Replicat. The specified parameter is only valid when parallelism is 1 and is ignored otherwise.
Action:
None
OGG-02546: Database is open in restricted mode. Unable to attach to database inbound server {0}.
The database is open in restricted mode. Replicat cannot attach to an inbound server.
Action:
Disable the restricted session and then restart Replicat.
OGG-02547: Cannot alter Coordinated Replicat {0} to integrated mode
Cannot switch to integrated apply mode because the specified Replicat is a Coordinated Replicat.
Action:
None
OGG-02549: IR Direct Apply not supported for table {0}
Direct apply will not work for this table as configured.
Action:
Possible actions include using the dbms_apply_adm.set_dml_handler procedure to remove the DML handler by specifying the user_procedure as NULL. For more information, see the "SET_DML_HANDLER Procedure" documentation in the Oracle Database PL/SQL Packages and Types Reference, version 12.1 and removing ACDR configuration.
OGG-02550: ORACLE_HOME is not set to Oracle software directory.
Environment variable ORACLE_HOME is not set.
Action:
Check your Oracle database configuration and set the ORACLE_HOME variable if not set to the Oracle software directory.
OGG-02551: ORACLE_HOME is not set to Oracle software directory.
Environment variable ORACLE_HOME is not set, but may exist in your Windows registry.
Action:
If Oracle GoldenGate failed to operate properly, check your Oracle database configuration and set the ORACLE_HOME variable if not set to the Oracle software directory.
OGG-02552: The SOURCECHARSET PASSTHRU parameter does not support CHAR/VARCHAR/CLOB to/from NCHAR/NVARCHAR/NCLOB mappings.
The parameter file contains the SOURCECHARSET PASSTHRU parameter. This parameter specification does not allow CHAR/VARCHAR/CLOB to NCHAR/NVARCHAR/NCLOB mappings.
Action:
To map the specified data types, remove SOURCECHARSET PASSTHRU. To determine how to map between different data types, see the Oracle GoldenGate data integration documentation.
OGG-02553: DDL filtering {0} {1} is not supported by data pump.
The DDL filtering options is not supported by data pump and is ignored.
Action:
Remove the DDL filtering option from data pump parameter.
OGG-02554: Error loading shared library {0}: {1,number,0} {2}
The library can not be found or loaded.
Action:
Add the library path to the dynamic linker search path in the environment variables i.e. LD_LIBRARY_PATH.
OGG-02555: Heartbeat table {0} is not captured, because trail file format does not support the heartbeat table.
The heartbeat table was created and specified in the GLOBALS parameter file though Extract does not associate it with trail file format release 12.2 or greater, or the NO_OBJECTDEFS option is specified for the trail file.
Action:
Specify trail file format release 12.2 or greater and do not specify NO_OBJECTDEFS option, or delete the heartbeat table.
OGG-02556: Command table {0} is not captured, because trail file format does not support the command table.
The command table was created and specified in the GLOBALS parameter file though Extract does not associate it with trail file format release 12.2 or greater, or the NO_OBJECTDEFS option is specified for the trail file.
Action:
Specify trail file format release 12.2 or greater and do not specify NO_OBJECTDEFS option, or delete the heartbeat table.
OGG-02557: Heartbeat table {0} metadata is resolved and will write to trail file {1}.
Heartbeat table capture is enabled and the heartbeat table metadata is resolved so write it to the trail file.
Action:
None
OGG-02558: Command table {0} metadata is resolved and write to the trail file {1}.
Command table capture is enabled and the command table metadata is resolved so write it to the trail file.
Action:
None
OGG-02560: Formatting error on: table name {0}, rowid {1}, XID {2}.{3}.{4}, position (Seqno {5}, RBA {6}).
Internal LCR format error. Column data may be corrupted or data type may be not supported by Oracle GoldenGate.
Action:
Contact Oracle Support.
OGG-02561: Failed to retrieve item from COM transaction {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02562: Missing first LONG column chunk on table {0}.
Internal LCR format error. Missing first LONG column chunk.
Action:
Contact Oracle Support.
OGG-02563: Internal LCR column {0} formatting error: {1}.
Internal LCR column format error.
Action:
Contact Oracle Support.
OGG-02564: Invalid opcode {0} {1} to format.
Internal LCR column format error. Invalid operation code found.
Action:
Contact Oracle Support.
OGG-02565: Failed to add GGS token for LOB erase on column {0}.
Internal LCR column format error. Failed to add GGS token.
Action:
Contact Oracle Support.
OGG-02566: Failed to add GGS token for LOB trim on column {0}.
Internal LCR column format error. Failed to add GGS token.
Action:
Contact Oracle Support.
OGG-02567: Failed to add GGS token for XMLDIFF on column {0}.
Internal LCR column format error. Failed to add GGS token.
Action:
Contact Oracle Support.
OGG-02568: Failed to add GGS token for XMLUDT on column {0}.
Internal LCR column format error. Failed to add GGS token.
Action:
Contact Oracle Support.
OGG-02569: Failed to add GGS token for XMLUDT on column {0}.
Internal LCR column format error. Failed to add GGS token.
Action:
Contact Oracle Support.
OGG-02570: Invalid numeric data detected. Error converting numeric from Oracle to ASCII on column {0}, raw length {1}, raw data: {2}.
Internal LCR column format error. Failed to convert numeric data to ASCII format.
Action:
Contact Oracle Support.
OGG-02571: Error converting timestamp from Oracle to ASCII format for column {0}.
Internal LCR column format error. Failed to convert timestamp data to ASCII format.
Action:
Contact Oracle Support.
OGG-02572: Error converting day to second interval from Oracle to ASCII format for column {0}.
Internal LCR column format error. Failed to convert day to second interval data to ASCII format.
Action:
Contact Oracle Support.
OGG-02573: Error converting year to month interval from Oracle to ASCII format for column {0}.
Internal LCR column format error. Failed to convert year to month interval data to ASCII format.
Action:
Contact Oracle Support.
OGG-02574: Error converting rowid from Oracle to ASCII format for column {0}.
Internal LCR column format error. Failed to convert rowid data to ASCII format.
Action:
Contact Oracle Support.
OGG-02575: Failed to add lob piece to lobmem.
Internal error. Failed to add lob piece to lobmem.
Action:
Contact Oracle Support with detailed error information.
OGG-02576: Failed to find transaction in COM {0} for LONG_CHUNK with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02577: Failed to retrieve lob lcr from COM {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02578: Failed to find end piece of LONG_CHUNK in COM {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02579: Interleaved pieces of LONG_CHUNK in COM {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02580: Incomplete LONG_CHUNK in COM {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02581: No thread local storage.
Internal error.
Action:
Contact Oracle Support.
OGG-02582: No OCI handle for fetch in thread local storage.
Internal error.
Action:
Contact Oracle Support.
OGG-02583: No Active Data Guard standby database with source-less Extract.
No Active Data Guard standby database configured for source-less Extract.
Action:
Check Oracle GoldenGate and database configurations for valid Active Data Guard standby database.
OGG-02584: Query to Active Data Guard standby database to retrieve applied SCN failed.
Failed to query applied SCN from Active Data Guard standby database.
Action:
Check Oracle GoldenGate and database configurations for valid Active Data Guard standby database.
OGG-02585: Query to source db to retrieve applied SCN of the target standby database failed.
Failed to query applied SCN of the target standby database.
Action:
Check Oracle GoldenGate and database configurations for valid target standby database.
OGG-02586: No applied SCN information available on source database or Active Data Guard.
Applied SCN information no available on source database or Active Data Guard.
Action:
Check Oracle GoldenGate and database configurations for valid standby database.
OGG-02587: No longer able to retrieve applied SCN on source database or Active Data Guard.
Could not retrieve applied SCN on source database or Active Data Guard.
Action:
Check health of standby database.
OGG-02588: Failed to find PLSQL tran in COM {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02589: Failed to retrieve PLSQL large arg lcr from COM {0} with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02590: Failed to get LCR: {0}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02591: Error (%hd, string) adding LCR item to transaction {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02592: Failed to find transaction in COM {0} for LONG_CHUNK with xid {1}.
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02593: Extra items in COM (row_count={0}; chunk_count={1})
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02594: Found gap in LOB (expected offset={0}; LCR offset={1})
Internal LCR transfer error.
Action:
Contact Oracle Support.
OGG-02595: Missing decryption key, failed to process command table {0}.
Command table found in the AES encrypted file, but the decryption key is missing.
Action:
Configure the right decryption key at the default or specified location or configure the command table to pass-thru mode. Contact Oracle Support if assistance is needed.
OGG-02596: {0} cannot be specified with wildcard TABLE specification. {1}.
The TABLE clause option ALTID/PARTITIONOBJID, is specified with wildcard TABLE specification, which is not allowed.
Action:
Remove the ALTID/PARTITIONOBJID option or use a non-wildcard TABLE specification.
OGG-02597: A database login was not established before {0} clause.
The [SOURCEDB │ TARGETDB] USERID parameter to login to the database was not specified before the TABLE/MAP/PROCEDURE/SEQUENCE clause.
Action:
Add the [SOURCEDB] USERID parameter before the TABLE/MAP/PROCEDURE/SEQUENCE clause.
OGG-02598: File {0}, with trail format release {1}, is not compatible with the current software version's trail file format release {2}. Modify the capture parameter file to generate the appropriate format using the FORMAT RELEASE {2} option.
The trail version must be the equal to or greater than that of the reader process. LEVEL is an internal option that specifies a compatibility level that is independent of the Oracle GoldenGate software release, which only changes when new functionality is added to a release that affects the trail format. A value of 1 or greater specifies a format that is supported by Oracle GoldenGate release 10.0 and later. A value of 0 specifies a format that is supported by Oracle GoldenGate releases prior to 10.0.
Action:
Edit the parameter file to set the EXTFILE, EXTTRAIL, RMTFILE, or RMTTRAIL parameter FORMAT RELEASE option to write a trail version that is backward compatible with the reader process. Next, issue the issue the ALTER EXTRACT command with the ETROLLOVER option in GGSCI. The rollover creates a new trail file in the specified format. Start Extract to begin writing to the new trail file. For more information, see the Oracle GoldenGate reference documentation for the trail or file parameters.
OGG-02599: {0} cannot be specified in a MAP statement if DDL is enabled.
The MAP clause option ALTID/PARTITIONOBJID is specified when DDL is enabled. DDL capture and replication is not supported when using the clause ALTID/PARTITIONOBJID option.
Action:
Remove either the ALTID/PARTITIONOBJID option or the DDL parameter in the Capture parameter file.
OGG-02600: OCI error ({0,number,0}-{1}) when validating checkpoint table {2}, SQL: {3}. The table may not exist. To add it, use the ADD CHECKPOINTTABLE command.
Validation of the checkpoint table failed, possibly because the checkpoint table does not exist.
Action:
Add the checkpoint table by using the ADD CHECKPOINTTABLE command in GGSCI. For help, see the ggsci online help or the Oracle GoldenGate reference documentation.
OGG-02601: OCI error ({0,number,0}-{1}) when validating supplemental checkpoint table {2}, SQL: {3}. The table may not exist. If you upgraded from Oracle GoldenGate 11.2.1.0.0 or earlier, add this table with the UPGRADE CHECKPOINTTABLE command.
Validation of the supplemental checkpoint table failed, possibly because the table does not exist. This table is required for upgrades from version 11.2.1.0.0 or earlier.
Action:
Add the supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI after an upgrade from release 11.2.1.0.0 or earlier. For help, see the ggsci online help or the Oracle GoldenGate reference documentation.
OGG-02602: Unable to determine the supplemental checkpoint table name from the checkpoint Table.
The process could not determine the name of the supplemental checkpoint table.
Action:
Make sure you used valid connection credentials to log into the database with the DBLOGIN command in GGSCI.
OGG-02603: Checkpoint table {0} does not exist. Create this table with the ADD CHECKPOINTTABLE command.
The checkpoint table does not exist.
Action:
Use the ADD CHECKPOINTTABLE command in GGSCI to create the table. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02604: Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command if you have upgraded from release 11.2.1.0.0 or earlier.
Supplemental checkpoint table does not exist.
Action:
Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02605: The use of a checkpoint table is not supported for {0}.
Oracle GoldenGate does not support the use of a checkpoint table for the specified target database.
Action:
None
OGG-02606: Error retrieving information on checkpoint table: {0}. Database error: {1}. Create the checkpoint table with the ADD CHECKPOINTTABLE command.
Validation of the Checkpoint table failed, possibly because the checkpoint table was not created.
Action:
Create the checkpoint table with the ADD CHECKPOINTTABLE command in GGSCI. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02607: Error reading status from the checkpoint table: {0}. Database error: {1}.
An error occurred while reading status information from the checkpoint table.
Action:
Re-create the checkpoint table by using the ADD CHECKPOINTTABLE command in GGSCI. For more information, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02608: Error reading row from checkpoint table: {0}. Database error: {1}.
An error occurred while reading row data from the checkpoint table.
Action:
Re-create the checkpoint table by issuing the ADD CHECKPOINTTABLE command in GGSCI. For more information, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02609: Error allocating statement handle for validating checkpoint table operations. Checkpoint table: {0}. Database error: {1}.
A statement handle could not be allocated to access the checkpoint table.
Action:
Fix the database connectivity problem according to the error message.
OGG-02610: Error retrieving information on checkpoint table: {0}. SQL Statement: {1}. Database error: {2}.
Validation of the checkpoint table failed, possibly because the table was not created.
Action:
Create or re-create the table with the ADD CHECKPOINTTABLE command in GGSCI. For more information, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02611: Error ({0,number,0}-{1}) when validating supplemental checkpoint table {2}, SQL: {3}. The table may not exist. If you upgraded from Oracle GoldenGate 11.2.1.0.0 or earlier, add this table with the UPGRADE CHECKPOINTTABLE command.
Validation of the supplemental checkpoint table failed, possibly because the table does not exist. This table is required for upgrades from version 11.2.1.0.0 or earlier.
Action:
Add the supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI after an upgrade from release 11.2.1.0.0 or earlier. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02612: Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command if you have upgraded from release 12.1.1.0.0 or earlier.
The supplemental checkpoint table does not exist.
Action:
Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02613: Could not update DB checkpoint.
An error occurred in the database server while updating the database checkpoint table.
Action:
Resolve the database error and restart Replicat.
OGG-02614: Checkpoint table {0} already exists.
The checkpoint table already exists.
Action:
For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02615: Login to the database as user {0} failed because of error {1}
Logon to the database failed because of the reported error.
Action:
Correct the error, and then restart the process.
OGG-02616: Unable to initialize database connection because of error {0}
Logon to the database was successful, but the connection could not be initialized because of the reported error.
Action:
Correct the error, and then restart the process.
OGG-02617: A default source catalog name is not specified for the SOURCECATALOG parameter.
The SOURCECATALOG parameter does not contain a specification for the default source catalog name.
Action:
Specify the default source catalog name or remove the SOURCECATALOG parameter.
OGG-02618: The SOURCECATALOG parameter is not supported for this database version.
The parameter file contains the SOURCECATALOG parameter, which is not supported for the database that is configured as the Oracle GoldenGate datasource.
Action:
Remove the SOURCECATALOG parameter from the parameter file.
OGG-02619: Wildcards are not supported for the default source catalog name "{0}" in the SOURCECATALOG parameter.
The SOURCECATALOG parameter specifies a wildcarded name as the default source catalog name. Wildcards are not permitted for the default catalog name.
Action:
Specify the full default source catalog name or remove the SOURCECATALOG parameter.
OGG-02620: The source catalog name for table {0} cannot be wildcard because no catalog name or non-wildcard catalog name is specified for target table {1} in TABLE/MAP.
The source catalog in the TABLE/MAP parameter is wildcarded, but a catalog is not specified or non-wildcard catalog name is specified for the target table. In this case, the source wildcard cannot be resolved to the correct target catalog.
Action:
Edit the TABLE/MAP parameter to specify the full source catalog name, or keep the source wildcard but also specify a wildcard catalog name for the target table.
OGG-02621: A catalog name is specified for source table {1} in the TABLE/MAP parameter, but no schema name is specified for target table {0}.
In the TABLE/MAP specification, a catalog is specified for the source table, but a schema name is not specified for the target table.
Action:
Specify a schema name for the target table in the TABLE/MAP statement.
OGG-02622: A catalog name is specified for target table {1} in the TABLE/MAP parameter, but no schema name is specified for source table {0}.
In the TABLE/MAP specification, a catalog is specified for the target table, but a schema name is not specified for the source table.
Action:
Specify a schema name for the source table.
OGG-02623: Default source catalog name {0} will be used for source table name {1} mapping.
A default source catalog name is specified with the SOURCECATALOG parameter and will be used when mapping the specified source table.
Action:
None
OGG-02624: Default source catalog name {0} is specified but schema name is not specified for the source table name {1}.
A default source catalog name is specified with the SOURCECATALOG parameter, but schema name is not specified for the source table name.
Action:
Remove SOURCECATALOG parameter or specify schema name for the source table name.
OGG-02625: Invalid TARGET wildcard table name {0} is specified.
The wildcard resolution failed because question mark is specified for the target table name or more than one wildcard was specified for a name part.
Action:
Fix the syntax. A target wildcarded specification can have only one asterisk (like rpt.* or rpt.tab*). For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-02628: Missing exclusion specification for {0} parameter.
An exclusion object specification for TABLEEXCLUDE, SCHEMAEXCLUDE or CATALOGEXCLUDE is not specified.
Action:
Specify an object name in the parameter or remove the parameter.
OGG-02629: Wildcarded schema names are not supported for this database. Ignoring SCHEMAEXCLUDE parameter.
The SCHEMAEXCLUDE parameter is specified for a database that does not support wildcarded schema names.
Action:
Remove the SCHEMAEXCLUDE parameter.
OGG-02630: Catalog names are not supported for this database. Ignoring CATALOGEXCLUDE parameter.
The CATALOGEXCLUDE parameter is specified for a database that does not support wildcarded catalog names.
Action:
Remove the CATALOGEXCLUDE parameter.
OGG-02631: NORENAME option is not supported for CATALOGEXCLUDE parameter.
The CATALOGEXCLUDE parameter does not support a NORENAME option.
Action:
Remove the NORENAME option from the CATALOGEXCLUDE parameter.
OGG-02632: Invalid exclusion specification {0} is specified for {1} parameter.
The parameter contains an invalid exclusion specification.
Action:
Specify a valid exclusion specification. For help, see the Oracle GoldenGate reference documentation.
OGG-02633: Exclusion specification {0} for parameter {1} excludes all objects.
The parameter contains an invalid exclusion specification that excludes all objects from mapping.
Action:
Specify a valid exclusion specification. For help, see the Oracle GoldenGate reference documentation.
OGG-02634: Default source catalog name {0} will be used for table exclusion specification {1}.
A default source catalog name is specified with the SOURCECATALOG parameter and will be used for the table exclusion specification.
Action:
None
OGG-02635: The database does not support catalog names. Ignoring SOURCECATALOG parameter {0} specified for TABLE clause '{1}'.
The source database does not support catalog names.
Action:
Remove the SOURCECATALOG parameter.
OGG-02636: The TABLE specification '{0}' for the source table {1} does not include a catalog name. The database requires a catalog name.
The source table name in the TABLE statement does not include a catalog name. The database requires a catalog name.
Action:
Add a catalog name to the source table specification of the TABLE/MAP statement.
OGG-02637: The target catalog name for table {0} cannot have a wildcard because no catalog name is specified for source table {1} in the MAP parameter.
The target catalog in the MAP parameter is wildcarded, but a catalog is not specified for the source table. The source wildcard cannot be resolved to the correct target catalog.
Action:
Edit the MAP parameter to specify the full target catalog name, or keep the target wildcard and specify a catalog name for the target table.
OGG-02638: No schema is specified for table {0} in the MAP clause '{1}'. Schema is required.
The table specification does not include an explicit schema name.
Action:
To specify a schema other than the default login schema, edit the parameter file to specify the correct schema.
OGG-02639: The table specification {0} in the MAP parameter '{1}' includes a catalog name, but the database does not support catalog names.
The name of the target table in the TARGET clause of the MAP statement includes a catalog name, but the target database does not support catalog names.
Action:
Remove the catalog from the table specification.
OGG-02640: The format of trail file {0} does not support catalog names. Remove the catalog name from table specification {1} in TABLE clause '{2}'.
The trail file format specified by FORMAT RELEASE/LEVEL does not support catalog names, but the table specification includes a catalog name.
Action:
Remove the catalog name from the target table specification.
OGG-02641: Source table name {0} in TABLE clause '{1} ' has a wildcarded catalog name. The format of trail file {2} does not support catalog names.
The trail file format specified by FORMAT RELEASE/LEVEL does not support catalog names. The source table name is being written to the trail file without the catalog name.
Action:
Specify a non-wildcarded source catalog name, or specify a trail format that supports catalog names.
OGG-02642: Trail file {0} format does not support catalog names. The catalog name of the source table {1} specified in TABLE clause '{2}' will be removed.
The trail file format specified by FORMAT RELEASE/LEVEL does not support catalog names. The source table name is being written to the trail file without the catalog name.
Action:
None
OGG-02643: Wildcarded catalog name of source table specification {0} cannot be mapped to target table specification {1} that has no catalog name in TABLE clause '{2}'.
The source table name includes a wildcarded catalog name and is being mapped to a target table name that does not include a catalog name. This is not supported.
Action:
Specify a non-wildcarded source catalog name, or specify a target table name that includes a catalog name.
OGG-02644: The catalog portion of source table name {0} in TABLE clause '{1}' will not be written to trail file {2}.
The catalog portion of the source table name will be removed before being written to the trail, because the source table name is explicitly mapped to a target table name that does not include a catalog name.
Action:
None
OGG-02645: Source table name {0} that does not include a catalog name cannot be mapped in TABLE clause '{2} to target table {1} that has a wildcarded catalog name.
A source table specification that does not include a catalog name is mapped to a target table specification that includes a wildcarded catalog name.
Action:
Specify a non-wildcarded target catalog name, or include a catalog name in the source table specification.
OGG-02646: Source table specification {0} in TABLE clause {1} has no catalog name and will be mapped to target table {2} specification that has a catalog name.
A source table specification that does not include a catalog name is mapped to a target table specification that includes a catalog name.
Action:
None
OGG-02647: Cannot specify table clause '{0}' for trail file {1} because the trail specifies a different target table name format.
A table name with a catalog name and one without a catalog name cannot be output to the same trail file. A different target table name format is specified by the table clause for the specified trail file.
Action:
Remove the catalog name from the TABLE clause or add a catalog name to the TABLE clause, or output the table to a different trail file.
OGG-02648: Table name {0} specified in TABLE/MAP clause '{1}' contains a wildcarded schema or catalog. The database does not support wildcards for those objects.
Wildcarded schemas or catalogs are not supported by this database.
Action:
See the rules for schema and catalog wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.
OGG-02649: Source wildcard specification {0} includes a catalog name, but the source table name {1} does not include a catalog name.
A catalog name is specified for the source wildcard specification, but the source table name does not include a catalog name.
Action:
Remove the catalog name from the source wildcard specification.
OGG-02650: Source wildcard specification {0} does not include a catalog name, but the source table name {1} includes a catalog name.
A catalog name is not specified for the source wildcard specification, but the source table name includes a catalog name.
Action:
Add a catalog name to the source wildcard specification.
OGG-02651: Parameter {0} syntax error: {1}
The syntax of the specified parameter is incorrect.
Action:
Check for spelling errors, or see the Oracle GoldenGate reference documentation for the correct syntax.
OGG-02652: Missing interval value.
The interval value was not specified.
Action:
Specify the interval value.
OGG-02653: Invalid interval value {0} was specified.
An invalid interval value was specified.
Action:
Specify the correct interval value.
OGG-02654: Missing time qualifier in interval specification.
The time/interval value was specified without a time qualifier such as DAYS, HOURS, MINUTES or SECONDS.
Action:
Specify the time qualifier.
OGG-02655: Invalid time qualifier {0} was specified. Time qualifier must be either DAYS, HOURS, MINUTES or SECONDS.
An invalid time qualifier was specified for the time/interval value.
Action:
Specify a valid time qualifier.
OGG-02656: The specified interval value {0} is out of range. The value must be between {1} and {2}.
The specified interval value is out of range.
Action:
Specify a valid interval value.
OGG-02657: No schema is specified for table exclusion specification '{0}'.
A schema was not explicitly specified for the TABLEEXCLUDE parameter and there was no default schema.
Action:
Edit the parameter file to specify the correct schema, or use the default schema by adding DBLOGIN to the parameter file.
OGG-02658: No schema is specified for table exclusion specification '{0}'. Using default schema {1}.
A schema was not explicitly specified for the TABLEEXCLUDE parameter. The process is using the default login schema.
Action:
To use a schema other than the default login schema, edit the parameter file to specify the correct schema.
OGG-02659: Could not retrieve logon catalog name
A database error may be preventing the process from retrieving the logon catalog name.
Action:
Contact Oracle Support.
OGG-02660: Retrieving table definition for table specification {0} is prohibited when logged on to database {1}.
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-02661: Replicat is not allowed to log on to the root level database.
Replicat logged into the root level database.
Action:
Modify the Replicat parameter file so that Replicat logs on to a pluggable database, not the root database.
OGG-02662: Exclusion specification {0} specified for {1} parameter has a catalog name, but catalog names are not supported by this database.
The parameter contains an exclusion specification that specifies a catalog name, but the database does not support catalogs.
Action:
Remove the catalog name from the exclusion specification.
OGG-02663: Missing catalog name in exclusion specification {0} specified for {1} parameter.
The catalog name is missing from the exclusion specification.
Action:
Specify a catalog name in the exclusion specification, or specify a default catalog name with the SOURCECATALOG parameter.
OGG-02664: Exclusion specification {0} specified for {1} parameter has a wildcarded schema, but the wildcarded schema name is not supported for the database.
Wildcarded schemas are not supported for this database.
Action:
See the rules for schema wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.
OGG-02665: Login catalog name {0} will be used for target table name {1} mapping.
A catalog name is not specified for the target table for the database. Login catalog will be used when mapping the specified target table.
Action:
None
OGG-02666: Could not retrieve default catalog name
A database error may be preventing the process from retrieving the default catalog name.
Action:
Contact Oracle Support.
OGG-02667: Default catalog name {0} will be used for table exclusion specification {1}.
A default catalog name will be used for the table exclusion specification.
Action:
None
OGG-02668: Default catalog name {0} will be used for source table name {1} mapping.
A default catalog name will be used when mapping the specified source table.
Action:
None
OGG-02669: Default catalog name {0} will be used for target table name {1} mapping.
A default catalog name will be used when mapping the specified target table.
Action:
None
OGG-02670: Default source catalog name {0} will be used for schema exclusion specification {1}.
A default source catalog name is specified with the SOURCECATALOG parameter and will be used for the schema exclusion specification.
Action:
None
OGG-02671: A database login was not established to retrieve a table definition.
The [SOURCEDB │ TARGETDB] USERID parameter to login to the database was not specified before the TABLE parameter.
Action:
Add the [SOURCEDB] USERID parameter before the TABLE parameter.
OGG-02672: No DB login established to retrieve a definition for table {0}
The [SOURCEDB │ TARGETDB] USERID parameter must be specified in order to retrieve a definition from the database.
Action:
Add the [SOURCEDB │ TARGETDB] USERID parameter before the TABLE or MAP parameter.
OGG-02678: Unrecognized GLOBALS parameter {0} is ignored. Parameter could be misspelled or unsupported.
The parameter is either specified incorrectly or is not valid for this version of Oracle GoldenGate.
Action:
Check the GLOBALS parameter file for the correct syntax, spelling, and any required terminators such as the semi-colon. Also make certain the parameter is supported for this version of Oracle GoldenGate. To do both of those things, check the reference documentation for your version of Oracle GoldenGate.
OGG-02679: The Replicat process logged on to database {0} and can only apply to that database.
Replicat can only apply to the database it logged on to, and cannot apply to any other database. Informational only.
Action:
None
OGG-02680: ENABLECATALOGNAMES parameter is specified, enabling catalog name support.
ENABLECATALOGNAMES parameter is specified in GLOBALS and the catalog name is supported.
Action:
None
OGG-02681: The catalog name is missing. Fully qualified name for table {0} is required for root database
The process logged on to the root level database, but the table name was specified without a catalog name. A three-part name is required to log onto the root database.
Action:
Add a catalog name to the table specification.
OGG-02682: Cannot execute a command to catalog {0} while logged in to catalog {1}
A process can only execute a command to its login catalog.
Action:
Specify a catalog that is the same as the login catalog or log in to the root level database.
OGG-02683: Invalid schema specification "{0}" for ADD/INFO/DELETE SCHEMATRANDATA.
An invalid schema was specified for the ADD/INFO/DELETE SCHEMATRANDATA command.
Action:
Specify a valid schema.
OGG-02684: Table definition output {0} {1} is specified but the output format level {2} is already specified.
Table definition file output format is specified twice or more in different output format using FORMAT LEVEL/RELEASE parameter.
Action:
Specify table definition file output format only once.
OGG-02685: Ignoring SOURCECATALOG parameter {0} specified for TABLE parameter '{1}' which contains a catalog specification.
The TABLE clause already specifies a catalog name for the specified source table.
Action:
Remove the SOURCECATALOG parameter or remove the catalog name from the source table name.
OGG-02686: Default catalog name {0} will be used for schema exclusion specification {1}.
A default catalog name will be used for the schema exclusion specification.
Action:
None
OGG-02687: Invalid catalog name "{0}" is specified for SOURCECATALOG parameter.
The catalog name specified for the SOURCECATALOG parameter is invalid.
Action:
Specify the correct catalog name.
OGG-02688: Table definition output character set {0} is specified, but the output character set {1} is already specified.
Multiple CHARSET parameters exist and specify different values for the output character set of the definitions file.
Action:
Specify only one CHARSET definition for the character set of the DEFGEN output file.
OGG-02689: The NOCATALOG parameter is specified after the TABLE parameter.
NOCATALOG parameter is specified after TABLE parameter.
Action:
Specify the NOCATALOG parameter before any TABLE parameters.
OGG-02690: Wildcard catalog name {0} is incompatible with the NOCATALOG parameter.
A catalog name is specified in a TABLE parameter, but the NOCATALOG parameter is specified for that TABLE parameter.
Action:
Remove the NOCATALOG parameter or remove the catalog specification from the TABLE specification.
OGG-02691: Cannot specify TABLE parameters with different catalog names when Defgen parameters NOCATALOG or FORMAT LEVEL 3 or less is specified.
The NOCATALOG parameter or FORMAT LEVEL 3 or less is being used in the Defgen parameter file to prevent the output of catalog names to the definitions file, but the TABLE parameters specify different catalog names.
Action:
Remove the NOCATALOG or FORMAT LEVEL parameter to allow three-part names from different catalogs to be written to the definitions file. To keep those parameters, specify TABLE parameters that all have the same catalog name.
OGG-02692: Cannot specify format level of {0} for definitions file {1} that already has a format level of {2}.
The output mode of DEFGEN is set to APPEND mode, and the specified format level is different from the current format level of the existing definitions file. In APPEND mode, the existing file and new output must be the same format level.
Action:
Remove the FORMAT parameter.
OGG-02693: The checkpoint table name cannot contain a wildcard.
The checkpoint table name specified with CHECKPOINTTABLE in the GLOBALS file cannot contain a wildcard.
Action:
Specify a non-wildcarded name.
OGG-02694: ASCII trail format does not support DDL.
The DDL option is enabled for one or more trails that are configured for FORMATASCII, FORMATSQL or FORMATXML output.
Action:
Remove the DDL option or do not specify FORMATASCII, FORMATSQL or FORMATXML as the trail format.
OGG-02695: ANSI SQL parameter syntax is used for parameter parsing.
Default parameter syntax is used.
Action:
None
OGG-02696: NON-ANSI SQL parameter syntax is used for parameter parsing.
NOUSEANSISQLQUOTES parameter is specified for compatibility with legacy parameter syntax.
Action:
None
OGG-02697: LOB write failed. LOB exceeds the supported size. LOB offset: {0}
The LOB write operation failed because the size of the LOB is equal to or greater than that maximum supported size of 4GB.
Action:
Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02698: LOB trim failed. LOB exceeds the supported size. LOB offset: {0}
The LOB trim operation failed because the size of the LOB is equal to or greater than that maximum supported size of 4GB.
Action:
Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02699: LOB erase failed. LOB exceeds the supported size. LOB offset: {0}, length: {1}
The LOB erase operation failed because the size of the LOB is equal to or greater than that maximum supported size of 4GB.
Action:
Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02700: LOB size exceeds the maximum supported size {0} bytes. LOB offset: {1}, length: {2}
The LOB size exceeds the Oracle GoldenGate maximum allowed size.
Action:
Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02701: LOB size exceeds the maximum supported size {0} bytes after character set conversion. LOB offset: {1}, length: {2}
The LOB size exceeds the Oracle GoldenGate maximum allowed size after character set conversion.
Action:
Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02703: The trail or definitions file is format level {0} and does not support database character set {1}.
The specified database character set is not supported by the previous release of Oracle GoldenGate. An older version of Replicat may not be able to apply the data properly.
Action:
Contact Oracle Support.
OGG-02704: Failed to read entire LOB column "{0}" of table {1}. Expected length was {2} characters. Only {3} bytes was read.
Internal LOB read error.
Action:
Contact Oracle Support.
OGG-02705: Invalid value given for the DDLOPTIONS parameter {0}
The specified value is not a valid one for DDLOPTIONS.
Action:
See the Oracle GoldenGate reference documentation for further information.
OGG-02706: Unable to set the USE_PASSWORD_VERIFIER_LEVEL to {0} as the requested verifier was not provided in the password.
The password verifier that was requested was not present in the password string that was generated by the database.
Action:
Change the SQLNET.ALLOWED_LOGON_VERSION_SERVER setting to generate the requested password verifier.
OGG-02707: UDT LOB buffer overflow, needed: {0}, allocated: {1}.
Not enough UDT read buffer was allocated.
Action:
Allocate a larger LOB read buffer using the DBOPTIONS LOBBUFSIZE parameter.
OGG-02708: UDT LOB write error: {0}.
OCI error occurs when writing UDT LOB.
Action:
Check the error message detail to resolve the error as described.
OGG-02709: Dictionary Log Files are not found on the source and mining database. Register the logs manually.
Dictionary Log Files are not found on the source and mining database in a downstream setup.
Action:
None
OGG-02710: Database metadata information is obtained from source database.
The database metadata information is from the source database.
Action:
None
OGG-02711: Database metadata information is obtained from LogMiner server.
The database metadata information is from LogMiner server.
Action:
None
OGG-02712: Failed to set default tag '00'. {0}
An error occurred while trying to set the default tag to 00.
Action:
None
OGG-02713: Standby database is behind the primary database. Please retry the {0} command.
Standby database returns an error while trying to execute the query because the standby is not caught up with the primary database.
Action:
Please retry the command again.
OGG-02714: ADG redirection on the standby database failed because of an error {0}
Enabling ADG Redirection failed on the standby database.
Action:
None
OGG-02715: You are now connected to an ADG and ADG Redirection was enabled successfully.
ADG Redirection was enabled successfully on the standby database.
Action:
None
OGG-02716: Extract group {0} can not be positioned to SCN {1,number,0} because of the following SQL error: {2}.
Extract could not be positioned to the requested SCN.
Action:
Re-issue the command with a valid SCN.
OGG-02717: DDL is too large or partial. DDL is ignored. Details: {0} DDL statement with marker sequence [{1}], ddl sequence [{2}], redo sequence [{3}], rba [{4}], thread id [{5}], start SCN [{6}], commit SCN [{7}] length [{8}] for {9}.{10}/{11} will be ignored. Either the length of DDL exceeded the supported maximum size or a partial DDL is received due to insufficient BUFSIZE. Increase the BUFSIZE if a partial DDL is received and the actual DDL size is less than the supported maximum size.
A DDL statement that exceeds the size supported by Oracle GoldenGate will be ignored. Partial DDLs will also be ignored.
Action:
If using the pre 19.1 trail file format, use the 19.1 trail file format. If running Oracle Extract, specify large enough buffer size to hold entire DDL text by TRANLOGOPTIONS BUFSIZE option. A future DML may cause an error if discarding the DDL causes metadata inconsistencies. In any case, you can apply the DDL on the target manually. You might need to restart processes if the condition caused an error.
OGG-02718: The database does not support catalog names. A SOURCECATALOG parameter {0} specified for TABLE clause '{1}'.
The source database does not support catalog names.
Action:
Remove the SOURCECATALOG parameter.
OGG-02719: Redo transport lag has exceeded the user supplied timeout value of {0} secs for all threads.
Redo transport lag has exceeded user specified timeout value. This may be due to redo transport LAD status being invalid or error.
Action:
Check if the redo transport LAD status is valid and restart extract.
OGG-02720: Log archive destination with matching db_unique_name {0} has {1} status. Please fix the LAD settings.
Redo transport LAD was not set properly or changed due to network issues.
Action:
Fix the LAD status and restart extract.
OGG-02721: Extract has been waiting for the standby database for {0} seconds.
Physical standby database is behind the primary database in the Dataguard Environment.
Action:
Please check why the standby database is behind the primary database.
OGG-02722: Extract abended waiting for {0} seconds for the standby database to be accessible or caught up with the primary database.
Physical standby database is not accessible or behind the primary database in the Dataguard Environment.
Action:
If the standby database is not setup, remove the HANDLEDLFAILOVER parameter from extract parameter file and restart extract. If the standby database is configured, fix the Dataguard configuration setup issue and restart the extract.
OGG-02723: Extract resumed from stalled state and started processing LCRs.
Extract processing LCR SCN is less than or equal to the standby APPLIED SCN, so Extract started processing the LCR.
Action:
None
OGG-02724: HANDLEDLFAILOVER STANDBY_ABEND time should be greater than the STANDBY_WARNING time.
HANDLEDLFAILOVER STANDBY_ABEND time specified is less than the specified STANDBY_WARNING time.
Action:
Please fix the values and restart Extract.
OGG-02725: This transaction cannot be forced to extract trail because this feature is not supported on mining database versions less than 12.2.0.1.
The Capture process is running on database version less than 12.2.0.1.
Action:
Please use database version 12.2.0.1 or higher.
OGG-02726: Mining database connection is unavailable.
Mining database connection is not available for Extract to connect.
Action:
Please verify if Extract parameter file has USERID details in case of upstream setup and TRANLOGOPTIONS MININGUSER/MININGPASSWORD details in case of downstream setup.
OGG-02727: Maximum Object ID should always be greater than or equal to Minimum Object ID in {0} command.
The maximum object id specified is less than the minimum object id.
Action:
Please fix the values for minimum and maximum object ids and retry.
OGG-02728: Transaction {0} not found.
The specified transaction is not found.
Action:
None
OGG-02729: Parallel query is disabled as Extract received {0}.
Parallel query has to be disabled as it cannot be enabled or database could not allocate slaves on all specified instances.
Action:
None
OGG-02730: TAF callback failed to allocate Context
TAF callback failed to allocate context as memory allocation failed.
Action:
Please ensure that there is enough memory.
OGG-02731: Failed to initialize connection.
Failed to initialize connection with the database.
Action:
None
OGG-02732: Failed to initialize connection from pool.
Failed to initialize connection from pool for connecting to the database.
Action:
None
OGG-02733: Heartbeat table found in the connected schema {0}, using this heartbeat table.
Heartbeat table found in the schema.
Action:
None
OGG-02734: Using heartbeat table from schema {0}.
ER recognized heartbeat table in this schema.
Action:
None
OGG-02735: No heartbeat table schema available. Heartbeat table is not enabled.
GGSCHEMA or HEARTBEATTABLE parameter definition is not found in GLOBALS.
Action:
Add GGSCHEMA or HEARTBEATTABLE parameter definition in GLOBALS to enable heartbeat table.
OGG-02750: The definition for table {0} from the target database overrides the table metadata from the trail.
ASSUMETARGETDEFS OVERRIDE was used to override the table metadata from the trail.
Action:
None
OGG-02751: Unable to generate metadata record for table {0} because its definition is obtained from an earlier release definitions file, {1}.
The provided definitions file was generated using format release prior to 12.1.
Action:
Regenerate the definitions file using format release 12.1 or later and restart the process.
OGG-02752: The definition for table {0} from definitions file {1} overrides the table metadata from the trail.
A SOURCEDEFS file was specified with OVERRIDE option to override the table metadata from the trail.
Action:
None
OGG-02753: Unable to generate table metadata records because there are no table definitions in {0}.
Data pump was unable to generate the table metadata when the specified input trail file contained no table metadata.
Action:
Perform one of the following steps: Specify a SOURCEDEFS file containing the correct definitions of all the tables in the input trail; 2) Add NO_OBJECTDEFS to the RMTTRAIL option to generate an output trail with no metadata records; 3) Remove the PASSTHRU option from the data pump's parameter file if it's specified.
OGG-02754: Initial load Extract does not support more than 65535 tables.
Initial load Extract does not support more than 65535 tables.
Action:
Reduce the number of tables in the TABLE option.
OGG-02755: Unable to process metadata record for {0} from trail seq# {1,number,0} at RBA {2,number,0}.
An error occurred when deserializing the metadata record at the specified position in the trail file. This may be due to incorrect encryption key or algorithm provided to the process.
Action:
None
OGG-02756: The definition for table {0} is obtained from the trail file.
The definition for the specified table is obtained from the trail file.
Action:
None
OGG-02757: Trail file {0} contains no table definition for {1}.
Data pump or Replicat encountered a trail file with no table definitions after the definition for the specified table was extracted from a previous file sequence.
Action:
If SOURCEDEFS is specified in the parameter file then verify the source definitions file contains the correct definitions for all the tables in the specified trail file then restart the application. If SOURCEDEFS is not specified then add a SOURCEDEFS option with a correct definitions file then restart the application.
OGG-02758: The definition for table {0} is obtained from definitions file {1}.
The definition for the specified table is obtained from a source definitions file.
Action:
None
OGG-02759: The definition for table {0} is obtained from the target database.
The definition for the specified table is obtained from the target database.
Action:
None
OGG-02760: ASSUMETARGETDEFS is ignored because trail file {0} contains table definitions.
Replicat ignored ASSUMETARGETDEFS because the table definitions from the specified trail file were more reliable.
Action:
Perform one of these actions: * Remove the ASSUMETARGETDEFS parameter. * Append OVERRIDE to the ASSUMETARGETDEFS parameter if you want the process to use the table definitions from the target database. Note that doing this may result in data corruption if the target table definitions are not in sync with the trail records.
OGG-02761: Source definitions file, {0}, is ignored because trail file {1} contains table definitions.
Data pump and Replicat ignored the source definitions files because the table definitions from the specified trail file were more reliable.
Action:
Perform one of these actions: * Remove the SOURCEDEFS parameter. * Append OVERRIDE to the SOURCEDEFS parameter if you want the process to use the source definitions file. Note that doing this may result in data corruption if the source definitions file is not in sync with the trail records.
OGG-02763: Unable to retrieve catalog metadata: {0}.
The query to retrieve catalog metadata did not complete successfully.
Action:
Make sure the extract user has privileges to query catalog metadata.
OGG-02765: Trail format version must be 12.2 or higher to extract changes from multiple catalogs with mixed character sets or timezones.
The trail format release is prior to Oracle GoldenGate 12c (12.2.1)
Action:
None
OGG-02766: Unsupported metadata record type {0} for {1}.
This process encountered an unsupported metadata record type. This is likely because the input trail was generated from a later Oracle GoldenGate release.
Action:
Re-generate the input trail using a lower FORMAT RELEASE version or upgrade existing GoldenGate.
OGG-02767: The metadata for {0} is obtained from the target database as the records for this table are mapped based on the TARGETDETS from a different database type.
Replicat assumed the metadata from the target database for the specified table because the metadata in the trail was based on a target defs file generated by a database of a type different from the source.
Action:
Avoid using TARGETDEFS by moving the mapping parameters from Extract to Replicat.
OGG-02768: All SOURCEDEFS statements must have the same OVERRIDE option.
You cannot define multiple SOURCEDEFS statements with different OVERRIDE options.
Action:
Modify the SOURCEDEFS statements to use the same OVERRIDE option.
OGG-02769: The operating system character set {0} is not supported.
The character set of the operating system may be not properly configured and is not supported.
Action:
Check the operating system character set and locale configuration.
OGG-02770: Cannot map the source XML, UDT or AnyData column {0} XML diff data to the XML diff incompatible target column {1}.
XML diff data exists in the source record that is mapped to the XML diff incompatible target column and unable to process the XML diff data.
Action:
Check the column mapping and map the source XML, UDT or AnyData column to the target XML, UDT, or AnyData column.
OGG-02771: Input trail file {0} format {1} is different from previous trail file format {2}.
The trail file format downgrade, pre-12.2 trail file format change, or format change using SOURCEDEFS or ASSUMETARGETDEFS aren't supported but Oracle GoldenGate trail file format was changed by Extract.
Action:
Apply all transactions right before the trail file that format is different from previous trail files. Stop the Replicat, reposition Replicat to the new format trail file sequence number and rba 0, and restart the Replicat.
OGG-02772: Overflow detected while converting numeric text {0} to the integer value. Maximum number supported by Oracle GoldenGate column mapping function is 9223372036854775807.
Numeric text data is too large.
Action:
Check the parameter file and resolve the issue if the large number is mapped by COLMAP clause.
OGG-02773: Underflow detected while converting numeric text {0} to the integer value. Minimum number supported by Oracle GoldenGate column mapping function is -9223372036854775808.
Numeric text data is too small.
Action:
Check the parameter file and resolve the issue if the small number is mapped by COLMAP clause.
OGG-02774: Overflow detected while adjusting number {0} from scale {1} to scale {2}. Maximum number supported by Oracle GoldenGate column mapping function for this scale adjustment is {3}.
Number data is too large.
Action:
Check the parameter file and resolve the issue if the large number is mapped by COLMAP clause.
OGG-02775: Underflow detected while adjusting number {0} from scale {1} to scale {2}. Minimum number supported by Oracle GoldenGate column mapping function form this scale adjustment is {3}.
Number data is too small.
Action:
Check the parameter file and resolve the issue if the small number is mapped by COLMAP clause.
OGG-02776: Native data capture is enabled for Oracle NUMBER data type.
The output trail file format is format release 19.1 or above and native data capture is enabled to support infinity and corrupted data capture. These values are captured as zero in column data, along with native data in GGS token.
Action:
None
OGG-02777: Disable Oracle native data apply mode.
Oracle native data apply mode is explicitly disabled by the DBOPTIONS _NONATIVE parameter. Replicat may apply alternative default value to TIMESTAMP and NUMBER data types.
Action:
To enable Oracle native data apply mode, remove the DBOPTIONS _NONATIVE parameter.
OGG-02778: Previous parameter line '{0}' may be unterminated.
A TABLE, MAP, FILE, QUERY or SEQUENCE command is found in the beginning line after an unterminated TABLE, MAP, FILE, QUERY or SEQUENCE command line.
Action:
Check the parameter file and terminated the line with a semicolon if the parameter line is not properly terminated.
OGG-02779: Output trail file {0}, specified format {1} is newer than current format specification of {2}. Perform automatic ETROLLOVER and upgrade the output trail file format.
The output trail file format version explicitly specified by the Extract parameter is newer than existing output trail file. Extract may be upgraded and newer trail file format is specified explicitly.
Action:
None
OGG-02780: Unexpected condition in function {0} at line {1,number,0}. Missing information for partition ID {2}.
An internal error occurred. Missing partition information.
Action:
Contact Oracle Support.
OGG-02781: Invalid partition name {0} is specified for parameter {1}.
The partition name is specified in an invalid format. It must have a schema name, table name, a partition name part, and optional catalog name part.
Action:
Specify the correct fully qualified partition name.
OGG-02782: {0} cannot be specified more than once in a MAP/TABLE statement.
The MAP/TABLE clause option PARTITIONOBJID is specified more than once.
Action:
Remove all but one of the PARTITIONOBJID options from the MAP/TABLE statement.
OGG-02783: Extract group checkpoint {0} is not log trail type.
Checkpoint TRAILSOURCEPATH update can be done only for Data Pump, but the Extract checkpoint type is not log trail type.
Action:
Specify TRAILPATH to update output trail path or Data Pump group name to update input trail path.
OGG-02784: Input trail file {0} format {1} is switched from previous trail file format {2}.
Oracle GoldenGate trail file format was changed by Extract.
Action:
None
OGG-02785: DB checkpoint position (Sequence: {0}, RBA: {1}, Timestamp: {2}) past beyond checkpoint position (Sequence: {3}, RBA: {4}, Timestamp: {5}). Force enable FILTERDUPTRANSACTIONS option and reposition to checkpoint position.
A slow file system may cause the database checkpoint position to go past the checkpoint position especially upon failover time to the standby system.
Action:
None
OGG-02786: DB checkpoint position (Sequence: {0}, RBA: {1}, Timestamp: {2}) past beyond checkpoint position (Sequence: {3}, RBA: {4}, Timestamp: {5}). Reposition to checkpoint position.
A slow file system may cause the database checkpoint position to go past the checkpoint position especially upon failover time to the standby system.
Action:
None
OGG-02787: Parallel Replicat DB checkpoint position (Sequence: {0}, RBA: {1}) past beyond checkpoint position (Sequence: {2}, RBA: {3}). Force enable FILTERDUPTRANSACTIONS option and reposition to checkpoint position.
A slow file system may cause the database checkpoint position to go past the checkpoint position especially upon failover time to the standby system.
Action:
None
OGG-02788: Parallel Replicat DB checkpoint position (Sequence: {0}, RBA: {1}) past beyond checkpoint position (Sequence: {2}, RBA: {3}). Reposition to checkpoint position.
A slow file system may cause the database checkpoint position to go past the checkpoint position especially upon failover time to the standby system.
Action:
None
OGG-02789: Could not start asynchronous checkpointing.
Failed to start asynchronous checkpointing.
Action:
Contact Oracle GoldenGate support.
OGG-02790: Asynchronous checkpointing error for writing checkpoint. {0}.
Failed to write checkpoint using asynchronous checkpointing.
Action:
Check the error detail to resolve the issue or contact Oracle GoldenGate support.
OGG-02791: Failed to stop background checkpointing thread.
Background checkpoint thread encountered unexpected error.
Action:
Contact Oracle GoldenGate support.
OGG-02792: The source LCR operation type {0} for the object '{1}' requires trail file format 19.1 with full metadata.
The source LCR operation is associated with the Replicat version target information that requires trail file format 19.1 with full metadata.
Action:
Specify the FORMAT RELEASE option to output trail file format 19.1. Remove NO_OBJECTDEFS option is specified.
OGG-02793: The source LCR operation type {0} for the object '{1}' requires Replicat version {2}.{3} or later.
Replicat is older than the minimum required Replicat version to replicate the record.
Action:
Upgrade Replicat or exclude the record.
OGG-02794: The source LCR operation type {0} for the object '{1}' requires Replicat for the database {2} and the version {3}.{4} or later.
The record requires a specific database version and the Replicat for the database.
Action:
Use a different database version of Replicat and upgrade the target database version, or exclude the record.
OGG-02795: The source LCR operation type {0} for the object '{1}' requires Replicat version {2}.{3} or later. Skip the record.
Replicat is older than the minimum required Replicat version to replicate the record.
Action:
Upgrade Replicat or exclude the record to replicate the record.
OGG-02796: The source LCR operation type {0} for the object '{1}' requires Replicat for the database {2} and the version {3}.{4} or later. Skip the record.
The record requires a specific database version and the Replicat for the database
Action:
Use a different database version of Replicat, and upgrade the target database version, or exclude the record to replicate the record.
OGG-02797: Source LCR operation type {0} is not supported for non-passthru mapping including filtering.
The source LCR operation type is generated by a newer version of Extract and is not supported by the current version for non-passthru mapping.
Action:
Use PASSTHRU by removing filtering or mapping, or upgrade the Oracle GoldenGate to the same or newest version with the Extract that generated the source operation type.
OGG-02798: Source LCR operation type {0} is not supported for DDL filtering.
The source LCR operation type is generated by a newer version of Extract and is not supported by the current version for DDL filtering.
Action:
Removing DDL filtering or upgrade the Oracle GoldenGate to the same or newest version with the Extract that generated the source operation type.
OGG-02799: Source LCR operation type {0} is not supported by LCR encoder {1}.
The source LCR operation type is generated by a newer version of Extract and is not supported by OUTPUTFORMAT parameter.
Action:
Upgrade the Oracle GoldenGate to same or newer version with the Extract that generated the source operation type.
OGG-02802: Classic Extract failed to retrieve the current system SCN from database.
The database is in a corrupted or unstable state.
Action:
Resolve the database issue.
OGG-02808: Standby database is not running. Start it, then start Extract again.
The Extract process tried to capture from a standby database that is not running.
Action:
Start the standby database.
OGG-02809: Oracle Managed Redo Process(MRP) is not running on the Standby database.
Oracle Managed Redo Process(MRP) is not running.
Action:
Start the Oracle Managed Redo Process (MRP).
OGG-02813: Cannot access database {0} to capture table {1}. Verify database name and login privileges.
The specified container database does not exist or the login user does not have sufficient privileges to access the container database.
Action:
Specify the correct container database name or make certain the Oracle GoldenGate user has sufficient privileges to access the container database. Consult the Oracle GoldenGate documentation for Oracle Database. If the problem persists, contact Oracle Support.
OGG-02817: DBOPTIONS FETCHTIMEOUT value {0} must be greater than FETCHCHECKFREQ value {1}
Value for FETCHTIMEOUT parameter (default is 30 seconds), must be greater than value for FETCHCHECKFREQ (default is 3 seconds).
Action:
Increase FETCHTIMEOUT value, or decrease FETCHCHECKFREQ value.
OGG-02818: Error ({0,number,0}, {1}) occurred when querying the database in {2}
An error occurred when querying the database.
Action:
Contact Oracle Support.
OGG-02819: Could not determine database version for following error {0}.
Determination of the database version failed because of the reported error.
Action:
Correct the error and restart the application.
OGG-02835: Invalid checkpoint type {0} to retrieve redo log checkpoint position.
Invalid checkpoint type was specified when retrieving redo log checkpoint position.
Action:
Contact Oracle Support.
OGG-02836: Error retrieving Oracle redo log checkpoint position for type {0}.
Could not retrieve redo log checkpoint position for the specified checkpoint type.
Action:
Contact Oracle Support.
OGG-02837: Invalid checkpoint type ({0}) retrieving Oracle redo log commit begin checkpoint.
Invalid checkpoint type found in the checkpoint record when retrieving redo log commit begin checkpoint.
Action:
Contact Oracle Support.
OGG-02838: Recovery record is missing from log with seqno {0} when Extract has reached log with seqno {1}, block size {2}, and next_checkpoint RBA at {3}.
Could not find recovery record when extract has reached the checkpointed log position.
Action:
Contact Oracle Support.
OGG-02839: Record position ({0}) is beyond end of recovery ({1}).
Redo log record position is beyond end of recovery point.
Action:
Contact Oracle Support.
OGG-02844: Position of first record processed for Thread {0}, Sequence {1}, RBA {2}, SCN {3}.{4} ({5}), {6,date} {6,time}
The processing began with the first record that has the specified timestamp.
Action:
None
OGG-02845: Position of first record processed Sequence {0}, RBA {1}, SCN {2}.{3} ({4}), {5,date} {5,time}
The processing began with the first record that has the specified timestamp.
Action:
None
OGG-02869: Too many producers {0} (exceeds a maximum of {1}).
Internal error.
Action:
Contact Oracle Support.
OGG-02870: Missing Log File {0}. Read Position SCN: {1}.
The log file is missing or checkpoint is corrupted.
Action:
Check to see if the log file exists in the system, and verify the checkpoint file.
OGG-02872: TRANLOGOPTIONS INCLUDEREGIONID option is deprecated and no longer required to capture TIMESTAMP WITH TIME ZONE with region ID format.
The TRANLOGOPTIONS INCLUDEREGIONID parameter is specified in the Extract parameter file.
Action:
Remove the TRANLOGOPTIONS INCLUDEREGIONID parameter from the Extract parameter file.
OGG-02873: Invalid Extract group name {0}. Must be 8 characters or less.
Specified Extract group name is too long.
Action:
Specify a correct Extract group name.
OGG-02874: Invalid sequence number length argument {0} for the trail file name {1}.
Specified sequence number length isn't SEQLEN_9D or SEQLEN_6D.
Action:
Specify sequence number length either SEQLEN_9D or SEQLEN_6D.
OGG-02875: Length of trail file name {0} exceeds maximum length of {1}.
Specified trail file name is too long.
Action:
Specify correct trail file name.
OGG-02876: Invalid option {0}.
Invalid option is specified.
Action:
Specify a valid option or don't specify the option.
OGG-02877: Extract group {0} was not gracefully stopped.
Checkpoint conversion is allowed only gracefully stopped Extract group unless the -force option is specified.
Action:
Perform ETROLLOVER the Extract group or specify the -force option.
OGG-02878: Could not retrieve current output checkpoint for Extract {0} trail index {1}.
Could not get the current output checkpoint for Extract.
Action:
Internal error. Contact Oracle Support.
OGG-02879: Trail file {0} is EXTFILE/RMTFILE and is not valid trail file to convert checkpoint.
Checkpoint sequence number length can be modified on EXTTRAIL or RMTTRAIL.
Action:
Specify the EXTTRAIL or RMTTRAIL trail file.
OGG-02880: Nothing to convert checkpoint for Extract group {0}, trail file {1}.
Checkpoint for specified Extract group and trail file name is already in specified sequence length and the conversion is not necessary.
Action:
None
OGG-02881: The current sequence number {0} is not valid for the new sequence length for the trail file {1}.
The current sequence number is too big and not valid for the new sequence length. For example, the sequence number is 999999 and SEQLEN_6D is specified.
Action:
Do not attempt to convert the checkpoint sequence number length for the trail file.
OGG-02882: Resetlogs SCN value too large {0} to convert it's field size to 32-bit.
Checkpoint resetlogs SCN field size was attempted to convert to older checkpoint field size 32-bit, but the value was too large to hold in 32-bit field.
Action:
Do not convert resetlogs SCN size to older checkpoint 32-bit field size.
OGG-02883: Nothing to convert checkpoint for Extract group {0}.
Checkpoint for specified Extract group and trail file name is already in specified resetlogs SCN size and the conversion is not necessary.
Action:
None
OGG-02884: Invalid resetlogs SCN size is specified.
Specified resetlogs SCN size is invalid.
Action:
Specify valid resetlogs SCN size either 32BIT or 64BIT.
OGG-02885: Wildcard resolution parameter {0} is no longer supported and is ignored.
Immediate wildcard resolution is automatically performed only on SOURCEISTABLE Extract and GENLOADFILES Replicat, and Oracle Extract with ALTID use. All other Extract and Replicat modes run in dynamic wildcard resolution mode.
Action:
Remove the parameter.
OGG-02886: Could not retrieve current input checkpoint for Extract or Replicat {0} trail index {1}.
Could not get the current output checkpoint for Extract or Replicat.
Action:
Internal error. Contact Oracle Support.
OGG-02887: Missing parameter file path prefix for Coordinated or Parallel Replicat group {0}.
Parameter file prefix is not specified, that is required for Coordinated Replicat or Parallel Replicat.
Action:
Specify parameter file path prefix using -PARAMPATH option.
OGG-02888: Ignoring parameter file path prefix {0} for Extract or Replicat group {1}.
Parameter file prefix is specified but the specified group is neither Coordinated nor Parallel Replicat.
Action:
Don't specify parameter file path prefix using -PARAMPATH option.
OGG-02889: Missing parameter path prefix value.
Parameter file prefix option -PARAMPATH is specified but no value is specified.
Action:
Specify the parameter file path prefix.
OGG-02890: Can't alter checkpoint for Extract group {0}, because the checkpoint was altered by the convchk utility.
Checkpoint was altered by the convchk utility and can't update by GGSCI or AdminClient.
Action:
Restart Extract before issue ALTER EXTRACT or ALTER TRAIL command.
OGG-02891: Can't alter checkpoint for Replicat group {0}, because the checkpoint was altered by the convchk utility.
Checkpoint was altered by the convchk utility and can't update by GGSCI or AdminClient.
Action:
Restart Replicat before issue ALTER REPLICAT or ALTER TRAIL command.
OGG-02892: Can't convert checkpoint for Extract group {0}, because the checkpoint was altered by user.
Checkpoint was altered by user using GGSCI or AdminClient.
Action:
Restart Extract before using convchk.
OGG-02893: Can't convert checkpoint for Replicat group {0}, because the checkpoint was altered by user.
Checkpoint was altered by user using GGSCI or AdminClient.
Action:
Restart Replicat before using convchk.
OGG-02894: Missing checkpoint path prefix value.
Checkpoint file prefix option -CPPATH is specified but no value is specified.
Action:
Specify the checkpoint file path prefix.
OGG-02895: Missing trail file path for TRAILPATH or TRAILSOURCEPATH.
TRAILPATH or TRAILSOURCEPATH option is specified but no value is specified.
Action:
Specify the trail file path.
OGG-02896: Could not open {0}:{1}.
The given file doesn't exist or the file path isn't valid.
Action:
Provide a valid file or file path.
OGG-02897: Failed to synchronize trail file. Error detail: {0}.
A system call to synchronize the trail file failed.
Action:
Contact Oracle Support.
OGG-02898: Invalid DDL fragment offset {0} is specified. Current DDL total size {1}.
Invalid DDL fragment offset is specified to add DDL fragment.
Action:
Internal error. Contact Oracle Support.
OGG-02899: Unexpected EOF while generating metadata record in {0} at rba {1,number,0}. Current DML record length {2,number,0}, trail maximum size {3,number,0}
Extract or Pump encountered an unexpected trail EOF.
Action:
Internal error. Contact Oracle Support.
OGG-02900: Replication of UDT and ANYDATA from redo logs is disabled. Trail FORMAT RELEASE must be 12.1 or later. Use fetch instead.
Trail FORMAT RELEASE must be 12.1 or later.
Action:
To support replication of UDT and ANYDATA from redo logs, you must set FORMAT RELEASE to release 12.1 or later.
OGG-02901: Replication of UDT and ANYDATA from redo logs is not supported with the Oracle compatible parameter setting. Using fetch instead.
Replication of UDT and ANYDATA from redo logs requires Oracle compatible parameter 12.0.0.0.0 or later.
Action:
See the Oracle GoldenGate documentation for help with required Oracle database compatible parameter setting requirements.
OGG-02902: Replication of UDT and ANYDATA from redo logs is not supported because the patch required for Oracle database is missing. Use fetch instead.
The patch that is required to replicate UDT and ANYDATA from redo logs cannot be found.
Action:
Apply Oracle Patch 18038108 to the source database.
OGG-02903: Replication of UDT and ANYDATA from redo logs is not supported because the Oracle database version is not release 12.1 or later.
Replication of UDT and ANYDATA from redo logs requires Oracle 12.1.0.1 or higher version.
Action:
Upgrade to Oracle Database release 12.1.0.1 or later. For Oracle Database release 12.1.0.1, apply Oracle Patch 18038108 to the target database.
OGG-02904: Replication of PARTIAL XML containing NCHAR/NVARCHAR/NCLOB data may cause divergence.
Full support to NCHAR/NVARCHAR/NCLOB in PARTIAL XML requires Oracle Database release 12.1.0.1 or later versions. For Oracle Database release 12.1.0.1, apply Oracle Patch 18038108 to the target database.
Action:
The workaround is to use the FETCHPARTIALXML option in Extract so that Replicat does not encounter PARTIAL XML. Contact Oracle support.
OGG-02905: Replication of OID column in object tables may diverge.
Extract is not configured to capture DML from CREATE TABLE AS SELECT statement.
Action:
Configure Extract to capture DML from CREATE TABLE AS SELECT statement, and then restart the process.
OGG-02906: Replication of UDT and ANYDATA from redo logs requires Replicat 12.1.2.1.0 or later.
Replication of UDT and ANYDATA from redo logs may diverge if Replicat 12.1.2.1.0 or later is not used.
Action:
Make sure that Replicat 12.1.2.1.0 or later is used. Ignore this message if you are using the right version.
OGG-02907: User provided parameters conflict.
_LOGMINER_GET_CTAS_DML and GETCTASDML cannot conflict.
Action:
Change _LOGMINER_GET_CTAS_DML or GETCTASDML.
OGG-02909: CTAS not supported with replicat versions lower than 12.1.2.1.0.
CTAS functionality must be used with replicat versions at or above 12.1.2.1.0.
Action:
Ensure that the trail files produced with CTAS enabled are not consumed by replicat versions less than 12.1.2.1.0.
OGG-02910: Sequence {0} not processed, sequence values are synchronized at run-time
SEQUENCE capture is not supported by initial load capture, and is ignored.
Action:
None
OGG-02911: Processing table {0}
Initial load capture is processing the table.
Action:
None
OGG-02912: Patch 17030189 is required on your Oracle mining database for trail format RELEASE 12.2 or later.
The patch that is required by Integrated Dictionary cannot be found.
Action:
Either apply Oracle Patch 17030189 to the mining database, or change the trail format to RELEASE 12.1 (or earlier). If neither of these options are viable, as a temporary workaround you may apply script prvtlmpg.plb (included in the Oracle GoldenGate installation directory) to the mining database.
OGG-02913: Metadata format of the definitions file for table {0} does not match trail format.
The definitions file uses a metadata format that is incompatible with the trail format.
Action:
Regenerate the definitions file using the correct metadata format then restart the application.
OGG-02915: Extract is configured with multiple incompatible trail formats.
Extract is configured with multiple trail formats that are not compatible with each other.
Action:
Configure Extract to use compatible trail formats. For compatibility of different trail formats, see the Oracle GoldenGate documentation.
OGG-02916: Global commit serialization is specified, {0} cannot be specified for a specific catalog without specifying no commit serialization for it.
Global commit serialization is specified for all PDB's, which is not compatible with apply_parallelism which is specified for a specific PDB.
Action:
When doing override, no commit serialization needs to be specified first.
OGG-02917: LONG and partial LOB updates written as UNIFIED UPDATE records require Replicat 12.3.0.1.0 or later.
Extract is configured to write LONG and partial LOB updates as UNIFIED UPDATE records.
Action:
To avoid downstream replicat failures, validate that all replicats consuming this trail are at version 12.3.0.1.0 or later.
OGG-02918: Monitoring parameters in the GLOBALS file are ignored in Microservices Architecture mode.
Monitoring parameters in the GLOBALS file are not recognized or used in Microservices Architecture mode.
Action:
Remove monitoring parameters from the GLOBALS file in Microservices Architecture mode.
OGG-02919: Parameter [enablemonitoring] has unrecognized keyword or extra value "{0}".
The specified data store type is not valid.
Action:
Correct the data store type.
OGG-02920: Parameter TRANLOGOPTIONS SOURCE_OS_TIMEZONE must be specified, but it is not. Source database OS time zone offset: {0}, Extract OS time zone: {1}.
The OS time zone of the source database must be specified if it is different from the OS time zone of the Extract process.
Action:
Specify the OS time zone of the source database using the TRANLOGOPTIONS SOURCE_OS_TIMEZONE parameter.
OGG-02921: Invalid TRANLOGOPTIONS SOURCE_OS_TIMEZONE value: {0}
Parameter TRANLOGOPTIONS SOURCE_OS_TIMEZONE is set to an invalid value.
Action:
Specify a valid value. For more information, see the Oracle GoldenGate reference documentation.
OGG-02922: Trail file {0}, with format {1}, does not match default format specification {2}. Extract is going to write new trail file in the format {1} to keep compatibility.
The version of Extract and the version of the output file or trail do not match. Extract may have been upgraded to a newer version. By default, Extract expects the trail version to be the same as its own version. In order to retain backward compatibility for an older Replicat, Extract is continue writing the trail file format with the older format.
Action:
You have two choices, depending on whether the Replicat process is the same version as the Extract process, or whether it is older. You can continue using an older Replicat process and no further action is necessary. Or to upgrade Replicat to the same version of Extract, issue the ALTER EXTRACT command with the ETROLLOVER option in GGSCI before you start Extract. The rollover sets the trail format to the same as that of the new Extract. For information about these parameters, see the Oracle GoldenGate Reference Guide.
OGG-02923: Replicat does not support UPSERT database operation for this Database type.
The source record operation type UPSERT found, but Replicat for the database type not support the UPSERT operation.
Action:
Add IGNOREUPSERTS to the Replicat parameter file to skip the UPSERT operation, or UPSERTINSERT to apply UPSERT record as INSERT operation.
OGG-02924: One of the following database properties is missing 'DBTIMEZONE', 'NLS_CHARACTERSET', or 'NLS_NCHAR_CHARACTERSET'.
A database property is missing.
Action:
You need to investigate which database property from the list specified in the message is missing and correct it.
OGG-02925: Metadata format of the definitions file for table {0} does not match trail format.
The definitions file uses a metadata format that may be incompatible with the trail format and potentially causes incorrect replication results.
Action:
Regenerate the definitions file using the correct metadata format then restart the application.
OGG-02926: Missing end generated transaction marker while PR/IR end processing initial load trail file and switching to trail file 'string', number of records read number.
Internal error, missing end generated transaction marker.
Action:
Internal error. Contact Oracle Support.
OGG-02927: Unexpected trail file seqno {0} is requested to check end generated transaction marker while PR/IR processing initial load trail file {1}.
Internal error, unexpected trail file sequence number.
Action:
Internal error. Contact Oracle Support.
OGG-02928: Server could not open remote file {0}, flags: {1}, idx: {2}, port: {3}, error: {4}.
Internal error. Server collector could not open remote file.
Action:
Internal error. Contact Oracle Support.
OGG-02929: Failed to open remote file {0}. Too many files are opened. Maximum number of files can be opened is number.
Internal error. Server collector could not open remote file because too many files are already opened.
Action:
Internal error. Contact Oracle Support.
OGG-02930: Failed to create remote file {0}. (error: {1,number,0}, {2}).
Internal error. Server collector could not create remote file.
Action:
Internal error. Contact Oracle Support.
OGG-02931: Failed to lock remote file {0}. (error: {1,number,0}, {2}).
Internal error. Server collector could not lock remote file.
Action:
Internal error. Contact Oracle Support.
OGG-02933: Failed to set runtime write buffer to the output trail file {0}.
Internal error.
Action:
Internal error. Contact Oracle Support.
OGG-02934: Error failed to start alias Extract. Manager replied message: {0}.
An Oracle GoldenGate component failed to start alias Extract.
Action:
Check the report file that is issued by the process, and check the error log for other messages adjacent to this one that might help you resolve the problem. Make certain Manager is running for other processes to start. The database also must be running. Trail files must be properly created. Parameter files must be in the expected location. For additional help, see the Oracle GoldenGate troubleshooting documentation. If you cannot resolve the problem, contact Oracle Support.
OGG-02935: Error failed to start Server Collector.
An Oracle GoldenGate component failed to start Server Collector.
Action:
Check the report file that is issued by the process, and check the error log for other messages adjacent to this one that might help you resolve the problem. Make certain Manager is running for other processes to start. The database also must be running. Trail files must be properly created. Parameter files must be in the expected location. For additional help, see the Oracle GoldenGate troubleshooting documentation. If you cannot resolve the problem, contact Oracle Support.
OGG-02936: Bounded Recovery has no persisted objects to recover.
Extract has no transaction data to recover from disk.
Action:
None
OGG-02937: No valid Bounded Recovery checkpoint found.
Extract could not find a valid Bounded Recovery checkpoint, and will revert to normal recovery. Previous CPF may have been examined. View the log file for the detail.
Action:
None
OGG-02938: Startup of Replicat group {0} failed. Detail: {1}.
The specified Replicat cannot start.
Action:
Look for additional error messages that indicate why the process cannot start, and then correct the problem.
OGG-02939: Startup of the application {0} failed. Detail: {1}.
The specified application cannot start.
Action:
Look for additional error messages that indicate why the process cannot start, and then correct the problem.
OGG-02940: Replicat group {0} restarted automatically.
The specified Replicat was restarted automatically based on rules in the AUTORESTART parameter.
Action:
None
OGG-02941: The WILDCARDRESOLVE and (NO)DYNAMICRESOLUTION parameters are deprecated. Defaulting to WILDCARDRESOLVE IMMEDIATE.
The WILDCARDRESOLVE parameter is deprecated and was specified.
Action:
Remove the WILDCARDRESOLVE parameter. If immediate resolution is necessary for Replicat or data pump, specify ASSUMETARGETDEFS or SOURCEDEFS with the OVERRIDE option.
OGG-02942: Extract group {0} is already running.
A START command was issued for an Extract that is already running.
Action:
None
OGG-02943: Replicat group {0} is already running.
A START command was issued for a Replicat that is already running.
Action:
None
OGG-02944: Cannot automatically start Extract group {0}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract, or Replicat, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Manager cannot start the specified Replicat. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action:
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-02945: Cannot automatically start Replicat group {0}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract, or Replicat, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Manager cannot start the specified Replicat. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action:
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-02946: Cannot automatically restart Extract group {0}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract, or Replicat, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Manager cannot start the specified Extract. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action:
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-02947: Cannot automatically restart Replicat group {0}, which abended due to an out of order transaction. Issue ETROLLOVER to advance the output trail sequence past the current trail sequence and restart. Then, use ALTER EXTSEQNO on the subsequent pump Extract, or Replicat, process group to start reading from the new trail file created by ALTER ETROLLOVER; the downstream process will not automatically switch to the new trail file.
Manager cannot start the specified Replicat. The transactions in the current trail file are out of order. One possible cause is that Extract was configured to write to this trail, and then was reconfigured to write to a different trail, but was subsequently reconfigured to write the original trail again. It is also possible that Extract was repositioned backward in the transaction log and the data from the new position was appended to the end of the current trail file. You need to skip this record, and then reposition Replicat to start at the next one.
Action:
Stop the Extract that should write to this trail, then issue the ALTER EXTRACT command with ETROLLOVER. Next, restart Extract. Next, issue the ALTER REPLICAT or ALTER EXTRACT command (depending on whether Replicat or a data pump Extract reads the trail) with the EXTSEQNO option and specify the sequence number of the new trail file. Finally, start Replicat or the data pump.
OGG-02948: {0}
This is a generic informational message and does not indicate any problem.
Action:
None
OGG-02949: Lag for Extract group {0} is {1} (checkpoint updated {2} ago).
The setting of the LAGINFO parameter prompted Manager to report lag information to the error log. This message is considered a warning message because the lag is greater than the value specified with the LAGCRITICAL parameter.
Action:
Correct the problem that is causing the lag. For help with configuring Oracle GoldenGate to reduce lag, see the Oracle GoldenGate troubleshooting and performance documentation.
OGG-02950: Lag for Extract group {0} is {1} (checkpoint updated {2} ago).
The setting of the LAGINFO parameter prompted Manager to report lag information to the error log. This message is considered an informational message because the lag is not greater than the value specified with the LAGCRITICAL parameter.
Action:
None
OGG-02951: Invalid checkpoint type ({1,number,0}), cannot determine lag threshold for Extract group {0}.
The checkpoint is invalid.
Action:
Contact Oracle Support.
OGG-02952: Lag for Replicat group {0} is {1} (checkpoint updated {2} ago).
The setting of the LAGINFO parameter prompted Manager to report lag information to the error log. This message is considered a warning message because the lag is greater than the value specified with the LAGCRITICAL parameter.
Action:
Correct the problem that is causing the lag. For help with configuring Oracle GoldenGate to reduce lag, see the Oracle GoldenGate troubleshooting and performance documentation.
OGG-02953: Lag for Replicat group {0} is {1} (checkpoint updated {2} ago).
The setting of the LAGINFO parameter prompted Manager to report lag information to the error log. This message is considered an informational message because the lag is not greater than the value specified with the LAGCRITICAL parameter.
Action:
None
OGG-02954: Invalid checkpoint type ({1,number,0}), cannot determine lag threshold for Replicat group {0}.
The checkpoint is invalid.
Action:
Contact Oracle Support.
OGG-02955: Extract group {0} abended.
The specified Extract abended.
Action:
Look for additional error messages that indicate why the Extract abended, and then correct the problem.
OGG-02956: Replicat group {0} abended.
The specified Replicat abended.
Action:
Look for additional error messages that indicate why the Replicat abended, and then correct the problem.
OGG-02957: Distribution Service path {0} abended.
The specified Distribution Service abended.
Action:
Look for additional error messages that indicate why the Distribution Service path abended, and then correct the problem.
OGG-02958: Extract group {0} is starting.
The specified Extract is starting.
Action:
None
OGG-02959: Replicat group {0} is starting.
The specified Replicat is starting.
Action:
None
OGG-02960: Distribution Service path {0} is starting.
The specified Distribution Service path is starting.
Action:
None
OGG-02961: Extract group {0} is running.
The specified Extract is running.
Action:
None
OGG-02962: Replicat group {0} is running.
The specified Replicat is running.
Action:
None
OGG-02963: Distribution Service path {0} is running.
The specified Distribution Service path is running.
Action:
None
OGG-02964: Extract group {0} is down (gracefully).
The specified Extract stopped gracefully.
Action:
None
OGG-02965: Replicat group {0} is down (gracefully).
The specified Replicat stopped gracefully.
Action:
None
OGG-02966: Distribution Service path {0} is down (gracefully).
The specified Distribution Service path stopped gracefully.
Action:
None
OGG-02967: Application {0} is down (gracefully).
The specified process stopped gracefully.
Action:
None
OGG-02968: Purged task Replicat group {0}.
The specified task was purged according to the rules in the PURGEOLDTASKS parameter.
Action:
None
OGG-02969: Purging task Replicat group {0}: could not delete file {1} ({2,number,0} {3}).
Manager could not purge the named remote task because it could not delete the specified file due to an operating system error.
Action:
Fix the operating system error.
OGG-02970: Task Replicat group {0} is running, cannot purge.
The specified task is still running.
Action:
Stop the task to enable purging.
OGG-02971: Terminate Extract group {0} failed ({1}),
The specified Extract cannot be terminated.
Action:
Look for additional error messages that indicate why the process cannot be terminated, and then correct the problem.
OGG-02972: Terminate Replicat group {0} failed ({1}),
The specified Replicat cannot be terminated.
Action:
Look for additional error messages that indicate why the process cannot be terminated, and then correct the problem.
OGG-02973: Stop of Extract group {0} failed ({1}).
The specified Extract cannot be stopped.
Action:
Look for additional error messages that indicate why the process cannot be stopped, and then correct the problem.
OGG-02974: Stop of Replicat group {0} failed ({1}).
The specified Replicat cannot be stopped.
Action:
Look for additional error messages that indicate why the process cannot be stopped, and then correct the problem.
OGG-02975: Application {0} is running.
The specified process is running.
Action:
None
OGG-02976: Extract group {0} stop forced by user.
The specified Extract process was stopped forcefully by a user.
Action:
None
OGG-02977: Replicat group {0} input trail file sequence number length can not be converted.
Checkpoint sequence number length can not be modified for the Replicat.
Action:
Do not attempt to convert the checkpoint sequence number length for the Replicat.
OGG-02978: Object table {0} with primary-key based Object Identifiers (OIDs) is unsupported.
Extract encountered an unsupported object table or XMLType table with primary-key based Object Identifiers (OIDs). Oracle GoldenGate supports tables with system-generated OIDs only.
Action:
Exclude the unsupport table from Extract.
OGG-02979: Invalid checkpoint configuration on SOURCEISTABLE initial load Extract.
SOURCEISTABLE initial load is created by GGSCI but the parameter file does not specify the Extract group name.
Action:
If SOURCEISTABLE is specified in the parameter file instead of Extract group name, replace the SOURCEISTABLE parameter with Extract group name. If Extract group name is specified, verify if the checkpoint exists.
OGG-02980: Trail file {0} not found or no last processed record found specified by trail file sequence number {1} and RBA {1}.
Trail file does not exist or no record matches the last processed record specified by sequence number and RBA.
Action:
Ensure that the valid sequence number and RBA are specified as last processed record position.
OGG-02981: Trail file {0} not found or no record matches to the transaction record, CSN: {1}, XID: {2}.
Trail file does not exist or no record matches the transaction record.
Action:
Ensure that the valid CSN and XID in the transaction are specified as start position.
OGG-02982: Trail file {0} not found or no record matches to the last processed transaction record, CSN: {1}, XID: {2}, record number in the transaction: {3}.
Trail file does not exist or no record matches the last processed transaction record.
Action:
Ensure that the valid CSN, XID and record number in the transaction are specified as last processed record position.
OGG-02983: No record matches to the last processed transaction record, CSN: {0}, XID: {1}, record number in the transaction: {2}.
No record matches the last processed transaction record while skipping already processed records after recovery. Primary Extract configuration may have changed or repositioned.
Action:
If Primary Extract configuration has been changed or repositioned, restore the previous configuration and restart from the last processed transaction.
OGG-02984: Found end of transaction in the trail file {0} while looking for the last processed transaction record, CSN: {1}, XID: {2}, record number in the transaction: {3}.
Unexpected end of the transaction found during startup position scanning for the last processed transaction record.
Action:
If Primary Extract configuration has been changed or repositioned, restore the previous configuration and restart from the last processed transaction.
OGG-02985: Either CSN or transaction ID or both tokens are missing in the first record of the transaction in the trail file {0}, RBA {1}.
CSN and/or XID GGS tokens are missing in the beginning of the transaction record.
Action:
Contact Oracle support.
OGG-02986: Error {0} reading trail file {1} while searching the transaction CSN {2}, transaction ID {3}, record number in the transaction {4}.
Trail file read error while looking for the specified transaction record.
Action:
Internal error. Contact Oracle support.
OGG-02987: Transaction unexpectedly ended in trail file {0} at RBA {1} while searching the CSN {2}, transaction ID {3}, record number in the transaction {4}.
Transaction ended unexpectedly when looking for the specified transaction record.
Action:
Check if the correct CSN, XID, or record number were specified for searching.
OGG-02988: CSN comparison error in trail file {0}, RBA {1}, CSN specified {2}, CSN from the trail file {3}.
CSN comparison error while looking for the specified transaction.
Action:
Check if correct CSN was specified.
OGG-02989: Cannot create external LOB file {0} ({1,number,0} {2}).
Failed to create external LOB file.
Action:
Check error detail and resolve the issue.
OGG-02990: Cannot create external LOB file directory {0} ({1,number,0} {2}).
Failed to create external LOB file directory.
Action:
Check error detail and resolve the issue.
OGG-02991: Cannot write external LOB file {0} ({1,number,0} {2}).
Failed to write external LOB file.
Action:
Check error detail and resolve the issue.
OGG-02992: Cannot delete external LOB file {0} ({1,number,0} {2}).
Failed to delete external LOB file.
Action:
Check error detail and resolve the issue.
OGG-02993: Trail header encoding is not supported for this configuration.
Trail header encoding is not supported.
Action:
Internal error. Contact Oracle GoldenGate support.
OGG-03000: Table {0} has a lower case ASCII, non-ASCII character or special character such as white space or dot that is not supported when NOEXTATTR option is specified.
DEFGEN was run with the NOEXTATTR parameter, and the specified table contains a lower case ASCII, non-ASCII or special character.
Action:
Exclude the table from the DEFGEN parameter file, or run DEFGEN without the NOEXTATTR parameter.
OGG-03001: Column {0} of table {1} has a lower case ASCII, non-ASCII character or special character that is not supported when NOEXTATTR option is specified.
DEFGEN was run with the NOEXTATTR parameter, and the column of the specified table contains a lower case ASCII, non-ASCII or special character, such as a white space or dot.
Action:
Exclude the table from the DEFGEN parameter file, or run DEFGEN without the NOEXTATTR parameter.
OGG-03002: Target table {0} does not exist. Inexact wildcard match table {1} is being used for target table.
No table name exactly matches the target wildcard specification. A table with a name that is an inexact match was used as the target.
Action:
None required.
OGG-03003: Target table {0} has a lower case ASCII, non-ASCII or special character, such as white space or dot, that is incompatible with trail format level {1}.
The name of the target table is incompatible with a trail format that is prior to the 11.2.1 release format.
Action:
Exclude or rename the table that is in the TARGET clause, or specify 11.2.1 or later for the FORMAT RELEASE option the of EXTTRAIL, RMTTRAIL, EXTFILE, or RMTFILE parameters.
OGG-03004: Unknown source column character set. Cannot map source column {0} to target column {1}
The trail file is written by Extract version 11.1 or earlier, but the SOURCECHARSET parameter isn't specified.
Action:
Specify the SOURCECHARSET parameter or do not map a CHAR/VARCHAR column to an NCHAR/NVARCHAR column.
OGG-03005: Unable to find matching parenthesis for token {0} at location {1}.
There is a syntax error in the parameter file.
Action:
Fix the syntax error in the token specification that contains incomplete parentheses.
OGG-03006: Source database character set or Target client character set is missing. OGG character set conversion is disabled.
Source database character set or Target client character set is missing.
Action:
Set up character set or Target client character set.
OGG-03007: Invalid or unsupported character set {0} specified with {1} parameter.
An invalid or unsupported character set is specified with the character set parameter.
Action:
Specify a valid character set, and then restart Replicat.
OGG-03010: Performing implicit conversion of column data from character set {0} to {1}.
Oracle GoldenGate is performing character set conversion because source data character set differs from target data character set.
Action:
None required.
OGG-03014: Source column {0} has more characters than target column {1} can hold. Some source characters will not be mapped during conversion from source character set {2} to target character set {3}.
The source column has more characters than the target column can hold.
Action:
Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03015: Character set conversion failure occurred between source column {0} and target column {1} when converting from source character set {2} to target character set {3}. Error code: {4}
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-03017: Target column {1} length becomes zero when converting from source column {0} character set {2} to target character set {3}.
This message is for sanity checking and should not occur in a production environment.
Action:
Contact Oracle Support.
OGG-03018: Alternative format data found (code = {0}). Character set conversion was not performed.
Data of an alternative format was processed. Examples are binary XML, XML diff, or partial LOB.
Action:
None
OGG-03019: The column that is being used to evaluate the WHERE clause or FILTER clause is missing in table {0}.
The column that is being used to evaluate the WHERE clause or FILTER clause is missing, and the process cannot perform the necessary filtering of the data.
Action:
Edit the WHERE or FILTER specification in the parameter file to specify a column that cannot contain a missing value.
OGG-03022: Unexpected return code {1} received while attempting to retrieve the {0} CCSID values.
SQLFetch returned an unexpected return code from select getvariable() for specified CCSID values.
Action:
Contact Oracle Support with the details from this message.
OGG-03023: {0} CCSID {1} is not recognized.
The CCSID value obtained from DB2 is not recognized by Oracle GoldenGate.
Action:
Contact Oracle Support with the details from this message.
OGG-03024: Character data marked as MIXED CCSID was encountered, but no TRAILCHARSET option was specified.
Character data marked as MIXED CCSID was encountered, but no TRAILCHARSET option was specified.
Action:
Add either TRAILCHARSETASCII, TRAILCHARSETEBCDIC, or TRAILCHARSETUTF8 in the Extract parameter file.
OGG-03025: The {0} character set specified for the A2E parameter in the GLOBALS file does not match the database CCSID.
The character set specified for the A2E parameter in the GLOBALS file does not match the database CCSID.
Action:
Either correct the charset specification for the A2E parameter in the GLOBALS file or edit the TABLE specification in the Extract parameter file to avoid processing tables with this native encoding.
OGG-03026: Unexpected return code {0} received while attempting to retrieve the APPLICATION ENCODING SCHEME.
An attempt to select the APPLICATION ENCODING SCHEME failed. This function is not supported prior to DB2 V9.1.
Action:
Ensure that the DEFAULT APPLICATION ENCODING SCHEME is EBCDIC.
OGG-03027: The DEFAULT APPLICATION ENCODING SCHEME is {0}. Only EBCDIC is supported.
The APPLICATION ENCODING SCHEME was determined to be a value other than EBCDIC.
Action:
Either change the value specified for CURRENTAPPENSCH in the ODBC initialization file to EBCDIC or remove the CURRENTAPPENSCH parameter.
OGG-03028: Table {0}, with {1} encoding, cannot be processed with {2} parameter specification.
A table was encountered with encoding that cannot be processed with the specified TRAILCHARSET parameter.
Action:
Correct the parameter file to either eliminate this table from processing or change the TRAILCHARSET specification to a value that supports the data in this table.
OGG-03029: Invalid source table name "{0}" specified.
An invalid source table name is specified in the TABLE/MAP parameter.
Action:
Specify the correct source table name.
OGG-03030: Invalid target table name "{0}" specified.
An invalid target table name is specified in the TABLE/MAP parameter.
Action:
Specify the correct target table name.
OGG-03031: Character set conversion is not supported in a data pump. Incoming ASCII data will not be converted to EBCDIC.
The character set of the input file does not match the character set of the platform on which the data pump is running.
Action:
Note that column data is ASCII and any attempt to process it as EBCDIC will likely fail.
OGG-03032: Character set conversion is not supported in a data pump. Incoming EBCDIC data will not be converted to ASCII.
The character set of the input file does not match the character set of the plat form on which the data pump is running.
Action:
Note that column data is EBCDIC and any attempt to process it as ASCII will likely fail.
OGG-03033: Character set conversion is not supported in a data pump.
The parameter EBCDICTOASCII was specified in the data pump parameter file.
Action:
Remove the parameter EBCDICTOASCII from the data pump parameter file.
OGG-03036: Database character set identified as {0}. Locale: {1}
The process verified the character set of the database. Informational only.
Action:
None
OGG-03037: Session character set identified as {0}.
The process verified the character set of the database connection. Informational only.
Action:
None
OGG-03038: Table {0}, column {1}, data type: {2} supported only for Unicode tables.
The data type shown is currently only supported for Unicode tables.
Action:
Exclude this table from Extract processing, either by removing its explicit specification in the TABLE parameter, or by using the TABLEEXCLUDE parameter if it was included as the result of a wildcard specification.
OGG-03039: Database character set {0} is not supported.
Database character set is not supported.
Action:
Contact Oracle Support.
OGG-03040: Session character set {0} is not supported.
Session character set is not supported.
Action:
Contact Oracle Support.
OGG-03041: Post-DDL command successful: {0}
Replicat is executing a post-DDL command.
Action:
None
OGG-03042: Character set value is not specified for defgen CHARSET parameter.
No value is specified for the Defgen CHARSET parameter.
Action:
Specify a character set for the CHARSET parameter in the Defgen parameter file.
OGG-03043: Character set value {0} specified for defgen CHARSET parameter is ignored.
The CHARSET parameter and the NOEXTATTR parameter are both specified in the Defgen parameter file. The CHARSET parameter is ignored.
Action:
Remove either NOEXTATTR or CHARSET.
OGG-03044: Invalid character set {0} is specified for defgen CHARSET parameter.
An invalid character set is specified for the Defgen CHARSET parameter.
Action:
Specify the correct character set for CHARSET.
OGG-03045: Character set {0} specified for defgen CHARSET parameter is not supported.
An unsupported character set is specified for the Defgen CHARSET parameter.
Action:
Specify a supported character set.
OGG-03046: The definitions file {0} is a version that does not support the extended attributes of character encoding and locale.
Defgen is in APPEND mode, and the existing contents are of an older format that does not include the extended attributes for character encoding and locale. For consistency, appended definitions will not have extended attributes.
Action:
Specify the Defgen parameter NOEXTATTR to cause Defgen to omit the extended attributes, or re-run Defgen for all tables to a new file if you want to include attributes that support character encoding and locale. See the Oracle GoldenGate documentation for more information on globalization support.
OGG-03047: Existing defs file {0} has extended attribute. NOEXTATTR parameter is ignored.
Defgen is in APPEND mode, and the existing contents are of the format that includes the extended attributes for character encoding and locale. For consistency, appended definitions will have extended attributes, and NOEXTATTR is being ignored.
Action:
Remove the NOEXTATTR parameter from the Defgen parameter file.
OGG-03048: Existing definitions file {0} is written in character set {1}. New definitions are being appended in the same character set.
Defgen APPEND mode is specified. For consistency, the new definitions are being appended in the same character set as those in the existing file.
Action:
None
OGG-03049: Existing defs file {0} is written in character set {1}. CHARSET parameter value {2} is ignored.
Defgen APPEND mode is specified. The character set specified by the CHARSET parameter is different from the one used in the existing definitions file and is being ignored.
Action:
None
OGG-03050: Existing definitions file {0} has invalid character set name or the file is corrupted.
The existing definitions file has an invalid character set. The character set tag may be incorrect, or the file may be corrupted.
Action:
Fix the character set tag if it is wrong, or create a new definitions file to replace to corrupt one.
OGG-03051: Invalid character set {0} is specified for defgen UPDATECS parameter.
An invalid character set is specified for the Defgen UPDATECS parameter.
Action:
Specify the correct character set.
OGG-03052: Definitions file is encoded in character set {0}. No character set update is necessary.
The definitions file is already encoded in the character set specified by the Defgen UPDATECS parameter.
Action:
None
OGG-03053: Cannot open the definitions file {0} to update the character set. Check file attributes and user permissions.
The definitions file may be read-only, or the Defgen user does not have permission to modify the file.
Action:
Change the attributes of the file or give the Defgen user write permission.
OGG-03054: The character set of definitions file {0} was updated from {1} to {2}.
The Defgen parameter UPDATECS is specified, and the character set of the definitions file was updated successfully.
Action:
None
OGG-03055: Failed to update character set of definitions file {0} from {1} to {2}. {3}
The disk may be full or the Defgen user does not have permission to write to the definitions file.
Action:
Make sure there is enough disk space for the definitions file, and make sure the Defgen user has full permissions on the file.
OGG-03056: Source table {0} column {1} data size exceeds the maximum target table {2} column {3} size. Automatic truncation is enabled for all tables/columns without further warnings.
The source column data size exceeds the maximum target column size.
Action:
Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03057: Unexpected error code {0} while converting column {1} of table {2} from {3} to {4}.
An unexpected error was encountered during character set conversion.
Action:
Contact Oracle Support.
OGG-03059: Operating system character set identified as {0}.
The process verified the character set of the operating system. Informational only.
Action:
None
OGG-03060: Source column {0} has more characters than target column {1} can hold. Some source characters will not be mapped during source column character validation of character set {2}.
The source column has more characters than the target column can hold.
Action:
Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03061: Character validation failure occurred between source column {0} and target column {1} when validating source column data that is in character set {2}. Error code: {3}
An internal error occurred during character validation.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-03062: Source column {0} contains an invalid character. Cannot write to XML file to convert from source character set {1} to XML encoding {2}.
The source column contains an invalid character and cannot be converted to XML file encoding.
Action:
Do any of the following: Specify another XML encoding, fix the source database data, or use the REPLACEBADCHAR parameter to replace the invalid character.
OGG-03063: Cannot write source column {0} to XML file during conversion from source character set {1} to XML encoding {2}. The source character set is not supported.
The specified column could not be written to an XML file because Oracle GoldenGate does not support the source character set.
Action:
Contact Oracle Support.
OGG-03064: Character set conversion failure occurred between source column {0} and XML file when converting from source character set {1} to XML encoding {2}. Error code: {3}
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-03065: Source column {0} has more characters than the maximum number of characters that target column {1} can hold. Some source characters will not be mapped during conversion from source character set {2} to target character set {3}.
The source column has more characters than the target column can hold.
Action:
Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03066: Source column {0} has more characters than the maximum number of characters that target column {1} can hold. Some source characters will not be mapped during source column character validation of character set {2}.
The source column has more characters than the target column can hold.
Action:
Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03067: Source Oracle database character set {0} is not supported.
The source Oracle database character set is not supported for this database and platform.
Action:
Contact Oracle Support.
OGG-03068: Could not initialize large object memory pool.
This is internal error, failed to initialize memory pool object for large object (LOB).
Action:
Contact Oracle Support.
OGG-03069: Unexpected LOB chunk ({0}) found. Expected chunk is 1.
Unexpected LOB chunk found in the trail file. Trail file may be corrupted.
Action:
Check if the trail file has base DML record followed by LOB chunk 1 using logdump. Contact Oracle Support.
OGG-03070: Failed to add LOB chunk in {0}, RBA {1}.
Failed to add LOB chunk into LOB memory.
Action:
Check additional error detail and contact Oracle Support.
OGG-03071: Unexpected LOB record, record fragment or out of row LOB marker in {0}, rba {1}
Unexpected LOB record found in the trail file. Trail file may be corrupted.
Action:
Check additional error detail and contact Oracle Support.
OGG-03072: NLS_LENGTH_SEMANTICS CHAR is specified. All column mapping functions takes string arguments use character semantics.
NLS_LENGTH_SEMANTICS CHAR is specified for Extract or Replicat parameter.
Action:
None
OGG-03073: TRANLOGOPTIONS EXCLUDETAG and INCLUDETAG can not be specified together.
Exclude tag and include tag options are specified together.
Action:
Remove one option or specify all tags using + for EXCLUDETAG.
OGG-03074: Standalone INCLUDETAG parameter is specified for a Primary Extract.
INCLUDETAG as a standalone parameter is only valid for data pump and Replicat.
Action:
Specify INCLUDETAG as a TRANLOGOPTIONS option for Primary Extract, or use it as a standalone parameter for data pump or Replicat.
OGG-03075: Unable to use {0} as input for the INCLUDETAG parameter. A valid hex value is expected.
An invalid value was used as input for the INCLUDETAG parameter.
Action:
Specify a valid hex value as input for the INCLUDETAG parameter, for example FF.
OGG-03076: Tags {0} length specified by TRANLOGOPTIONS EXCLUDETAG exceeds maximum length of {1}.
Tag length specified by EXCLUDETAG exceeds maximum length allowed.
Action:
Reduce tag names to exclude or remove TRANLOGOPTIONS EXCLUDETAG parameter.
OGG-03077: EXCLUDETAG and INCLUDETAG can not be specified together.
Exclude tag and include tag options are specified together.
Action:
Remove one option or specify all tags using + for EXCLUDETAG.
OGG-03098: Failed to parse extended session information GGS token. Length: {0}.
Extended session information token may be corrupted.
Action:
Internal error. Contact Oracle GoldenGate support.
OGG-03506: The source database character set, as determined from the trail file, is {0}.
The source database character set information in the trail file is being assumed as the source database character set.
Action:
None
OGG-03507: The source database character set is {0} as specified by SOURCECHARSET.
The trail file version is pre-11.2.1, so the character set that is specified with the SOURCECHARSET parameter is assumed as the source database character set.
Action:
None
OGG-03508: SOURCECHARSET PASSTHRU is specified. Ignoring the source database character set.
The SOURCECHARSET PASSTHRU parameter is specified, which directs the process to pass the data as it exists in the trail record, without performing character set conversion.
Action:
None
OGG-03509: Using NLS_LANG character set {0} as the source database character set.
The version of the trail file is pre-11.2.1 and the SOURCECHARSET parameter is not specified. To assign a character set to the source data, Replicat used the character set that is specified with the NLS_LANG variable.
Action:
Specify the source database character set with the SOURCECHARSET parameter.
OGG-03510: The source database character set is unknown, and the SOURCECHARSET parameter is not specified.
The trail file does not have source character set information and the SOURCECHARSET parameter is not specified. Replicat cannot map the source character data to the target database.
Action:
Specify the source database character set with the SOURCECHARSET parameter.
OGG-03515: Source character set {0} is specified with the SOURCECHARSET parameter.
The SOURCECHARSET parameter is being used to specify the character set of the source data.
Action:
None
OGG-03516: The trail file is version 11.2.1 or later and contains the source character set {1}. The SOURCECHARSET {0} parameter will be ignored.
Because the trail file is version 11.2.1 or later and contains the source character set, the SOURCECHARSET parameter is unnecessary and is being ignored.
Action:
Remove SOURCECHARSET parameter.
OGG-03517: Conversion from character set {2} of source column {0} to character set {3} of target column {1} failed because the source column contains a character that is not available in the target character set.
The source column contains a character that is not available in the character set of the target column.
Action:
Set the target database character set to the same set or a superset of the source database character set.
OGG-03518: Source column {0} cannot be mapped to target column {1} during conversion from source character set {2} to target character set {3}, because the source or the target character set is not supported.
Either source or target column character set is not supported.
Action:
Contact Oracle Support
OGG-03519: Found NCHAR, NVARCHAR2 or NCLOB attribute in user-defined datatype but the required HAVEUDTWITHNCHAR parameter is missing.
The source database has a user-defined datatype with the NCHAR, NVARCHAR2 or NCLOB attribute, but the HAVEUDTWITHNCHAR parameter is not specified in the Replicat parameter file.
Action:
Add the HAVEUDTWITHNCHAR parameter to the Replicat parameter file.
OGG-03520: Connecting to the Oracle database using the AL32UTF8 client character set to support a user-defined type that has an NCHAR, NVARCHAR2 or NCLOB attribute.
The HAVEUDTWITHNCHAR parameter is specified to support user-defined datatypes that have an NCHAR, NVARCHAR2 or NCLOB attribute.
Action:
None
OGG-03521: Invalid character for character set {0} was found while performing character validation of source column {1} maps target column {2}.
An invalid character was found in the source column.
Action:
Fix the source database data or use the REPLACEBADCHAR parameter to replace the invalid character.
OGG-03522: Setting session time zone to source database time zone '{0}'.
Replicat is setting its session time zone to the source database time zone.
Action:
None
OGG-03523: Failed to set session time zone to source database time zone '{0}'.
Replicat could not set its session to the specified time zone. Either the specified value is invalid or the target database does not support that time zone.
Action:
You can do one of the following, depending on the Extract version: If Extract is pre-12.1.2, use the SOURCETIMEZONE parameter to specify a time zone that is supported by the target database. If Extract is 12.1.2 or later, you can use the PRESERVETARGETTIMEZONE parameter to ignore the source database time zone (the Replicat default) and direct Replicat to use the target time zone in its session, or you can use the SOURCETIMEZONE parameter to direct Replicat to use a specific time zone.
OGG-03524: Invalid or unsupported time zone '{0}' is specified by SOURCETIMEZONE parameter.
The specified time zone is not valid or is not supported by Replicat.
Action:
Specify a valid source database time zone.
OGG-03525: Invalid or unsupported time zone '{0}' in trail file.
The source database time zone in the trail file is not supported by this release of Replicat.
Action:
Specify the source time zone with the SOURCETIMEZONE parameter or use PRESERVETARGETTIMEZONE to ignore the source time zone and use the target time zone for the Replicat session.
OGG-03526: The source database character set is specified for DB2 z/OS trail version 9.0/9/5 by SOURCECHARSET.
SOURCECHARSET DB2ZOS is specified, and replicat assumes the trail file version is 9.0/9.5 and is written by an Extract capturing from DB2 z/OS.
Action:
None
OGG-03527: Ignoring the invalid source database character set specified for DB2 z/OS trail version 9.0/9.5 by SOURCECHARSET.
The source database character set is specified for DB2 z/OS trail version 9.0/9.5. However the trail file version is not 9.0/9.5 or not written by an Extract for DB2 z/OS.
Action:
Remove the SOURCECHARSET parameter from Replicat parameter file.
OGG-03528: The source database character set, as determined from the table definition file, is {0}.
The source database character set information in the table definition file is being assumed as the source database character set. The source database character set may be overwritten by the source database character set information in the trail file.
Action:
None
OGG-03529: The source character set name is missing for the SOURCECHARSET parameter
The SOURCECHARSET parameter is specified without requiring character set name.
Action:
Specify the character set name.
OGG-03530: The SOURCECHARSET OVERRIDE {0} parameter is specified. The trail file is version 11.2.1 or later and contains the source character set {1} will be ignored.
Because the SOURCECHARSET parameter is specified with OVERRIDE option, the source character set of the trail file is ignored.
Action:
None
OGG-03531: Conversion from character set {1} of SQLEXEC parameter {0} to character set {2} failed because the source column contains a character that is not available in the target character set.
The source data contains a character that is not available in the character set of the target during SQLEXEC data conversion.
Action:
Set the target database character set to the same set or a superset of the source database character set.
OGG-03532: Conversion from character set {1} of column {0} to character set {2} failed because the source column contains a character that is not available in the target character set.
The source data contains a character that is not available in the character set of the target during column mapping conversion.
Action:
Set the target database character set to the same set or a superset of the source database character set.
OGG-03533: Conversion from character set {4} of source column {2} to character set {5} of target column {3} failed because the source column contains a character '{0}' at offset {1} that is not available in the target character set.
The source column contains a character that is not available in the character set of the target column.
Action:
Set the target database character set to the same set or a superset of the source database character set.
OGG-03534: Invalid character '{0}' at offset {1} for character set {2} was found while performing character validation of source column {3} maps target column {4}.
An invalid character was found in the source column.
Action:
Fix the source database data or use the REPLACEBADCHAR parameter to replace the invalid character.
OGG-03535: Conversion from character set {2} of column {1} to character set {3} in function {0} failed because the source column contains a character that is not available in the target character set.
The source data contains a character that is not available in the character set of the target during column mapping function conversion.
Action:
Set the target database character set to the same set or a superset of the source database character set.
OGG-03536: Conversion from character set {4} of source column {2} to character set {4} failed because the source column contains a character '{0}' at offset {1} that is not available in the target character set.
The source column contains a character that is not available in the target character set.
Action:
Check the source column data and repair the data if the source column contains a partial character or an invalid character. Alternatively, use the REPLACEBADCHAR option to replace, escape, or skip the invalid character.
OGG-03537: Source column {0} cannot be mapped to target during conversion from source character set {1} to target character set {2}, because the source or the target character set is not supported.
Either the source or the target column character set is not supported.
Action:
Contact Oracle Support.
OGG-03538: Source column {0} has more characters than target can hold. Some source characters will not be mapped during conversion from source character set {1} to target character set {2}.
The source column has more characters than the target can hold and the source column data was truncated during mapping.
Action:
None
OGG-03539: Character set conversion failure occurred between source column {0} and target when converting from source character set {1} to target character set {2}. Error code: {3}
An internal error occurred during the character set conversion.
Action:
Save the error message and contact Oracle Support.
OGG-03540: The {0} statement is ignored.
The process ignores the specified SETENV statement because setting ORACLE_HOME and ORACLE_SID is not needed.
Action:
None
OGG-03541: Oracle Environment Variables: {0}
Report Oracle environment variables.
Action:
None
OGG-03542: Failed to connect to the database. Verify that the connection string and following environment variables are correct: {0}
Report Oracle environment variables after a database connection failure.
Action:
Ensure that the correct user ID and password have been provided. If the connect string did not include TNS alias then either provide an alias or set the TWO_TASK environment variable to that alias. Also make sure that the TNS_ADMIN environment variable is set to the correct location.
OGG-03543: Failed to validate character boundary on column {0} that character set is {1}. Error code: {2}.
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-03544: Character set conversion failure occurred on column {0} when converting from column character set {1} to character set {2}. Error code: {3}.
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-04000: VAM module attempted to retrieve Conflict Detection Resolution column indexes for deletes from GG_ATTR_MD_CDRCOLS_DEL array, but none are available (GG_ATTR_MD_CDRCOLS_COUNT_DEL =0).
The VAM module failed to retrieve the column array of the indexes that represent the Conflict Detection Resolution columns for deletes in the table. GG_ATTR_MD_CDRCOLS_COUNT_DEL gives the number of delete CDR column indexes in the array; if zero, no indexes exist. In this case, a call to GG_ATTR_CDRCOLS_DEL should not be made. This is a development error that may require a bug report.
Action:
Contact Oracle Support.
OGG-04001: VAM module attempted to retrieve Conflict Detection Resolution column indexes for updates from GG_ATTR_MD_CDRCOLS_UPD array, but none are available (GG_ATTR_MD_CDRCOLS_COUNT_UPD =0).
The VAM module failed to retrieve the column array of the indexes that represent the Conflict Detection Resolution columns for updates in the table. GG_ATTR_MD_CDRCOLS_COUNT_UPD gives the number of update CDR column indexes in the array; if zero, no indexes exist. In this case, a call to GG_ATTR_CDRCOLS_UPD should not be made. This is a development error that may require a bug report.
Action:
Contact Oracle Support.
OGG-04002: VAM module set the three CDR and compression related parameters incorrectly.
The VAM module set the three CDR and compression related parameters incorrectly. When GG_ATTR_VAMMOD_CDR_SUPPORTED is set to GG_VALUE_TRUE, both GG_ATTR_VAMMOD_CDEL_SUPPORTED and GG_ATTR_VAMMOD_CUPD_SUPPORTED need to be set to GG_VALUE_TRUE. CDR processing in VAM module while delete and update compression in VAM API is not a supported scenario. This is a development error that may require a bug report.
Action:
Contact Oracle Support.
OGG-04003: Initialization of user module failed: Callback functions must be implemented
The VAM module in Extract failed to initialize.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04004: Object {0}.{1}.{2} does not exist in data source
An invalid table was encountered in the VAM Module Application Framework in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04005: Invalid value encountered in case statement: {0}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04006: Call to function {0} to load library {1} failed.
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04007: Call to {0} failed to retrieve the address of {1}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04008: Invalid CDR setting attribute value {2} for the object {0}, attribute {1}.
A CDR validation error occurred when checking the CDR processing parameters. Please check the message for details.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04009: Column index {0}: {1} returned with error status {2}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04010: Object {0}: Attribute {1}: Maximum number of columns exceeded
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04011: Object {0}: Attribute {1}: {2} returned with length {3}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04012: Object {0}: Attribute {1}: {2} returned with error status {3}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04013: Object {0}: Attribute {1}: {2} returned with value {3}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04014: Object {0}: Attribute GG_ATTR_OP_COMPLETE: GGAttrGet returned with missing attribute {1}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04015: {0}
An internal logic error occurred in the VAM Simulator Module in Extract.
Action:
Review the error message and take appropriate action, or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04016: Object {0}: Column Index {1}: Column Format {2}: {3} returned with error status {4}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04017: Object {0}: Record Type {1}: Transaction ID {2}: Transaction ID does not exist in transaction lookup table
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04018: Object {0}: Record Type {1}: Transaction ID {2}: Transaction ID already exists in transaction lookup table
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04019: No metadata was found for {0}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04020: Unexpected condition in function {0} at line {1,number,0}.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-04021: VAM module must support CDR in order to send unified trail records via the VAM API.
To support unified trail records, the GG_ATTR_VAMMOD_CDR_SUPPORTED attribute of the VAM must be set. This indicates that the VAM supports CDR handling.
Action:
Remove UPDATERECORDFORMAT [FULL/COMPACT] from the Extract parameter file. If this error still occurs, contact Oracle Support or, if you are a developer, contact the VAM module development team.
OGG-04022: VAM module must support CDR in order to send unified trail records via the VAM API.
To support unified trail records, the GG_ATTR_VAMMOD_CDEL_SUPPORTED attribute of the VAM must be set. This indicates that the VAM supports CDR handling.
Action:
Remove UPDATERECORDFORMAT [FULL/COMPACT] from the Extract parameter file. If this error still occurs, contact Oracle Support or, if you are a developer, contact the VAM module development team.
OGG-04023: VAM module must support compressing updates in order to send unified trail records via the VAM API.
To support unified trail records, the GG_ATTR_VAMMOD_CUPD_SUPPORTED attribute of the VAM must be set. This indicates that the VAM supports CDR handling.
Action:
Remove UPDATERECORDFORMAT [FULL/COMPACT] from the Extract parameter file. If this error still occurs, contact Oracle Support or, if you are a developer, contact the VAM module development team.
OGG-04024: GG_OBJ_RECORD: GG_ATTR_BEFORE_AFTER can only be used with GG_OPTYPE_UPDATE_UNIFIED for unified trail records
The VAM module tried to add a before key column for a record that is not a primary key update.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04025: CHECKOPCOMPLETE: No before columns in a unified update were added for operation type: {0,number,0}
No before image key fields were sent for a unified update record being passed to the VAM API.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04026: CHECKOPCOMPLETE: Before column(s) in primary key update were added that are not a primary key column: {1}: Operation type: {0,number,0}
Before image columns were sent for a primary key update record being passed to the VAM API that are not primary key columns.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-04027: Source record exceeds the size of the output buffer used to assemble trail file records. The length required was {0,number,0} but the maximum length allowed is {1,number,0}.
The size of the output buffer used to hold the internal record written to the trail file is not large enough to contain the record that was sent to the VAM API.
Action:
Contact Oracle Support.
OGG-04028: COMPRESSUPDATES is ignored since LOGALLSUPCOLS has been specified.
LOGALLSUPCOLS parameter takes precedence over COMPRESSUPDATES.
Action:
None
OGG-04029: NOCOMPRESSUPDATES is ignored for the before image of the update to table {0} because GETBEFORECOLS has been specified.
GETBEFORECOLS parameter takes precedence over COMPRESSUPDATES.
Action:
None
OGG-04030: NOCOMPRESSUPDATES is ignored for the after image of the update to table {0} because UPDATERECORDFORMAT COMPACT has been specified.
UPDATERECORDFORMAT COMPACT takes precedence over NOCOMPRESSUPDATES for the after image of the update to the table.
Action:
None
OGG-04031: UPDATERECORDFORMAT FULL is ignored since COMPRESSUPDATES has been specified for table {0}.
COMPRESSUPDATES parameter takes precedence over UPDATERECORDFORMAT FULL.
Action:
None
OGG-04032: LOGALLSUPCOLS has set the NOCOMPRESSDELETES, NOCOMPRESSUPDATES and GETUPDATEBEFORES parameters on.
The LOGALLSUPCOLS settings take precedence over the previous settings of [NO]COMPRESSDELETES, [NO]COMPRESSUPDATES and [GET/IGNORE]UPDATEBEFORES.
Action:
None
OGG-04033: LOGALLSUPCOLS has set the NOCOMPRESSDELETES and GETUPDATEBEFORES parameters on.
The LOGALLSUPCOLS settings take precedence over the previous settings of [NO]COMPRESSDELETES and [GET/IGNORE]UPDATEBEFORES.
Action:
None
OGG-04034: Column {1} in table {0} has a data type of SYS.ANYDATA with an opaque value and cannot be mapped using column mapping.
The value of a SYS.ANYDATA column is opaque, which means the data type is held along with the value internally. Because the value is not visible to Oracle GoldenGate, the column cannot be mapped.
Action:
Do not use column mapping on tables containing SYS.ANYDATA columns.
OGG-04035: To replicate SYS.ANYDATA columns using fetch requires an Oracle GoldenGate release of 12.1 or higher. The trail file compatibility setting is set to level {0}, a compatibility level of {1} or above is required.
Using the fetch-based functionality to replicate SYS.ANYDATA columns requires an Oracle GoldenGate release of 12.1 or higher.
Action:
Replication of SYS.ANYDATA columns requires Oracle GoldenGate release of 12.1 or higher.
OGG-04036: Positioning sequence ID is out of order, old sequence ID is {0}, new sequence ID is {1}.
The positioning sequence number should remain the same or increase rather than decrease.
Action:
If you are working with an Oracle GoldenGate Developer, contact that person or contact Oracle Support.
OGG-04037: GG_OBJ_RECORD: {0} must be set.
A required attribute in the VAM API record object was not set.
Action:
If you are working with an Oracle GoldenGate Developer, contact that person or contact Oracle Support.
OGG-04038: Object {0}: Callback {1} returned with error status {3}.
An internal logic error occurred in the VAM module in Extract.
Action:
If you are working with an Oracle GoldenGate Developer, contact that person or contact Oracle Support.
OGG-04039: NOLOGALLSUPCOLS has reset the NOCOMPRESSDELETES and GETUPDATEBEFORES parameters.
The NOLOGALLSUPCOLS settings take precedence over the previous settings of [NO]COMPRESSDELETES and [GET/IGNORE]UPDATEBEFORES.
Action:
None
OGG-04040: Error ({0,number,0}, {1}) start select object id for (2) in {3}
Parse and binding on one of the internal queries failed.
Action:
Contact Oracle Support.
OGG-04041: Error ({0,number,0}, {1}) selecting objectid for (2) in {3}
An error occurred when fetching data from an internal cursor.
Action:
Contact Oracle Support.
OGG-04042: The session context has not been initialized
This is an internal error.
Action:
Contact Oracle Support.
OGG-04043: Cannot map column {0} to {1}. The source data type is incompatible with {2}.
The Source data type is incompatible with target data type.
Action:
Use the column function to transform source data type to a number or string type that is compatible with target data type.
OGG-04044: A catalog name is required in order to alter the session and set the new PDB container
This is an internal error.
Action:
Contact Oracle Support.
OGG-04045: Identity columns are only supported when the Integrated Dictionary is in use.
Identity columns are being used, but Extract is not configured to use the Integrated Dictionary.
Action:
Exclude replication of the operation or configure Extract to capture in integrated mode and to use the Integrated Dictionary.
OGG-04046: Begin transaction - transaction {0} is detected while processing a committed transaction {1}
A new begin transaction is received while currently processing a committed transaction.
Action:
If you are working with an Oracle GoldenGate developer, then contact that person or contact Oracle Support.
OGG-04047: Record at {0} has transaction id {1} that doesn't match with the committed transaction id {2}
The record has a mismatch transaction id with the committed transaction's id that is currently being processed.
Action:
If you are working with an Oracle GoldenGate developer, then contact that person or contact Oracle Support.
OGG-04048: Processed graceful restart record at seq {0} rba {1}.
A graceful restart record from a trail file has been processed by Replicat at the given sequence number and rba.
Action:
None required.
OGG-04049: Detected metadata mismatch for column {0} of type {1}, in table {2}. Expected length {3}, actual length {4}.
There is a mismatch between metadata and data for column.
Action:
Contact Oracle Support.
OGG-04501: Charset information: Client charset: [{0}], Database/Server charset: [{1}], CHARSETCONVERT: [{2,choice,0#OFF│1#ON}].
Oracle GoldenGate is performing character set conversion. This message shows the source and target character sets, and the conversion set.
Action:
None required.
OGG-04502: The client charset: {0} is not supported.
The character set that is used in the client is deprecated by Sybase or is not supported by Oracle Goldengate.
Action:
See the Sybase and Oracle GoldenGate documentation for supported character sets.
OGG-04503: The server charset: {0} is not supported.
The character set that is used in the database server is deprecated by Sybase or is not supported by Oracle Goldengate.
Action:
See the Sybase and Oracle GoldenGate documentation for supported character sets.
OGG-04504: Sybase warning 2401 occurred. Conversion of the character set can not be performed between the client and the server. This may break data integrity. Using default settings for the conversion: Client charset: [{0}], Database/Server charset: [{1}], CHARSETCONVERT: [OFF].
The process cannot force a conversion between the different client and server character sets because the Sybase server cannot interpret some of the client characters.
Action:
Change the client or server character set to one that fixes the Sybase message 2401 and enables conversion.
OGG-04505: Wildcards not supported for database user.
The wildcard for the specified user is not supported. Check the database login configuration and also make certain _ALLOWWILDCARDSCHEMAS is used in the GLOBALS file.
Action:
See the rules for schema wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.
OGG-04506: Failed to convert source data type {2} to target data type {3} for column "{1}" in table "{0}".
These two data types are not compatible for character set conversion.
Action:
Use the following Replicat parameter to ignore this conversion: reperror(error_number, ignore), where error_number is the error number returned from the database. If the problem persists, contact Oracle Support.
OGG-04507: Legacy {0} functionality started at the request of an Oracle GoldenGate user
The specified functionality was started by the VAM. Informational only.
Action:
None
OGG-04508: Oracle GoldenGate is searching the Sybase CS library version that is to be used. Please ignore any error that is reported by Sybase as a part of this search process
Oracle GoldenGate is searching the Sybase CS library version that it needs to use.
Action:
You can ignore any error that is reported by Sybase as a part of this search process.
OGG-04510: {0}
The specified database error occurred. The cause can be any of the following: Unknown user or invalid password, unknown host machine, server name not in interface file, maximum number of connections already established, sufficient memory not available, or cannot open the interface file. Another cause could be that the Adaptive Server is unavailable, does not exist, or is not configured.
Action:
Take any actions based on the problem: Check the user name and password, and make sure the user exists in the database. Make certain the interface file exists and that Oracle GoldenGate can access it. Make certain the server name in the interface file is correct, or try adding another entry for the host machine , but use the IP address instead of the name. Make certain the Adaptive Server is configured in the local machine where Oracle GoldenGate is running. Increase the number of connections permitted to the database. Free up storage in the network layer and free up system memory. If the problem persists, see the instructions in the Oracle GoldenGate report file or contact Oracle Support.
OGG-04511: The current Sybase database version is not supported for the BatchSQL feature; Sybase ASE 15.7 ESD 4 (SP110) or greater is required.
BatchSQL is not supported with the current version of the Sybase database.
Action:
See Installing and Configuring Oracle GoldenGate for Sybase for a list of supported Sybase database versions.
OGG-04512: Sybase database version ASE 15.7 ESD 4 (SP110) and greater is required to support the BatchSQL feature.
BatchSQL is only supported with Sybase version ASE 15.7 ESD 4 (SP110) and greater.
Action:
Ensure that a supported Sybase version is installed. See Installing and Configuring Oracle GoldenGate for Sybase for a list of supported Sybase database versions.
OGG-04514: The log transfer context for the current database({1}) is already reserved by previous instance of Oracle GoldenGate extract process{0}.SQL Error text ({2}).Grant SA_ROLE to Oracle GoldenGate replication user to release the log transfer context.Alternatively,the log transfer context can be released manually with SA_ROLE user by finding SPID of the process using sql query (select SPID from master..sysprocesses where dbid=db_id('dbName') and program_name = 'GG_SYBLTM') and then terminating the process by ASE provided kill command eg 'kill SPID'.
Oracle GoldenGate Extract process has reserved the log transfer context of the database due to abnormalities in ASE such as crash, forceful termination, slowness in response of the server, the log transfer context reserved during startup is not released by previous instance Oracle GoldenGate extract process, hence the next start of extract will fail with the above error.
Action:
Grant the Oracle GoldenGate database replication user with SA_ROLE to terminate the extract process that has reserved the log context.
OGG-04521: Stopping at the request of a user exit.
Stopping at the request of a user exit. Informational only.
Action:
None
OGG-04522: Unable to determine user exit compatibility level. {0} running with user exit library {1}, using default compatibility level ({2}).
The process could not determine the compatibility level of the user exit. The default compatibility level is being used. Informational only.
Action:
None
OGG-04523: {0} running with user exit library {1}, compatibility level ({2}) is not current, using compatibility level ({3}).
The user exit compatibility level is not current. The specified compatibility level will be used.
Action:
None
OGG-04524: {0} running with user exit library {1}, compatibility level ({2}) is current.
The user exit compatibility level is current. Informational only.
Action:
None
OGG-04525: {0} running with user exit library {1}, current session character set is {2}.
The specified user exit library and session character set are in use. Informational only.
Action:
None
OGG-04526: {0} running with user exit library {1}. Current session character set is operating system default character set.
The user exit session character set is the operating system default character set. Informational only.
Action:
None
OGG-04527: The character set of the data source or the session could not be determined. Using ULIB_CS_DEFAULT. No character set conversion is performed for column data.
The character set of the data source or the session could not be determined. The default operating system character set is being used.
Action:
None
OGG-05000: There is no MySQL database character set corresponding to ULibCharset {0}
A character set is specified in the SOURCEDB or TARGETDB parameter that is not supported by MySQL.
Action:
Specify a character set that is supported by MySQL. If the problem persists, contact Oracle GoldenGate Support.
OGG-05001: Invalid sequence identifier length encountered. The current sequence identifier length:{0} must be equal to or greater than the length of its predecessor:{1}
The length of the new sequence identifier is not equal to or greater than the previous sequence identifier length.
Action:
Contact Oracle Support.
OGG-05002: GoldenGate does not support MySQL column character set {0} for column:"{1}" of table:"{2}".
A character set specified for the column in a MySQL table is not supported by GoldenGate.
Action:
If the character set is listed in the MySQL documentation as a supported character set please contact Oracle Support and request that GoldenGate implements its support. As a possible workaround consider using an alternative character set if possible.
OGG-05003: Schema name or table name is empty while trying to fetch metadata.
Without the schema and table name, it is not possible to fetch metadata from the history table.
Action:
Undefined
OGG-05004: Out of range value ({1}) for column {0} of type {2} for table {3}. Supported range is ({4})
The specified column contains a data value that is out of range and is not supported by Oracle GoldenGate for MySQL.
Action:
Remove or modify values that contain unsupported data values from the Oracle GoldenGate configuration. For supported data ranges, see Using Oracle GoldenGate for Heterogeneous Databases.
OGG-05005: Userid {0} invalid
The specified USERID in USERIDALIAS is not supported by Oracle GoldenGate for MySQL.
Action:
Supported USERID formats are: 1) user/db 2) user@host/db 3) user@host:port/db Create or modify the USERIDALIAS with USERID that confirms the supported userid formats as given above.
OGG-05006: MySQL Error {1} (status = {0,number,0}). {2}
An error occurred while executing the MySQL Query.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-05007: MySQL Error {1} (status = {0,number,0})
An error occurred in the executing MySQL Query.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-05008: Query to get the case sensitivity information failed.
An error occurred while accessing lower_case_table_names variable in MySQL
Action:
Undefined
OGG-05009: Query to get the case sensitivity information: Result returned no value.
The variable name used for fetching case sensitivity was not found in MySQL DB. Please contact Oracle Support.
Action:
Undefined
OGG-05010: Query to get the case sensitivity information: Row returned no value.
The lower_case_table_names variable is not configured in MySQL. Please contact Oracle Support.
Action:
Undefined
OGG-05016: Capture is configured for gtid based recovery, can not use Lognumber and offset based position sequenceid {0}.
The capture is restarted after changing configuration to support lognumber-offset based recovery in previous run to gtid based recovery in the current run.
Action:
Undefined
OGG-05017: Capture is configured for lognumber offset based recovery, can not use gtid based position sequenceid {0}.
The capture is restarted after changing configuration to support the gtid based recovery in previous run to lognumber-offset based recovery in the current run.
Action:
Undefined
OGG-05018: Invalid argument {0} provided for TRANLOGOPTIONS ALTLOGDEST in capture parameter file.
The valid argument values of TRANLOGOPTIONS ALTLOGDEST are either REMOTE or the complete path for the binlog index file."
Action:
To run the local capture specify the full path of the binlog index file as the argument value to the TRANLOGOPTIONS ALTLOGDEST. To run the remote capture specify TRANLOGOPTIONS ALTLOGDEST REMOTE.
OGG-05019: Enabling autocommit mode
The query to set the auto-commit variable (autocommit=1) failed.
Action:
Make certain the user has the appropriate privilege to perform this operation, and make certain that the MySQL server is running.
OGG-05020: The CSN value read from the trail file does not match the MySQL CSN format of <sequence-number>:<gtid>: {0}.
The CSN value in the trail file is corrupted.
Action:
Check the operating system kernel messages and system logs for I/O error.
OGG-05101: Cannot specify both ETOLDFORMAT and ENCRYPTTRAIL for '{0}'
The Extract parameter ETOLDFORMAT is specified with the ENCRYPTTRAIL parameter.
Action:
Remove ENCRYPTTRAIL from the parameter file.
OGG-05102: Retrying logon to Oracle database after previous attempt failed.
The process could not log on to the Oracle database because of a database error that showed the database is in the process of starting up or shutting down. The process will try the operation again.
Action:
No action needed.
OGG-05103: Unrecognized field type ({1}) for column {0}
The specified column contains a data type that is not supported by Oracle GoldenGate MySQL.
Action:
Remove tables or columns that contain unsupported data types from the Oracle GoldenGate configuration. For supported data types, see Installing and Configuring Oracle GoldenGate for MySQL.
OGG-05105: The SSL client Certificate Authority is required for Mode {0}.
The certificate Authority information is required for this mode
Action:
Specify the sslCa option along with the SSL parameters in the connection string.
OGG-05106: The SSL client client certificate is required for Mode {0}.
The client certificate is required for this mode.
Action:
Specify the sslCert option along with the SSL parameters in the connection string.
OGG-05107: The SSL client private key is required for Mode {0}
The client key information is required for this mode.
Action:
Specify the sslKey option along with the SSL parameters in the connection string.
OGG-05108: No SSL Mode specified. MySQL will default to PREFERRED Mode.
The sslMode option was not specified in the connection string.
Action:
If a specific mode is required, then provide it as part of sslMode key in the connection string
OGG-05109: Connected to MySQL database using SSL.
User specified SSL options were utilized while establishing a MySQL DB connection.
Action:
No action required if done intentionally. If this was not intended to happen: 1) Stop the current Extract/Replicat 2) Unset the environment variables OGG_MYSQL_OPT_SSL_CA, OGG_MYSQL_OPT_SSL_CERT, OGG_MYSQL_OPT_SSL_KEY, OGG_MYSQL_OPT_SSL_MODE 3) Configure the Extract/Replicat parameter file to use SOURCEDB ... userid ... password i.e, no USERIDALIAS OR Configure the Extract/Replicat parameter file to use USERIDALIAS without the SSL option configuration. 4) Restart the Extract/Replicat
OGG-05110: The specified mode '{0}' is not recognized. Please use one of DISABLED/PREFERRED/REQUIRED/VERIFY_CA/VERIFY_IDENTITY. Defaulting to PREFERRED Mode.
The sslMode option specified in the connection string is not recognized. Defaulting to PREFERRED Mode
Action:
Please use one of DISABLED/PREFERRED/REQUIRED/VERIFY_CA/VERIFY_IDENTITY to configure the SSL Mode
OGG-05200: The schema of table {0} (object id {1}) was altered. {2} If the change affected the physical data layout, you must re-synchronize the source and target databases.
An unsupported DDL change was done to the the specified object.
Action:
Exclude the table from the TABLE parameter or re-synchronize the source and target tables.
OGG-05201: Backup {0} has been overwritten. LSN range {1} to {2} was found, but LSN range {3} to {4} was expected.
The backup was overwritten by a subsequent backup.
Action:
Re-synchronize the source and target tables.
OGG-05202: The server name is reported as NULL by SQL Server. Assign a valid server name with the @@servername variable.
The SQL Server variable "@@servername" is NULL.
Action:
Rename the server to a valid name according to the Microsoft recommended procedure.
OGG-05203: The SQL Server Native Client 11 driver is known to cause a memory leak when used to connect to SQL Server 2012 or later.
SQL Server Native Client 11 when used with OLE DB causes a memory leak see http://support.microsoft.com/kb/2894115 and http://support.microsoft.com/kb/2881661 for more details.
Action:
Please switch to ODBC or upgrade to the patch levels as per the referenced KB articles.
OGG-05204: {0} is a third party backup file. Third party backups are not supported.
Third party backups are not supported.
Action:
Convert backup file to native Microsoft tape format.
OGG-05205: {0} is a tape backup. Tape backups are not supported.
Tape backups are not supported.
Action:
Backup to file.
OGG-05206: Backup, {0}, is of an unknown type.
Backup is of an unknown type.
Action:
Backup to a supported format.
OGG-05207: Backup, {0}, is of an unsupported type: {1}.
Backup is of an unsupported type.
Action:
Backup to a supported format.
OGG-05208: Failed to duplicate the SQL Server process handle {0} with Windows system error {1}.
Extract needed to duplicate the SQL Server process handle but was unable to do so.
Action:
Please ensure that the SQL Server process is running.
OGG-05209: Failed to open the SQL Server process, {0}, with Windows system error {1}.
Extract needed to open the SQL Server process but was unable to do so.
Action:
Verify the connection is to a local instance and that permissions are granted for access the SQL Server process.
OGG-05210: {0}: A query to SQL Server has failed: {1} : {2}.
A query issued against SQL Server has failed.
Action:
None. Action depends on error.
OGG-05211: Buffer initialization has failed with a count of {0} and block size of {1}.
Initialization of an internal log data buffer has returned failure.
Action:
Please ensure there exists enough memory for use by Extract.
OGG-05212: Failed to get value for object {0}, attribute {1} from API.
An internal function returned failure.
Action:
Contact Oracle Support.
OGG-05213: Hardware parity failure detected for file id {0} at offset {1}.
File was incorrectly written to disk.
Action:
Verify the integrity of the file using SQL Server.
OGG-05214: Unable to open device {0} with Windows system error {1}.
Unable to open device.
Action:
Action depends on system error.
OGG-05215: Unable to find device {0} with Windows system error {1}.
Unable to find device.
Action:
Action depends on system error.
OGG-05216: Invalid start type: {0}.
Invalid start type.
Action:
Supply a valid start type.
OGG-05217: The starting LSN ({0}) is greater than the flush LSN ({1}) of this database. Positioning not attempted.
The starting LSN is too high.
Action:
Supply a valid starting LSN that is less than or equal to the flush LSN.
OGG-05218: The LSN, {0}, is lower than the first LSN in the online log of this database, {1}, and cannot be found in any backups.
Extract cannot find the LSN in the logical log span of the database.
Action:
Ensure that backups exist, that they are readable, and that they are not currently open.
OGG-05219: The log data provider could not be started.
The log data provider failed to start.
Action:
None
OGG-05220: A read attempt failed on device {0} at offset {1} with Windows system error {2}.
A device read failed.
Action:
Action depends on system error.
OGG-05221: Unable to retrieve virtual log information for LSN {0}.
Could not get virtual log information for the specified lsn.
Action:
None
OGG-05222: {0} is not a valid SQL Server backup.
The backup device is not a valid native MTF (Microsoft Tape Format) backup.
Action:
Supply a valid native MTF backup.
OGG-05223: LEGACYLOBREADING is no longer supported for SQL Server extract.
User supplied LEGACYLOBREADING parameter which is no longer supported.
Action:
Remove the parameter from the param file.
OGG-05224: The LSN, {0}, does not exist in the logical log span of this database.
Extract cannot find the LSN in the logical log span of the database.
Action:
Ensure that backups exist, that they are readable, and that they are not currently open.
OGG-05225: SQL Server {0} is not supported. The minimum supported version is SQL Server {1}.
The SQL Server version is not supported.
Action:
Review the Oracle GoldenGate Certification Matrix for the supported versions of SQL Server.
OGG-05226: Record processing will begin at LSN 0x{0}.
The start LSN has been found.
Action:
None
OGG-05227: Debug backup starting at LSN {0}.
Extract is beginning a debug backup run at the specified LSN.
Action:
None
OGG-05228: Debug backup complete.
Extract has reached the end of the debug backup.
Action:
None
OGG-05229: An internal LOB Buffer was overrun. Expected {0}, appended {1} to Marker [{2}]
More data was appended to an internal LOB buffer than expected.
Action:
Contact Oracle Support.
OGG-05230: An internal LOB Buffer was completed before all of the data was appended. Expected {0}, appended {1} to Marker [{2}]
Less data was appended to an internal LOB buffer than expected.
Action:
Contact Oracle Support.
OGG-05231: COM unexpectedly returned a read offset by {0} bytes.
Data was not returned to the buffer correctly from COM.
Action:
Contact Oracle Support.
OGG-05232: COM unexpectedly returned {0} bytes more than requested.
Data was not returned to the buffer correctly from COM.
Action:
Contact Oracle Support.
OGG-05233: An invalid identifier ({0}) was specified for DBOPTIONS TRANSNAME in the Replicat parameter file.
The value of DBOPTIONS TRANSNAME is not a valid transaction identifier.
Action:
Identifier rules:\n\n- Must start with a letter\n- Can have up to 32 characters, but no spaces\n- Are case insensitive (PART, Part, and part are identical)\n- Can include any combination of letters, numbers, and these special characters:\n- -Dash\n- _ Underscore\n- $ Dollar sign\n- # Number sign
OGG-05234: Native backup compression version {0} not supported.
Extract is trying to decompress a SQL Server backup that was compressed with an algorithm that is not supported. This likely means you are using a version of SQL Server is not supported.
Action:
Verify the SQL Server version. If that is a supported version, uncompress the backup and restart Extract. If it fails again, contact Oracle support.
OGG-05235: The current LSN {0} is out of sequence, the previous LSN was {1}.
The current LSN is out of sequence.
Action:
This is an internal failure, contact Oracle support.
OGG-05237: Error getting character set for column {1} of table {0}: Database error: {2,number,0} ({3})
An internal error occurred while fetching column collation information.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-05238: Unknown character set for column {1} of table {0} : {2}
An internal error occurred while fetching column character set information.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-05239: The LSN, {0}, does not exist in the online log of this database. The first LSN of the online log is {1}.
Extract cannot find the LSN in the online log of the database.
Action:
Ensure that the LSN has not already been backed up.
OGG-05240: Waiting for transaction log backups...
Extract is in ARCHIVEONLY mode and is waiting for a backup.
Action:
None
OGG-05241: Table {0} contains both compressed and uncompressed partitions, this configuration is not supported.
The table has both compressed and uncompressed partitions.
Action:
Exclude the table from replication or recreate the table to contain either all compressed or uncompressed partitions.
OGG-05242: The TRANLOGOPTIONS ALTARCHIVELOGDEST 'FILESPEC' parameter has been deprecated for SQL Server Extract.
The FILESPEC parameter has been deprecated.
Action:
Remove FILESPEC from the TRANLOGOPTIONS ALTARCHIVELOGDEST specification.
OGG-05243: The primary replica on server {0} for database {1} is not in a healthy state.
The primary replica for the database is not in a healthy state.
Action:
Make sure the primary replica for this availability group is healthy and restart extract.
OGG-05244: The local replica on server {0} for database {1} is not in a healthy state.
The local replica for the database is not in a healthy state.
Action:
Make sure the local replica for this availability group is healthy and restart extract.
OGG-05245: Connection to the primary node {0} failed.
The primary node is inaccessible.
Action:
Check if the primary node is running and the current login has access.
OGG-05246: Secondary truncation point management is running on server {0}.
The current database is part of an availability group that has a secondary role.
Action:
None
OGG-05247: SQL Server {0} is not supported. The maximum supported version is SQL Server {1}.
The SQL Server version is not supported.
Action:
Review the Oracle GoldenGate Certification Matrix for the supported versions of SQL Server.
OGG-05248: The cdc.lsn_time_mapping table does not exist. Please ensure that CDC is enabled on the database.
The CDC LSN time mapping table does not exist. This means CDC is not enabled on the database.
Action:
Enable CDC on the database.
OGG-05249: User '{0}' is not authorized to disable CDC on the '{1}' database. Sysadmin privileges are required. To fully remove CDC from database '{1}', grant sysadmin to user '{0}' and re-run DELETE TRANDATA *.* or manually run sys.sp_cdc_disable_db against the database
Sysadmin privileges are required.
Action:
Grant sysadmin privileges to the user.
OGG-05250: Change data capture has been disabled for the database '{0}' successfully
A shell command expressed the successful execution of CDC stored procedure. Information only.
Action:
None
OGG-05251: Could not resolve metadata for object ID {0}.
Could not get the metadata for this object ID from the database.
Action:
Ensure that the object exists on the database.
OGG-05252: Could not resolve metadata for table [{0}].[{1}].
Could not get the metadata for this table from the database.
Action:
Ensure that the table exists on the database.
OGG-05253: The SQL Server provider has thrown an exception. {0}
The database has encountered an error.
Action:
Review the message returned from SQL Server.
OGG-05254: SQL Server does not allow Change Data Capture to be set for table '{0}' based on its maximum row size. Reduce the size of the table or consult the Microsoft SQL Server documentation about how to enable Change Data Capture.
The row size exceeded the maximum allowable table row size.
Action:
Reduce the size of the table or consult the Microsoft SQL Server documentation.
OGG-05255: Current CDC Capture Settings - job name {0}, maxtrans: {1}, maxscans: {2}, continuous: {3}, polling interval: {4}
Reporting CDC capture job settings.
Action:
None
OGG-05256: Current CDC Cleanup Settings - job name: {0}, retention: {1}, threshold: {2}
Reporting CDC cleanup job settings.
Action:
None
OGG-05257: For CDC tuning best practices, please see https://technet.microsoft.com/en-us/library/dd266396number=sql.100%29.aspx.
Reporting CDC tuning best practices link.
Action:
None
OGG-05258: Could not retrieve the current Change Data Capture settings for database {0}. Ensure that the database is enabled for Change Data Capture. For information regarding enabling supplemental logging, see Installing and Configuring Oracle GoldenGate for SQL Server.
Could not get CDC settings from the database.
Action:
Could not retrieve the current Change Data Capture settings for database {0}. Ensure that the database is enabled for Change Data Capture. For information regarding enabling supplemental logging, see Installing and Configuring Oracle GoldenGate for SQL Server.
OGG-05259: The Extract's recovery checkpoint LSN {0} is not in the cdc.lsn_time_mapping table of database '{1}'. Extract cannot re-position without possible data loss.
Extract cannot find the recovery LSN in the cdc.lsn_time_mapping table.
Action:
Increase the retention period of the CDC cleanup job and re-sync the target with the source, then re-enable change data capture. Review the Installing and Configuring Oracle GoldenGate for SQL Server guide for more information.
OGG-05260: The specified filter table {0} is not found in the database.
The specified filter table is not found in the database.
Action:
Specify the correct filter table name or create one using ADD CHECKPOINTTABLE, and then enable supplemental log data using ADD TRANDATA.
OGG-05261: Logging of supplemental log data is not enabled for filter table {0}.
Supplemental (extended) logging is not enabled for the specified filter table.
Action:
Issue the DBLOGIN command in GGSCI, and then issue the ADD TRANDATA command to enable the supplemental logging. For more information, see the Oracle GoldenGate for SQL Server documentation.
OGG-05262: Using filter table {0} with capture instance of {1}.
Extract to identify as a Replicat transaction any transaction that has operation on the filter table.
Action:
None
OGG-05263: No GGSCHEMA clause was specified in the GLOBALS file. Specify a GGSCHEMA schema name.
No GGSCHEMA clause was specified in the GLOBALS file.
Action:
Specify a GGSCHEMA schema name.
OGG-05264: Opening DSN connection: {0}, Server: {1}, Database: {2}
This is an informational message that indicates the DSN string that Extract/Replicat/Ggsci used to connect to the source database.
Action:
None
OGG-05265: The SQL Agent on server {0} is not running. SQL Server CDC requires that the SQL Agent be running to capture change records.
The SQL Agent process is not running. SQL Server requires that the agent be running in order to capture change records. This means Extract will not capture data either.
Action:
Start the SQL Agent on the server.
OGG-05266: Unable to check the status of SQL Server Agent on server {0}. Ensure that it is running. Oracle GoldenGate for SQL Server CDC requires that SQL Server Agent be running in order to capture change records.
Extract was unable to check the status of the SQL Agent.
Action:
Ensure that the SQL Agent is running on the server.
OGG-05267: Change data capture is disabled for the database
This is an informational message that indicates the CDC is already disabled for the database.
Action:
None
OGG-05268: Failed to enable change data capture for table '{3}' in the database '{2}'. SQL error: {0,number,0}: {1}
Failed to enable change data capture for the specified table.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-05269: Failed to disable change data capture for the database '{2}'. SQL error: {0,number,0}: {1}
This is a generic error message that is used to report Change Data Capture failure.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-05270: Failed to create object '{2}'. SQL error: {0,number,0}: {1}
This is a generic error message that is used to report various different conditions.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-05271: Failed to drop object '{2}'. SQL error: {0,number,0}: {1}
This is a generic error message that is used to report various different conditions.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-05272: Failed to execute stored procedure '{2}'. SQL error: {0,number,0}: {1}
This is a generic error message that is used to report various different conditions.
Action:
Take corrective action based on the message text. Look for related messages that were logged along with this message. If you cannot resolve the problem based on the context provided in the messages, contact Oracle Support.
OGG-05273: Invalid LSN value: {0}
The LSN value is invalid.
Action:
LSN values are generated and validated by the system and should always be valid. Contact Oracle support for help.
OGG-05274: Unsupported datatype '{2}' in column '{1}' for table '{0}'. Column '{1}' will not be captured.
The table contains an unsupported column.
Action:
Review the Installing and Configuring Oracle GoldenGate for SQL Server Guide for more information.
OGG-05275: Unsupported datatype '{2}' in key column '{1}' for table '{0}'. Table '{0}' will not be captured.
The table contains an unsupported column as primary key.
Action:
Review the Installing and Configuring Oracle GoldenGate for SQL Server Guide for more information.
OGG-05276: Table '{0}' contains no supported datatypes. Table '{0}' will not be captured.
All columns of the table are unsupported.
Action:
Review the Installing and Configuring Oracle GoldenGate for SQL Server Guide for more information.
OGG-05278: Failed to enable logging of supplemental log data for table: {0}
Oracle GoldenGate failed to enable supplemental logging for the specified table.
Action:
Look for other warnings or error messages, because there are many possible causes for this error, such as insufficient privileges for the Oracle GoldenGate user and connectivity failures.
OGG-05279: Failed to disable logging of supplemental log data for table: {0}
Oracle GoldenGate failed to disable supplemental logging for the specified table.
Action:
Look for other warnings or error messages, because there are many possible causes for this error, such as insufficient privileges for the Oracle GoldenGate user and connectivity failures.
OGG-05280: Could not retrieve the Oracle GoldenGate CDC Cleanup Job settings for database {0}. Ensure that the Oracle GoldenGate CDC Cleanup Job exists and is enabled on the database.
Could not get Oracle GoldenGate clean up job settings for the given database.
Action:
Ensure that the Oracle GoldenGate clean up job is enabled for the given database.
OGG-05281: The Oracle GoldenGate CDC Cleanup job, '{0}', in database, '{1}', is configured with threshold = {2} and retention = {3}.
Reporting Oracle GoldenGate cleanup job settings.
Action:
None
OGG-05282: Could not retrieve the Oracle GoldenGate CDC Cleanup Job settings for database {0}. Ensure that the Oracle GoldenGate CDC Cleanup Job exists and is enabled on the database.
Could not get the Oracle GoldenGate cleanup job settings for the given database.
Action:
Ensure that the Oracle GoldenGate cleanup job is enabled for the given database.
OGG-05283: Could not retrieve the Change Data Capture (CDC) clean up job settings for database {0}. Ensure that the Change Data Capture (CDC) clean up job is enabled on the database.
Could not get Change Data Capture (CDC) clean up Job settings from the database.
Action:
Ensure that the database is enabled with Change Data Capture (CDC) clean up Job.
OGG-05284: The Change Data Capture (CDC) clean up job is not currently running on database {0}.
Clean up Job is disabled by the user or the Change Data Capture (CDC) is not enabled on the current database.
Action:
Ensure that the database is enabled with Change Data Capture (CDC) Clean up Job.
OGG-05285: The Oracle GoldenGate clean up job is not running on database {0}.
Oracle GoldenGate job is disabled by the user.
Action:
Ensure that the Oracle GoldenGate cleanup job is enabled for the database.
OGG-05286: Neither the Oracle GoldenGate clean up job nor the Change Data Capture (CDC) clean up job are running on database {0}. Change Data Capture (CDC) enabled tables will not be purged.
Oracle GoldenGate clean up job and the Change Data Capture (CDC) clean up is disabled by the user.
Action:
Ensure that the database is enabled with either the Oracle GoldenGate clean up job or Change Data Capture (CDC) clean up job from the database.
OGG-05287: The Oracle GoldenGate clean up job and the Change Data Capture (CDC) clean up job are both running on database {0}. Running both jobs simultaneously could result in data integrity issues.
Oracle GoldenGate clean up job and the Database provided Change Data Capture (CDC) clean up job are running on the same database. This may result in data inconsistency and/or loss.
Action:
Ensure that the database is enabled with either the Oracle GoldenGate clean up job or the Change Data Capture (CDC) clean up job, but not both.
OGG-05288: The Change Data Capture (CDC) clean up job for database {0} is disabled by the Oracle GoldenGate capture process to avoid any data loss.
Oracle GoldenGate capture process is running with TRANLOGOPTIONS MANAGECDCCLEANUP and it is found that user has also enabled the Change Data Capture (CDC) clean up job. So it has disabled the Change Data Capture (CDC) clean up job.
Action:
Ensure that the database is enabled with either the Oracle GoldenGate clean up job or Change Data Capture (CDC) clean up job. Disable either Change Data Capture (CDC) clean up job or the Oracle GoldenGate clean up job.
OGG-05292: Oracle GoldenGate Capture is running on database {0} with NOMANAGECDCCLEANUP. Any enabled CDC Cleanup job will not honor this Extract's recovery checkpoint. Oracle recommends that you run with MANAGECDCCLEANUP for production environments.
The Oracle GoldenGate capture process is running with NOMANAGECDCCLEANUP.
Action:
Ensure that the cleanup of CDC enabled tables is done by the SQL Server CDC cleanup job. Additionally, make sure that if the capture process is not running, the SQL Server CDC cleanup job does not purge the records that have not yet been read by the Oracle GoldenGate capture process. For production environments, Oracle recommends allowing Oracle GoldenGate to manage CDC cleanup.
OGG-05295: Change Data Capture (CDC) is disabled on database {0}. Ensure that Change Data Capture (CDC) is enabled for the database. For information regarding enabling supplemental logging, see Using Oracle GoldenGate for Heterogeneous Databases.
CDC is disabled.
Action:
Enable CDC on the database.
OGG-05296: Could not determine if Change Data Capture (CDC) is enabled on database {0}. Ensure that the database is enabled for Change Data Capture. For information regarding enabling supplemental logging, see Installing and Configuring Oracle GoldenGate for SQL Server.
Could not get Change Data Capture (CDC) clean up Job settings from the database.
Action:
Ensure that the database is enabled with Change Data Capture (CDC) clean up Job.
OGG-05297: Logging of supplemental log data is disabled for table {0}
The process could not determine whether the specified table has supplemental logging enabled.
Action:
Check the database connection settings and whether SQL Server was configured according to the directions in the Oracle GoldenGate configuration documentation for SQL Server.
OGG-05298: Oracle GoldenGate object(s) {1} is missing from database {0}. Run ADD TRANDATA for table {2} to re-enable supplemental logging.
The process could not find the global CDC object(s) in the current database.
Action:
Ensure that the Oracle GoldenGate required global CDC object(s) exist in the database. If object(s) are missing, then Run ADD TRANDATA for any table to create the required global CDC object(s).
OGG-05299: Native Transactional Replication is enabled for database {0}. Ensure that the SQL Server Log Reader Agent job is running.
Native transactional replication is enabled on the database.
Action:
Ensure that the SQL Server Log Reader Agent job is running.
OGG-05300: The Oracle GoldenGate cleanup job and the SQL Server CDC cleanup job both exist on database {0}. Ensure the SQL Server CDC cleanup job is disabled to allow Oracle GoldenGate to manage CDC cleanup.
The SQL Server provided CDC cleanup job exists alongside the Oracle GoldenGate CDC cleanup job.
Action:
Ensure the SQL Server CDC cleanup job is disabled.
OGG-05301: Shell command output: '{0}'
A SHELL Command declared as part of an EVENTACTIONS expression has produced output which was captured for reporting purposes. Informational only.
Action:
None
OGG-05302: An error occurred while doing commit handling.
An error occurred while doing commit handling.
Action:
Contact Oracle Support.
OGG-05303: GRAPHIC/VARGRAPHIC/DBCLOB column support requires a Unicode character set.
Oracle GoldenGate supports GRAPHIC, VARGRAPHIC and DBCLOB columns only if the character set of the column is Unicode.
Action:
Create the GRAPHIC, VARGRAPHIC or DBCLOB column in a Unicode database or with a Unicode character set, if that is not possible, exclude the table from the Oracle GoldenGate configuration.
OGG-05304: Database instance {0} has logarchmeth1 set to off.
The DB2 configuration parameter LOGARCHMETH1 is set to off.
Action:
Set LOGARCHMETH1, LOGRETAIN or USEREXIT configuration parameter appropriately to enable DB2 log retention.
OGG-05305: Process {0} is not in a suspended state. RESUME is ignored.
A SEND command with RESUME was issued for a process that is not in the SUSPEND state. The RESUME request is being ignored.
Action:
None
OGG-05306: Table {0}, column {1}, contains data type: {2,number,0} which is not a supported datatype with COMPRESS SYSTEM DEFAULT ON.
The specified column is not supported for COMPRESS SYSTEM DEFAULT.
Action:
Specify one of the valid COMPRESS SYSTEM DEFAULT data types: numerical, fixed-length character, fixed-length graphic string. For more information on supported data types, see the Oracle GoldenGate documentation for this database.
OGG-05307: No GGSCHEMA clause was specified in the GLOBALS file. Specify a GGSCHEMA schema name.
No GGSCHEMA clause was specified in the GLOBALS file.
Action:
Specify a GGSCHEMA schema name.
OGG-05310: Oracle GoldenGate does not support {0}. Supported versions are {1}.
Oracle GoldenGate does not support this SQL Server.
Action:
Use a supported version of SQL Server.
OGG-05311: Oracle GoldenGate does not support {0} {1} edition. Supported editions are {2}.
Oracle GoldenGate does not support this SQL Server engine edition.
Action:
Use a supported SQL Server engine edition.
OGG-05312: The SQL Server driver {0} is not supported for SQL Server version {1}. Supported drivers are {2}.
The driver does not support the SQL Server version/engine edition.
Action:
Use a compatible driver.
OGG-05313: Invalid ADD HEARTBEATTABLE command for the target database. Use 'ADD HEARTBEATTABLE TARGETONLY'.
Invalid ADD HEARTBEATTABLE command for the target database.
Action:
Use the TARGETONLY parameter.
OGG-05315: {0} command is not supported on database '{1}'.
Command not supported on the specified database.
Action:
None
OGG-05318: The {0} driver is not supported for {1}. Supported drivers are {2}.
The driver does not support the SQL Server version/engine edition.
Action:
Use a compatible driver.
OGG-05319: Using filegroup '{0}' from GLOBALS file.
The filegroup parameter has been specified in GLOBALS file.
Action:
None
OGG-05320: The filegroup '{0}' does not exist in the database.
The filegroup does not exist in the database.
Action:
Use a valid filegroup name.
OGG-05321: Logging of supplemental log data is already enabled for table '{0}' in filegroup '{1}'.
The CDC table is already enabled in filegroup.
Action:
None
OGG-05322: The ODBC driver has returned an error. State: {0}, Error number: {1}, Message: {2}
The ODBC driver has returned an error through GGDBSQL.
Action:
Dependent on error message from ODBC.
OGG-05323: The number of columns ({0}) in user table '{2}' does not match that of CDC table '{3}' ({1}). Please execute DELETE TRANDATA followed by ADD TRANDATA for table '{2}' in order to synchronize the metadata. Unprocessed change records in the CDC table will be lost and will require manually resyncing the source and target table.
The number of columns in the user table is not the same as CDC table.
Action:
See Using Oracle GoldenGate for Heterogeneous Databases for information on handling ALTER TABLE statement in CDC.
OGG-05324: Oracle GoldenGate does not support {0} release version {1}.
Oracle GoldenGate does not support this SQL Server.
Action:
Use a supported release version.
OGG-05327: The SQL Server CDC Capture job does not exist for database {0}. Ensure that the SQL Server CDC Capture job exists and is running.
The SQL Server CDC Capture job does not exist for the database.
Action:
Execute " sys.sp_cdc_add_job @job_type = N'capture' " to create the SQL Server CDC Capture job.
OGG-05328: The SQL Server CDC Capture job is disabled for database {0}. Please ensure that the SQL Server CDC Capture job is enabled and running.
CDC Capture job has been disabled.
Action:
Please Enable the capture Job.
OGG-05329: The SQL Server CDC Capture job for database {0} is not running. Please ensure that the SQL Server Agent and CDC Capture job are running.
The SQL Server CDC Capture job is not in a running state.
Action:
Please start the SQL Server CDC Capture job and ensure that it is running correctly.
OGG-05330: The status of the SQL Server CDC Capture job could not be determined due to insufficient privileges.
Failed to determine the status of the SQL Server CDC Capture job.
Action:
Please ensure that the SQL Server CDC Capture job is enabled and running.
OGG-05331: The Oracle GoldenGate CDC Cleanup job for database, {0}, does not exist. Install the Oracle GoldenGate CDC Cleanup job and ensure it is enabled.
The Oracle GoldenGate CDC Cleanup job does not exist.
Action:
Install the Oracle GoldenGate Cleanup job and ensure it is enabled.
OGG-05332: The Oracle GoldenGate CDC Cleanup job, '{0}', created on {1}, is enabled in database, '{2}'.
The Oracle GoldenGate CDC Cleanup Job is enabled.
Action:
None
OGG-05333: The Oracle GoldenGate CDC Cleanup job, {0}, for database, {1}, is disabled. Enable the Oracle GoldenGate CDC Cleanup job.
The Oracle GoldenGate CDC Cleanup Job is disabled.
Action:
Enable the Oracle GoldenGate CDC Cleanup job.
OGG-05334: Could not confirm the existence of the Oracle GoldenGate CDC Cleanup job due to insufficient privileges.
Failed to verify the existence of the Oracle GoldenGate CDC Cleanup job.
Action:
Please ensure that the Oracle GoldenGate CDC Cleanup job exists.
OGG-05335: The Oracle GoldenGate CDC Cleanup job status table, {0}, exists. Extract will assume the Oracle GoldenGate CDC Cleanup job exists.
The Oracle GoldenGate CDC Cleanup job status table exists so assuming the job does exists.
Action:
Please ensure that the Oracle GoldenGate CDC Cleanup job exists.
OGG-05336: The Oracle GoldenGate CDC Cleanup job status table, {0}, does not exist. Install the Oracle GoldenGate CDC Cleanup job and ensure it is enabled.
The Oracle GoldenGate CDC Cleanup job status table does not exist so assuming the job does not exist.
Action:
Please ensure that the Oracle GoldenGate CDC Cleanup job exists.
OGG-05337: Successfully added supplemental logging for heartbeat table {0} in filegroup '{1}'.
Added supplemental logging for heartbeat table for all columns. Information only.
Action:
None
OGG-05338: The versions of the Oracle GoldenGate CDC objects on database, {2}, are not consistent with the expected version, {0}. The following version(s) were found: {1}. Rerun ADD TRANDATA for all tables previously enabled, including heartbeat, heartbeat seed, and filter tables.
The Oracle GoldenGate CDC object versions on the database are different than the version expected by this application.
Action:
Rerun ADD TRANDATA for all tables previously enabled, including heartbeat, heartbeat seed, and any filter table to correct this issue.
OGG-05339: Logging of supplemental log data is already enabled for table '{0}' in filegroup '{1}'. The filegroup '{1}' will be used to re-enable logging for the table and filegroup '{2}' will be ignored.
The CDC table is already enabled in filegroup.
Action:
None
OGG-05340: Failed to {3} object '{2}': error: SQLCODE {0,number,0}. SQL Error {1}
This is a generic error message used to report different types of errors.
Action:
Take corrective action based on the associated messages that were logged along with the generic error message. Contact Oracle support if you are unable to resolve the issue.
OGG-05341: Failed to fetch version number for table '{0}' from table '{1}'. {2}
The ODBC driver has returned an error.
Action:
Dependent on the error message from ODBC.
OGG-05342: The stored procedure '{1}' resolved for table '{0}'.
Failed to disable change data capture for the specified table.
Action:
Take corrective action based on the specified database error.
OGG-05343: Failed to disable change data capture for table '{3}' in the database '{2}'. SQL error: {0,number,0}: {1}
Failed to disable change data capture for the specified table.
Action:
Take corrective action based on the specified database error.
OGG-05344: {0}
The specified SQL Server error occurred.
Action:
Follow the directions in the error message to resolve the problem, or contact Oracle Support.
OGG-05345: An Oracle GoldenGate query to the database has timed out. Use the TRANLOGOPTIONS QUERYTIMEOUT parameter in Extract's parameter file to increase the timeout value. The current timeout value is {0} seconds.
A query to the database has timed out.
Action:
Check the database to determine why the query timed out and/or increase the timeout value by using the TRANLOGOPTIONS QUERYTIMEOUT parameter in the Extract parameter file.
OGG-05346: A connection to the database could not be established. Database error {0,number,0} ({1})
Could not establish a connection to the database.
Action:
Determine the root cause from the error message to resolve the problem, or contact Oracle Support.
OGG-05347: A connection to the secondary replica could not be established. Database error {0,number,0} ({1})
Could not establish a connection to the secondary replica.
Action:
Determine the root cause from the error message to resolve the problem, or contact Oracle Support.
OGG-05349: The column at index {0} in table {1} is an identity column. Identity columns are not supported for Azure Synapse Analytics.
Identity columns are not supported for Azure Synapse Analytics.
Action:
Remove the identity column from replication.
OGG-05350: The OracleCDCExtract stored procedure does not exist in GGSCHEMA {0} defined inside the GLOBALS file.
The 'add trandata' was not performed with the current GGSCHEMA specified inside the GLOBALS file.
Action:
Ensure that the 'add trandata' is done and the GGSCHEMA inside the GLOBALS is not altered after doing the 'add trandata'. If unable to determine the root cause, contact Oracle Support.
OGG-05351: The versions of the Oracle GoldenGate CDC objects for table {2} in database {3} are not consistent with the expected version, {0}. The following version(s) were found: {1}. Rerun ADD TRANDATA for table {2}.
The Oracle GoldenGate CDC object versions for the table are different than the version expected by this application.
Action:
Rerun ADD TRANDATA for this table.
OGG-05352: Checking Oracle GoldenGate CDC object versions.
The Oracle GoldenGate CDC object versions are being verified.
Action:
None
OGG-05353: Checking Oracle GoldenGate CDC object versions for table {0}.
The Oracle GoldenGate CDC object versions for the table are being verified.
Action:
None
OGG-05354: Failed to allocate statement handle for query to check Oracle GoldenGate CDC object version consistency. Database error ({0}).
Failed to allocate statement handle.
Action:
Review error text and take appropriate action. If unable to determine the root cause, contact Oracle Support.
OGG-05355: Failed to get query results while attempting to check Oracle GoldenGate CDC object version consistency. Database error ({0}).
Failed to get Oracle GoldenGate CDC object version check query results.
Action:
Review error text and take appropriate action. If unable to determine the root cause, contact Oracle Support.
OGG-05356: A column metadata mismatch has been detected for table {0}. This could be a symptom of a DDL change. If there was a DDL change, please review the DDL change policy in the Oracle GoldenGate documentation.
This is usually caused by a DDL change.
Action:
Review the DDL change policy in the Oracle GoldenGate documentation.
OGG-05357: The change tracking table for table {0} does not contain column {1}. This could be a symptom of a DDL change. If there was a DDL change, please review the DDL change policy in the Oracle GoldenGate documentation.
This is usually caused by a DDL change.
Action:
Review the DDL change policy in the Oracle GoldenGate documentation.
OGG-05358: Purge change data tasks are not supported for this database.
Purge change data tasks are not implemented for the database.
Action:
None
OGG-05359: Successfully purged change data older than {0} hours.
The purge change data task has executed successfully.
Action:
None
OGG-05360: Purge change data older than {0} hours failed.
The purge change data task execution failed.
Action:
See other error messages. If the error cannot be remedied, contact Oracle support.
OGG-05361: The SQL Server CDC cleanup job exists on database {0}, which indicates that an Oracle GoldenGate purge change data task has not been enabled. Ensure that a purge change data task is enabled to allow Oracle GoldenGate to manage CDC cleanup.
The SQL Server native CDC cleanup job exists, which indicates that a change data purge task has not been enabled.
Action:
Create and enable an Oracle GoldenGate change data purge task to manage CDC cleanup of the database. The change data purge task will remove the native CDC cleanup job.
OGG-05362: Schema name is required for filter table: "{0}"
The filter table specification does not include a schema name.
Action:
Specify the schema name in the filter table specification.
OGG-05363: Wildcard schema is not allowed in filter table: "{0}"
Wildcard schema is not allowed in the FILTERTABLE option.
Action:
Please specify an exact schema name in the FILTERTABLE option.
OGG-05364: Duplicate filter table "{0}" is ignored.
The specified filter table name matches the previous FILTERTABLE specification.
Action:
Remove the duplicate filter table entry.
OGG-05365: The USEREPLICATIONUSER parameter is deprecated. Connections are now established as a replication agent by default.
USEREPLICATIONUSER is specified in the parameter file.
Action:
None
OGG-05366: The installed ODBC driver for SQL Server version {0} does not support connecting as a replication agent. Upgrade the ODBC driver for SQL Server to version {1} or later
The installed ODBC driver for SQL Server does not support connecting as a replication agent.
Action:
Upgrade the ODBC driver for SQL Server to the suggested or later version.
OGG-05367: The installed ODBC driver for SQL Server version {0} does not support connecting as a replication agent. For optimal performance, upgrade the ODBC driver for SQL Server to version {1} or later.
The installed ODBC driver for SQL Server does not support connecting as a replication agent.
Action:
Upgrade the ODBC driver for SQL Server to the suggested or later version.
OGG-05368: The installed ODBC driver for SQL Server version {0} does not support connecting as a replication agent. For optimal performance, upgrade the ODBC driver for SQL Server to version {1}, or later, and enable the NOT FOR REPLICATION option in the identity column of table {2}.
The installed ODBC driver for SQL Server does not support connecting as a replication agent, and the NOT FOR REPLICATION option is not enabled in the identity column of the specified table.
Action:
Upgrade the ODBC driver for SQL Server to the suggested or later version and enable the NOT FOR REPLICATION option in the identify column of the specified table.
OGG-05369: The installed ODBC driver for SQL Server version {0} does not support connecting as a replication agent. To suppress triggers from firing, upgrade the ODBC driver for SQL Server to version {1}, or later, and enable the NOT FOR REPLICATION option in the triggers of table {2}.
The installed ODBC driver for SQL Server does not support connecting as a replication agent, and the NOT FOR REPLICATION option is not enabled in the triggers of the specified table.
Action:
Upgrade the ODBC driver for SQL Server to the suggested or later version and enable the NOT FOR REPLICATION option in the triggers of the specified table.
OGG-05370: For optimal performance, enable the NOT FOR REPLICATION option in the identity column of table {0}.
The specified table has an identity column which requires additional SQL commands to insert an explicit value to an identity column. See SQL Server documentation for details on the NOT FOR REPLICATION option.
Action:
Enable the NOT FOR REPLICATION option in the identity column of the specified table.
OGG-05371: The check constraint in table {0} is not enforced on insert, update, or delete operation executed on this connection.
The check constraint in the specified table is set to NOT FOR REPLICATION. In this mode, the target database does not enforce the check constraint when insert, update or delete operation is performed by Replicat as a replication agent. The assumption is that the constraint checking was performed by the source database.
Action:
None
OGG-05372: The foreign key constraint in table {0} is not enforced on insert, update, or delete operations executed on this connection.
The foreign key in the specified table is set to NOT FOR REPLICATION. In this mode, The target database does not enforce the foreign key constraint when insert, update, or delete operation is performed by Replicat operating as a replication agent. This includes CASCADE operations. The assumption is that the constraint was checked on the source database and that the cascaded operations are captured and replicated.
Action:
Make sure that the referenced tables are included in the replication configuration with the referencing table to see alerts for integrity violations, such as if a row gets inserted into a table that contains a foreign key to a non-replicated table.
OGG-05373: The trigger in table {0} is not executed on insert, update, or delete operations executed on this connection.
The trigger in the specified table is set to NOT FOR REPLICATION. In this mode, the target database does not execute the trigger when insert, update or delete operation is performed by Replicat operating as a replication agent. The assumption is that the triggered operations from the source are captured and replicated.
Action:
Make sure that the tables affected by the trigger are included in the replication configuration, otherwise, there will be no errors to alert you to integrity violations.
OGG-05376: Oracle GoldenGate support for {0} requires a database patch {1} or above. For details, see {2}
Oracle GoldenGate support for the specified database requires a software patch due to a server issue.
Action:
Apply the required software patch to the database server.
OGG-05500: Detected database metadata mismatch between current trail file {0} and the previous sequence. The source database may be upgraded or downgraded. {1}
An inconsistency in database metadata was detected between the current and previous trail file.
Action:
If the source database is upgraded or downgraded and the error occurs on Replicat, reposition the Replicat to the current trail sequence number and rba 0 and restart the Replicat. If there is no database upgrade or downgrade, contact Oracle support.
OGG-05501: Detected trail format inconsistency between current trail file {0} and the previous sequence
An inconsistency in the trail format was detected between the current and previous trail file.
Action:
Contact Oracle Support.
OGG-05503: WARNING: Improper VAM Implementation. The LOB data handle is not associated with the same transaction that contains the base row.
The LOB data handle was associated with a different transaction than the base row that is being replicated at the time the data handle was created. Data handles can only be assigned to columns that belong to base rows that are in the same transaction.
Action:
Contact Oracle Support for help with using TRANLOGOPTIONS LEGACYLOBREADING as a temporary workaround.
OGG-05506: Table {0}, column {1}, contains an unsupported data type: {2}.The column will be excluded.
The specified column contains an unsupported data type. The column will be excluded.
Action:
For supported data types, see the Oracle GoldenGate documentation for this database.
OGG-05507: Table {0} column {1} : the fractional part of the captured timestamp will be truncated to {2,number,0} digits.
The timestamp column has higher granularity than the maximum supported fraction digits. The captured timestamp data will be truncated.
Action:
None. Extract will process the timestamp data with less granularity.
OGG-05508: The CSN value {0} given with the ATCSN or AFTERCSN option is less than the CSN value {1} already committed by the previous instance of this process. Only transactions not yet committed will be processed.
START EXTRACT or START REPLICAT was issued with an ATCSN or AFTERCSN option, but the specified CSN value is lower than the highest CSN that has already been committed to the trail or target database. This would cause duplicate transactions if allowed.
Action:
If you issued START EXTRACT or START REPLICAT at the given CSN to confirm that all transactions starting from that CSN got captured to the trail, no action is necessary. However, if it is your intention to start the output of the new process with the transaction at the specified CSN or immediately after it, contact Oracle Support for assistance in determining which output trail is to be affected.
OGG-05509: The CSN value {0} given in the command line was not seen. Processing begins with the first actual CSN value seen above the value in the command line.
The ATCSN option was used with a CSN value that does not exist in the transaction stream. This CSN value may not be a valid CSN.
Action:
Make certain the provided CSN value exists in the input transaction stream. You can use the Logdump utility to examine the input trail file if you issued START REPLICAT, or START EXTRACT for data pump with the ATCSN option. Refer to the Oracle GoldenGate reference documentation for how CSN values are determined for your specific database.
OGG-05510: The CSN value {0} given with the ATCSN or AFTERCSN option is less than a CSN value {1} already committed by the previous instance of this process to at least one output trail file. Some transactions associated with the given CSN might be skipped, but others cannot be skipped because they have already been committed to a trail.
START EXTRACT was issued with an ATCSN or AFTERCSN option, but the specified CSN value is lower than the highest CSN that has already been committed to at least one of multiple output trails. This same specified CSN value is also higher than the highest CSN already committed to least one of the same set of multiple output trails. Some transactions might be skipped, but other transactions that were already committed to a trail during the previous process run cannot be skipped.
Action:
None
OGG-05511: DROP TABLE encountered for {0}, DBID: {1}, OBID: {2}.
A DROP TABLE was the first log record encountered for the specified table after Extract started. Because WILDCARDRESOLVE IMMEDIATE was not specified, an entry in the definitions file for this table cannot be created, and no truncate record can be created for it.
Action:
None
OGG-05512: TRUNCATE cannot be generated for table DBID: {0}, OBID: {1}. Refer to previous message for the name of the table.
A log record that indicates a DROP TABLE was processed. Because the DB2 catalog no longer contains the table, a TRUNCATE record cannot be captured for it.
Action:
Refer to the previous message to get the name of the table. Then, resolve the target table so that it matches the source table, such as deleting or truncating the target table as appropriate.
OGG-05513: An INSERT, UPDATE, or DELETE was encountered for table DBID: {0}, OBID: {1}. A table with the same DBID / OBID was identified as dropped during the current execution of Extract.
An INSERT, UPDATE, or DELETE was encountered for a table that was identified as dropped during the current run of Extract. Because Extract did not acquire the definition of the dropped table from the DB2 catalog, it is not possible to determine if the table definition has changed.
Action:
Refer to the previous message to get the name of the table. Then, resolve the target table so that it matches the source table, such as deleting or truncating the target table as appropriate. If using the SOURCEDEFS parameter, make certain that the data definitions file is current. Then, restart Extract.
OGG-05514: An INSERT, UPDATE, or DELETE was encountered for table {0}, DBID: {1}, OBID: {2}, which was identified as dropped during the current execution of Extract. The current table definition does not match that of the dropped table.
An INSERT, UPDATE, or DELETE was encountered for a table that was identified as dropped during the current run of Extract. The current table definition does not match that of the dropped table.
Action:
Resolve the target table so that it matches the source table, such as deleting or truncating the target table as appropriate. If using the SOURCEDEFS parameter, make certain that the data definitions file is current. Then, restart Extract.
OGG-05515: DATA CAPTURE CHANGES is not enabled for SYS IBM.SYSTABLES. Processing will be switched from APIFILTER to NOAPIFILTER to allow the capture of data related to SYSIBM.SYSTABLES.
APIFILTER is enabled and DATA CAPTURE CHANGES is not enabled for SYSIBM. SYSTABLES. NOAPIFILTER will be used to capture data.
Action:
To enable DATA CAPTURE CHANGES for SYSIBM.SYSTABLES, use this GGSCI command: ADD TRANDATA sysibm.systables. This may allow processing to be done with APIFILTER, if no other conditions exist that would force NOAPIFILTER. One such condition is the need to capture change data for any table that includes one or more LOB columns.
OGG-05516: A table with one or more LOB column was encountered. Processing will be switched from APIFILTER to NOAPIFILTER to allow capture of data from the LOB column(s).
A table with one or more LOB column was encountered and APIFILTER is enabled, which would prevent capture of data from the LOB column(s).
Action:
To allow filtering for this Extract group, move all tables that contain LOB columns to a different Extract group.
OGG-05517: OCI error ({0}-{1}) determining whether to ignore the object.
The process encountered the specified OCI error when trying to determine whether or not to ignore the object.
Action:
Check the OCI error detail to resolve the cause of error.
OGG-05518: No data found when determining whether or not to ignore the object.
No data was found when determining if the object is to be ignored.
Action:
Contact Oracle Support for help.
OGG-05519: Output trail file encryption: {0}
The ENCRYPTTRAIL parameter was specified or the data pump is sending an encrypted trail file.
Action:
None
OGG-05520: Input trail file encryption: {0}
The input trail is encrypted.
Action:
None
OGG-05531: This Extract configuration does not support catalog name. A catalog parameter '{0}' is specified.
The specified parameter is not valid for this Oracle GoldenGate Extract configuration.
Action:
Check the reference documentation for your version of Oracle GoldenGate. This parameter may need to be removed.
OGG-05532: ORA-00942: table or view does not exist. Either the SYS.DBA_REGISTRY_BACKPORTS table does not exist or the user has insufficient privileges to access it. Please ensure that the privileges are set correctly for user {0}. If the error still persists, contact Oracle Support.
Cannot open the SYS.DBA_REGISTRY_BACKPORTS table because either it does not exist or the user has insufficient privileges to access it.
Action:
Contact Oracle Support if the table does not exist, otherwise ensure that the user has sufficient privileges to access the table.
OGG-05533: OGG-05533: Per-PDB logon access is not available for user {0} on container database {1}, and therefore Per-PDB capture is not supported. Please retry using a login credential to the root container.
Local Per-PDB access is not available on this database.
Action:
Supply connection details to the root level database.
OGG-05535: Cannot register or unregister EXTRACT {0} because Per-PDB access is not supported on an Active Data Guard standby database.
Local Per-PDB access is not supported on an Active Data Guard standby database.
Action:
Check Oracle GoldenGate and database configurations for a valid Active Data Guard standby database.
OGG-05536: Provided {0} input was {1}, actually being set to {2} due to Cloud Resource Management.
Provided parameter value is not allowed due to Cloud Resource Management.
Action:
Use a value allowed by Cloud Resource Management or use the auto-adjusted value.
OGG-05600: Table {0} has a self-referencing foreign key. Records from this table will be ignored.
The specified table has a self-referencing foreign key. Oracle GoldenGate does not support this type of table and ignores operations on them.
Action:
None
OGG-05601: Error determining whether to ignore the object. OCI error ({0}-{1}) encountered executing SQL query: <{2}>
The process encountered the specified OCI error when trying to determine whether or not to ignore the object.
Action:
Check the OCI error detail to resolve the cause of error. Ensure that the user has privileges to execute the SQL statement.
OGG-05663: CSN-based filtering suppressed a duplicate transaction from trail Seqno {0,number,0}, RBA {1,number,0}, with CSN {2} and transaction ID {3}.
CSN-based filtering identified a duplicate transaction and filtered it out.
Action:
None
OGG-05664: CSN-based filtering suppressed {8,number,0} duplicate transactions, from trail Seqno {0,number,0}, RBA {1,number,0} to Seqno {4,number,0}, RBA {5,number,0}. The first transaction suppressed has CSN {2} and transaction ID {3}, and the last suppressed one has CSN {6} and transaction ID {7}
CSN-based filtering identified duplicate transactions and filtered them out.
Action:
None
OGG-05672: CSN-based duplicate suppression is disabled because there is no checkpoint table for this Replicat.
There is no checkpoint table for the Replicat group. To store the CSN state, a checkpoint table is required.
Action:
To use duplicate suppression, add a checkpoint table for Replicat.
OGG-05673: CSN-based duplicate suppression is disabled because there is no checkpoint table for this Replicat.
There is no checkpoint table for the Replicat group. To store the CSN state, a checkpoint table is required.
Action:
To use duplicate suppression, add a checkpoint table for Replicat.
OGG-05700: WARNING: The ADD TRANDATA command was not issued for table {0}. No records will be processed for this table.
The ADD TRANDATA command was not issued for the specified table to enable supplemental logging.
Action:
Issue the DBLOGIN command in GGSCI, and then issue the ADD TRANDATA command. For more information, see the Oracle GoldenGate reference documentation.
OGG-05701: Failed to drop supplemental log group on table {0} due to {1} SQL {2}
DELETE TRANDATA was issued for the specified table, but Oracle GoldenGate was not able to drop a supplemental log group on the table.
Action:
Fix the problem based on the database error that is returned in the message.
OGG-05702: XML parse error encountered in an ANYDATA column
XML Parser returned an error when processing a fetched ANYDATA column.
Action:
If you cannot determine the cause and resolution from the message, contact Oracle Support.
OGG-05797: Unknown DataFormat 0x{4} detected trail file {0}, RBA {1,number,0} for table {2}, column {3}.
The data format token in the trail record contains invalid data.
Action:
Verify that the version of Extract and Replicat are compatible.
OGG-05798: {5} (token 0x{4}) detected at trail file {0}, RBA {1,number,0}, for table {2}, column {3}. {5} is not supported for this target.
Partial LOB/XML update operations are not supported for this target.
Action:
Add FETCHPARTIALLOB/FETCHPARTIALXML option(s) as appropriate in the TRANLOGOPTIONS parameter in the Extract parameter file, and then restart Extract.
OGG-05799: Oracle object table (token 0x{3}) detected at trail {0}, RBA {1,number,0}, for table {2}. Oracle object tables are not supported for this target.
Oracle object tables are not supported for this target.
Action:
Exclude the table from the MAP statement.
OGG-06000: Replicat Coordinator failed to start Replicat thread {0}.
An error occurred when Replicat Coordinator attempted to start a Replicat thread.
Action:
Contact Oracle Support.
OGG-06001: Replicat Coordinator failed to send a message to Replicat thread {0}. Detail: {1}
An error occurred when Replicat Coordinator attempted to send a message to a Replicat thread.
Action:
Contact Oracle Support.
OGG-06002: Coordinated Replicat process received an unsupported message: type {0}
An unsupported message was received by a Coordinated Replicat process.
Action:
None
OGG-06003: All Replicat threads are registered.
The communication links with all Replicat threads are established.
Action:
None
OGG-06004: Coordinated Replicat thread {0} exited unexpectedly. Please check the report file of {0} for more details.
The coordinator of the coordinated Replicat group received an unexpected thread disconnect event.
Action:
Contact Oracle Support if you cannot determine the cause after viewing the report file for the specified thread.
OGG-06005: Replicat Coordinator failed to receive a message from Replicat thread {0}. Detail: {1}
An error occurred when Replicat Coordinator attempted to receive a message from a Replicat thread.
Action:
Contact Oracle Support.
OGG-06006: Replicat thread failed to make a connection to Replicat Coordinator at {0}. Detail: {1}
An error occurred when Replicat thread attempted to connect to Replicat Coordinator.
Action:
Contact Oracle Support.
OGG-06007: Replicat thread failed to register with Replicat Coordinator. Detail: {0}
An error occurred when Replicat thread attempted to register with Replicat Coordinator.
Action:
Contact Oracle Support.
OGG-06008: Replicat thread failed to send a message to Replicat Coordinator. There was a communication error, or Replicat Coordinator may be in the process of stopping. Detail: {0}
An error occurred when Replicat thread attempted to send a message to Replicat Coordinator.
Action:
Contact Oracle Support.
OGG-06009: Replicat thread failed to receive a message from Replicat Coordinator. Detail: {0}
An error occurred when Replicat thread attempted to receive a message from Replicat Coordinator.
Action:
Contact Oracle Support.
OGG-06010: Not the default Partition, not applying DDL record. This is informational only.
Coordinated Replicat thread is not executing a barrier record. This is expected for all but one of the threads.
Action:
None
OGG-06011: Not the default thread, canceling transaction containing PKUPDATE and letting barrier thread apply the transaction.
Coordinated Replicat thread is not executing a record containing PK Updates. This is expected for all but one of the threads.
Action:
None
OGG-06012: The parameter file of a non-coordinated Replicat contains a THREAD, THREADS or THREADRANGE parameter. These parameters are ignored by non-coordinated Replicats.
The parameter file for a non-coordinated Replicat contains the THREAD, THREADS, or THREADRANGE parameter, which is not supported.
Action:
Remove the THREAD, THREADS, or THREADRANGE parameter or run the Replicat as a coordinated Replicat.
OGG-06013: A HANDLECOLLISIONS clause in the parameter file for a non-coordinated Replicat contains a THREAD, THREADS, or THREADRANGE parameter. The THREAD, THREADS, or THREADRANGE parameter will be ignored.
The parameter file for a non-coordinated Replicat contains a HANDLECOLLISIONS or NOHANDLECOLLISIONS clause with a THREAD, THREADS, or THREADRANGE parameter, which is not supported.
Action:
Remove the THREAD, THREADS, or THREADRANGE parameters from the HANDLECOLLISIONS clause or run the replicat as a coordinated Replicat.
OGG-06014: A non-coordinated Replicat received a HANDLECOLLISIONS or NOHANDLECOLLISIONS command with a THREAD, THREADS, or THREADRANGE parameter. The THREAD, THREADS, or THREADRANGE parameter will be ignored.
A non-coordinated Replicat received a HANDLECOLLISIONS or NOHANDLECOLLISIONS command with a THREAD, THREADS, or THREADRANGE parameter, which is not supported by a non-coordinated Replicat.
Action:
Do not send HANDLECOLLISIONS commands with the THREAD, THREADS, or THREADRANGE parameter to a non-coordinated Replicat.
OGG-06015: The last Coordinated Replicat run did not stop at a clean state and the parameter file has changed.
Changes have been made to the parameter file, and the last run of this Coordinated Replicat group stopped in an inconsistent state.
Action:
Make sure the previous configuration stopped in a consistent state, where all the threads are at the same position (synchronized). Use the normal STOP command to stop threads in a synchronized state, or if they are already stopped, use the SYNCHRONIZE command.
OGG-06016: Unable to set the Coordinated thread checkpoint files or checkpoint table to the desired states. Error: {0}
There was a problem reading or writing a checkpoint file or checkpoint table.
Action:
Make sure the checkpoint files exist and have the proper read/write permissions for Replicat to access them and ensure that the state of the checkpoint table is correct. Contact Oracle support if the problem persists.
OGG-06017: MAP statements can only have one THREAD or THREADRANGE parameter: {0}
A MAP statement contains more than one THREAD or THREADRANGE parameter.
Action:
Remove all but one of the THREAD or THREADRANGE parameters from the MAP statement.
OGG-06018: A HANDLECOLLISIONS or NOHANDLECOLLISIONS parameter in a MAP statement does not match the THREAD or THREADRANGE parameter in that MAP statement: {0}
A HANDLECOLLISIONS or NOHANDLECOLLISIONS parameter within the MAP statement specifies a thread that is not in the THREAD or THREADRANGE clause in that MAP statement.
Action:
Modify the parameters so that HANDLECOLLISIONS and NOHANDLECOLLISIONS specify only threads that are within the map's THREAD or THREADRANGE clause.
OGG-06019: The last Coordinated Replicat run did not stop at a clean state, and the threads were changed in the parameter file. Make sure the previous run stopped in a consistent state (synchronized).
Changes were made to the THREAD or THREADRANGE option in the parameter file, but the last run of this Coordinated Replicat group stopped in an inconsistent state.
Action:
Make sure the previous configuration stopped in an consistent state, where all the threads are at the same position (synchronized). Use the normal STOP command to stop threads in a synchronized state, or if they are already stopped, use the SYNCHRONIZE command.
OGG-06020: Register timed out
A TCP/IP error occurred while the thread was trying to register with the coordinator.
Action:
Check for any firewalls that forbid the connection, such as blocking certain ports or processes. Consult your network administrator if you cannot resolve the problem, before contacting Oracle Support, to rule out any other network issues.
OGG-06021: Register timed out
The Coordinated Replicat thread received an incorrect message from the Coordinator.
Action:
Check for any network issues that may be causing the problem, then contact Oracle Support.
OGG-06022: Cannot execute global SQLEXEC because the thread is not in the coordinated Replicat THREAD list.
The coordinated Replicat thread is not in the list specified in the parameter file. This is expected behavior.
Action:
None
OGG-06023: Parameters associated with the THREAD token in {0} are invalid.
SQLEXEC when used with the THREAD parameter requires valid thread id's.
Action:
Modify THREAD parameter associated with SQLEXEC to include valid id's.
OGG-06024: The {0} parameter is not supported for Coordinated Replicat.
The specified parameter is not supported for Coordinated Replicat.
Action:
Remove the parameter from the parameter file or delete the Replicat and add it as a non-coordinated Replicat.
OGG-06025: The THREAD, THREADS, or THREADRANGE options of the TRACE parameter cannot be used for a non-coordinated Replicat.
A THREAD, THREADS, or THREADRANGE option was detected in the TRACE parameter for a non-coordinated Replicat. These are only supported for Coordinated Replicat.
Action:
Remove the THREAD, THREADS, or THREADRANGE specification from the parameter file or delete the Replicat and then add it as a Coordinated Replicat.
OGG-06026: The parameter file has been changed since Coordinated Replicat started. The Coordinator and threads must all be using the same parameter file.
The parameter file CRC value does not match the one recorded when Coordinated Replicat started. This indicates the parameter file was edited and changed during the startup sequence.
Action:
Restart Coordinated Replicat to make sure Coordinator and threads are using the same file.
OGG-06027: Coordinator received a message that it was not expecting. Detail: {0}
A Coordinated Replicat thread belonging to another group (or another program) has sent the Coordinator a message. This can happen if the Coordinator reused a port used by a previous program or if the sending program is using the wrong port number.
Action:
Check the process that sent the bad message, or restart Coordinated Replicat.
OGG-06028: Coordinated thread {0} cannot continue because the Coordinator is not running.
The Coordinator is not running.
Action:
Check the Coordinator logs to see why it stopped working before the threads could register.
OGG-06029: Coordinator cannot continue because all Coordinated threads failed to register in the time allowed.
The Coordinator waits for a period of time before assuming Coordinated threads have died or had problems registering. The reason for the threads not registering could mean the processes died or had issues connecting with the Coordinator.
Action:
Check the thread logs to see why they had issues starting and registering.
OGG-06030: The THREADRANGE option is only valid for the MAP statement. Use the THREADS option instead
It is not valid to specify the THREADRANGE option outside of a MAP statement.
Action:
Use the THREADS option instead.
OGG-06031: The THREADS option is not valid for the MAP statement. Use the THREADRANGE option instead
It is not valid to specify the THREADS option in a MAP statement.
Action:
Use the THREADRANGE option instead.
OGG-06032: Coordinator has not received message from thread {0}. Heartbeat timer expired.
The Coordinator did not receive a statistics response from the specified thread in the time period specified by the heartbeat timer.
Action:
Check the logs to see what may have caused the thread to be unresponsive.
OGG-06033: Thread {0} has not received message from Coordinator. Heartbeat timer expired.
The coordinated thread did not receive a statistics request from the Coordinator in the time period specified by the heartbeat timer.
Action:
Check the logs to see what may have caused the Coordinator to be unresponsive.
OGG-06034: This Coordinated Replicat thread matches multiple login specifications. Only the first will be used
There are multiple login specifications in the Replicat parameter file that match the Coordinated Replicat thread.
Action:
Modify the parameter file so that no Coordinated Replicat thread is specified in multiple login specifications.
OGG-06035: The startup line or parameter file contains a Coordinated Replicat specific option (like THREAD or THREADS). This option is incompatible with regular Replicat.
The parameter file or startup options for a non-coordinated Replicat contains an option such as THREAD, THREADS, or THREADRANGE, which is not supported.
Action:
Remove the coordinated specific option or run the Replicat as a Coordinated Replicat.
OGG-06036: Unable to access checkpoint table for thread: {0}. Ignore if this is the first startup of this group.
A call to access CSN information in the checkpoint table failed.
Action:
If this is the first time that you started this group after creating it, ignore this message. Contact Oracle Support if it persists.
OGG-06037: Start parameters SKIPTRANSACTION, ATCSN, AFTERCSN and FORCECURRENTPOSITION are mutually exclusive. Only one may be specified per thread. Thread {0} has multiple specifications
Two or more mutually exclusive parameters are specified in the START REPLICAT command.
Action:
Re-issue the START REPLICAT command with only one of the options per thread. Do not use FORCECURRENTPOSITION. It is not valid for START REPLICAT.
OGG-06038: Thread ID {0} is greater than the MAXTHREADS value specified when the Replicat group was created
A thread ID was specified that is greater than the maximum number of threads specified when the Replicat was created.
Action:
Specify a thread ID less than the specified maximum number of threads or delete the Replicat and then re-create it with a greater maximum.
OGG-06039: Thread ID {0} is not active.
A thread ID was specified for a thread that is not active.
Action:
Specify the ID of an active thread.
OGG-06040: Column "{0}" specified in the THREADRANGE parameter does not contain a before image. Either use primary key columns for THREADRANGE or specify the GETUPDATEBEFORES parameter for Extract.
The THREADRANGE parameter contains a column that is not a primary key and that column was updated. The THREADRANGE parameter uses the before image for update operations but cannot find one in this case, because before images are not logged unless the GETUPDATEBEFORES parameter is specified for Extract.
Action:
Either use primary key columns for the THREADRANGE clause or add GETUPDATEBEFORES to the Extract parameter file. Contact Oracle Support if the error persists.
OGG-06041: Sequence {0} is specified in a MAP statement containing a THREADRANGE clause. This is not allowed in Coordinated Replicat. Please map sequence to THREAD clause instead.
THREADRANGE and sequence object type are incompatible in a MAP statement in Coordinated Replicat.
Action:
MAP the sequence to a THREAD clause.
OGG-06042: This thread and the Coordinator are connected to different catalogs. All processes of a Coordinated Replicat must be connected to the same catalog.
All processes of a Coordinated Replicat must connect to the same catalog, but the parameter file specifies different catalogs for some processes.
Action:
Modify the parameter file so that all processes connect to the same catalog.
OGG-06043: The coordinator has not received a heartbeat message from thread {0}. ({1} seconds since last stat message received)
The coordinator did not receive a heartbeat message from the specified thread. If the coordinator does not receive a heartbeat message soon, Replicat may abend.
Action:
Check the status of specified thread. It may be hung or in bad state.
OGG-06044: Statements can only have one THREAD, THREADS, or THREADRANGE parameter
A statement contains more than one THREAD, THREADS, or THREADRANGE parameter.
Action:
Remove all but one of the THREAD, THREADS, or THREADRANGE parameters from the statement.
OGG-06045: Could not find column {0} specified in the THREADRANGE parameter
The process cannot find a column that is specified in a THREADRANGE clause.
Action:
Check the THREADRANGE clause to make certain the name of the column is spelled correctly and that it exists in the source data.
OGG-06046: Not the default thread, canceling transaction containing EVENTACTIONS and letting barrier thread apply the transaction.
Coordinated Replicat thread is not executing a record containing EVENTACTIONS. This is expected for all but one of the threads.
Action:
None
OGG-06047: Not the default thread, canceling transaction containing coordinated record and letting barrier thread apply the transaction.
Coordinated Replicat thread is not executing a transaction containing coordinated records. This is expected for all but one of the threads.
Action:
None
OGG-06048: Error in Replicat communication: {0}
There was an error in Replicat communication.
Action:
If possible, resolve the condition listed in the error message. Otherwise, contact Oracle Support.
OGG-06049: Replicat received an invalid connection
Replicat received an invalid connection.
Action:
Make sure that the ports configured for use by GoldenGate are not used by other processes. Contact Oracle Support if the problem persists.
OGG-06050: Error communicating with thread {0}
Replicat encountered an error when trying to communicate with a thread.
Action:
Fix any problems indicated by other error messages. Contact Oracle Support if the problem persists.
OGG-06051: Connection to Master Replicat unexpectedly terminated
Replicat was disconnected from the master Replicat unexpectedly.
Action:
Fix any problems indicated by other error messages. Contact Oracle Support if the problem persists.
OGG-06052: Error communicating with master Replicat.
Replicat encountered an error when trying to communicate with the master Replicat.
Action:
Fix any problems indicated by other error messages. Contact Oracle Support if the problem persists.
OGG-06053: Conflict in NUM_MAPPERS or NUM_APPLIERS specification for TARGETCATALOG "{0}"
The parameter file contains two TARGETCATALOG specifications for a catalog with conflicting values for NUM_MAPPERS or NUM_APPLIERS.
Action:
Remove the conflicting specification from the parameter file.
OGG-06054: TARGETCATALOG specifications require more Appliers than are available
The TARGETCATALOG specifications in the parameter files specify a number of Appliers greater than the NUM_APPLIERS parameter.
Action:
Modify the TARGETCATALOG specifications to reduce the number of Appliers or increase the value specified for NUM_APPLIERS.
OGG-06055: TARGETCATALOG specifications require more Mappers than are available
The TARGETCATALOG specifications in the parameter files specify a number of Mappers greater than the NUM_MAPPERS parameter.
Action:
Modify the TARGETCATALOG specifications to reduce the number of Mappers or increase the value specified for NUM_MAPPERS.
OGG-06056: A THREAD, THREADS, or THREADRANGE option specifies Thread ID {0}, which is greater than the group's MAXTHREADS ({1}).
A THREAD, THREADS, or THREADRANGE option specifies a Thread ID that is greater than the value of MAXTHREADS, which was specified when the group was created.
Action:
Change the option so that the Thread IDs specified are less than or equal to the value of MAXTHREADS or recreate the Replicat with a higher value of MAXTHREADS.
OGG-06057: The value of SPLIT_TRANS_RECS was changed after Replicat ABENDED. Previous value: {0}.
The value specified for the SPLIT_TRANS_RECS parameter was changed after Replicat abended. Changes to SPLIT_TRANS_RECS should only be made when Replicat is stopped.
Action:
Change the value of SPLIT_TRANS_RECS back to the previous value, START and STOP the Replicat, and then change the value of SPLIT_TRANS_RECS as needed.
OGG-06058: The parameter file of a non-Parallel Replicat contains the SPLIT_TRANS_RECS parameter. This parameter is ignored by non-Parallel Replicats.
The parameter file for a non-Parallel Replicat contains the SPLIT_TRANS_RECS parameter, which is not supported.
Action:
Remove the SPLIT_TRANS_RECS parameter or recreate the Replicat as a Parallel Replicat.
OGG-06059: Not the default thread, canceling transaction containing updated source metadata and letting barrier thread apply the transaction.
Coordinated Replicat thread is not executing a transaction containing updated source metadata. This is expected for all but one of the threads.
Action:
None
OGG-06060: Before image record for table {0} does not exist. Either use primary key columns for THREADRANGE or specify the GETUPDATEBEFORES parameter for Extract.
The THREADRANGE parameter contains a column that is not a primary key and the trail does not contain before image records for that table. The THREADRANGE parameter uses the before image for update operations, but cannot find one in this case, because before images are not logged unless the GETUPDATEBEFORES parameter is specified for Extract.
Action:
Either use primary key columns for the THREADRANGE clause or add GETUPDATEBEFORES to the Extract parameter file. Contact Oracle Support if the error persists.
OGG-06061: Cannot alter Parallel Replicat {0} to non-integrated mode.
Cannot switch apply mode because the specified Replicat is a Parallel Replicat.
Action:
None
OGG-06062: Integrated Parallel Replicat not supported for this DB version.
Integrated Parallel Replicat requires Oracle Database release 12.2 or later.
Action:
Run in a supported Oracle Database release or use non-integrated Parallel Replicat.
OGG-06063: Integrated Replicat not supported for this DB version.
Integrated Parallel Replicat requires Oracle Database release 11.2.0.4 or later.
Action:
Run in a supported Oracle Database release or use non-integrated Replicat.
OGG-06064: The dynamic INTEGRATEDPARAMS only supported for integrated Parallel Replicat in commit serialization mode.
The dynamic INTEGRATEDPARAMS option is only supported for integrated Parallel Replicat in commit serialization mode.
Action:
Add INTEGRATEDPARAMS option to the parameter file and restart replicat.
OGG-06065: Map parallelism must not exceed {1}, current parallelism: {0}.
Map parallelism exceeds the limit for this configuration.
Action:
Reduce Map parallelism in the parameter file.
OGG-06066: Max Apply parallelism must not exceed {1}, current parallelism: {0}.
Max Apply parallelism exceeds the limit for this configuration.
Action:
Reduce Max Apply parallelism in the parameter file.
OGG-06067: Spawned {0} with pid {1}
Replicat spawned a worker process.
Action:
None
OGG-06068: Parallel Replicat only supports trails with full metadata
A Parallel Replicat was configured to replicate data from a trail without full metadata.
Action:
Configure a Replicat that is not Parallel or generate a trail with full metadata.
OGG-06069: Table {0} operations will be handled as barriers as it have more than {1} constraints defined.
Table has more constraints than PR supports, so it will be marked as barrier.
Action:
Modify table so that it have less constraints than the supported by PR.
OGG-06070: DependencyInfo command only valid for Parallel Replicat.
DependencyInfo command issued for a non-Parallel Replicat.
Action:
None
OGG-06071: DEPENDENCYINFO option {0} has invalid argument: {1}.
DependencyInfo command option has an invalid argument.
Action:
Use a valid DependencyInfo command option.
OGG-06072: Invalid DEPENDENCYINFO option: {0}.
DependencyInfo command has an invalid option.
Action:
Use a valid DependencyInfo command option.
OGG-06073: Removed {0} with pid {1}
Replicat removed a worker process.
Action:
None
OGG-06074: Unique constraint columns used in dependency calculation for table {0}: {1}
Map resolved.
Action:
Map resolved.
OGG-06075: Referential constraint columns used in dependency calculation for table {0}: {1}
Map resolved.
Action:
Map resolved.
OGG-06078: Column constraint columns used in dependency calculation for table {0}: {1}
Map resolved.
Action:
Map resolved.
OGG-06079: Scheduler {0}done initializing
Scheduler has completed initialization.
Action:
Scheduler has completed initialization.
OGG-06080: Large transaction processing has started. XID: {0}, Seqno: {1,number,0}, RBA: {2,number,0}. Size of first chunk: {3}
Scheduler has started processing a large transaction.
Action:
Scheduler has started processing a large transaction.
OGG-06081: Large transaction has completed. Total size: {0}
Scheduler has completed a large transaction.
Action:
Scheduler has completed a large transaction.
OGG-06082: Transaction with error {0,number,0} processed in fallback.
An applier found an error in a transaction and processed it in fallback.
Action:
An applier found an error in a transaction and processed it in fallback.
OGG-06084: User requested START SKIPTRANSACTION. The last error transaction will be skipped. Transaction ID {0}, CSN {1}, chunk id {2,number,0}.
The START REPLICAT command was issued with the SKIPTRANSACTION option. Replicat will skip the error transaction from the last run.
Action:
None
OGG-06085: Cannot alter Parallel Replicat {0} to integrated mode.
Cannot switch apply mode because the specified Replicat is a Parallel Replicat.
Action:
None
OGG-06086: Columns {1} in table {0} are deduplicated LOBs and transactions updating these columns will be serialized.
Replicat resolved a table that has deduplicated LOB columns and will serialize transactions that update this LOB column.
Action:
None
OGG-06087: Table {0} is Hybrid Columnar Compressed and transactions on this table will be serialized.
Replicat resolved a table that is Hybrid Columnar Compressed and will serialize transactions on this table.
Action:
None
OGG-06088: Object constraint used in dependency calculation for table {0}, and transactions on this table will be serialized.
Replicat resolved a table with object constraint and will serialize transactions on this table.
Action:
Map resolved.
OGG-06089: Unique index or unique constraint detected on virtual columns and replicat will serialize transactions involving this table {0}.
Replicat resolved a table that has a unique index or unique constraint involving virtual columns and will serialize transactions involving this table.
Action:
None
OGG-06090: Replicat resolved table {0} with bitmap indexes and this may impact applying transactions concurrently. Bitmap columns for table {0}: {1}
Replicat resolved a table with bitmap indexes and this may impact applying transactions concurrently.
Action:
Map resolved.
OGG-06091: Replicat resolved table {0} with bitmap indexes and bitmap index serialization enabled. Transactions on this table will be serialized.
Replicat resolved a table with bitmap indexes and bitmap index serialization enabled.
Action:
Map resolved.
OGG-06092: Table {0} is Hybrid Columnar Compressed and optimistic concurrent apply is enabled. This may result in occasional deadlocks if the HCC table does not have row level locking enabled.
Optimistic concurrent apply to Hybrid Columnar Compressed tables has been enabled.
Action:
Map resolved.
OGG-06093: Initiating barrier to clean up data structures
One of Parallel Replicat's data structures became full.
Action:
None
OGG-06094: Detected inconsistency in internal data structure
An inconsistency was detected in an internal data structure. Replicat will re-initialize the data structure.
Action:
Contact Oracle Support
OGG-06095: Using unified progress checkpoint tables for this Parallel Replicat group.
Parameter _PR_SHARED_CP specified in GLOBALS.
Action:
None
OGG-06096: Using per applier progress checkpoint tables for this Parallel Replicat group.
Parameter _PR_SHARED_CP not specified in GLOBALS.
Action:
None
OGG-06100: Unable to convert an Oracle NUMBER attribute to a CHARACTER string. OCI Error {0}
A NUMBER attribute of a UDT could not be converted to a CHARACTER string, possibly because the data is corrupted.
Action:
Fix the column value in the source database, and then restart Extract so that it captures the corrected data.
OGG-06101: The feature '{0}' is not supported on the current platform.
An option or resource which is not supported on the current platform has been used.
Action:
Use a proper option according to your platform.
OGG-06102: Unable to open credential store. Error code {0}.
The function call to open a credential store returned with an error code.
Action:
Contact Oracle Support for help.
OGG-06103: Alias '{0}' not found in credential store.
The specified alias-credential group are not contained in current credential store.
Action:
Verify the alias and credential group were typed correctly.
OGG-06104: Replicat does not support DDL operations for this database. Ignoring this operation.
Replicat encountered a DDL operation in the trail. DDL is not supported for this database, so this operation will be ignored.
Action:
None
OGG-06105: SHELL argument {0} failed with error value {1}.
The SHELL argument failed due to improper argument specification or an internal expansion processing error.
Action:
Verify that the SHELL expression is valid. If it appears valid, contact Oracle Support for further assistance.
OGG-06106: Bad value for source record.
The source record required to process SHELL arguments is invalid.
Action:
Contact Oracle Support.
OGG-06107: Parameter {0} value was adjusted from {1} to {2}.
The specified parameter value was adjusted by the system.
Action:
None
OGG-06108: Error generating encryption key. Error code {0}. Contact Oracle Support.
Oracle GoldenGate failed to generate an encryption key.
Action:
Contact Oracle Support.
OGG-06109: Error encoding encryption key. Contact Oracle Support.
Trail encryption failed because an encryption key could not be generated.
Action:
Contact Oracle Support.
OGG-06110: Error decoding encryption key. Contact Oracle Support.
An internal error occurred when trying to decode the trail encryption key.
Action:
Contact Oracle Support.
OGG-06111: Error trying to use AES for trail encryption. The cipher is not defined properly.
The process tried to use an AES cipher that is not defined correctly.
Action:
Verify that the AES specification is correct in the parameter file. Note that the same AES specification and key must be used to encrypt the trail and also to decrypt it. For example, if the trail is encrypted with AES 256, it must be decrypted with AES 256. If this problem persists, contact Oracle Support.
OGG-06112: AES encryption key length of {0} bytes exceeds the maximum allowed.
The process tried to use an AES encryption key that is larger than the maximum supported size of 256 bits.
Action:
If the AES key is specified in the parameter file, change it to a supported key size. If the key is Oracle GoldenGate-generated, contact Oracle Support.
OGG-06113: Invalid AES encryption key.
The process attempted to use an AES encryption key with an incorrect value.
Action:
If the AES key is specified in the parameter file, change it to a supported AES key value. If the key is Oracle GoldenGate-generated, contact Oracle Support.
OGG-06114: Error retrieving master encryption key {0} from wallet at location {1}.
The process tried to use an encryption key from the master encryption key wallet but could not find either the wallet or the name or version of the master encryption key.
Action:
Make certain that the GLOBALS parameter WALLETLOCATION contains the path to the appropriate wallet and that the parameter MASTERKEYNAME specifies a valid name and version of a master encryption key that is stored in the specified wallet.
OGG-06115: Error decrypting trail file. Algorithm not supported on this platform.
The trail file header specifies that data has been encrypted with an algorithm not supported on this platform.
Action:
Make certain that the Oracle GoldenGate source configuration for encryption is supported on the target system. If necessary, recreate and resend the trail file with the new configuration.
OGG-06116: The name of a trace file specified in an EVENTACTIONS clause is too long: {0}
The name of the specified trace file in the EVENTACTIONS parameter exceeds the length that is supported by Oracle GoldenGate.
Action:
Use a shorter file name or file path for the name of the trace file, up to the maximum number of characters supported by the operating system for file names.
OGG-06117: Processed LOG event {0}{1}
This is a generic Event Marker Infrastructure informational message relating to the use of the EVENTACTIONS parameter. It may be useful for operational, performance, or diagnostic purposes.
Action:
None
OGG-06118: Processed LOG event {0}{1}
This is a generic Event Marker Infrastructure warning message related to the use of the EVENTACTIONS parameter. It may indicate a potential problem and can be used for operational, performance, or diagnostic purposes.
Action:
Take action based on the message that is returned. If you cannot resolve the problem, contact Oracle Support.
OGG-06119: Trail file {0} is encrypted but no decryption key was found.
The trail file header indicates that its content is encrypted, but the reading process could not find the key in the trail metadata. The Oracle GoldenGate source configuration might be using an ENCKEYS file to store an encryption key, but the reading process is not configured to use this method.
Action:
Make certain that the source and target configuration for trail encryption matches. If using ENCKEYS in source, target needs this method as well. Contact Oracle Support if assistance is needed.
OGG-06120: Trail file is encrypted with master encryption key. Ignoring ENCKEYS configuration
The trail file header indicates that its content has been encrypted using the master encryption key, but the parameter file contains the ENCKEYS configuration.
Action:
Remove the ENCKEYS configuration or specify DECRYPTTRAIL with no options to prevent further warning messages.
OGG-06121: Trail file is not encrypted. Ignoring DECRYPTTRAIL parameter
The trail file header indicates that its content is not encrypted, but the parameter file contains the DECRYPTTRAIL parameter.
Action:
Remove the DECRYPTTRAIL parameter to prevent further warning messages.
OGG-06122: Unable to encrypt a trail file twice with master encryption key. Encryption algorithm found in parameter file: {0}
Encryption with a master encryption key is specified in the parameter file, but the input trail file that the data pump reads is already encrypted with a master encryption key.
Action:
Delete the ENCRYPTTRAIL parameter, or specify the DECRYPTTRAIL parameter if you want to keep ENCRYPTTRAIL.
OGG-06123: Cannot encrypt a trail file twice. Encryption algorithm found in parameter file: {0}. Encryption algorithm found in input trail file {1}.
Encryption is specified in the parameter file, but the input trail file that the data pump reads is already encrypted.
Action:
Delete the ENCRYPTTRAIL parameter, or specify the DECRYPTTRAIL parameter if you want to keep ENCRYPTTRAIL.
OGG-06124: Cannot find AES key when attempting to reencrypt data record at trail file {0}, RBA {1,number,0}.
Added/removed token has forced record reencryption in passthru mode, but the AES key is unavailable in the trail file header.
Action:
Copy the ENCKEYS file to the ABENDED pump's Oracle GoldenGate installation directory if not already available. Set the DECRYPTTRAIL and ENCRYPTTRAIL parameters at pump configuration file in order to force reencryption of the affected record. Optionally, revert back to the previous configuration when the affected record has been processed.
OGG-06125: Trail file uses AES encryption, but the AES key cannot be found in the trail header.
The incoming trail file was originally encrypted using ENCKEYS file enabled key, but the process's parameter file is either missing a DECRYPTTRAIL statement completely, or the DECRYPTTRAIL statement lacks the KEYNAME option needed to identify a individual keys in the ENCKEYS file.
Action:
Copy the ENCKEYS file to the ABENDED pump's Oracle GoldenGate installation directory if not already available. Set the correct DECRYPTTRAIL and ENCRYPTTRAIL parameters in the process configuration file to force decryption and reencryption of user data.
OGG-06126: Oracle Wallet does not exist.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key was not found.
Action:
Ensure the 'CREATE WALLET' command executed successfully.
OGG-06127: Oracle Wallet already exists.
The Oracle Wallet already exists.
Action:
The 'CREATE WALLET' command should be executed once. To open a previously created wallet, use the 'OPEN WALLET' command.
OGG-06128: Oracle Wallet cannot be opened.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key cannot be opened.
Action:
Check file permissions on the wallet file.
OGG-06129: Oracle Wallet cannot be created.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key cannot be created.
Action:
Check file permissions on the wallet file.
OGG-06130: Oracle Wallet cannot be saved.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key cannot be saved.
Action:
Check file permissions on the wallet file.
OGG-06131: Oracle Wallet cannot be read.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key cannot be read.
Action:
Check file permissions on the wallet file.
OGG-06132: Oracle Wallet cannot be written.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key cannot be written.
Action:
Check file permissions on the wallet file.
OGG-06133: Oracle Wallet in use by another process.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key is in use by another process and cannot be used by the current process.
Action:
Exit other Oracle GoldenGate applications and try again.
OGG-06134: Oracle Wallet cannot be purged.
The Oracle Wallet used to store the Oracle GoldenGate master encryption key cannot be purged.
Action:
Contact Oracle Support.
OGG-06135: Oracle Wallet purged successfully.
The Oracle Wallet used to store Oracle GoldenGate master encryption key was purged successfully.
Action:
No action is required.
OGG-06136: Oracle Wallet does not contain a master encryption key.
The Oracle Wallet is empty.
Action:
Use the 'ADD MASTERKEY' command to create the master encryption key.
OGG-06137: Master encryption key '{1}' does not exist in Oracle Wallet {0}.
The Oracle Wallet does not contain the requested master encryption key.
Action:
Use the 'ADD MASTERKEY' command to create the master encryption key.
OGG-06138: Version {2,number,0} of master encryption key '{1}' does not exist in Oracle Wallet.
The Oracle Wallet does not contain the requested master encryption key.
Action:
Use the 'ADD MASTERKEY' command to create the master encryption key.
OGG-06139: Key generation not supported on this platform.
Key generation requires support for random data generation that is not supported on this platform.
Action:
Contact Oracle Support.
OGG-06140: Failed to create new version of master encryption key '{0}'.
Creation of a new version of the master encryption key failed.
Action:
Contact Oracle Support.
OGG-06141: Failed to activate version {1,number,0} of master encryption key '{1}'.
Activation of a version of the master encryption key failed.
Action:
Contact Oracle Support.
OGG-06142: Created version {2,number,0} of master encryption key '{1}' in Oracle Wallet.
A new version of the master encryption key was created and stored in the Oracle Wallet.
Action:
No action is required.
OGG-06143: Master encryption key '{1}' already exists in Oracle Wallet.
A master encryption key already exists in the Oracle Wallet.
Action:
Try the 'RENEW MASTERKEY' command.
OGG-06144: Version {2,number,0} of master encryption key '{1}' in Oracle Wallet already deleted.
The master encryption key version cannot be deleted because it is already deleted.
Action:
No action is required.
OGG-06145: Version {2,number,0} of master encryption key '{1}' in Oracle Wallet is not deleted.
The master encryption key version cannot be undeleted because it is not deleted.
Action:
No action is required.
OGG-06146: Deletion of version {2,number,0} of master encryption key '{1}' in Oracle Wallet failed.
The master encryption key version cannot be deleted.
Action:
Contact Oracle Support.
OGG-06147: Undelete of version {2,number,0} of master encryption key '{1}' in Oracle Wallet failed.
The master encryption key version cannot be undeleted.
Action:
Contact Oracle Support.
OGG-06148: Version {2,number,0} of master encryption key '{1}' in Oracle Wallet was deleted.
The master encryption key version was deleted successfully.
Action:
No action is required.
OGG-06149: All versions of master encryption key '{1}' in Oracle Wallet were deleted.
All versions of the master encryption key were deleted successfully.
Action:
No action is required.
OGG-06150: Version {2,number,0} of master encryption key '{1}' in Oracle Wallet was undeleted.
The master encryption key version was undeleted successfully.
Action:
No action is required.
OGG-06151: Cannot set latest version of master encryption key '{0}'.
Creation of a new version of the master encryption key failed.
Action:
Contact Oracle Support.
OGG-06152: Option {1} not supported for feature {0} on the current platform. Fallback to default behavior.
An option or resource that is not supported on the current platform has been selected. However, it is possible to continue execution using the default option.
Action:
Use a correct option according to your platform to remove warning message.
OGG-06153: FIPS 140 support has been enabled. Process {0,number,0} is using compliant shared libraries to perform encryption for the rest of its execution.
You have designated CRYPTOENGINE FIPS140 in parameter file. This message is positive confirmation that the selected option has been executed for the current process.
Action:
None
OGG-06154: Attempt to enable FIPS 140 support for process {0,number,0} has failed. Error code: {1}, Error Detail: {2}.
You have designated CRYPTOENGINE FIPS140 in parameter file, but the selected option could no be executed for the current process.
Action:
Confirm that the CRYPTOENGINE parameter options are valid. Check the error code and fix the root cause.
OGG-06155: An error was encountered when deleting a Parallel Replicat's database checkpoint.
An error was encountered when deleting a Parallel Replicat's database checkpoint.
Action:
Retry the operation. If the problem persists, Contact Oracle Support.
OGG-06200: A catalog name {0} is specified in an environment where database does not support a catalog.
A catalog name is specified in a database that does not support a catalog.
Action:
Provide a table specification that is valid for your database.
OGG-06201: Parameter {0} is invalid because wildcards in catalog names are not supported.
A wildcard was used to specify a catalog name. Wildcards in catalog names are not supported.
Action:
Change the wildcarded names to their exact names.
OGG-06203: Failed to switch to catalog {0}. OCI Error {2} (status = {1,number,1}), SQL <{3}>
There was a failure when the process attempted to switch catalogs.
Action:
Contact Oracle Support
OGG-06204: A catalog name {0} is specified in a parameter file. However, the target database does not support a catalog.
The database does not support catalogs.
Action:
Provide a table specification that is valid for your database.
OGG-06206: The database connection must be to the root level database for user {0}.
Supply connection information for the root level database.
Action:
Supply connection details to the root level database.
OGG-06207: Connection user {0} is not a common user.
The supplied connection user must be a common user.
Action:
Supply a user who has common user privileges.
OGG-06208: DEFGEN was running against catalog {1}. Only tables in the login catalog {0} can be processed by DEFGEN.
Only tables in the login catalog can be processed by DEFGEN.
Action:
Login to the catalog where target tables reside.
OGG-06209: Use either two-part or three-part names in the DEFGEN parameter file, but not both.
The DEFGEN parameter file contains TABLE specifications that have both two-part names (schema.table) and three-part names (catalog.schema.table). All table names in a given DEFGEN definitions file must be of the same format.
Action:
Edit the DEFGEN parameter file to make the table names consistent.
OGG-06210: Replicat cannot apply transactions to catalog {0} while it is logged into catalog {1}.
Replicat can only apply transactions to its login catalog for the database.
Action:
Specify a target catalog in the TARGET clause that is the same as the login catalog specified in the USERID clause or remove the catalog name from the TARGET clause to use the login catalog as the target catalog.
OGG-06211: DEFGEN failed to access catalog {0} to retrieve table definitions.
DEFGEN was not able to access the specified catalog to retrieve table definitions for the definitions file.
Action:
Make certain the USERID user specified in the parameter file has sufficient privileges to access the catalog, and that the catalog is available in the database.
OGG-06212: Wildcarded catalog names is only supported if DEFGEN logs into the database at the root level.
DEFGEN is configured to log into a specific catalog, but the TABLE specification contains at least one wildcarded catalog specification. To use wildcarded catalog names, DEFGEN must log into the root catalog.
Action:
Take either of these actions: To keep the wildcarded catalog specifications, configure DEFGEN to log into the root catalog, or else remove the wildcarded catalog specifications and change them to match the name of the catalog that DEFGEN logs into.
OGG-06213: DEFGEN cannot use the default catalog for table specification {0} while logged into the root level of a database.
The TABLE parameter does not include a catalog name.
Action:
Specify the fully qualified table name, including the catalog name, in the TABLE parameter in the DEFGEN parameter file.
OGG-06214: Invalid version found in DEFGEN file: {0}
The version number found in DEFGEN's output file is not valid.
Action:
Contact Oracle GoldenGate Support.
OGG-06215: Cannot obtain Pluggable Database information for metadata handle {0}.
Oracle GoldenGate could not obtain information about the Oracle Pluggable Database.
Action:
Make certain that Oracle was installed correctly. If the problem persists, contact Oracle Support.
OGG-06216: The DDL OBJNAME specification {0} does not include a catalog name, and a default source catalog name is not specified for the SOURCECATALOG parameter.
The object name in the DDL OBJNAME statement does not include a catalog name. If a default source catalog name is not specified with the SOURCECATALOG parameter, DDL OBJNAME requires a catalog name.
Action:
Add a catalog name to the DDL OBJNAME object name specification or specify a default source catalog name with the SOURCECATALOG parameter.
OGG-06217: A catalog name {0} is specified in DDL OBJNAME parameter, but the database does not support a catalog.
The database does not support catalogs.
Action:
Provide a DDL OBJNAME specification that is valid for your database.
OGG-06218: The parameter {0} is invalid for a container database.
The specified parameter is not supported for container databases.
Action:
Remove the unsupported parameter.
OGG-06219: Unable to extract data from the Logmining server {0}
An error occurred while reading the input data stream from the Logmining server.
Action:
Query the DBA_CAPTURE view from the mining database to obtain additional information on the specified Logmining server.
OGG-06221: Source container database requires trail FORMAT {0} or higher.
Source container database cannot be supported with the current trail file format.
Action:
Specify a trail file format supported for the source container database.
OGG-06222: An invalid request was made to switch into an empty catalog name.
An attempt was made to switch into a catalog by specifying an empty catalog name.
Action:
Specify a valid catalog name.
OGG-06223: Target character set not supported. Target CCSID: {2}. Error occurred while converting {1} column of table {0}.
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-06224: Character set conversion failure occurred for table {0} in column {1} when converting from source character set {2} to target character set {3}. Error code: {4,number,0}
An internal error occurred during character set conversion.
Action:
Save the error message and contact Oracle GoldenGate Support.
OGG-06300: The '{1}' option for the '{0}' parameter is no longer supported.
The parameter option specified is no longer supported by Oracle GoldenGate.
Action:
Fix the syntax. For help with syntax and values, see the Oracle GoldenGate reference documentation.
OGG-06301: Error calling ftok() on file, '{0}'. Error {1,number,0} - {2}.
An operating system error was returned when attempting to obtain a token for a file.
Action:
Check the local file systems for errors.
OGG-06302: File '{0}' is missing the expected token, '{1}'.
The file specified does not contain the expected contents.
Action:
Correct the file contents and try again.
OGG-06303: Unable to read from file '{0}' (error {1,number,0}, {2}).
An error occurred while the process was reading from an open file.
Action:
Check for related errors in the error log of the operating system. If you cannot resolve the problem, contact Oracle Support.
OGG-06304: Unable to write to file '{0}' (error {1,number,0}, {2}).
An error occurred while the process was writing to an open file.
Action:
Check for related errors in the error log of the operating system. If you cannot resolve the problem, contact Oracle Support.
OGG-06305: Invalid option: expecting 'MMAP', 'SHM', or 'SHM ID N', but found '{0}'.
The datastore was created with an invalid memory specification.
Action:
Issue the DATASTORE command with the correct syntax. For help, see the GGSCI help or the Oracle GoldenGate reference documentation.
OGG-06306: Datastore alter failed.
The datastore environment cannot be altered.
Action:
After stopping all GoldenGate processes, including Manager, issue the ALTER DATASTORE command with the correct syntax. For help, see the GGSCI help or the Oracle GoldenGate reference documentation.
OGG-06307: Datastore does not exist.
The command failed because the datastore does not exist.
Action:
Issue the CREATE DATASTORE command with the correct syntax. For help, see the GGSCI help or the Oracle GoldenGate reference documentation.
OGG-06308: Datastore uses memory mapped (MMAP) environment files.
The datastore uses memory mapping files for its environment resources.
Action:
No action required.
OGG-06309: Datastore uses shared memory (SHM) environment files with a starting ID of 0x{0}.
The datastore uses System V shared memory for its environment resources.
Action:
No action required.
OGG-06310: The {0} DATASTORE command requires that all Oracle GoldenGate processes are stopped, including Manager.
Modifications to the datastore cannot take place while other local Oracle GoldenGate processes are running.
Action:
Stop all GoldenGate processes, including Manager, and try the original command again. For help, see the GGSCI help or the Oracle GoldenGate reference documentation.
OGG-06311: Datastore does not support shared memory on Windows platforms.
The SHM option was used in the command. This option is not supported on Windows.
Action:
Retry the command using the MMAP option.
OGG-06312: '{0}' command unavailable because statistics collection is disabled.
The 'NOSTATS' parameter in the file, 'GLOBALS', disables all statistics collection. When 'NOSTATS' is present, the 'TRACE' and 'TRACE2' commands cannot be used.
Action:
Remove the 'NOSTATS' parameter if statistics collection is desired.
OGG-06313: Collection profiles could not be loaded for this process and are disabled.
When the Collection Profiles cannot be loaded by EXTRACT or REPLICAT, all statistics collection is disabled.
Action:
Enable Activity Logging for additional reasons for the failure.
OGG-06314: Default thread stack size could not be modified.
The default value of the stack size could not be increased because an internal function failed.
Action:
Set PTHREAD_DEFAULT_STACK_SIZE directly in the command shell. If the problem persists, contact Oracle Support.
OGG-06315: Modified the default thread stack size to {0,number,0} bytes.
putenv function succeeded in changing the PTHREAD_DEFAULT_STACK_SIZE. The value of PTHREAD_DEFAULT_STACK_SIZE was successfully changed.
Action:
No action required.
OGG-06316: Table {0} cannot be processed. Capture is not supported for DB2 Catalog tables.
A DB2 Catalog table was specified for capture.
Action:
Remove this table from the TABLE parameter.
OGG-06317: GG_OBJ_METADATA: Catalog name has a length of {0,number,0}, but the maximum allowed is {1,number,0}
The catalog name of the table contains too many characters to be supported by Oracle GoldenGate.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-06318: File name {0} is too long and caused truncation.
While formulating the group file name, a truncation error occurred.
Action:
Use a fully qualified file name that is shorter than 250 characters.
OGG-06319: Could not retrieve definition for table {0}
Unable to retrieve definition for table.
Action:
Contact Oracle Support.
OGG-06320: Replication of UROWID type is only supported for logical ROWID values. In table {0}, UROWID at Column {1,number,0} will not be replicated.
Extract only supports logical ROWID values in a UROWID column. Other ROWID values will be ignored.
Action:
Capture of UROWID values, other than logical ROWIDs, is not supported. Contact Oracle Support.
OGG-06321: DDL Replication is not supported when the source and target databases are from different vendors.
Replication is not supported when the source and target are not from the same database vendor
Action:
None
OGG-06322: Object {0} is an IBM i native name, which is incompatible with trail format level {1}.
The name of the IBM i native object is incompatible with trail formats prior to the 11.2.1 release format.
Action:
Use a SQL alias for the object name, or specify 11.2.1 or later for the FORMAT RELEASE option the of EXTTRAIL, RMTTRAIL, EXTFILE, or RMTFILE parameters.
OGG-06323: {0} is specified. Non ANSI SQL string syntax is used for parameter.
NOUSEANSISQL parameter is specified. Multi byte and special character can not be used for object name for parameter file compatibility.
Action:
None
OGG-06324: Expecting schema name in table name {0}.
Table name parameter doesn't have required schema name.
Action:
Edit the parameter file and supply the schema name.
OGG-06325: Expecting schema name in checkpoint table name {0} in GLOBALS.
Checkpoint table name parameter doesn't have required schema name.
Action:
Edit the GLOBALS parameter file and supply the schema name.
OGG-06326: Extract encountered a snapshot-related error retrieving table {0} during initial load. OCI Error {2} (status = {1,number,0}).
The initial load session encountered a snapshot-related error.
Action:
Refer to the Oracle database documentation for information on the database error code.
OGG-06327: File {0} has invalid byte order specification of 0x{1}.{2,choice,-1#│0# Error when processing RBA {2}}
Oracle GoldenGate found an unrecognized byte order in the specified trail file.
Action:
Contact Oracle Support.
OGG-06328: Invalid byte order found: 0x{0}.{1,choice,-1#│0# RBA: {1}}.
Oracle GoldenGate found an invalid byte order when processing a record or other type of information.
Action:
Contact Oracle Support.
OGG-06329: Trail file {0} using compatibility level {1} is incompatible with byte order specification of {2}. Using default format of {3}.
Oracle GoldenGate found an incompatible byte order specification for a trail file and is replacing it with the proper format.
Action:
Delete the BYTEORDER parameter or specify a compatible format.
OGG-06330: Failed to initialize the parameter file parser.
The parameter file parser could not be initialized.
Action:
Contact Oracle Support.
OGG-06331: Failed to create backup file {0}.
The backup file could not be created.
Action:
Verify that the file doesn't already exist and check the permissions for the parent directory.
OGG-06332: Parameter file {0} has already been converted.
The parameter file is specified more than once on the command line or is included more than once.
Action:
None
OGG-06333: Converting string literals to ANSI SQL while NOUSEANSISQLQUOTES parameter is specified.
This will convert string literals to ANSI SQL (single quotes), and ignore the NOUSEANSISQLQUOTES parameter specified in GLOBALS.
Action:
Remove NOUSEANSISQLQUOTES parameter from GLOBALS.
OGG-06334: Missing option: expecting 'MMAP', 'SHM', or 'SHM ID N'.
The datastore statement requires a valid memory specification.
Action:
Issue the ALTER DATASTORE command with the correct syntax. For help, see the GGSCI help or the Oracle GoldenGate reference documentation.
OGG-06335: Activity Logging wrote {0,number,0}MB ({1,number,0}MB/sec) {2,choice,0#since the application started│1#since last reported}.
Activity Logging is normally generated for all Oracle GoldenGate processes.
Action:
A high rate of Activity Logging may impact Oracle GoldenGate performance.
OGG-06350: Error adding item to transaction {0} for table={1}, op={2,number,0}, record id={3}, length={4,number,0}, errmsg={5}.
An internal error occurred in the Cache Object Manager (COM) when the process added an item to a transaction.
Action:
Contact Oracle Support.
OGG-06351: The LOB columns in table {0} are not supported by the ALLOWTABLECOMPRESSION parameter.
The ALLOWTABLECOMPRESSION parameter is being used for tables that contain LOB columns. Compressed tables with LOB columns are not supported by Oracle GoldenGate for DB2 LUW v9.7.
Action:
Remove the compressed tables that have LOB columns from the Oracle GoldenGate configuration or remove the ALLOWTABLECOMPRESSION parameter and use uncompressed table.
OGG-06352: CACHEMGR: filecaching error 0x{0} truncating file name: {1}, size: 0x{2}, co_uid: 0x{3}, mb_uid: 0x{4}, mf: 0x{5}, mb: 0x{6}, co: 0x{7}
An error occurred truncating a CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-06353: CACHEMGR: filecaching: cm_mf_write_lower WriteFile: {0} error: {1}
An error occurred accessing the CACHEMGR temporary cache file.
Action:
Contact Oracle Support.
OGG-06354: CACHEMGR: object co: 0x{0} co_uid: 0x{1} already exists
An object with the same id (primary or secondary) is already active in CACHEMGR.
Action:
Contact Oracle Support.
OGG-06355: A cache file name is too long for an internal buffer
A cache file name is too long for an internal buffer.
Action:
Contact Oracle Support.
OGG-06356: cm_cachedir_cleanup: ggGetFileList: directory: {0} filespec: {1} err_code: {2} ({3})
An error occurred while cleaning up cache files.
Action:
Contact Oracle Support.
OGG-06357: cm_cachedir_cleanup: remove: file: {0} errno: {1} ({2})
An error occurred while cleaning up cache files.
Action:
Contact Oracle Support.
OGG-06358: CACHEMGR: filecaching wrong temporary file count. opens current 0x{0}, closes: 0x{1}, opens: 0x{2}
The CACHEMGR filecaching has a wrong count for temporary file opens or closes.
Action:
Contact Oracle Support.
OGG-06359: CMDSEC: Failed to retrieve group information ({0}, {1})
The specified error occurred when the process attempted to get group information from the operating system.
Action:
Fix the cause of the error, and then restart the program.
OGG-06360: CMDSEC: Failed to retrieve token information ({0}, {1})
The specified error occurred when the process attempted to get group information from the operating system.
Action:
Fix the cause of the error, and then restart the program.
OGG-06361: CMDSEC: Failed to retrieve token information buffer size ({0}, {1})
The specified error occurred when the process attempted to get group information from the operating system.
Action:
Fix the cause of the error, and then restart the program.
OGG-06362: CMDSEC: Failed to open process token ({0}, {1})
The specified error occurred when the process attempted to get group information from the operating system.
Action:
Fix the cause of the error, and then restart the program.
OGG-06363: CMDSEC: Failed to retrieve user information ({0}, {1})
The specified error occurred when the process attempted to get group information from the operating system.
Action:
Fix the cause of the error, and then restart the program.
OGG-06364: Invalid CMDSEC access specifier (line {0}): {1}
There is an invalid access specifier in the CMDSEC file.
Action:
Fix the CMDSEC file to resolve the cause of the error.
OGG-06365: Invalid CMDSEC uid specifier (line {0}): must be between 0 and {1}
There is an invalid user ID specifier in the CMDSEC file.
Action:
Fix the CMDSEC file to resolve the cause of the error.
OGG-06366: Invalid CMDSEC gid specifier (line {0}): must be between 0 and {1}
There is an invalid group ID specifier in the CMDSEC file.
Action:
Fix the CMDSEC file to resolve the cause of the error.
OGG-06367: Missing CMDSEC entry (line {0}): {1}
There is a missing entry on the specified line in the CMDSEC file.
Action:
Fix the CMDSEC file to resolve the cause of the error.
OGG-06368: The full name of the CMDSEC file is too long
The name of the CMDSEC file (including the path) exceeds the length that is supported by Oracle GoldenGate.
Action:
Use a shorter file path for the CMDSEC file, up to the maximum number of characters supported by the operating system for file names.
OGG-06369: Failed to retrieve user information from the operating system
An error occurred when the process attempted to get group information from the operating system.
Action:
Contact Oracle Support.
OGG-06370: Failed to retrieve user information from the operating system for this process, ({0}, {1})
The process could not retrieve user information from the operating system.
Action:
Fix the cause of the cause of the error and then restart the process.
OGG-06371: Failed to retrieve group entry, ({0}, {1})
There was an error retrieving the user group for the process from the operating system.
Action:
Fix the cause of the error and then restart the process.
OGG-06372: Failed to retrieve user entry, ({0}, {1})
There was an error retrieving the user group for the process from the operating system.
Action:
Fix the cause of the error and then restart the process.
OGG-06373: Failed to retrieve primary group entry, ({0}, {1})
There was an error retrieving the user group for this process from the operating system.
Action:
Fix the cause of the error and then restart the process.
OGG-06374: Invalid DDL statement: No INCLUDE
There is a DDL parameter that does not contain an INCLUDE clause. This parameter will always evaluate to false.
Action:
Correct the DDL statement, remove it altogether, or comment the line out.
OGG-06375: Invalid DDL statement: Missing scope specification
There is a DDL parameter that is missing a scope specification.
Action:
Specify a scope (MAPPED, UNMAPPED, OTHER) in the DDL parameter.
OGG-06376: {0} value must be quoted in single quotes (').
The required single quote marks are missing from a value in the specified parameter.
Action:
Correct the parameter value.
OGG-06377: Single quote marks cannot be used to delimit {0}. Use double quotes.
A value in the specified parameter is enclosed within single quotes, but the correct syntax requires double quotes.
Action:
Replace the single quote marks with double quote marks.
OGG-06378: Double quote marks cannot be used to delimit {0}. Use single quotes.
A value in the specified parameter is enclosed within double quotes, but the correct syntax requires single quotes.
Action:
Replace the double quote marks with single quote marks.
OGG-06379: Operating system user group name {0} is too long for an internal buffer. Maximum supported length is {1}.
The specified operating system user group name is too long for an internal buffer.
Action:
Use a user with a shorter group name.
OGG-06380: Operating system user name {0} is too long for an internal buffer. Maximum supported length is {1}.
The specified operating system user name is too long for an internal buffer.
Action:
Use a user with a shorter user name.
OGG-06381: Error retrieving OS version ({0},{1})
The specified error was encountered while retrieving the operating system version.
Action:
Fix the cause of the error and then restart the process.
OGG-06382: Unrecognized INCLUDE/EXCLUDE option: [{0}]
The specified option is not recognized as a valid INCLUDE or EXCLUDE option.
Action:
Fix the invalid syntax.
OGG-06383: Error checking command security
The process could not verify the security of a command when checking the rules in the CMDSEC file.
Action:
Contact Oracle Support.
OGG-06384: The definition for {0} is missing from the definitions file.
The specified definition template was not available in the definitions file.
Action:
Remove the DEF option from the TABLE/MAP statement or provide a definitions file containing the missing table definition.
OGG-06385: Upgrade operation was not performed because the checkpoint table {0} is already upgraded.
The upgrade operation was not performed because the checkpoint table is already upgraded.
Action:
None
OGG-06386: Purging log history from {0} older than {1}: {2}
Manager was not able to purge rows in the log table that were older than the date shown for the reason shown.
Action:
None
OGG-06387: Purging log history from {0} older than {1}: {2}
Manager is purging history from the log table. Informational only.
Action:
None
OGG-06388: {0} rows deleted from history table
Manager is purging history from the log table. Informational only.
Action:
None
OGG-06389: Unknown number of rows deleted from history table
Manager is purging history from the log table. Informational only.
Action:
None
OGG-06390: Could not delete rows because no database specified
Manager failed to purge history from the log table because no database was specified.
Action:
Specify a database.
OGG-06391: Error deleting rows because of error: {0}
Manager failed to purge history from the log table because of the specified error.
Action:
Correct the specified error.
OGG-06392: PURGEDDLHISTORY parameter will be ignored because it is not supported with this configuration.
Either the database does not support it or the DDL history table does not exist.
Action:
Remove the PURGEDDLHISTORY parameter.
OGG-06393: The data length of {0} exceeds the maximum allowed record length of {1}.
The length of the specified record exceeds the maximum length that is allowed for a remote-task Replicat.
Action:
Contact Oracle Support.
OGG-06394: BEFORE.<column name> syntax has been deprecated, use @BEFORE(<column name>) instead.
The BEFORE.<column name> syntax is deprecated.
Action:
Use @BEFORE(<column name>) syntax instead.
OGG-06395: Extract is not configured to capture DDL, but a DDL operation has occurred for table "{0}", which could adversely affect the integrity of DML capture.
DDL occurred on a table that is in the Extract configuration, but Extract is not configured to capture DDL.
Action:
Configure Extract to capture DDL by adding the appropriate parameters. See the Oracle GoldenGate reference documentation for parameter options.
OGG-06396: WARNING: SPECIALRUN not supported by Integrated Replicat. INTEGRATED keyword ignored
SPECIALRUN is not supported by Integrated Replicat.
Action:
Remove the INTEGRATED keyword.
OGG-06397: The TRANSEXCEPTION option was specified in the REPERROR parameter, but no exceptions mapping was provided for table {0}. The exception cannot be handled.
The TRANSEXCEPTION option was specified for REPERROR, but a mapping to an exceptions table is missing.
Action:
Create an exceptions MAP statement that includes either the MAPEXCEPTION or the EXCEPTIONSONLY option and a mapping of the source table to an exceptions table. For help, see the Oracle GoldenGate administration documentation.
OGG-06398: Unknown encryption type.
The specified encryption algorithm is unknown.
Action:
Specify an encryption algorithm that Oracle GoldenGate supports. See the Oracle GoldenGate security documentation for supported encryption options.
OGG-06399: The specified encryption method is not supported for this platform.
The specified encryption method is not implemented for this platform.
Action:
Specify an encryption method that Oracle GoldenGate supports for this platform. See the Oracle GoldenGate security documentation for supported encryption options.
OGG-06400: The key specified with KEYNAME is not present in the ENCKEYS file.
The ENCKEYS file does not contain a key name that matches the one in the KEYNAME specification.
Action:
Make certain the key name is spelled correctly in the input, or add the key name to the ENCKEYS file.
OGG-06401: No value given for KEYNAME specification.
No key value was specified for the KEYNAME specification in the parameter file.
Action:
Edit the parameter file to specify a key name for the KEYNAME option.
OGG-06402: KEYNAME value exceeds maximum allowed length.
The key value specified for KEYNAME exceeds the maximum allowed length.
Action:
Specify a key value that is compatible with the selected encryption algorithm.
OGG-06403: KEYNAME key value is not a valid hex string.
The value specified for KEYNAME is not a valid hex string.
Action:
Specify a key value that is a valid hex string.
OGG-06404: The key value in KEYNAME does not have a closing quote mark.
The syntax that specifies the key value in KEYNAME does not contain a closing quote mark.
Action:
Add the closing quote mark.
OGG-06405: The length of the key specified in KEYNAME does not match the encryption method.
The length of the key is not appropriate for the encryption algorithm that is specified.
Action:
Specify a key that is appropriate for the algorithm. For supported algorithms and key values, see the Oracle GoldenGate security documentation.
OGG-06406: An error occurred when implementing encryption.
An error occurred during encryption that Oracle GoldenGate could not identify.
Action:
Contact Oracle Support.
OGG-06407: Failed to retrieve encryption key for {0} in file ENCKEYS: {1} {2}.
The specified key could not be retrieved.
Action:
Make sure that the key exists in the ENCKEYS file.
OGG-06408: Failed to initialize encryption context. Detail: {0}
An error occurred during encryption context initialization.
Action:
If the problem persists, contact Oracle Support.
OGG-06409: Failed to encrypting string.
The string could not be encrypted.
Action:
Make certain that the string is valid or use a different one.
OGG-06410: Failed to freeing encryption context. Detail: {0}
An internal error occurred when freeing the encryption context.
Action:
If the error persists, contact Oracle Support.
OGG-06411: Failed to initialize decryption context. Detail: {0}
An internal error occurred when initializing the decryption context.
Action:
If the error persists, contact Oracle Support.
OGG-06412: Failed to decrypt string (-12). Detail: {0}
The string could not be decrypted.
Action:
Decrypt the string with the same algorithm that was used to encrypt it.
OGG-06413: No encryption key specified. Using default key.
An encryption key was not specified for the Blowfish encryption algorithm, so the default key is being used.
Action:
None if the default key is acceptable. To use a specific key, use the ENCRYPTKEY option with a key name in the ENCRYPT command.
OGG-06414: Missing password specification.
The ENCRYPT PASSWORD command was issued without a password specification.
Action:
Issue the command again and include the password that is to be encrypted. For help with syntax, see the Oracle GoldenGate reference documentation or the ggsci help.
OGG-06415: The specified encryption algorithm requires a key value.
The specified encryption algorithm requires a key value.
Action:
Specify an encryption key. For help, see the ggsci help or the Oracle GoldenGate security documentation.
OGG-06416: Default key is not allowed for AES encryption.
An Oracle GoldenGate DEFAULT key was specified for AES encryption. AES requires a user-defined encryption key.
Action:
Generate a valid encryption key for use with AES encryption. For more information, see the Oracle GoldenGate security documentation.
OGG-06417: Using Blowfish encryption with DEFAULT key.
The specified encryption is Blowfish with a DEFAULT key generated by Oracle GoldenGate.
Action:
None
OGG-06418: Must include an 'ENCRYPTKEY' clause to specify a key value for AES algorithm.
AES encryption is specified without an appropriate key value.
Action:
Specify a valid encryption key. For more information, see the Oracle GoldenGate security documentation.
OGG-06419: Must have 'ENCRYPTKEY' clause
The command was issued without an ENCRYPTKEY clause.
Action:
Specify the ENCRYPTKEY clause with a valid keyname when executing this command. For help, see the Oracle GoldenGate security documentation.
OGG-06420: Encryption command invalid. Expecting 'ENCRYPTKEY' or an encryption algorithm.
The encryption command was issued without an ENCRYPTKEY clause or an algorithm specification.
Action:
Issue the command again with the correct input. For help, see the Oracle GoldenGate security documentation or the ggsci help.
OGG-06421: Password encryption failed. Error, key must be specified.
The password could not be encrypted.
Action:
Make sure the password is a valid string, and check for spelling errors. If using an encryption key, make certain that the selected algorithm and the key are compatible. See the Oracle GoldenGate security documentation for help.
OGG-06422: The specified password is not long enough to encrypt; size {0}.
The password is too small to be encrypted.
Action:
Make sure the password has a valid string length. For supported values, see the Oracle GoldenGate security documentation.
OGG-06423: Error decoding encrypted password for TRANLOGOPTIONS ASM password [{0}].
The ASM password in TRANLOGOPTIONS could not be decoded.
Action:
Correct the problem that caused the error shown in the message.
OGG-06424: Error decoding encrypted password for TRANLOGOPTIONS MININGPASSWORD [{0}].
The password specified for the mining database user is not valid.
Action:
Correct the problem that caused the error shown in the message.
OGG-06425: Failed to decrypt password (-12). Detail: {0}
The mining database password could not be decrypted.
Action:
Correct the problem that caused the error shown in the message.
OGG-06426: Decryption failed with error {0}.
The buffer could not be decoded.
Action:
Correct the problem that caused the error shown in the message.
OGG-06427: Error decoding key name {0}, {1}.
The key specified with KEYNAME could not be decrypted.
Action:
Correct the problem that caused the error shown in the message.
OGG-06428: The key specified with KEYNAME could not be decrypted. Key: {0}, Detail: {1}.
The key specified with the KEYNAME option could not be decrypted.
Action:
Correct the problem that caused the error shown in the message.
OGG-06429: Specified key length does not match length of actual key
The length of the key is not appropriate for the encryption algorithm that is specified.
Action:
Specify a key that is appropriate for the algorithm. For supported algorithms and key values, see the Oracle GoldenGate security documentation.
OGG-06430: Encryption algorithm specified without ENCRYPTKEY clause
The algorithm specified requires a key in the ENCRYPTKEY clause.
Action:
Specify a key that is appropriate for the algorithm in the ENCRYPTKEY clause. For supported algorithms and key values, see the Oracle GoldenGate security documentation.
OGG-06431: Auto-encryption and decryption of password failed, passwords do not match
There was a problem with Auto-encryption and decryption of the password.
Action:
Please contact Oracle Support.
OGG-06432: '{0}': This feature is not supported by Oracle GoldenGate Replicat on PostgreSQL. Please refer to the Oracle GoldenGate reference documentation for more details.
This feature is not supported by Oracle GoldenGate Replicat on PostgreSQL.
Action:
Please refer to the Oracle GoldenGate reference documentation for more details.
OGG-06433: No schema is specified for sequence {0} in statement '{1}'. Using default login schema {2}.
A schema was not explicitly given in the specification for this sequence in the parameter file. The default login schema of the process is being used.
Action:
To specify a schema other than the default login schema, edit the parameter file to specify the correct schema.
OGG-06434: Invalid source sequence name {0} specified.
An invalid source sequence name is specified in the TABLE/MAP parameter.
Action:
Specify the correct source sequence name.
OGG-06435: Invalid target sequence name {0} specified.
An invalid target sequence name is specified in the TABLE/MAP parameter.
Action:
Specify the correct target sequence name.
OGG-06436: Missing sequence name specification in TABLE/MAP parameter.
The name of the source sequence is missing from the TABLE or MAP parameter.
Action:
Specify the name of the source sequence.
OGG-06437: No schema is specified for sequence {0} in statement '{1}'. No mapping will be applied.
The sequence specification does not include a schema name. No mapping can be performed without a schema specification.
Action:
Add a schema to the sequence specification, as in schema.sequence. Otherwise, Oracle GoldenGate will assume the login specified in the USERID or USERIDALIAS parameter.
OGG-06438: No schema is specified for table {0} in statement '{1}'. No mapping will be applied.
A schema was not explicitly given in the specification for this table in the parameter file. No mapping will be applied.
Action:
Add a schema to the table specification, as in schema.table. Otherwise, Oracle GoldenGate will assume the login specified in the USERID or USERIDALIAS parameter.
OGG-06439: No unique key is defined for table {0}. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
No unique key is defined for the specified table.
Action:
Use a KEYCOLS clause in TABLE or MAP to define a key that contains unique values. Using a defined key ensures uniqueness and improves performance.
OGG-06440: No viable unique key is defined for table {0}. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
The table definition does not contain a unique key of the type that can be used by Oracle GoldenGate.
Action:
Use a KEYCOLS clause in TABLE or MAP to define a key that contains unique values. Using a defined key ensures uniqueness and improves performance.
OGG-06442: Little-endian byte order and targetdefs specification found.
Oracle GoldenGate found a possible misconfiguration in parameters. In case the target system is NSK, little-endian format for trail files is inadequate.
Action:
Change byte order for output trails to big-endian format.
OGG-06443: No KEYNAME given for {0} encryption algorithm
The encryption or decryption method that is being used requires a key specification with the KEYNAME option.
Action:
Add the KEYNAME option to the ENCRYPT clause, as in ENCRYPT AES128, KEYNAME key_name. For more information, see the Oracle GoldenGate security documentation.
OGG-06444: Database major/minor version not available.
Oracle GoldenGate does not have the database version in its database metadata.
Action:
Please contact Oracle Support.
OGG-06445: Application {0} is starting.
The specified process is starting.
Action:
None
OGG-06446: Schema name is required for table specification "{0}"
The table specification does not include a schema name. A schema name is required when a catalog name is specified.
Action:
Add the schema name to the table specification.
OGG-06447: Default schema name is not allowed for table specification {0}
A default schema name is not allowed to be used in this configuration.
Action:
Specify schema names in the table specifications.
OGG-06448: Could not assign a default schema name for table specification "{0}"
A default schema name or a wildcard schema name is not supported for this configuration.
Action:
Specify a schema name or enable wildcard schemas to be used.
OGG-06449: TARGETDEFS may adversely affect the DDL that is being captured.
The parameter file contains both TARGETDEFS and DDL parameters. DDL is only supported between like tables.
Action:
Remove DDL support for tables affected by TARGETDEFS.
OGG-06450: WARNING: Source column {0} data cannot fit target column {1} buffer. The data will be truncated..
The source column has more bytes/characters than the target column can hold.
Action:
Contact Oracle Support for workaround.
OGG-06451: Triggers will be suppressed by default
By default, Replicat suppresses DML triggers.
Action:
Use SUPPRESSTRIGGERS or NOSUPPRESSTRIGGERS to explicitly indicate the trigger settings.
OGG-06452: DBOPTIONS NOSUPPRESSTRIGGERS is not supported for the RDBMS version you are using.
DML trigger firing is not available on the target database.
Action:
Do not use DBOPTIONS NOSUPPRESSTRIGGERS in the Replicat parameter file.
OGG-06453: DBOPTIONS SUPPRESSTRIGGERS is not supported for the RDBMS version you are using.
DML trigger firing suppression is not available on the target database.
Action:
Do not use DBOPTIONS SUPPRESSTRIGGERS in the Replicat parameter file.
OGG-06454: Database link {0} not supported.
The object type database links are not supported in DDL.
Action:
Filter out DDL operations that involve database links. For filtering options, see the Oracle GoldenGate for Oracle documentation or the DDL parameter in the Oracle GoldenGate reference documentation.
OGG-06455: Empty DEFAULT resolution column group for conflict {0}
The specified conflict has an empty column group for the DEFAULT resolution.
Action:
Ensure that DEFAULT column group contains columns.
OGG-06456: Default tracetable name not allowed on CDB.
A valid tracetable name was not provided in the parameter file.
Action:
Include a valid tracetable name with TRACETABLE statement in parameter file.
OGG-06457: One part tracetable name in replicat parameter file.
One part tracetable name given in replicat parameter file.
Action:
Include a valid 2 or 3 part tracetable name in replicat parameter file.
OGG-06458: Wrong number of tracetable name parts in extract parameter file.
1 or 3 part tracetable name given in extract parameter file.
Action:
Include a valid 2 part tracetable name with TRACETABLE statement in extract parameter file.
OGG-06460: Trail file FORMAT RELEASE {0} or higher is required to support {1} option for table {2}.
The EXTFILE, EXTTRAIL, RMTFILE, or RMTTRAIL parameter contains the FORMAT option, but the given RELEASE value does not support the specified option.
Action:
To support the specified option, set FORMAT RELEASE to at least the version shown in the error message.
OGG-06461: Trail record option {0} is incompatible with {1} for table {2}.
Two different trail record options {0} and {1} are specified for the same table.
Action:
Edit the parameter file so that there is only one trail record format per table.
OGG-06462: The trail file was generated by an Extract that has the UPDATERECORDFORMAT parameter in its parameter file. It is not supported for this database
The trail file was generated by an Extract that has the UPDATERECORDFORMAT parameter in its parameter file. This type of trail is supported only for Oracle version 12 and above.
Action:
Remove the UPDATERECORDFORMAT [FULL│COMPACT] parameter from the Extract parameter file and then restart Extract. Restart the data pump. Stop Replicat and issue the ALTER REPLICAT command with the EXTSEQNO and EXTRBA options to reposition Replicat to the new trail file, and then start Replicat.
OGG-06463: Invalid or incomplete option {0} for UPDATERECORDFORMAT.
Invalid or incomplete option {0} specified for UPDATERECORDFORMAT.
Action:
Edit the parameter file and provide valid UPDATERECORDFORMAT option.
OGG-06464: Duplicate specification of UPDATERECORDFORMAT.
The parameter file contains more than one UPDATERECORDFORMAT parameter.
Action:
Edit the parameter file so that it contains only one UPDATERECORDFORMAT parameter.
OGG-06465: Missing option for UPDATERECORDFORMAT.
The parameter file contains no option for the UPDATERECORDFORMAT parameter.
Action:
Edit the parameter file to add an option for UPDATERECORDFORMAT parameter. Options are FULL or COMPACT.
OGG-06466: The given proxy URI '{0}' is not valid.
The specified URI is not recognizable or is missing.
Action:
Verify that the URI schema is correct (for example http:// and socks5://). Also verify that credentials, address and port number have been specified correctly.
OGG-06467: Invalid proxy type '{0}' found. Expected value is '{1}'.
Cannot use the specified proxy type.
Action:
Specify a valid proxy type according to the message description and try again.
OGG-06471: Unable to disable trigger firing
Replicat was unable to disable trigger firing on the target database.
Action:
Check if the Replicat user has the required privileges to enable trigger suppression.
OGG-06472: Failed to enable DBOPTIONS SUPPRESSTRIGGERS
Replicat was unable to disable trigger firing on the target database.
Action:
Check if the Replicat user has the required privileges to enable trigger suppression or remove DBOPTIONS SUPPRESSTRIGGERS from the Replicat parameter file.
OGG-06473: The parameter list is too long for {0}.
The parameter list is too long for the specified parameter.
Action:
Reduce the number of values for specified parameter, or see the Oracle GoldenGate reference documentation for the correct syntax.
OGG-06474: Cannot specify parameters {0} and {1} together.
The specified parameters cannot be used together in the same parameter file.
Action:
Specify only one of the parameters. See the Oracle GoldenGate reference documentation for the correct syntax.
OGG-06475: {0} {1} was terminated after {2,number,0} seconds
The specified process was terminated because it did not terminate in a timely manner.
Action:
None
OGG-06476: {0} {1} could not be stopped after {2,number,0} seconds
The specified process could not be stopped and is still running.
Action:
None
OGG-06477: After image does not match table definition for {0} at {1}.{2,number,0}. Restart Extract to acquire the most current table definition.
The table may have been altered so that the current definition does not match the log record.
Action:
Restart Extract to acquire the most current table definition.
OGG-06478: {2}: Buffer overflow, needed: {1,number,0}, allocated: {0,number,0}. Table {3}, column {4} at SeqNo {5,number,0} RBA {6,number,0} Transaction {7}.
A numeric conversion failed because the value in the archive logs has more digits that the specified column can contain.
Action:
Verify that the column definitions are correct.
OGG-06479: Schema level supplemental logging, including non-validated keys, is enabled on schema "{0}".
Schema-level supplemental logging, including non-validated keys, is enabled for all objects in the specified schema, as the result of the ADD SCHEMATRANDATA command. Informational only.
Action:
None
OGG-06480: Schema level supplemental logging, excluding non-validated keys, is enabled on schema "{0}".
Schema-level supplemental logging, excluding non-validated keys, is enabled for the specified schema, as the result of the ADD SCHEMATRANDATA command. Informational only.
Action:
None
OGG-06481: The database character set {0} is not English. Use TRAILCHARSETASCII or TRAILCHARSETEBCDIC to ensure correct conversion by Replicat.
The database character set is not English and the TRAILCHARSETASCII or TRAILCHARSETEBCDIC is not specified. Replicat may not be able to correctly perform any required character set conversion.
Action:
Specify either TRAILCHARSETASCII or TRAILCHARSETEBCDIC in the Extract parameter file.
OGG-06482: The parameter _ALLOWTABLECOMPRESSION is deprecated. Use ALLOWTABLECOMPRESSION instead
The startup parameter _ALLOWTABLECOMPRESSION is deprecated.
Action:
Use ALLOWTABLECOMPRESSION to capture compressed tables.
OGG-06483: ALLOWTABLECOMPRESSION is set. LOB columns in compressed tables are not supported with this parameter.
ALLOWTABLECOMPRESSION does not support compressed tables that contain LOB columns.
Action:
For DB2LUW version 9.7 and earlier, uncompress tables that contain LOB columns and capture them with a separate Extract group that does not include ALLOWTABLECOMPRESSION in the parameter file.
OGG-06484: ALLOWTABLECOMPRESSION is only valid for DB2LUW versions 9.7 and earlier. Ignoring this parameter.
ALLOWTABLECOMPRESSION is only valid for DB2LUW versions 9.7 and earlier. For DB2 version 10, Oracle GoldenGate fully supports capturing LOB columns and data from compressed tables simultaneously, without the need for the ALLOWTABLECOMPRESSION parameter.
Action:
Remove the ALLOWTABLECOMPRESSION parameter.
OGG-06485: The {0} link is missing or unreadable from the Oracle GoldenGate product directory. Error {1,number,0}: {2}
The required object link has not been created or may have been deleted. See the previous message for more information.
Action:
Re-run the ggos400install installation script to recreate the link.
OGG-06486: Unable to resolve the object {0}. Error {1,number,0}: {2}
Possible permission issue accessing the object. See the previous message for more information.
Action:
Ensure the user profile has permission to access {0}.
OGG-06487: Failure to load the native object {0}. Error {1,number,0}: {2}
Possible permission issue accessing the object. See the previous message for more information.
Action:
Ensure the user profile has permission to access {0}.
OGG-06488: Failure to load symbol {3} from object {0}. Error {1,number,0}: {2}
The version of the specified Oracle GoldenGate object does not match the version of the installed Oracle GoldenGate build.
Action:
Re-run the ggos400install installation script to update the version of the Oracle GoldenGate objects.
OGG-06489: Datastore created
The datastore was created successfully.
Action:
None
OGG-06490: Datastore altered
The datastore was altered successfully.
Action:
None
OGG-06491: Datastore repaired
The datastore was repaired successfully.
Action:
None
OGG-06492: Datastore deleted
The datastore was deleted successfully.
Action:
None
OGG-06494: Restart Extract to initiate triggerless DDL capture.
It is safe for Extract to switch to triggerless DDL capture.
Action:
Allow Extract to abend, and then restart Extract.
OGG-06495: OGG created a session pool with SESSIONPOOLMAX {0}, SESSIONPOOLMIN {1} and SESSIONPOOLINCR {2}.
A session pool was created for Oracle GoldenGate. The default values are SESSIONPOOLMAX-10, SESSIONPOOLMIN-5, SESSIONPOOLINCR-2.
Action:
Make certain that SESSIONPOOLMAX is equal to the number of pluggable databases. For more information, refer to the Oracle database documentation for session pooling.
OGG-06496: Conflict detection is enabled for target table {0}, but the before values for the key columns are missing.
The specified table has a RESOLVECONFLICT parameter, but the before columns required by COMPARECOLS are not specified with GETBEFORECOLS.
Action:
Specify GETBEFORECOLS in the Extract parameter file so that before images are captured for COMPARECOLS.
OGG-06497: The sequence number {1,number,0} for output trail file '{0}' is approaching the maximum threshold ({2,number,0}) at which point extract will abend. Please consult Oracle Knowledge Management Doc ID 1559048.1 for further actions.
The output trail file sequence number is incremented each time the trail file rolls over. The output trail file sequence number is approaching the maximum threshold value. When this threshold has been exceeded, extract will abend.
Action:
To avoid this, extract will need to be assigned a new trail. Please consult Oracle Knowledge Management Doc ID 1559048.1 for further actions.
OGG-06498: The sequence number {1,number,0} for output trail file '{0}' has exceeded the maximum threshold ({2,number,0}). Please consult Oracle Knowledge Management Doc ID 1559048.1 for further actions.
The output trail file sequence number is incremented each time the trail file rolls over. The output trail file sequence number has reached the maximum threshold value.
Action:
To continue, extract will need to be assigned a new trail. Please consult Oracle Knowledge Management Doc ID 1559048.1 for further actions.
OGG-06500: DDL of length [{5}], marker sequence [{0}], DDL sequence "{1}" for {2}.{3}/{4} is too large. It will be ignored because _IGNORE_TRUNCATE_DDL parameter is specified.
The DDL statement is larger than the supported size. It will be truncated and ignored because the _IGNORE_TRUNCATE_DDL is used in the Extract parameter file.
Action:
Discarding the DDL may cause metadata inconsistencies and generate errors if subsequent DML is issued for the same object. Apply the original DDL on the target, so that the metadata is consistent for future DDL. You may need to restart processes if the condition caused an error.
OGG-06501: Extract is not configured to run on a snapshot standby database. To enable this mode, add TRANLOGOPTIONS MINEFROMSNAPSHOTSTBY to the Extract parameter file.
Oracle GoldenGate is not configured correctly for Extract to run on a snapshot standby database.
Action:
To enable Extract to run on a snapshot standby database, use the TRANLOGOPTIONS parameter with the MINEFROMSNAPSHOTSTBY option in the Extract parameter file.
OGG-06502: Standalone EXCLUDETAG parameter is specified for a Primary Extract.
EXCLUDETAG as a standalone parameter is only valid for data pump and Replicat.
Action:
Specify EXCLUDETAG as a TRANLOGOPTIONS option for Primary Extract, or use it as a standalone parameter for data pump or Replicat.
OGG-06503: Environment variable 'TAG' contains invalid value {0}.
The environment variable 'TAG' must be in a format that represents the binary byte stream in hexadecimal.
Action:
To customize the TAG variable, contact Oracle Support.
OGG-06504: A change record bearing tag {0} is excluded. All following changes with the same tag will also be excluded.
This tag value is specified in EXCLUDETAG clause in the parameter file.
Action:
None
OGG-06510: Using the following key columns for target table {0}: {1}
Map resolved.
Action:
Map resolved.
OGG-06514: Rollback ID {1,number,0} does not match last record ID of {0,number,0} in FM transaction manager. This will be ignored because _ALLOWMISMATCHEDROLLBACKID is set.
An internal inconsistency was detected in the Extract process while processing a transaction rollback.
Action:
Contact Oracle Support.
OGG-06515: Record containing mismatched rollback ID has LRI: {0,number,0}.{1,number,0} and Transaction ID: {2,number,0}.
An internal inconsistency was detected in the Extract process while processing a transaction rollback.
Action:
Contact Oracle Support.
OGG-06516: Could not find definition for {0}, possibly due to insufficient user access privilege.
The process could not find a definition for the specified table when building the object cache, possibly due to insufficient user privilege to access the table metadata.
Action:
Check to make sure the user that is assigned to the process has access privilege to retrieve table metadata from the database. If the user privilege is verified to be sufficient, remove the table from the TABLE and/or MAP parameter. If using wildcards, you can exclude the table with TABLEEXCLUDE or MAPEXCLUDE.
OGG-06517: INFO TRANDATA failed on schema "{0}" because of the following OCI error: {1}-{2}
A OCI error prevented Oracle GoldenGate from getting information about schema-level supplemental logging through the INFO TRANDATA command.
Action:
Fix the OCI error and retry the INFO TRANDATA command. If the OCI error cannot be resolved, contact Oracle Support.
OGG-06518: INFO TRANDATA failed due to error during select start.
The SELECT statement that underlies the INFO TRANDATA command failed.
Action:
Try the command again. If the problem persists, contact Oracle Support.
OGG-06519: Error ({0,number,0}, no data found) selecting data in {1}. Check all DMLs and DDLs are processed before UDT DDLs are processed.
An error occurred when fetching data from an internal cursor. Extract did not complete all of the current DML and DDL before processing the DDL of a UDT.
Action:
Make sure that all current DML and DDL are processed by Extract before issuing DDL for a UDT.
OGG-06520: BATCHSQL is disabled. An issue exists in IBM i that prevents BATCHSQL from functioning correctly. Once resolved through a PTF, BATCHSQL will require IBM i7.1 or greater.
The parameter file contains the BATCHSQL parameter, but BATCHSQL is currently not supported on IBM i due to an IBM issue.
Action:
Remove BATCHSQL or specify the NOBATCHSQL parameter in the parameter file.
OGG-06521: BATCHSQL is disabled because the database or database version does not support it.
The parameter file contains the BATCHSQL parameter, but the database or the database version does not support BATCHSQL.
Action:
Remove BATCHSQL or specify the NOBATCHSQL parameter in the parameter file.
OGG-06522: Cannot verify existence of table function that is required to {0} schema level supplemental logging, {1}.
The function that is used to enable/verify/delete schema level supplemental logging (ADD/INFO/DELETE SCHEMATRANDATA commands) is missing from the database.
Action:
All pre-11204 RDBMS releases need be patched with fix for bug-13794550. Apply the Oracle Patch to the source database.
OGG-06524: The trail or file has reached the 2GB size limit. Add a MAXFILES clause to RMTTFILE or EXTFILE.
The RMTFILE or EXTFILE parameter does not have a MAXFILES clause. Extract abends when the size of the file reaches the 2GB size limit unless a MAXFILES clause exists.
Action:
Add a MAXFILES clause to the EXTFILE or RMTFILE parameter. MAXFILES permits as many files to be created as needed.
OGG-06525: Fetch failed for DBCLOB data type, column {0} in table {1}.
DB2 z/OS ODBC fails to correctly fetch data for data type DBCLOB > 2,000 bytes. IBM APAR PM99329 tracks this issue.
Action:
Apply the fix for IBM APAR PM99329 if available, or, If possible, change Extract to avoid the fetch for this column.
OGG-06526: Internal error: Column with XMLDiff content does not have LOB data: (table {0}, column {1})
There was an internal error when the process tried to compose an UPDATE statement for an XMLtype column.
Action:
Try using the TRANLOGOPTIONS parameter with the FETCHPARTIALXML option in Extract parameter file so that Replicat does not encounter PARTIAL XML. If the problem persists, contact Oracle support.
OGG-06527: Internal error: XMLDiff rewrite failed: (table {0}, column {1}) OCI Err: {2}
There was an internal error when the process tried to compose an UPDATE statement for an XMLtype column.
Action:
Try using the TRANLOGOPTIONS parameter with the FETCHPARTIALXML option in Extract parameter file so that Replicat does not encounter PARTIAL XML. If the problem persists, contact Oracle support.
OGG-06528: Internal GG error: missing key columns for statement (table {0}, io_type={1})
The process could not compose a WHERE clause because the key columns are not available in the transaction record.
Action:
Contact Oracle Support.
OGG-06529: Table name {0} specified in TABLE/MAP clause '{1}' contains a wildcarded catalog. The database does not support wildcards for those objects.
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-06530: Berkeley Database encountered a critical error.
The Berkeley Database cannot be repaired automatically or there is a critical error, such as the system is out of memory.
Action:
Repair the Berkeley Database environment and restart the Oracle GoldenGate groups to re-enable Oracle GoldenGate Monitor activity.
OGG-06531: Table {1} not in default catalog {0} specified in the ODBC connection. TRUNCATE on this table is not allowed by Informix. A DELETE was performed.
The specified table could not be truncated because it does not reside in the default catalog that is specified in the ODBC connection. A DELETE was performed on the table instead.
Action:
None
OGG-06532: Failed to switch to edition {0} in the database. OCI Error {2} (status = {1,number,1}), SQL <{3}>.
There was a failure when the process attempted to switch editions.
Action:
Contact Oracle Support
OGG-06533: Failed to determine default Edition. OCI Error {1} (status = {0,number,0}), SQL <{2}>.
There was a failure when the process attempted to query the default edition.
Action:
Contact Oracle Support
OGG-06534: Reporting diagnostic information for unexpected fetching error. Table Name "{0}", Object Type {1,number,0}, Object ID {2,number,0}, Sequence # {3,number,0}, RBA {4,number,0}, SCN {5}, xid {6}
This is an internal error. The process is reporting diagnostic information to troubleshoot the root cause of an unexpected fetching error.
Action:
Contact Oracle Support.
OGG-06535: Extract does not support the database compatible setting {0}.
Oracle GoldenGate Extract does not support the specified database compatible setting.
Action:
To view a list of supported versions and compatible settings for this database, log onto http://support.oracle.com and select the Certifications tab.
OGG-06537: SOCKS proxy server replied with error: {0}
Oracle GoldenGate received an error reply from the SOCKS proxy server.
Action:
Verify that the SOCKS proxy is configured adequately to accept requests from your host. If required, make sure the authentication information is correctly specified in the Oracle GoldenGate configuration. Finally, contact the server administrator to look for useful information reported by the proxy.
OGG-06538: An error occurred during network communication with the SOCKS proxy server. {0}
Oracle GoldenGate received an unexpected message or an error occurred when sending or receiving information from the network.
Action:
Verify that the SOCKS proxy server is visible from your host. Next, verify that the proxy is running and that the correct host and port have been specified in the parameter file. Finally, contact the server administrator to look for useful information reported by the proxy.
OGG-06539: The server authentication method {0} is not valid.
The SOCKS proxy server asked the client to authenticate with an invalid or unexpected authentication method during the handshake.
Action:
Contact the server administrator to look for useful information reported by the proxy.
OGG-06540: The SOCKS proxy destination address {0} with size {1} exceeds the maximum length of 255 characters allowed.
The address specified in the RMTHOST or RMTHOSTOPTIONS parameter, which the proxy tries to connect with your host, is too long to be managed by the SOCKS 5 protocol.
Action:
Use a shorter name of the address specifying an IPV4 or IPV6 format.
OGG-06541: The SOCKS proxy username or password with size {0} exceeds the maximum length of 255 characters allowed.
Either the username or password specified to authenticate with the proxy server is too long to be managed by the SOCKS 5 protocol.
Action:
Change the username or password for a shorter one.
OGG-06542: An invalid proxy destination address has been specified: {0}:{1}.
The target address and port which the application is trying to connect through the proxy is not valid.
Action:
Verify that the parameter for proxy address and port number has been specified correctly or contact Oracle Support.
OGG-06543: The parameters FORMATASCII/FORMATXML/FORMATSQL are not supported in PASSTHRU mode.
When PASSTHRU mode is specified, table metadata is not available to support the FORMATASCII/FORMATXML/FORMATSQL parameters.
Action:
Either remove the FORMATASCII/FORMATXML/FORMATSQL parameter or remove the PASSTHRU parameters from the parameter file, depending on your configuration requirement.
OGG-06544: Editioned objects are not supported by this version of the Oracle database.
A DDL on an editioned object was found. This DDL cannot be applied because this version of the Oracle database does not support editioned objects.
Action:
Filter the DDL out of the Oracle GoldenGate configuration.
OGG-06545: Failed to switch to edition {0} before applying the following DDL: {1}.
There was a failure when the process attempted to switch editions.
Action:
Correct the error shown or filter the DDL out of the Oracle GoldenGate configuration.
OGG-06546: Failed to reset edition after applying the following DDL: {0}.
There was a failure when the process attempted to reset the edition back to the default.
Action:
Correct the error shown or filter the DDL out of the Oracle GoldenGate configuration.
OGG-06547: Failed to remove the session tag before applying the DDL. DDLOPTIONS NOTAG will be disabled.
There was a failure when the process attempted to remove the session tag.
Action:
No action necessary. DDLOPTIONS NOTAG will be automatically disabled.
OGG-06548: Failed to restore the session tag to {0}. DDLOPTIONS NOTAG will be disabled.
There was a failure when the process attempted to restore a session tag.
Action:
No action necessary. DDLOPTIONS NOTAG will be automatically disabled.
OGG-06549: Value of column {1} in {0} is out of row and FETCHCOLS is not set for this column. Column value cannot be extracted.
Extended row size is enabled for this database, but Extract is not configured to fetch the value from the database.
Action:
Specify this column with the FETCHCOLS option of the TABLE parameter in the Extract parameter file. See the Oracle GoldenGate reference documentation for syntax.
OGG-06550: Unable to position in log buffer, current size {0}. Use parameter TRANLOGOPTIONS BUFSIZE to increase the size, within the range {1} to {2}.
An attempt to position in the log buffer failed because the buffer contained only records with duplicate LRSN values.
Action:
Increase the buffer size, as indicated, to avoid the problem.
OGG-06551: Could not translate host name {0} into an Internet address.
There was an error resolving the host name into an IP address.
Action:
Make sure the host name in the parameter file is specified correctly.
OGG-06552: TRANLOGOPTIONS parameter MINEFROMSNAPSHOTSTBY is not supported for a database that is not a Snapshot Standby database.
TRANLOGOPTIONS parameter MINEFROMSNAPSHOTSTBY is specified for a database that is not a Snapshot Standby database.
Action:
Remove the parameter from the parameter file.
OGG-06553: DDL Annotation, operation [{0}], Number of Annotations: {1,number,0}
A DDL operation has annotations for DDL text
Action:
None
OGG-06554: Failed to set default edition after applying the following DDL: {0}.
There was a failure when the process attempted to set the edition to the database default edition.
Action:
Correct the error as described or filter the DDL out of the Oracle GoldenGate configuration.
OGG-06555: Set default session edition to [{0}].
The process set the session edition to the database default edition. This is an informational message.
Action:
None
OGG-06556: The following columns will not be considered for CDR :{0}
This list of columns are not supported by CDR. Extract will not write the before image for these columns. Replicat will not include these columns for conflict detection.
Action:
None
OGG-06557: PROCESS_GETINFOLIST_() failed, Cpu {0}, Pin {1}, err ({2}, {3}).
Unknown.
Action:
Evaluate the error message details and correct.
OGG-06558: FILENAME_TO_PATHNAME_() failed, for {0}, error {1}.
Unknown.
Action:
Evaluate the error message details and correct.
OGG-06559: FILE_GETINFOBYNAME_() failed, for {0}, error {1}.
Unknown.
Action:
Evaluate the error message details and correct.
OGG-06560: Invalid device type ({0},{1}) for Hometerm {2}.
Hometerm must be either a process or terminal.
Action:
Change hometerm option to valid entry for hometerm.
OGG-06561: PATHNAME_TO_FILENAME_() failed, for {0}, error {1}.
Unknown.
Action:
Evaluate the error message details and correct.
OGG-06562: PROCESS_SPAWN_() failed result {0}, tcpErr/detail ({1}/{2}).
Either the CPU, PRI, HOMETERM, or PROCESSNAME parameter is not valid.
Action:
Evaluate the error message details and correct.
OGG-06563: Value ({0}) out of range for {1}, Range is -1, or {2} through {3}.
Invalid CPU or PRI.
Action:
Evaluate the error message details and correct.
OGG-06564: Invalid parameter {0} for PROCESS_SPAWN_().
Invalid parameter.
Action:
Evaluate the error message details and correct.
OGG-06565: Formatting error on: table name {0}, rowid {1}. Error converting timestamp with timezone from Oracle to ASCII format for column "{2}"
An issue occurred during an attempt to convert column data from Oracle to ASCII format.
Action:
Check the source TIMESTAMP WITH TIME ZONE data. The timestamp value may be invalid or out of range that Oracle GoldenGate can support. Refer to Oracle GoldenGate Reference for Oracle GoldenGate for Windows and UNIX documentation.
OGG-06566: Invalid number ({0}) for {1}
Invalid CPU or PRI.
Action:
Evaluate the error message details and correct.
OGG-06567: Missing attribute value for {0}
Invalid CPU or PRI.
Action:
Evaluate the error message details and correct.
OGG-06568: DBLOGIN can only be used once on the IBM i platform. To use DBLOGIN again, you must restart the application.
DBLOGIN can only be used once on the IBM i platform. To use DBLOGIN again, you must restart the application.
Action:
Exit from GGSCI then use DBLOGIN again.
OGG-06569: Remote Collector/Server version {0}.{1} receiving data is a different version than this Extract {2}.{3} sending data.
The version of the collector is different than the version of this installation.
Action:
To avoid compatibility issues it is suggested to format to the lowest common version using the 'FORMAT RELEASE' parameter in the primary Extract.
OGG-06570: Unable to resolve the object {0}. OGGJRN not found in the GoldenGate installation library. Run the ggos400install script to create OGGJRN, and then run the ADD CHECKPOINTTABLE command again.
OGGJRN not found in the GoldenGate installation library.
Action:
Run the ggos400install script to create OGGJRN, and then run the ADD CHECKPOINTTABLE command again.
OGG-06571: Unexpected path for GoldenGate Service program {0}. Expected {1} part. For example, '/QSYS.LIB/INSTALL_LIBRARY.LIB/OGGPRCJRN.SRVPGM'. Run the ggos400install script.
Unexpected path for GoldenGate Service program.
Action:
Run the ggos400install script.
OGG-06572: Add journaling for the checkpoint table failed. Table name: "{0}". Physical file name: {1}. Journal name: {2}. Review the previous error logs and correct the issues. Run the ADD CHECKPOINTTABLE command after correcting the error log issues.
Review the previous error logs.
Action:
Run the ADD CHECKPOINTTABLE command after correcting the issues specified in the previous error logs.
OGG-06573: Attempt to resolve the GoldenGate installation library failed. Review the previous error logs. Run the ggos400install script, and then run the ADD CHECKPOINTTABLE command again
Review the previous error logs.
Action:
Locate the GoldenGate installation library. Run the ggos400install script, and then run the ADD CHECKPOINTTABLE command again.
OGG-06574: Attempt to resolve the native table name from SQL name failed. Verify that the table was created. Table:{0}. Run the ADD CHECKPOINTTABLE command again
Call to fetch native table name returned zero rows.
Action:
Verify that the table exists then run the ADD CHECKPOINTTABLE command again.
OGG-06575: The value of CHECKPOINTSECS must be greater than zero (0).
The value specified for the CHECKPOINTSECS parameter is invalid.
Action:
Supply a positive integer value for the CHECKPOINTSECS parameter.
OGG-06576: Extended Row Size feature in DB2LUW is not supported when UPDATERECORDFORMAT parameter is set in OGG. Table {0} seems to have columns outside the row due to DB2 extended row size feature.
OGG does not support extended row size when UPDATERECORDFORMAT is set in the extract parameter file.
Action:
Either remove the UPDATERECORDFORMAT parameter or move the table to a tablespace with larger page size.
OGG-06577: Invalid TRACETABLE parameter: {0}. Schema is required.
No schema is specified for the trace table in the TRACETABLE parameter.
Action:
Edit the parameter file and specify the schema name for the TRACETABLE parameter.
OGG-06578: Invalid CHECKPOINTTABLE parameter: "{0}". Schema is required.
No schema is specified for the checkpoint table in the CHECKPOINTTABLE parameter.
Action:
Edit the parameter file and specify the schema name for the CHECKPOINTTABLE parameter.
OGG-06579: Invalid parameter {0} for exclusion specification {1}. Schema is required.
The default schema is not allowed for the TABLEEXCLUDE/MAPEXCLUDE parameter.
Action:
Edit the parameter file and specify the schema name.
OGG-06580: No schema is specified for the source table {0}. The default schema is not allowed.
No schema is specified for the source table in the TABLE/MAP parameter.
Action:
Edit the parameter file and specify the schema for the source table.
OGG-06581: No schema is specified for the target table {0}. The default schema is not allowed.
No schema is specified for the target table in the TABLE/MAP parameter.
Action:
Edit the parameter file and specify the schema for the target table.
OGG-06582: No schema is specified for the table {0} in the DEFGEN parameter file. The default schema is not allowed.
No schema is specified for the table in the DEFGEN parameter file.
Action:
Edit the DEFGEN parameter file and specify the schema.
OGG-06583: No schema is specified for the source sequence {0}. The default schema is not allowed.
No schema is specified for the source sequence in the SEQUENCE parameter.
Action:
Edit the parameter file and specify the schema for the source sequence.
OGG-06584: No schema is specified for the target sequence {0}. The default schema is not allowed.
No schema is specified for the target sequence in the SEQUENCE parameter.
Action:
Edit the parameter file and specify the schema for the target sequence.
OGG-06585: No schema is specified for the DDL/DDLSUBST/DDLERROR INCLUDE/EXCLUDE object name {0}. The default schema is not allowed.
No schema is specified for the include/exclude object name in the DDL/DDLSUBST/DDLERROR parameter.
Action:
Edit the parameter file and specify the schema for the target sequence.
OGG-06586: Trail {0} has an invalid number of digits for the sequence number {1,number,0}.
Trail files can have either 6 or 9 digits for the sequence number.
Action:
Trail files can have either 6 or 9 digits for the sequence number.
OGG-06587: Seqno {0} is out of range, valid range is from {1} to {2}.
Sequence number provided is out of range for the trail's sequence length.
Action:
Provide a sequence number that is within the range for trail's sequence length.
OGG-06588: The remote peer for remote trail {0} does not support 9 digit sequence number.
Remote trail is defined to have a 9 digit sequence number, but the remote peer does not support this feature.
Action:
Recreate the remote trail with a 6 digit sequence number or upgrade the remote peer.
OGG-06589: The startup input position has been rolled back from trail file {0} seqno {1} RBA {2} to seqno {3} RBA {4}.
Recovery repositioned the input trail to an earlier position based on checkpoint information and output trail scanning results.
Action:
None
OGG-06590: The output trail file {0} is not found, rescan for previous ones.
The output trail file indicated by checkpoint record is not found. A rescan will be scheduled to try to recover from a previous trail file.
Action:
None
OGG-06591: Reading the output trail file {0} encounters an error from position {1}, rescan from the file header to recover.
Scanning the output trail file encountered an error, when starting from the position indicated by checkpoint record. A rescan will be scheduled to recover from the beginning of this trail file.
Action:
None
OGG-06592: Recovering from output trail {0} is failed
A recovery attempt on corrupt input position failed.
Action:
Contact Oracle Support.
OGG-06593: Not enough information from output trail {0} to rollback input position.
A recovery attempt on corrupt input position failed, not enough information to find a safe rollback point.
Action:
Contact Oracle Support.
OGG-06594: Replicat {0} has been altered. Even the start up position might be updated, duplicate suppression remains active in next startup. To override duplicate suppression, start {0} with NOFILTERDUPTRANSACTIONS option.
The duplicate suppression is active at startup time by default, even the replicat is altered by GGSCI. To skip duplicate suppression at startup time, use the NOFILTERDUPTRANSACTIONS command line option.
Action:
None
OGG-06595: The replicat command line option FILTERDUPTRANSACTIONS is already a default. It is not necessary to explicitly specify this option.
FILTERDUPTRANSACTIONS is a default option for replicat.
Action:
None
OGG-06596: Internal error processing Component Failed: {0}. Error Message: {1}. Error Text: {2}.
This is an internal processing error.
Action:
Contact Oracle Support.
OGG-06597: Unexpected error when mapping from {0} to {1}. Wildcarded member encountered when it was not expected Member Name: {2}.
This is an internal processing error.
Action:
Contact Oracle Support.
OGG-06598: {0} is a compressed table but TRANLOGOPTIONS ALLOWTABLECOMPRESSION parameter is not specified in the extract parameter file.
OGG can capture compressed tables only when ALLOWTABLECOMPRESSION parameter is specified in the extract parameter file. This applies to DB2 v9.7 and earlier.
Action:
Add ALLOWTABLECOMPRESSION in extract parameter file. Tables with LOB columns cannot be captured when this parameter is set.
OGG-06599: Unable to set replication tag due to OCI error {1} (status = {0, number, 0}), SQL <{2}>
There was an error while setting replication tag in database. This is expected behavior in some RDBMS versions, such as Oracle Database Standard Edition 11.2.0.1.
Action:
None
OGG-06600: The remote peer for remote trail {0} does not support 9 digit seqlen feature. Continuing with 6 digit seqlen.
Remote trail is defined to have a 9 digit sequence number, but the remote peer does not support this feature.
Action:
Downgrade the remote trail with a 6 digit sequence number or upgrade the remote peer.
OGG-06601: Mismatch between the length of seqno from checkpoint ({1}) and recovery ({2}) for extract trail {0}.
The seqlen of trail files returned by recovery process is different from the checkpoint. It's possible that residual trail files from a previous extract process still exist.
Action:
Upgrade/downgrade the seqlen of the trail to match existing trail files or remove any residual trail files from a previous extract process.
OGG-06602: Invalid DBA_GOLDENGATE_SUPPORT_MODE value on table {0}.
Query into DBA_GOLDENGATE_SUPPORT_MODE view returns an unexpected value.
Action:
Contact Oracle Support.
OGG-06603: Invalid parameter {0} specification. Detail: ({1})
The parameter contains an invalid input substitution string.
Action:
Specify a valid substitution string for this parameter. For help, see the Oracle GoldenGate reference documentation.
OGG-06604: Connected to database {0}, CPU info: CPU Count {1}, CPU Core Count {2}, CPU Socket Count {3}
Report the CPU statistics.
Action:
None
OGG-06605: Error ({0,number,0}, {1}) fetching schema name "{2}"
The process could not find the specified schema name in the database.
Action:
Add the schema to the database.
OGG-06606: A root container connection is required when requesting the list of known containers.
The supplied connection must be connected to the root level database.
Action:
Supply connection details to the root level database.
OGG-06607: The user must have common user privileges when requesting the list of known containers.
The supplied connection user must be a common user.
Action:
Supply a user who has common user privileges.
OGG-06608: Cannot obtain container list because the database does not support catalogs.
The database does not support catalogs.
Action:
Make sure the database supports catalogs.
OGG-06609: Cannot find any container matching the container specification {0}.
The container specification does not match any open containers in the database.
Action:
Make sure the container specification is correct.
OGG-06610: Cannot retrieve checkpoint tables while logged into the root level of a database.
Do not retrieve checkpoint tables while logged into the root level of a database.
Action:
Log into the specified container database.
OGG-06611: Multiple journal Extracts are not supported. Split your Extract so that each Extract is reading from only a single journal.
Multiple journal Extracts are not supported. The Extract will be reading from multiple journals based on the tables that are defined in the ALTER EXTRACT command in GGSCI.
Action:
Split your Extract so that each Extract is reading from only a single journal.
OGG-06612: An error occurred during network communication with the SOCKS proxy server. {0}. Please make sure the SOCKS proxy server is running with SOCKS v5 protocol version.
Oracle GoldenGate received an unexpected message or an error occurred when sending or receiving information from the network.
Action:
Verify that the SOCKS proxy server is visible from your host. Next, verify that the proxy is running with SOCKS v5 protocol version and that the correct host and port have been specified in the parameter file. Finally, contact the server administrator to look for useful information reported by the proxy.
OGG-06613: Journal Sequence Number out of order in single journal Extract. Journal: {0}. Current Journal Receiver: {1}. Current Journal Sequence Number: {2}. Previous Journal Sequence Number: {3}. This is likely due to Journal Sequence Number has been reset for the journal {0}. Review this and position the Extract manually on the new journal receiver then start the Extract.
Journal Sequence Number out of order in single journal Extract. This is likely due to Journal Sequence Number has been reset for the journal {0}.
Action:
Position the Extract manually on the new journal receiver then start the Extract.
OGG-06614: Oracle version {0} is not supported.
A connection was made to an unsupported version of the Oracle Database.
Action:
Connect to a supported version of Oracle Database. See the Oracle GoldenGate reference documentation for more details.
OGG-06615: Oracle redo compatible version {0} is not supported.
Extract does not support this redo compat version.
Action:
See the Oracle GoldenGate reference documentation for more details.
OGG-06616: End of broken receiver chain. Please position the extract to read from the next journal receiver chain manually and restart the extract. Current Journal Receiver : {0}/{1}
End of broken receiver chain.
Action:
Position the extract to read from the next journal receiver chain manually and restart the extract.
OGG-06617: Exception when calling System API. Details: {0}
Exception while calling Native API.
Action:
Review the error details.
OGG-06618: Database {0} Platform: {1}
Report the database platform.
Action:
None
OGG-06619: Cross Endian support for Integrated Extract is enabled
Integrated Extract is running on a CPU architecture with an Endian format that is different than that of the Oracle Database instance it is connecting to.
Action:
None
OGG-06620: System Sequence Number (*SYSSEQ) is not included in the fixed length data (FIXLENDTA) for journal {0} which is required for a multi-journal Extract. Add *SYSSEQ to the FIXLENDTA for the journal and restart the Extract, or remove the journal from the Extract if not required.
System Sequence Number (*SYSSEQ) is not included in the fixed length data (FIXLENDTA) for journal {0} which is required for a multi-journal Extract.
Action:
Add *SYSSEQ to the FIXLENDTA for the journal and restart the Extract, or remove the journal from the Extract if not required.
OGG-06621: Cannot replicate table {0} to database version {1} in Direct mode. The minimum required database version is 12.1.0.2.
Replicat was unable to process a table with DML handlers because the target database was earlier than 12.1.0.2 release.
Action:
Use the dbms_apply_adm.set_dml_handler procedure to remove the DML handler by specifying the user_procedure as NULL. For more information, see the "SET_DML_HANDLER Procedure" documentation in the Oracle Database PL/SQL Packages and Types Reference, version 12.1 release.
OGG-06622: System Sequence Number (*SYSSEQ) is not included in the fixed length data (FIXLENDTA) for at least one journal in the multi-journal capture set up. Refer the previous warning messages and add *SYSSEQ in the FIXLENDTA for the journals, then restart the Extract.
System Sequence Number (*SYSSEQ) is not included in the fixed length data (FIXLENDTA) for at least one journal in the multi-journal capture set up.
Action:
Refer the previous warning messages and add *SYSSEQ in the FIXLENDTA for the journals, then restart the Extract.
OGG-06623: System CCSID {0} is not supported. CCSID {1} will be used instead.
The CCSID value obtained from the system is not recognized by Oracle GoldenGate or cannot be used for character conversion.
Action:
Set an appropriate CCSID to match the expected encoding on the system. See the IBM documentation for how to change this correctly as this may not match what the system SQL catalog uses.
OGG-06624: Job CCSID {0} is not supported. CCSID {1} will be used instead.
The CCSID value obtained for the job is not recognized by Oracle GoldenGate or cannot be used for character conversion.
Action:
Set an appropriate CCSID to match the expected encoding for the data if not converting text data to UTF-8.
OGG-06625: The Physical File {0} mentioned in the Extract parameter file is not journalled. Enable trandata for this file by ADD TRANDATA command or remove this table from the Extract parameter file and restart the Extract.
Physical File {0} mentioned in the Extract parameter file is not journalled.
Action:
Enable trandata for this file by ADD TRANDATA command or remove this table from the Extract parameter file and restart the Extract.
OGG-06626: ODBC Error {1} (status = {0,number,0}). {2}
An error occurred in the ODBC.
Action:
Resolve the problem based on the error that is shown in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-06627: Replicat sets the key columns for each table replicated by inbound server {0}
Replicat explicitly sets the key columns for each table replicated by the specified inbound server.
Action:
None
OGG-06628: Journal Sync timeout: A time out occurred while trying to wait for the cached journal entries. Resolution: Increase the number of retries, or use the JOURNALSYNCFLUSHCACHE option. Increasing the wait time could cause an increased latency in the Extract. However, the optimal combination of JOURNALSYNCWAITTIME and RETRIES is dependent on the particular environment Extract is running in. Journal Name :{0}/{1} Journal Receiver Name :{2}/{3} Actual Last Entry :{4} Current Last Entry :{5}
A time out occurred while trying to wait for the cached journal entries.
Action:
Use the 'JOURNALSYNCFLUSHCACHE' option, or increase the number of retries by tuning 'JOURNALSYNCWAITTIME' and 'RETRIES' parameters.
OGG-06630: A change record bearing tag {0} is included. All following changes with the same tag will also be included.
This tag value is specified in INCLUDETAG clause in the parameter file.
Action:
None
OGG-06631: EXCLUDETAG + is specified. All change record with tags will be excluded.
EXCLUDETAG + is specified.
Action:
None
OGG-08000: Could not create OCI environment.
Failed to create OCI environment by OCIEnvNslCreate() call.
Action:
Ensure that your Oracle Database instance is installed and configured properly.
OGG-08001: Could not retrieve error detail after failed to allocate OCI error handle. OCI status: {0}.
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}.
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}.
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}.
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}.
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}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08007: Failed to allocate the server context. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08008: Failed to allocate the service context. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08009: Failed to attach the remote server {1}. OCI status: {0}.
Could not attach 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}.
Could not attach 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}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08012: Failed to set the external name {1} attribute. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08013: Failed to set the internal name {1} attribute. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08014: Failed to allocate the session context. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08015: Failed to set the user name {1} attribute. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08016: Failed to set the password attribute. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08017: A connect descriptor is required for connection creation.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08018: Module attribute was not set to the OCI session.
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}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08020: Failed to retrieve OCI error detail on OCI session begin failure.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08021: Oracle password may be expired soon. Error code: {0}, Error Detail: {1}.
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}.
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}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08024: Failed to end the OCI session. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08025: Failed to detach from the server. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08026: Failed to free the service context. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08027: Failed to free the session context. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08028: Failed to free the server context. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08029: Failed to free the describe handle. OCI status: {0}.
This is an internal OCI error.
Action:
Contact Oracle Support.
OGG-08030: Username required for database connection.
A username was not supplied.
Action:
Supply a password.
OGG-08031: Password required for database connection.
A password was not supplied.
Action:
Supply a password.
OGG-08032: Invalid username specification for OS authentication.
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.
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.
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.
Transparent Application Failover (TAF) has initiated a reconnect.
Action:
None
OGG-08036: The database connection failover has completed.
Transparent Application Failover (TAF) has completed a reconnect.
Action:
None
OGG-08037: The database connection failover is being retried because of an error.
Transparent Application Failover (TAF) was unable to reconnect. The reconnect is being retried.
Action:
None
OGG-08038: The database connection failover has been canceled.
Transparent Application Failover (TAF) reconnect was canceled.
Action:
Restart the application.
OGG-08039: Mixing bind by position and bind by name is unsupported.
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.
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}.
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.
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.
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.
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}.
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.
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}.
An attempt to destroy a session pool failed with the reported error.
Action:
Correct the error reported.
OGG-08048: Failed to initialize timezone information. Check location of ORACLE_HOME.
Received ORA-01804 while trying to initialize OCI environment. Ensure that your ORACLE_HOME setting is valid.
Action:
Correct the error reported.
OGG-08049: Invalid operation on a connection to a single pluggable container.
An application attempted to execute an invalid operation on a single pluggable container connection.
Action:
Do not attempt this operation on a single pluggable container connection.
OGG-08050: User does not have update access to the LOGMNR_BUILD LOG table.
The user lacked the required permissions to update the LOGMNR_BUILD LOG table in the RDBMS.
Action:
Do not attempt this operation on a single pluggable container connection.
OGG-08051: Database connection failover is not supported for Replicat.
Transparent Application Failover (TAF) reconnect is not supported for Replicat.
Action:
Restart the application.
OGG-08053: Database connection failover is not supported for Extract.
Transparent Application Failover (TAF) reconnect is not supported for Extract.
Action:
Restart the application.
OGG-08100: {0}
A generic information message was printed, check the message for more detail.
Action:
None
OGG-08101: Invalid TARGETEXTTRAIL name.
The name of the trail file specified is not correct.
Action:
Verify the correct usage of enclosing quotes.
OGG-08102: Invalid file name.
The name of the trail file specified is not correct.
Action:
Verify the correct specification of path and trail filename.
OGG-08103: File portion of the trail file name must be two characters.
The name of the trail file specified is larger than two characters.
Action:
Specify a file name consisting of only two characters.
OGG-08104: Extract group {0} does not exist.
The specified Extract group has not been added.
Action:
Add the Extract group first or use an existing one.
OGG-08105: Extract group {0} is running, cannot be altered.
The Extract process cannot be modified when running.
Action:
Stop the Extract process first.
OGG-08106: Trails cannot be used with an EXTRACT task.
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.
The specified trail file was previously added.
Action:
Specify a different trail file name.
OGG-08108: TARGETEXTTRAIL does not exist.
The specified trail file has not been added.
Action:
Add the specified trail file.
OGG-08109: Unable to get current checkpoint data.
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}
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}.
The value is not valid for reported argument.
Action:
None
OGG-08112: Cannot {0} {1} - Legacy protocol disabled in the Oracle GoldenGate Admin Service
The configuration setting for the 'enableLegacyProtocol' in the Oracle GoldenGate Admin Service is set to 'false'.
Action:
Change the 'enableLegacyProtocol' setting to 'true' to enable the legacy protocol.
OGG-08114: Command '{0} {1}' is not supported by the Oracle GoldenGate Admin Service
The Oracle GoldenGate Admin Service does not recognize or support the specified command.
Action:
Contact Oracle Support.
OGG-08115: The Task Manager is disabled in the Oracle GoldenGate Admin Service
The configuration setting for the 'enableTaskManager' in the Oracle GoldenGate Admin Service 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
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.
Oracle GoldenGate Services Edition does not support creation of passive extract processes.
Action:
Use the Oracle GoldenGate Distribution Service to specify a connection initiated by the Receiver Service.
OGG-08118: EXTRACT tasks cannot be registered.
Extract tasks cannot be registered with the database.
Action:
Remove the registration option.
OGG-08119: Trails cannot be added for the specified group
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.
Files do not exist for the trails specified.
Action:
Ensure that the trail files are present on the system.
OGG-08121: The file name '{0}' does not match the pattern '{1}'.
The passed file does not match the specified pattern.
Action:
Ensure that the file name matches the pattern.
OGG-08122: The managed process settings profile '{0}' does not exist.
The specified managed process settings profile does not exist.
Action:
Check the managed process settings profile name.
OGG-08123: The auto-restart rule feature no longer exists.
The auto-restart rule feature no longer exists. It is replace with auto-restart configuration data.
Action:
Use the auto-restart configuration endpoints.
OGG-08124: The managed process settings profile '{0}' is used by {1} '{2}'.
The specified managed process settings profile is in use and cannot be deleted.
Action:
Update the specified process to not use the profile and try the delete operation again.
OGG-08125: Replicat group {0} does not exist.
The specified Replicat group has not been added.
Action:
Add the Replicat group first or use an existing one.
OGG-08126: Replicat group {0} is running, cannot be altered.
The Replicat process cannot be modified when running.
Action:
Stop the Replicat process first.
OGG-08127: ER group {0} does not exist.
The specified ER group has not been added.
Action:
Add the ER group first or use an existing one.
OGG-08201: Extract group {0} is running. Stop the Extract group to execute this command.
The specified Extract group is currently running. The command cannot be executed unless the Extract group is stopped.
Action:
Stop the Extract group, and then issue the command.
OGG-08202: Could not delete file {0} ({1,number,0}, {2}).
Failed to delete the file.
Action:
None
OGG-08203: Could not delete DB checkpoint for Replicat group {0} ({1}).
Failed to delete the database checkpoint.
Action:
None
OGG-08204: Extract group {0} deleted.
Extract or Replicat group is deleted by the user.
Action:
None
OGG-08205: Replicat group {0} deleted.
Extract or Replicat group is deleted by the user.
Action:
None
OGG-08209: Error: {0}
Used by GGSCI to print into console, but by Admin Service to log elsewhere.
Action:
None
OGG-08211: {0}
Cause is not known before hand, check error message for more detail.
Action:
None
OGG-08212: Error: Database {0} is in READ ONLY mode.
Undefined
Action:
Undefined
OGG-08216: Error: Cannot register or unregister Extract group {0} because no database login was provided. Use DBLOGIN to establish a connection.
Undefined
Action:
Undefined
OGG-08217: A root container connection is required when registering or unregistering Extract for a container database.
Undefined
Action:
Undefined
OGG-08218: A root container connection to the downstream database is required when registering or unregistering Extract on a container database.
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.
Undefined
Action:
Undefined
OGG-08220: The user must have common user privileges when registering or unregistering Extract for a container database.
Undefined
Action:
Undefined
OGG-08221: Cannot register or unregister Extract group {0} because of the following SQL error: {1}.
Undefined
Action:
Undefined
OGG-08222: Extract group {0} must be registered with the database to perform this operation.
Undefined
Action:
Undefined
OGG-08223: Error: One or more containers must be specified when registering Extract for a container database.
Undefined
Action:
Undefined
OGG-08224: Error: CONTAINER option was specified though the database does not support containers.
Undefined
Action:
Undefined
OGG-08225: Extract {0} successfully registered containers with database at SCN {1}.
Undefined
Action:
Undefined
OGG-08226: Extract {0} successfully dropped containers from database.
Undefined
Action:
Undefined
OGG-08227: Container list contains too many containers.
Undefined
Action:
Undefined
OGG-08228: Invalid container name {0}.
Undefined
Action:
Undefined
OGG-08229: Error: Database container {0} is not registered.
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.
Undefined
Action:
Undefined
OGG-08231: Error: Drop container for Extract group {0} is already in progress; wait then try again.
Undefined
Action:
Undefined
OGG-08232: Error: Database container {0} has already been registered.
Undefined
Action:
Undefined
OGG-08233: Error: The global name of the database container {0} is in restricted mode.
Undefined
Action:
Undefined
OGG-08234: Error: Database container {0} does not exist.
Undefined
Action:
Undefined
OGG-08235: Error: Database container {0} is not open.
Undefined
Action:
Undefined
OGG-08236: Wildcard is not allowed in container name {0}.
Undefined
Action:
Undefined
OGG-08237: Error: This Extract group {0} cannot be used as a SHARE candidate. Use SHARE AUTOMATIC for finding a valid share candidate.
Undefined
Action:
Undefined
OGG-08238: Error: This database does not have the required patch to support a SHARE clause. Remove the SHARE clause.
Undefined
Action:
Undefined
OGG-08239: Error: Downstream Integrated Extract requires SCN clause in conjunction with the SHARE clause. See REGISTER command with the SHARE clause in the Oracle GoldenGate documentation.
Undefined
Action:
Undefined
OGG-08240: Error: The SHARE clause is not supported when registering Extract for a container database.
Undefined
Action:
Undefined
OGG-08241: Error: This Extract group {0} is already registered with the database.
Undefined
Action:
Undefined
OGG-08242: Error: The logmining server failed to locate dictionary for PDB {0}.
Undefined
Action:
Undefined
OGG-08243: WARNING: Extract group {0} failed to archive the current redo log file on the source database because of the following SQL error: {1}. See Extract user privileges in the Oracle GoldenGate documentation.
Undefined
Action:
Undefined
OGG-08244: Root container {0} can not be specified in any REGISTER CONTAINER command because it is automatically registered.
Undefined
Action:
Undefined
OGG-08245: Container {0} was specified more than once in the container list.
Undefined
Action:
Undefined
OGG-08246: Wrong syntax.
Undefined
Action:
Undefined
OGG-08247: Cannot unregister Replicat group {0} because no database login was provided. Use DBLOGIN to establish a connection.
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.
Undefined
Action:
Undefined
OGG-08250: Option {0} is not allowed for Extract group {1}.
A command was issued with an invalid option for the given Extract mode.
Action:
Use a valid option for the given Extract mode.
OGG-08251: This command is being forced
A command was issued with the bang[!] option. The user will not be prompted for confirmation.
Action:
None
OGG-08252: Error: Wildcard not allowed for this command.
Undefined
Action:
Undefined
OGG-08253: Error: Invalid command.
Undefined
Action:
Undefined
OGG-08254: Could not delete file {0} ({1,number,0}, {2})
Undefined
Action:
Undefined
OGG-08255: Process {0} not currently running.
A process that is not currently running was tried to be stopped.
Action:
None
OGG-08257: Could not find port information for Extract group {0}.
Oracle GoldenGate could not find the listening port for the Extract.
Action:
Contact Oracle Support.
OGG-08258: Data source is required for Extract {0} command.
No data source was specified.
Action:
Specify a data source.
OGG-08259: Specified data source is not known.
An unsupported data source was detected.
Action:
Specify a supported data source.
OGG-08260: Apply mode is required for {0} REPLICAT.
No apply mode was specified.
Action:
Specify an apply mode.
OGG-08261: Specified apply mode is not known.
An unsupported apply mode was detected.
Action:
Specify a supported apply mode.
OGG-08262: EXTFILE or EXTTRAIL required for ADD REPLICAT.
No valid data source was specified.
Action:
Specify either EXTTRAIL or EXTFILE.
OGG-08264: Berkeley DB repository version mismatch error.
The Berkeley DB version used by the repository does not match the dirbdb files.
Action:
Delete and Re-Create the Datastore.
OGG-08265: Error: Database container {0} is unsupported
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}'.
Trail file name and path specifications are not case-sensitive.
Action:
None
OGG-08267: A source database connection is required when unregistering or deleting an extract in an upstream configuration.
UNREGISTER or DELETE EXTRACT command in an upstream configuration was issued but a connection to the source database is not established.
Action:
Logon to the source database, and then retry the command.
OGG-08270: {0} option is not supported for register command with the current release
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.
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.
The specified trail file was found in the local filesystem.
Action:
Purge old trail files prior to starting the Extract process.
OGG-08274: Extract {0} cannot be registered as it is a pump
The REGISTER command is being run on a pump Extract, which cannot be run in integrated mode.
Action:
Do not run the REGISTER EXTRACT command on a pump Extract.
OGG-08276: Auto-restart rule '{0}' has been added.
Informational only.
Action:
None
OGG-08277: Auto-restart rule '{0}' has been updated.
Informational only.
Action:
None
OGG-08278: Auto-restart rule '{0}' has been deleted.
Informational only.
Action:
None
OGG-08279: Cannot parse the 'q' parameter to be a valid JSON or JavaScript Object: {0}
The 'q' query parameter could not be parsed as a valid JSON or JavaScript Object string.
Action:
Check the syntax of the 'q' query parameter.
OGG-08280: Cannot parse a valid combination of filters in the 'q' parameter: {0}
The 'q' query parameter does not specify a valid combination of filters for this endpoint.
Action:
Check the filters in the 'q' query parameter.
OGG-08281: Cannot parse to be a valid '{0}' filter: {1}
A filter in the 'q' query parameter is not specified correctly.
Action:
Check the filter in the 'q' query parameter.
OGG-08282: Could not find port information for Replicat group {0}.
Oracle GoldenGate could not find the listening port for the Replicat.
Action:
Contact Oracle Support.
OGG-08283: Replicat group {0} is running. Stop the Replicat group to execute this command.
The specified Replicat group is currently running. The command cannot be executed unless the Replicat group is stopped.
Action:
Stop the Replicat group, and then issue the command.
OGG-08284: Extract group {0} not currently running.
Extract that is not currently running was tried to be stopped.
Action:
None
OGG-08285: Replicat group {0} not currently running.
Replicat that is not currently running was tried to be stopped.
Action:
None
OGG-08286: Extract group {0} is initializing, please try the command later.
A command for the Extract that is in an initialization stage was tried to be executed.
Action:
Retry the command later.
OGG-08287: Replicat group {0} is initializing, please try the command later.
A command for the Replicat that is in an initialization stage was tried to be executed.
Action:
Retry the command later.
OGG-08288: Extract group {0} does not exist.
The specified Extract does not exist.
Action:
Check Extract type or group name.
OGG-08289: Replicat group {0} does not exist.
The specified Replicat does not exist.
Action:
Check Replicat type or group name.
OGG-08290: ER group {0} does not exist.
The specified ER does not exist.
Action:
Check ER group name.
OGG-08291: Extract group {0} is not registered with the database.
The extract group may have already been unregistered or registered with different database credentials.
Action:
Log in to the database with the same credentials that were used to register the extract group.
OGG-08500: {0}
A generic information message was printed, check the message for more detail.
Action:
None
OGG-08501: Requested Operation on path {0} failed
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
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
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: Distribution Service Shared Context is not initialized
The shared context for Distribution Service cannot be initialized.
Action:
Contact Oracle Support.
OGG-08505: Distribution Service TPC {0} is not valid
The TPC thread for a distribution path cannot be started with invalid command context.
Action:
Contact Oracle Support.
OGG-08506: Distribution Service failed to add path {0}
Distsvc failed to add the specified path to the system.
Action:
Contact Oracle Support.
OGG-08507: Target path {0}, is prefixed by an unsupported protocol
Protocol specified at the URL is not known to Distribution Service.
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.
Informational only.
Action:
None
OGG-08509: The begin time string {0} is invalid.
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}.
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.
Informational only.
Action:
None
OGG-08512: The path '{0}' has been updated.
Informational only.
Action:
None
OGG-08513: The path '{0}' has been started.
Informational only.
Action:
None
OGG-08514: The path '{0}' has been stopped.
Informational only.
Action:
None
OGG-08515: The path '{0}' has been terminated.
Informational only.
Action:
None
OGG-08516: The path '{0}' has been deleted.
Informational only.
Action:
None
OGG-08517: The operation for path '{0}' timed out.
Distribution Service 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}'.
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.
Informational only.
Action:
None
OGG-08520: The path '{0}' is already stopped.
Informational only.
Action:
None
OGG-08521: The path '{0}' is already terminated.
Informational only.
Action:
None
OGG-08522: Invalid command context.
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.
Informational only.
Action:
None
OGG-08524: The path '{0}' is already in the process of stopping.
Informational only.
Action:
None
OGG-08525: The network connection could not be established.
The connection between the Distribution Service and the Receiver Service 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 Service or the Manager is running and listening on the expected port.
OGG-08526: The specified encryption algorithm '{0}' is not supported for trail encryption. Only AES is supported.
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.
Informational only.
Action:
None
OGG-08528: The AES library could not be loaded.
The AES library could not be loaded.
Action:
Contact Oracle Support.
OGG-08529: Invalid command received for path '{0}'.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-08530: Path '{0}' could not be reloaded.
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.
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.
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}'.
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}'.
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}
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}
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 '{0}' URI values other than the host and port is not allowed
The property specified cannot be changed with a PATCH operation.
Action:
Correct the property from the PATCH request.
OGG-08538: Invalid status {1} in path '{0}' request. Expected {2}.
There was an error processing the distribution path request because the specified status is invalid.
Action:
Try the request again specifying a valid status for the distribution path.
OGG-08539: Invalid JSON response returned by the Distribution Service command handler.
Oracle GoldenGate Distribution Service failed to create a valid JSON response.
Action:
Contact Oracle Support.
OGG-08540: Invalid JSON request received by the Distribution Service command handler.
The command request received by Oracle GoldenGate Distribution Service is an invalid JSON object or does not conform to any expected JSON schemas.
Action:
Contact Oracle Support.
OGG-08541: Command '{0}' is not supported by Oracle GoldenGate Distribution Service
Oracle GoldenGate Distribution Service does not recognize or support the specified command.
Action:
Contact Oracle Support.
OGG-08542: Error serializing the Distribution Service command response.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-08543: Unallowed operation for target-initiated path {0}.
Distribution Service cannot apply the specified operation because the path is target-initiated.
Action:
Perform the operation in Receiver Service.
OGG-08544: Cannot create path '{0}' because there is already a checkpoint file that belongs to another path with the same name.
Distribution Service cannot create a new checkpoint file for the given path name because it already exists. This is indication that a target-initiated path exists but it is currently not running.
Action:
Use a different path name. Otherwise, if there are no target-initiated paths and the checkpoint file is not used anymore, manually delete it.
OGG-08545: Error returned from Distribution Service at {0}: {1}.
Distribution Service failed to execute a 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-08546: Could not complete HTTP request {0} {1} to Distribution Service at {2}. Reason: {3}.
The Receiver Service failed to make an HTTP request to the Distribution Service, even though the path is running. As a result, some information returned with this response may be unavailable or incomplete.
Action:
Verify that the Distribution Service is running and can accept requests from Receiver Service's host. If you cannot resolve the problem, contact Oracle Support.
OGG-08547: HTTP request {0} {1} to server at {2} failed. Server replied: HTTP {3} - {4}.
The Receiver Service received an error response from the Distribution Service.
Action:
Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.
OGG-08548: {4}: {0} records processed as of {1} (rate {2}, delta {3})
Information only.
Action:
None
OGG-08549: {0} records processed as of {1} (rate {2}, delta {3})
Information only.
Action:
None
OGG-08550: {0} records processed as of {1}. Caller: {2}.
Information only.
Action:
None
OGG-08551: {0} records processed as of {1}
Information only.
Action:
None
OGG-08552: Can only make NULL comparisons using EQ or NE operator
Invalid filter rule.
Action:
Don't use any operator other than EQ or NE when making a NULL comparison.
OGG-08553: Waiting at EOF on input trail file {0}, which is not marked as complete, but succeeding trail file {1} exists. Likely ALTER ETROLLOVER has been performed on source extract. Automatically updated the checkpoint to read from the next trail file.
Extract was upgraded, and an ALTER EXTRACT command with ETROLLOVER was issued to roll over the existing trail to a new file that is of the correct format for the new version.
Action:
None
OGG-08555: Input trail file checkpoint is missing for the distribution path {0}.
The Distribution server may not be properly configured or checkpoint may be corrupted.
Action:
Check the Distribution server configuration and the checkpoint. Contact Oracle GoldenGate support.
OGG-08556: Could not read the input trail file checkpoint position for the distribution path {0}.
The checkpoint may be corrupted.
Action:
Contact Oracle GoldenGate Support.
OGG-08557: The stop operation for path '{0}' is in progress, the path will be fully stopped after finishing processing the current open transaction.
The stop operation on the distribution path could not be completed before timeout because a transaction is still in progress.
Action:
Query the status of the path again later.
OGG-08558: Message from server at {0}: {1}
The remote server replied with an error response while performing an HTTP request.
Action:
Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.
OGG-08559: Invalid partition name based rule filters mixed in an inclusion rule with OR relation among filters.
There was an invalid usage of partition name based filters mixed with non-partition name filters in the distribution path request. Inclusion rules with OR relation among filters can not have partition name based filters.
Action:
Try the request again specifying a valid rule filters for the distribution path by restructuring the rule filters.
OGG-08560: The length of the key {0} found in ENCKEYS file ({1} bytes) does not match the specified encryption method {2}.
The length of the key is not appropriate for the encryption algorithm that is specified.
Action:
Specify a key that is appropriate for the algorithm or verify that the ENCKEYS file contains the correct encryption keys. For supported algorithms and key values, see the Oracle GoldenGate security documentation.
OGG-08561: Could not retrieve the encryption key {0} from ENCKEYS file.
A problem occurred when trying to get the encryption key from ENCKEYS file.
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-08562: The JSON property '{0}' can only be used with algorithms AES128, AES192 or AES256. Incorrect algorithm found: '{1}'.
An invalid combination of keyname property and algorithm value found in the JSON specification.
Action:
Correct the JSON payload by specifying a valid algorithm or removing the keyname property.
OGG-08563: Request for path '{0}' failed because the path metadata was not loaded correctly.
There was a problem with loading an existing path definition when initiating the server.
Action:
Delete and create the path again.
OGG-08564: Invalid or missing OAuth resource - audiencescope in Client application
Path could not be started because the client application in the Identity Provider does not have the correct resource - audiencescope.
Action:
Assign the right audience and scope in the client application to include the resource of target.
OGG-08565: The network connection could not be established: '{0}' - '{1}'
The connection between the Distribution Service and the Receiver Service or the Manager could not be established. This can be due to a network problem or an error in the setup.
Action:
Check for the reason - Verify the URI provided for the Distribution Path. Check that the Receiver Service or the Manager is running and listening on the expected port.
OGG-08566: The client certificate with name '{0}' for distpath {1} does not exist.
There was a problem with loading a named client certificate for this distpath.
Action:
Make sure the named certificate has been uploaded into the certificate store properly.
OGG-08567: The client certificate with name '{0}' does not exist.
There was a problem with loading a named client certificate for this distpath.
Action:
Make sure the named certificate has been uploaded into the certificate store properly.
OGG-08569: UUID '{1}' generated for path '{0}'
Informational only.
Action:
None
OGG-08600: The data stream '{0}' has been added.
Informational only.
Action:
None
OGG-08601: The data stream '{0}' has been updated.
Informational only.
Action:
None
OGG-08602: Data Stream {0} not found
A data stream specified in the request cannot be found in the system.
Action:
Verify the data stream name in the service request.
OGG-08603: Data stream {0} already exists
The specified data stream already exists in the system.
Action:
Use a different data stream name in the service request.
OGG-08604: The data stream '{0}' has been deleted.
Informational only.
Action:
None
OGG-08605: The data stream request specification contains invalid property.
The given data stream request specification in the handshake is invalid.
Action:
Check the syntax of the data stream request specification.
OGG-08606: Failed to start the data streaming.
The start of data streaming encounters an error.
Action:
Check the the data stream request specification in the handshake.
OGG-08607: Failed to pack data into the data streaming buffer.
Error encountered while filling the data streaming buffer.
Action:
Contact Oracle GoldenGate Support
OGG-08608: internal error encountered while streaming data.
Error encountered streaming the data to the client
Action:
Contact Oracle GoldenGate Support
OGG-08609: Data Stream {0} is already in use
A data stream request cannot be completed due to a resource conflict.
Action:
Verify the data stream resource is not in use already.
OGG-08610: Data Stream {0} request does not have query parameter begin
The websocket establish request does not have begin query parameter.
Action:
Verify the data streaming request has a valid begin position inside query parameter.
OGG-08701: Unsupported datatype {0} ({1,number,0}) found in a UDT in a nested table.
An unsupported datatype is defined in an object table.
Action:
Exclude the UDT from the Oracle GoldenGate configuration.
OGG-10000: The column data type '{0}' is not supported Oracle GoldenGate.
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.
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.
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.
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.
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}'.
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}'.
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.
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.
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.
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.'
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}".
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}'.
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}
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}".
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}".
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}
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.
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 is not being used for restore. Extract will revert to normal recovery for this recovery and then turn on Bounded Recovery again.
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. Please report any failure of a bounded recovery to Oracle, even if Extract fully recovers.
OGG-10020: DDL statement succeeded with the following message: {0}.
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.
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.
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.
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}.
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}.
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}.
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.
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}]
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.
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}".
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}].
The process is setting the session Edition for the DDL operation. This is an informational message.
Action:
None
OGG-10033: The catalog name is missing in the stored procedure {0}.
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}.
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} .
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.
The SYSCDC functions required for Oracle GoldenGate capture are not installed in the current database.
Action:
Check the ODBC Datasource 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}.
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}.
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.
Invalid input for VAM PARAMS in the capture parameter file.
Action:
Refer to Reference for Oracle GoldenGate for Windows and UNIX.
OGG-10040: Capture process cannot handle CDC record type {0}.
Capture process cannot handle CDC record type.
Action:
Refer to Reference for Oracle GoldenGate for Windows and UNIX for the supported record types.
OGG-10041: CDC session is still valid and the error received {0} can be ignored.
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.
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 block' command. 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.
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}.
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.
Problem reading from the static repository file for parameter definitions
Action:
Contact Oracle Support.
OGG-10103: File {0}, line {1}: Parsing error, value "{2}" is out of legal range ({3}) for [{4}].
Specified parameter value is out of the legal range for that value.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the valid range.
OGG-10104: File {0}, line {1}: Parsing error, value "{2}" is not a valid argument for "{3}".
Specified value is not valid.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the legal values.
OGG-10105: File {0}, line {1}: Parsing error, parameter [{2}] is expected to immediately precede [{3}].
Specified parameter needs to be specified immediately after another.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10106: File {0}, line {1}: Parsing error, parameter [{2}] is expected to precede [{3}].
Specified parameter needs to be specified after another.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10107: File {0}, line {1}: Parsing error, parameter [{2}] conflicts with parameter [{3}].
Specified parameter cannot be specified with another.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10108: File {0}, line {1}: Parsing error, parsing encountered an error.
Issue found while parsing the parameter files.
Action:
Contact Oracle Support.
OGG-10109: File {0}, line {1}: Parsing error, parameter with name "{2}" is not defined.
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.
An unexpected internal error occurred.
Action:
Contact Oracle Support.
OGG-10111: Error opening parameter definition file: {0}. errno: {1,number,0} - {2}
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}
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
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}
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
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
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
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
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}"
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.
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
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
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.
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}].
A specified value does match any value in the accepted list of valid strings.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10125: ({0}): Required parameter [{1}] is missing.
A parameter is required but has not been specified.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification and include the required parameter.
OGG-10126: The GLOBALS file is missing.
The GLOBALS file is missing.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification, and then include the required parameter.
OGG-10127: ({0}) line {1}: Parsing error, required parameter option [{2}] is missing.
A parameter option is required though has not been specified.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification, and then include the required parameter.
OGG-10128: Timestamp {0,date} {0,time} is not found within LRI range {1}.{2} - {3}.{4}.
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.
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
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
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}
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.
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.
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.
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}).
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.
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.
The parameter file for a Parallel Replicat that is applying to multiple target catalogs contains an EVENTACTIONS specification.
Action:
None
OGG-10140: ({0}) line {1} column {2}: Parsing error, unexpected value "{3}".
Parameter parser encountered an unexpected value.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10141: ({0}) line {1} column {2}: Parsing error, value "{3}" syntax error.
Parameter parser encountered a syntax error.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX 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.
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.
Parameter parser could not find a specific parameter definition.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10144: ({0}) line {1}: Parameter [{2}] is not valid for this configuration.
This parameter is not recognized for this running process.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10145: ({0}) line {1}: Parsing error, parameter [{2}] is missing a required value.
This parameter is missing a required value.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10146: Invalid algorithm: {0} Use AES128 AES192 AES256 or BLOWFISH.
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.
This parameter cannot be specified more than once.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10148: Original expression [{0}] -- Expanded expression [{1}]
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.
This option is missing a required value.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10150: ({0}) line {1}: Parsing error, option [{2}] for parameter [{3}] cannot be specified multiple times.
This option cannot be specified more than once.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10151: ({0}) line {1}: Parsing error, parameter [{3}] has unrecognized keyword or extra value "{2}".
Specified parameter value is not valid.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the legal values.
OGG-10152: ({0}) line {1}: Parsing error, option [{3}] for parameter [{4}] has unrecognized value "{2}".
Specified option value is not valid.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the legal values.
OGG-10153: SHELL contains DDL argument {0} is not allowed for DML record.
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}"
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}
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}.
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.
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}.
Specified parameter is required to be on a specific line.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10159: ({0}) line {1}: Parsing error, parameter [{2}] is missing a required unit value.
This parameter is missing a required unit value.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10160: ({0}) line {1}: Parsing error, option [{2}] for parameter [{3}] is missing a required unit value.
This option is missing a required unit value.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10161: Logical end of file reached on {0} at RBA {1,number,0}.
A logical end of file was reached while reading the trail file.
Action:
None
OGG-10162: End of file reached on trail file {0}.
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}.
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.
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}.
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}
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}].
Parameter or option needs to be specified immediately after one of the parameters or options in the shown list.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10168: ({0}) line {1}: Parsing error, one of the following parameters or options [{2}] is expected to precede [{3}].
Parameter or option needs to be specified after one of the parameters or options in the shown list.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10169: ({0}): Parsing error, one of the following parameters or options [{1}] is required to be used with [{2}].
One of the required parameters in the displayed list is missing.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10170: ({0}): Parsing error, one of the following parameters [{1}] is required to be used in this file.
One of the required parameters in the displayed list is missing.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10171: ({0}) line {1}: Parsing error, parameters or options [{2}] conflict with parameter [{3}].
Specified parameters cannot be specified with one another.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10172: ({0}) line {1}: Parsing error, [{2}] requires at least one option to be used.
Specified parameter requires at least one option to be used.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10173: {0}
A parameter parsing error was detected, but can be ignored.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-10174: ({0}): Fatal error in parser [{1}].
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-10175: ({0}) line {1}: Parsing error, [{2}] is obsolete.
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.
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.
Specified range is not valid.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX 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.
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 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.
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.
All unique indexes on virtual columns are ignored as specified by the DBOPTIONS parameter.
Action:
None
OGG-10183: Parameter file {0} passed validity check.
The specified parameter file has been parsed and validated.
Action:
None
OGG-10184: Parameter file {0} failed validity check.
The specified parameter file has been parsed and validated.
Action:
Check the syntax and values of the parameters.
OGG-10187: Instantiation CSN filtering on table {0} has started at CSN {1}.
Instantiation Filtering is enabled and the source table has an instantiation CSN set. Replication for this table will begin after the instantiation CSN.
Action:
None
OGG-10188: Instantiation CSN filtering on table {0} has ended, now passing transactions starting at CSN {1}.
Instantiation CSN Filtering is disabled. Replication for this table will begin now.
Action:
None
OGG-10200: PLSQL operation found [{0}]
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.
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.
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 datatype {2}:{3} is not supported by Oracle GoldenGate.
The specified column data type is not supported by Oracle GoldenGate.
Action:
Refer to the Informix Oracle GoldenGate documentation for the datatypes 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 datatype {2}:{3} is ignored by CDC capture.
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 param file. Otherwise, data will not be captured for this column.
OGG-10303: Extract VAM PARAMS {0} specified is invalid and unsupported.
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}.
Undefined
Action:
Undefined
OGG-10352: Could not complete the send operation.
The data channel contains an invalid internal state and cannot complete the send request. Previous errors were detected.
Action:
Contact Oracle Support.
OGG-10354: Stopping path writing trail {0} from {1} due to incoming primary request from {2} to write the same trail.
The Receiver Service 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}.
The Receiver Service 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}.
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.
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-10360: Conflict detected, duplicate request for target trail file received with 'Override' activated.
The Receiver Service 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: Distsvc expected a message from recvsvc that was not received.
A probable cause is that the Receiver Service failed or was stopped.
Action:
Try restarting the distribution path or both the Distribution Service and Receiver Service. If the problem persists, contact Oracle Support.
OGG-10362: A message was expected to complete the negotiation, but no message was received.
A probable cause is that the other end failed or was stopped.
Action:
Try restarting the distribution path or both the Distribution Service and Receiver Service. If the problem persists, contact Oracle Support.
OGG-10363: Unable to create channel because the URI schema '{0}' is unrecognizable.
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.
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 documentation for the allowed values of this property.
OGG-10365: Incorrect port or port range specification {0}. Error: {1}. This specification will be ignored.
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 documentation for the allowed values of this property.
OGG-10366: Ending port {0} must be greater than or equal to starting port {1}. This specification will be ignored.
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.
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
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 Service
Oracle GoldenGate Receiver Service does not recognize or support the specified command.
Action:
Contact Oracle Support.
OGG-10370: Error processing legacy Collector configuration parameters.
There was an error processing the legacy Collector configuration in Receiver Service.
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 Service shared context. {0}
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}.
An internal error occurred and an incorrect path name was generated in Receiver Service.
Action:
Contact Oracle Support.
OGG-10373: Invalid socket value when receiving network data: {0}.
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
A probable cause is that the remote process is stopped or terminated.
Action:
Ensure that the remote process is running. Contact your Network Administrator to rule out any other network issues before contacting Oracle Support.
OGG-10375: There was a problem creating the Receiver Service shared context. {0}
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-10376: Distsvc expected a message from recvsvc at {0} that was not received.
A probable cause is that the Receiver Service failed or was stopped.
Action:
Try restarting the distribution path or both the Distribution Service and Receiver Service. If the problem persists, contact Oracle Support.
OGG-10377: Invalid DELETE operation for read-only Receiver Service path '{0}'.
An attempt to delete a non target-initiated distribution path was performed on Receiver Service.
Action:
Make sure that the name of the path was spelled correctly and that the path is a target-initiated distribution path.
OGG-10378: Request on path {0} failed.
The operation on this path failed.
Action:
Review log files and other error messages and correct the issues before retry.
OGG-10379: Could not communicate with Distribution Service at {0}. The checkpoint file in the source host may require to be manually deleted.
Receiver Service could not send the DELETE command to Distribution Service.
Action:
The checkpoint file in the Distribution Service host may need to be manually removed.
OGG-10380: Path name '{0}' cannot be used. Please specify a different one.
The specified distribution path name cannot be used because the pattern matches the autogenerated path names.
Action:
Specify a different name.
OGG-10381: Checkpoints request on path {0} is not supported.
The endpoint for checkpoints is supported only for target-initiated paths.
Action:
Make sure that the name of the path was spelled correctly and that the path is a target-initiated distribution path.
OGG-10382: Only network options are allowed in requests for path {0}.
The JSON payload is missing the network options.
Action:
Specify the network options in the request payload. Also, make sure the request was not meant for a target-initiated path.
OGG-10383: Ignoring non-network payload fields for PATCH request on path {0}.
The JSON payload contains extra properties that are not part of network options.
Action:
Specify only network options in the request payload. Also, make sure that the request was not meant for a target-initiated path.
OGG-10384: DELETE request on path {0} is not supported.
The DELETE operation is supported only for target-initiated paths.
Action:
Make sure that the name of the path was spelled correctly and that the path is a target-initiated distribution path.
OGG-10385: Progress request on path {0} is not supported.
The progress endpoint is not supported for target-initiated paths.
Action:
Make sure that the name of the path was spelled correctly and that the path is not a target-initiated distribution path.
OGG-10386: Info request on path {0} is not supported.
The info endpoint is supported only for target-initiated paths.
Action:
Make sure that the name of the path was spelled correctly and that the path is a target-initiated distribution path.
OGG-10387: Cannot process the request for path {0} because it is no longer active.
The specified path is no longer connected to the Distribution Service and cannot be modified anymore.
Action:
Make sure that the name of the path was spelled correctly or specify a different path.
OGG-10388: Timeout after {0} seconds establishing a websocket communication with {1}.
The connection with the server could not be established before the timeout was reached.
Action:
Set a bigger timeout value in the network configuration options. Also, make sure the destination server is running and accepting connections.
OGG-10389: Cannot get checkpoint information for target-initiated path {0}. The path is not running.
The checkpoint information for target-initiated paths is only available when the path is running and Receiver Service is connected to Distribution Service.
Action:
Start the target-initiated path and try again.
OGG-10390: Generic error {1} noticed for endpoint {0}. Error description - {2}.
A generic error occurred while establishing network connection to the specified endpoint.
Action:
Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.
OGG-10392: Duplicate request to write trail {0} received. Ignoring new request. Trail is already being written by path '{1}'
The Receiver Service is already processing a trail with the same name as the new request.
Action:
Change the target trail name for one of the conflicting Distribution Path.
OGG-10393: Conflict detected, duplicate request for target trail file received. Trail is also being written by path '{0}'
The Receiver Service is already processing a trail with the same name as the new request.
Action:
Change the target trail name for one of the conflicting Distribution Path.
OGG-10394: Existing request for target trail file received from the same UUID '{0}'. Conflict detected and resolved.
The Receiver Service started processing a trail with the same name as the new request.
Action:
This is informational only.
OGG-10402: System-period and Bitemporal tables are not supported with 'INSERTALLRECORDS'
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.
The column is one among SYS_START, SYS_END and TS_ID columns. These columns are auto filled by DB 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}"
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}"
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}"
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}"
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}
A RENAME operation was processed. Informational only.
Action:
None
OGG-10456: Metadata not invalidated for object "{1}".{2} because of parameter {0}, SQL [{3}], catalog {4}.
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}
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}
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.
The heartbeat object being added is invalid.
Action:
Contact Oracle Support.
OGG-10460: Failed to process operation on tombstone table {0}.
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}".
Extract process failed to retrieve tombstone timestamp information in order to generate acdr token.
Action:
Contact Oracle GoldenGate Support.
OGG-10462: Schema "{0}" have {1} prepared tables for instantiation
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.
GGSCI command 'SET_INSTANTIATION_CSN' was successfully executed.
Action:
None
OGG-10464: Instantiation CSN has been cleared successfully.
GGSCI command 'CLEAR_INSTANTIATION_CSN' was successfully executed.
Action:
None
OGG-10467: Table {0}.{1} cannot be natively captured. {2}
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}
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}
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}.
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}
Oracle GoldenGate support related information on this table.
Action:
It's for your information only.
OGG-10472: System partitioned table {0} is only supported with integrated dictionary.
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-10473: DDL on global temporary table excluded, optype [{0}], objtype [{1}], objowner "{2}", objname "{3}"
The specified DDL operation was excluded from DDL replication because it was performed on a global temporary table. Specifying DDLOPTIONS CAPTUREGLOBALTEMPTABLE will direct Extract or Replicate to process this DDL.
Action:
None
OGG-10474: DDL on global temporary table excluded, optype [{0}], objtype [{1}], catalog "{4}", objowner "{2}", objname "{3}"
The specified DDL operation was excluded from DDL replication because it was performed on a global temporary table. Specifying DDLOPTIONS CAPTUREGLOBALTEMPTABLE will direct Extract or Replicate to process this DDL.
Action:
None
OGG-10475: PDB [{0}], object ID [{1}], table {2} skipped due to NO_SUPPORT from DBA_GOLDENGATE_SUPPORT_MODE view.
The table is determined to be unsupported as result of query against DBA_GOLDENGATE_SUPPORT_MODE view.
Action:
If the table should have been supported, then check the metadata of the table and take appropriate action.
OGG-10501: Heartbeat object "{0}" already exists.
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.
The heartbeat object does not exist.
Action:
None
OGG-10503: Heartbeat object "{0}" creation failed.
The heartbeat object creation failed.
Action:
None
OGG-10505: Job schedule [{0}] does not exist.
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.
Job schedule for updating the heartbeat tables was dropped. Informational only.
Action:
None
OGG-10507: Job [{0}] does not exist.
Job updating for heartbeat tables does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the job.
OGG-10508: Job [{0}] dropped.
Job for updating the heartbeat tables was dropped. Informational only.
Action:
None
OGG-10509: Job schedule [{0}] does not exist.
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.
Job schedule for purging heartbeat tables dropped. Informational only.
Action:
None
OGG-10511: Job [{0}] does not exist.
Job for purging heartbeat tables does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the job.
OGG-10512: Job [{0}] dropped.
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.
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.
The user is either not added/created in SYBMGMTDB database or user has not proper roles( replication_role, js_admin_role, js_user_role) enabled.
Action:
Add/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}).
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}) .
Procedure already exist in the current database.
Action:
Execute the DELETE HEARTBEATTABLE command to drop the procedure.
OGG-10522: Scheduled job ({0}) already exist.
The scheduled job exists.
Action:
Execute the DELETE HEARTBEATTABLE command to drop the schedule job.
OGG-10523: Cannot alter heartbeat scheduler job, heartbeat tables ({0},{1} and {2}) do not exist in the database.
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.
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}
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}).
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}.
Logging of supplemental log data is disabled. Information only.
Action:
None
OGG-10533: Unable to open {0}, err {1} {2}
A file error was returned when attempting to open/create a required file.
Action:
Evaluate the file system error and correct.
OGG-10534: Error writing file {2}. Error code {0}. Detail: {1}.
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}".
Heartbeat rate table has been created. Informational only.
Action:
None
OGG-10536: Successfully populated heartbeat rate table.
Heartbeat seed table populated. Informational only.
Action:
None
OGG-10538: Unable to stop the heartbeat process.
Unknown error; Contact Oracle support.
Action:
None
OGG-10540: Unable to start the heartbeat process.
Unknown error; Contact Oracle support.
Action:
None
OGG-10541: Manager restarted the heartbeat process.
Unknown error; If the error persists, contact Oracle support.
Action:
None
OGG-10544: The heartbeat process was unable to open $RECEIVE.
Unknown error; Contact Oracle support.
Action:
None
OGG-10545: The heartbeat process was unable to obtain required rate values.
Unknown error; Delete and re-add heartbeat configuration using the heartbeattable commands from GGSCI.
Action:
None
OGG-10548: Schema.table is required for heartbeattable.
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.
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.
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}.
Validation of the table existence failed.
Action:
Contact Oracle Support
OGG-10552: Unsupport option is FETCH; No row found. tablename:{0}
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}
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 application {0} group {1} failed ({2}).
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}".
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}>.
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}>.
The database returned no data when the specified SQL statement was executed.
Action:
None
OGG-10559: File '{0}' deleted
The specified file was deleted.
Action:
None
OGG-10560: Error loading module. Library name {0}. Detail: {1}.
An error occurred while loading a dynamically loadable library.
Action:
Contact Oracle Support.
OGG-10561: Error loading function {1} from module {0} - {2}.
An error occurred while loading a function from a dynamically loadable module.
Action:
Contact Oracle Support.
OGG-10562: Failed to delete the heartbeat object "{0}".
The heartbeat object delete failed.
Action:
None
OGG-10563: Failed to alter the heartbeat object "{0}".
The heartbeat object alter failed.
Action:
None
OGG-12000: General service error.
There was some internal problem that prevented proper processing of the request.
Action:
Contact Oracle GoldenGate Support.
OGG-12001: Poorly formed service request payload.
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. See the Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12002: Poorly formed request URI.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12003: Poorly formed HTTP request context.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12004: Service request handler error.
The service request handler returned an error.
Action:
Review the message details and verify the service request was properly and completely formed. See the Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12005: No configuration file found at '{0}'. New configuration file created with default settings.
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 Reference for Oracle GoldenGate for Windows and UNIX for configuration details.
OGG-12006: Loaded configuration file from '{0}'.
Report the location from which the configuration was loaded.
Action:
None. Informational only.
OGG-12007: Unable to access the configuration file at '{0}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for configuration details.
OGG-12008: Unable to parse the configuration at line {1,number,0} column {2,number,0} in file '{0}'.
Unable to parse the configuration information in the file at the specified location.
Action:
Verify that the configuration information formats are valid. See the Reference for Oracle GoldenGate for Windows and UNIX for configuration details.
OGG-12009: Unable to completely read the configuration file at '{0}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for configuration details.
OGG-12010: The requested service completed successfully but did not return a result.
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}'.
The verb provided in the HTTP URI is invalid for this service request.
Action:
Verify the HTTP URI specifies a valid verb. See the Reference for Oracle GoldenGate for Windows and UNIX for valid Accept media types.
OGG-12012: Poorly formed HTTP request context for '{0} {1}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12013: Poorly formed request URI for '{0} {1}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid URI resource paths.
OGG-12014: The HTTP Accept media-type '{0}' is deprecated for '{1} {2}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid Accept media types.
OGG-12015: The HTTP Accept value is invalid for '{0} {1}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid Accept media types.
OGG-12016: The request URI template '{3}' placeholder name '{0}' conflicts with the request context names for '{1} {2}'.
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}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12018: Poorly formed request payload for '{0} {1}'.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid payload formats and structure.
OGG-12019: The request payload for '{0} {1}' defines a root level array. Root level arrays are not currently supported
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. Reference for Oracle GoldenGate for Windows and UNIX for valid service request formats and values.
OGG-12020: The request payload for '{0} {1}' is not defined as an object.
The root of the JSON payload document is not defined as an object.
Action:
Define the JSON payload root document as an object. Reference for Oracle GoldenGate for Windows and UNIX for valid service request formats and values.
OGG-12021: Poorly formed response from service handler for '{0} {1}'.
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.
The service request handler returned an empty response.
Action:
Contact Oracle GoldenGate Support.
OGG-12023: Service request handler error.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid header and attribute names and values.
OGG-12024: No service handler registered for '{0} {1}'.
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}.
The handler method caused an exception. See error messages for details.
Action:
Contact Oracle GoldenGate Support.
OGG-12026: Node '{0}' at position {1,number,0} in JsonPath '{2}' is missing.
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 Reference for Oracle GoldenGate for Windows and UNIX for valid JsonPath specifications.
OGG-12027: There is no JsonPath specified. The JsonPath is empty.
The JsonPath has not been initialize or the specification is empty.
Action:
Verify the JsonPath specification describes a valid path. See the Reference for Oracle GoldenGate for Windows and UNIX for valid JsonPath specifications.
OGG-12028: No service handler implemented for '{0} {1}'.
No service handler is implemented for the service request URI.
Action:
Contact Oracle GoldenGate Support.
OGG-12029: The item type {0} with name '{1}' does not exist.
The requested item does not exist.
Action:
Check the request URI for accuracy.
OGG-12030: The {0} with name '{1}' already exists.
The requested item already exists.
Action:
Check the request URI for accuracy.
OGG-12031: The requested resource does not exist.
The requested resource does not exist.
Action:
Check the request resource URI for accuracy.
OGG-12032: The requested URI contains the illegal or restricted character '{0}' at position {1,number,0}.
The service request URI contained illegal or restricted character values.
Action:
Verify the service request URI specified by the client is correct and contains only valid native and post-decoded characters. See the Oracle GoldenGate Reference for valid request URI characters and character encodings.
OGG-12033: The requested content does not exist (error {0,number,0}, {1}).
The requested content does not exist.
Action:
Check the request content URI for accuracy.
OGG-12034: No permission to access requested content (error {0,number,0}, {1}).
Insufficient privileges to access content.
Action:
Verify permissions to access content.
OGG-12035: Error accessing requested content (error {0,number,0}, {1}).
Unhandled error accessing content.
Action:
Verify existence, accessibility and permissions on content.
OGG-12036: The URI is invalid - {0} .
The URI is valid due to incorrect syntax or illegal character use.
Action:
Verify the URI is defined using the correct syntax and contains only valid characters. See the Oracle GoldenGate Reference for valid URI syntax, characters and character encodings.
OGG-12037: The Host header is invalid - {0}.
The Host header is valid due to incorrect syntax or illegal character use.
Action:
Verify the Host header is defined using the correct syntax and contains only valid characters. See the Oracle GoldenGate Reference for valid Host header syntax, characters and character encodings.
OGG-12038: The Host header is missing .
The Host header is missing from the request.
Action:
Verify the Host header is included in the request. See the Oracle GoldenGate Reference for valid Host header syntax, characters and character encodings.
OGG-12050: The wrl configuration is missing.
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. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12051: The configured communications role '{0}' is not recognized.
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. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12052: The communications role configuration is missing.
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. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12053: The communications protocol configuration is missing.
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. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12054: The communications protocol configuration '{0}' is not recognized.
The communications security protocol was not recognized.
Action:
Verify that the 'protocol' value in the security configuration refers to a valid communications security protocol. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12055: Expected communications security configuration id '{1}' but received '{0}'.
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. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12056: Communications security configuration id is missing.
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. See 4 Installing and Configuring Oracle GoldenGate for Oracle Databases.
OGG-12057: Method for specified URI must be GET.
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.
Internal error.
Action:
Contact Oracle Support.
OGG-12059: Internal error, a pointer could not be retrieved.
Internal error.
Action:
Contact Oracle Support.
OGG-12060: The client submitted an empty HTTP Authorization header.
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}'.
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.
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.
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.
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 imported {0} users.
The import processing of user specifications will successful.
Action:
None
OGG-12066: Failed to import {0} users.
The import processing of user specifications failed.
Action:
None
OGG-12069: User import file '{0}' does not exist or cannot be read, error {1} - {2}.
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}'.
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}'.
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}'.
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}'.
The authorization role of the user did no meet the resource's role requirement.
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.
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.
In the configuration file of the service, the '/config/securityDetails/network/outbound' property 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.
There was an error while configuring communication security interface.
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 specified role '{1}'.
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.
Cannot complete the request because user authorization is required on a service configured with authorization disabled.
Action:
Use a request that does not required authorization or configure the service to enable authorization services.
OGG-12079: Unable to complete the request. User not logged in.
Cannot complete the request because user is not logged in.
Action:
Ensure user credentials or a valid authorization cookie or token is presented with the request.
OGG-12080: Password must be 8 to 30 characters and contain at least 1 uppercase, 1 lowercase, 1 numeric and 1 special character. The special characters must not be '$', '^' or '?'.
The OGG deployment has certain password complexity requirements that are not met.
Action:
Consult with the OGG administrator to determine password complexity requirements and try again.
OGG-12081: The provided credential does not meet complexity requirements.
The OGG deployment has certain password complexity requirements that are not met.
Action:
Consult with the OGG administrator to determine password complexity requirements and try again.
OGG-12082: The regular expression used to check password complexity is not valid.
The OGG deployment uses an invalid custom password complexity check.
Action:
Consult with the OGG administrator to review password complexity requirements.
OGG-12083: Request not honored. Request violated cross-site request policy.
The request did not include or included an invalid CSRF information.
Action:
Consult with the OGG administrator to review cross-site request requirements.
OGG-12084: A credential is required but is missing from this request.
The request requires that a credential (password) be provided.
Action:
Ensure the user information in the request includes a user credential and try again.
OGG-12085: Successfully exported {0} users.
The export processing of user specifications will successful.
Action:
None
OGG-12086: Failed to export {0} users.
The export processing of user specifications failed.
Action:
None
OGG-12089: Successfully updated {0} users.
The update processing of user specifications will successful.
Action:
None
OGG-12090: Failed to update {0} users.
The update processing of user specifications failed.
Action:
None
OGG-12093: Successfully removed {0} users.
The remove processing of user specifications will successful.
Action:
None
OGG-12094: Failed to remove {0} users.
The remove processing of user specifications failed.
Action:
None
OGG-12095: Successfully removed {0} user roles.
The remove processing of user role specifications was successful.
Action:
None
OGG-12096: Failed to removed {0} user roles.
The remove processing of user role specifications failed.
Action:
None
OGG-12100: Required JSON element '{0}' is missing
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
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
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
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
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}'
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
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
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}'
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
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
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
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
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}
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}
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}
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}
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}
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}
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}
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}
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}
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}'
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
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
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
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 service's security configuration.
The JSON item does not validate against the provided JSON schema.
Action:
Correct the JSON so that it matches with the service security setup.
OGG-12127: Given URI '{0}' is not valid.
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.
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.
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.
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.
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
You cannot change the status to killed.
Action:
Specify another status.
OGG-12133: An operation that sets path status to 'stopping' is not allowed
You cannot change the status to stopping.
Action:
Specify another status.
OGG-12134: An operation that sets path status to 'uninitialized' is not allowed
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.
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}'.
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}'.
The authorization information is not provided when a non-secure WebSocket protocol is used.
Action:
Correct the JSON to provide authorization information (either username/password or domain/alias) in your request.
OGG-12138: Credential Domain '{0}' does not match any pre-imported entry.
The Credential Domain is incorrect.
Action:
Correct the JSON to provide the correct domain name in your request.
OGG-12139: Credential Alias '{0}' could not be found in Credential Domain '{1}'.
The specified Credential Alias does not exist in the specified Credential Domain.
Action:
Correct the JSON to provide the correct credential alias in your request.
OGG-12140: The schema of the given URI '{0}' is not recognizable, invalid or missing. Expected values are: {1}.
The JSON item does not validate against the provided JSON scheme.
Action:
Correct the JSON so that the schema part of the URI is correct.
OGG-12141: Credential Alias '{0}' in Credential Domain '{1}' is reserved for internal use, it cannot be updated or deleted.
The specified Credential Alias is reserved for internal use, it cannot be updated or deleted.
Action:
No action required.
OGG-12142: The json property '{0}' has been deprecated. Expected value is: '{1}'.
The JSON property has deprecated from the provided JSON schema.
Action:
Remove the deprecated property and use the correct JSON property.
OGG-12143: Authorization information (username/password, or domain/alias) is required in given URI schema '{0}' or authenticationMethod property.
The authorization information is not provided when a non-secure WebSocket protocol is used.
Action:
Correct the JSON to provide authorization information in your request.
OGG-12150: No log files found for application '{0}'.
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.
The specified log is read-only and cannot be disabled or deleted.
Action:
No action required.
OGG-12300: Service Manager is terminating.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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}
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.
An attempt was made to delete the Service Manager deployment.
Action:
The Service Manager deployment is permanent and cannot be deleted.
OGG-12313: The '{1}' service in the '{0}' deployment is disabled and can only be modified by a Security user.
An attempt was made to modify a disabled service in a deployment, but only Security users can modify disabled services.
Action:
Retry the operation after setting the 'locked' property to false using an account with the 'Security' role.
OGG-12314: The '{1}' service in the '{0}' deployment cannot be disabled, except by Security users.
An attempt was made to disable a service in a deployment, but only Security users can disable services.
Action:
Retry the operation using an account with the 'Security' role.
OGG-12315: Disabled services can only be created by a Security user.
An attempt was made to create a disabled service in a deployment, but only Security users can create disabled services.
Action:
Retry the operation without the 'locked' property or using an account with the 'Security' role.
OGG-12316: The '{1}' service in the '{0}' deployment is disabled and must be enabled before being modified.
An attempt was made to update a disabled service in a deployment, which is not allowed.
Action:
Retry the operation after setting the 'locked' property to false using an account with the 'Security' role.
OGG-12317: The '{1}' service in the '{0}' deployment is running and must be stopped before being disabled.
An attempt was made to disable a running service.
Action:
Stop the service and then retry the operation.
OGG-12318: The Service Manager service, '{0}', cannot be deleted.
An attempt was made to delete the Service Manager service.
Action:
The Service Manager service is permanent and cannot be deleted.
OGG-12319: The "status" property for the Service Manager service, '{0}', cannot be "{1}".
An attempt was made to change a Service Manager service to an invalid status. Only the "restart" status is allowed.
Action:
The Service Manager service can only be restarted.
OGG-12320: A PATCH operation that changes the property '{0}' is not allowed for the Service Manager service.
The JSON property specified cannot be changed with a PATCH operation.
Action:
Remove the identified property from the PATCH request.
OGG-12350: Query for this request returned an error - {0}
The query for this request returned an error.
Action:
None
OGG-12351: UDP is deprecated as communication protocol for PM Service.
UDP is specified as a monitoring communication protocol.
Action:
Remove deprecated UDP parameters.
OGG-12375: No Heartbeat entries for process '{0}' exist.
Heartbeat entries with given process name do not exist. Information only.
Action:
None
OGG-12420: The maximum filesystem path length of {2,number,0} for {0, choice,0#environment variable│1# file path} '{1}' has been exceeded.
The filesystem path value set for the variable is longer than the maximum defined for filesystem paths.
Action:
Use a short filesystem 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-12421: The current OGG version does not support adding a Classic Extract. Switch to Integrated mode.
The current OGG version no longer supports Classic Extract.
Action:
Add an Integrated Extract.
OGG-12900: NZ-Toolkit error {0,number,0} - {1}.
An error was returned from NZ-Toolkit function.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12901: The specified wallet does not exist at '{0}'.
The wallet does not exist at the path provided.
Action:
Verify that the path is correct and that the wallet is reachable.
OGG-12902: An existing wallet found at '{0}'.
An existing wallet was unexpectedly found at the specified location.
Action:
Verify that the path is correct for a new wallet and that no wallet exists at that location.
OGG-12903: Failed to create a new wallet context. Low-level details: {0}.
Failed to create a new wallet context due to invalid input specification or resource limitations. Please review the low-level details for additional information.
Action:
Review the low-level details for possible resolution strategies.
OGG-12905: The Wallet Resource Locator path has not been specified. The path value is empty.
The Wallet Resource Locator path used to store the wallet context has not been specified or is empty.
Action:
Ensure that a valid Wallet Resource Locator path has been specified before attempting to save the wallet context.
OGG-12906: Failed to open wallet at '{0}'. Low-level details: {1}
Failed to open the wallet at the specified path. Causes include allocation errors, read permissions not granted, and incorrect password specification. Please review the low-level details for additional information.
Action:
Review the low-level details for possible resolution strategies.
OGG-12907: The WRL (Wallet Resource Locator) path '{0}' refers to an invalid resource type in this context. Type requested was a WRL Directory, type found was a File.
The Wallet Resource Locator path specified refers to a file instead of a directory.
Action:
The Wallet Resource Locator path specified refers to a file instead of a directory. Please check the WRL path and ensure that it does not refers to a file.
OGG-12908: Failed to save wallet with mode {0, choice,0#AutoLogin│1#Secured│2#AutoLoginOnly}.
Unable to save the wallet as requested. See message for details of the specific error.
Action:
Review the accompanying message and information for resolution strategies.
OGG-12909: In sufficient write permissions accessing wallet at '{0}'.
There are insufficient filesystem privileges to allow write access to the wallet. The wallet may be marked read-only or the wallet may be located on a read-only medium.
Action:
Ensure the wallet is not marked as read-only or is not located on a read-only filesystem or device.
OGG-12910: Unable to reset the wallet at '{0}' to its initial state. Deletion of the Wallet failed.
Deletion of the wallet's context and data structure failed. See message details of the specific error. An error was returned from NZ-Toolkit function.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12911: Failed to retrieve the list of personas from wallet at '{0}'.
Failed to retrieve the persona list from the wallet context.
Action:
Verify that the wallet is open and valid.
OGG-12912: Failed adding a persona '{0}' to wallet at '{1}'.
Failed to add a persona the wallet context.
Action:
Verify that the wallet is open and valid.
OGG-12913: Failed deleting a persona '{0}' from wallet at '{1}'.
Failed to add a persona to the wallet context.
Action:
Verify that the wallet is open and valid.
OGG-12920: Persona '{0}' contains no certificates.
The named persona has no associated certificates. The size of the certificate list is 0. The persona may have been created and stored without associating any certificates or the certificate association may have been removed.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12921: Contents of persona '{1}' cloned from '{0}' do not match. {4, choice,0#Certificate counts differ│1#Certificates differ on hash}: {0}({2}), {1}({3})
Comparison of 2 persona's contents detected a difference indicating the persona's contents are not the same. Persona comparison checks that the count of certificates held by the personas is the same and that each of the certificates held by the personas are in the same order and have the same unique hash value.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12922: Failed to add certificate '{0}' to persona '{1}'.
Unable to add certificate to a persona.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12923: Failed to delete certificate '{0}' from persona '{1}'.
Unable to delete certificate from a persona.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12930: Failed to acquire identity list for {0, choice,0#Certificates│1#Trustpoints│2#Keys│3#Generic} from persona '{1}'.
Unable to get identity list from a persona for specific identity type.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12931: Failed to destroy {0, choice,0#Certificate│1#Trustpoint│2#Key│3#Generic} identity from persona '{1}'.
Unable to get identity list from a persona for specific identity type.
Action:
Review the accompanying messages and information for resolution strategies.
OGG-12977: TLS/SSL communications error reported from remote peer - '{0}'.
An alert was raised by the remote peer while establishing a secure connection using TLS.
Action:
Use the information to make corrections to the configuration.
OGG-12978: TLS/SSL communications error while connecting to remote peer - '{0}'.
An alert was raised locally while establishing a secure connection to a remote peer using TLS.
Action:
Use the information to make corrections to the configuration.
OGG-12979: A certificate or certificate-chain member may have expired or references an invalid issuer.
A certificate or a certificate in the certificate-chain may have expired or may reference an invalid issuer.
Action:
Ensure the participating certificates have not expired and the issuers is valid and available.
OGG-12980: The required certificate was not found in {0, choice,2#persona context│3#certificate store}.
The required certificate was not found in the persona or certificate store.
Action:
Ensure the certificate being requested exists in the persona or certificate store.
OGG-12981: The certificate did not qualify against the Certificate ALC (Access Control List).
A certificate access control list rule denied the certificate.
Action:
Ensure the certificate being used qualified against the certificate access control list.
OGG-12982: Failed to establish secure communication with a remote peer. The TLS handshake processing and negotiation was unsuccessful.
The secure connection handshake and security negotiation failed.
Action:
Review the accompanying messages for additional details.
OGG-12983: Invalid certificate details: {0}
The certificate failed one or more verification actions.
Action:
Review the accompanying messages for additional details and consult the provided details to determine the cause or causes of the verification failures.
OGG-12984: The remote peer submitted a {0, choice,0#certificate│1#certificate-chain certificate} that failed validation.
Certificate validation failed.
Action:
Review the accompanying messages for additional details.
OGG-12985: Failed to negotiate secure communication with remote peer. The TLS handshake processing and negotiation was unsuccessful.
The secure connection handshake and security negotiation failed.
Action:
Review the accompanying messages for additional details.
OGG-12986: Attempted to establish secure communications with a remote peer using a invalid or unaccepted protocol version. The local protocol version set as {0}.
The secure connection handshake and security negotiation failed due to an invalid or unaccepted protocol version.
Action:
Review the accepted protocol versions specified by the client and the server and ensure that they have at least one protocol version in common.
OGG-12987: The remote peer's certificate failed to qualify against the Certificate ACL (Access Control List). The certificate was disqualified by Cert ACL rule # {0}.
A Certificate ACL rule rejected the remote peer's certificate.
Action:
Contact the service administrator to address the certificate's ACL status.
OGG-12988: The remote peer's #{3} {0, choice,0#certificate│1#certificate-chain certificate} is outside its validity time period and is invalid. The declared valid FROM time is {1} and valid TO time is {2}.
The current date-time value is outside the specified validity time period of the certificate. A certificate's validity period is described as being between a start date-time value and an end date-time value inclusive. This error indicates that the certificate is either not yet available or has passed its expiration time.
Action:
Review and ensure that a the remote peer is using an unexpired certificate and the certificates in the certificate-chain are within their validity periods.
OGG-12989: Unable to acquire the validity periods for the #{1} {0, choice,0#certificate│1#certificate-chain certificate} from the remote peer.
Failed to acquire validity period from the remote peer's security object due to a processing or data formatting error. Acquisition errors may be a result of an invalid certificate or may an internal context or processing error.
Action:
Review the accompanying low-level error message for additional details.
OGG-12990: Unable to acquire the {0, choice,0#certificate│1#certificate-chain certificate} from the remote peer. The remote peer's security context does not contain a {0, choice,0#certificate│1#certificate-chain certificate}.
Failed to acquire remote peer's certificate due to a processing or data formatting error. Acquisition errors may be a result of an invalid certificate or may an internal context or processing error.
Action:
Review the accompanying low-level error message for additional details.
OGG-12991: One or more of the certificates in the remote peer's certificate-chain is invalid.
Unable to successfully verify all the certificates participating in the remote peer's certificate-chain. Certificates may be invalid due to expired validity times, incorrect extended key-usage specifications, inappropriate security policies or an inability to locate a required valid issuers or root CA certificates.
Action:
Review and confirm that the remote peers is sending a sufficiently complete certificate-chain, that each of the certificates in the chain has not expired, that each certificate has a valid and available issuer certificate, that each certificate includes certificate signing ability and that the security policies allow the certificate to be used as a certificate signing authority.
OGG-12993: Unable to install the certificate into the TLS/SSL security context.
Installation of the certificate into the TLS/SSL security context failed. Installation failure may be due to specifying the wrong certificate, specifying a expired certificate or specifying a certification with incorrect policies or key-usages declarations.
Action:
Review and ensure the specified certificate is correct for the intended use and that the policies, usages and validity periods are valid.
OGG-12994: Unable to set the certificate validation policy during credential initialization.
Unable to the set the certificate validation policy.
Action:
Review and ensure the specified certificate validation policy is correct.
OGG-12995: Unable to set peer authentication mode to {0}.
Unable to the set the peer authentication mode.
Action:
Review and ensure the specified peer authentication mode is correct.
OGG-12996: Unable to open the specified wallet: {0}.
The persona holding the TLS/SSL certificate was not found in the specified wallet.
Action:
Review and ensure the specified wallet contains the appropriate security persona and credential.
OGG-12997: The security persona was not retrieved from the specified wallet: {0}.
The persona holding the TLS/SSL certificate was not found in the specified wallet.
Action:
Review and ensure the specified wallet contains the appropriate security persona and credential.
OGG-12998: The value for the wallet resource locator was not specified.
The wallet resource locator was not provided. An empty specifier or a specifier with only the 'file:' prefix was detected.
Action:
Review and ensure the value of the wallet resource locator is correctly set.
OGG-12999: Invalid security configuration for {0} - {1}: '{2}'.
The security configuration is invalid.
Action:
Review and ensure both the configuration key and value are correct.
OGG-13000: With procedural replication, only single output trail is allowed.
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
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.
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.
Oracle Goldengate Procedural Replication is supported for an Oracle Database release 12.2 or later.
Action:
Upgrade to a supported Oracle Database release.
OGG-13005: PROCEDURETRANDATA supplemental logging has been enabled
The ADD PROCEDURETRANDATA command enabled supplemental logging for procedures. Informational only.
Action:
None
OGG-13006: PROCEDURETRANDATA supplemental logging has been disabled
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
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
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.
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
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
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.
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-13013: PARTITION and PARTITIONEXCLUDE parameters require format release 19.1 or higher.
The format release must be 19.1 or later when PARTITION or PARTITIONEXCLUDE parameters are specified.
Action:
Ensure that the proper format release is specified in the Extract parameter file.
OGG-13014: FEATURE list is empty for PROCEDURE INCLUDE/EXCLUDE
The INCLUDE/EXCLUDE procedure FEATURE should be followed by a feature list or ALL_SUPPORTED keyword.
Action:
Specify a feature list for INCLUDE/EXCLUDE FEATURE parameter clause.
OGG-13015: PROCEDURETRANDATA operation failed because of the following SQL error: {0}
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-14000: Successfully created heartbeat table "{0}".
Heartbeat table has been created. Information only.
Action:
None
OGG-14001: Successfully created heartbeat seed table "{0}".
Heartbeat seed table has been created. Information only.
Action:
None
OGG-14002: Implicit column function heartbeat routing has incorrect format.
Column function used to parse heartbeat routing is incorrect.
Action:
Contact Oracle Support.
OGG-14003: Successfully populated heartbeat seed table with "{0}".
Heartbeat seed table populated. Information only.
Action:
None
OGG-14004: Successfully created procedure "{0}" to update the heartbeat tables.
Update procedure for heartbeat tables created. Information only.
Action:
None
OGG-14005: Successfully created scheduler job "{0}" to update the heartbeat tables.
Scheduler job for updating heartbeat tables created. Information only.
Action:
None
OGG-14006: Heartbeat seed table "{0}" does not exist.
Heartbeat seed table does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the heartbeat tables.
OGG-14007: Heartbeat seed table "{0}" dropped.
Heartbeat seed table dropped. Information only.
Action:
None
OGG-14008: Heartbeat table {0} does not exist.
Heartbeat table does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the heartbeat tables.
OGG-14009: Heartbeat table "{0}" dropped.
Heartbeat table dropped. Information only.
Action:
None
OGG-14010: Heartbeat history table "{0}" does not exist.
Heartbeat history table does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the heartbeat tables.
OGG-14011: Heartbeat history table "{0}" dropped.
Heartbeat history table dropped. Information only.
Action:
None
OGG-14012: Procedure "{0}" does not exist.
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.
Update procedure for heartbeat tables dropped. Information only.
Action:
None
OGG-14014: Scheduler job "{0}" does not exist.
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.
Scheduler job for updating heartbeat tables dropped. Information only.
Action:
None
OGG-14016: Successfully created heartbeat history table "{0}".
Heartbeat history table has been created. Information only.
Action:
None
OGG-14017: Successfully created procedure "{0}" to purge the heartbeat history table.
Purge procedure for heartbeat history table created. Information only.
Action:
None
OGG-14018: Successfully created scheduler job "{0}" to purge the heartbeat history table.
Scheduler job for purging heartbeat history table created. Information only.
Action:
None
OGG-14019: Procedure "{0}" does not exist.
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.
Purge procedure for heartbeat history table dropped. Information only.
Action:
None
OGG-14021: Scheduler job "{0}" does not exist.
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.
Scheduler job for purging heartbeat history table dropped. Information only.
Action:
None
OGG-14023: Successfully created heartbeat lag view "{0}".
Heartbeat Lag View has been created. Information only.
Action:
None
OGG-14024: Successfully created heartbeat lag history view "{0}".
Heartbeat Lag History View has been created. Information only.
Action:
None
OGG-14025: Heartbeat lag view "{0}" does not exist.
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.
Heartbeat lag view dropped. Information only.
Action:
None
OGG-14027: Heartbeat lag history view "{0}" does not exist.
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.
Heartbeat lag history view dropped. Information only.
Action:
None
OGG-14029: Frequency of scheduler job "{0}" modified.
Frequency of scheduler job for updating heartbeat tables has been modified. Information only.
Action:
None
OGG-14030: Frequency of purge scheduler job "{0}" modified.
Frequency of scheduler job for purging heartbeat history table has been modified. Information only.
Action:
None
OGG-14031: Retention time of heartbeats modified.
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}".
Added supplemental logging for heartbeat seed table for all columns. Information only.
Action:
None
OGG-14033: Successfully added supplemental logging for heartbeat table "{0}".
Added supplemental logging for heartbeat table for all columns. Information only.
Action:
None
OGG-14034: Heartbeat entries with [{0}] deleted.
Heartbeat entries with given process name deleted from heartbeat table. Information only.
Action:
None
OGG-14035: The heartbeat table name cannot contain a wildcard.
The heartbeat table name specified with HEARTBEATTABLE in the GLOBALS file cannot contain a wildcard.
Action:
Specify a non-wildcarded name.
OGG-14037: Catalog login required to add heartbeat tables.
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.
Catalog login required to delete heartbeat tables.
Action:
Login to a pdb and retry the command.
OGG-14039: Catalog login required to alter heartbeattable.
Catalog login required to alter heartbeattable.
Action:
Login to a pdb and retry the command.
OGG-14040: Catalog login required to delete heartbeatentry.
Catalog login required for command 'delete heartbeatentry'.
Action:
Login to a pdb and retry the command.
OGG-14041: {0} exists already.
Heartbeat object exists already.
Action:
Rename object and retry the command again.
OGG-14042: Catalog name not supported for heartbeat table "{0}".
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}.
Invalid ADD HEARTBEATTABLE specification.
Action:
None
OGG-14044: Invalid ALTER HEARTBEATTABLE specification {0}.
Invalid ALTER HEARTBEATTABLE specification.
Action:
None
OGG-14045: Invalid DELETE HEARTBEATENTRY specification {0}.
Invalid DELETE HEARTBEATENTRY specification.
Action:
None
OGG-14046: The ADD HEARTBEATTABLE option: {0} is ignored.
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.
An attempt was made to drop a job that is currently running.
Action:
Reissue the command.
OGG-14048: Invalid DELETE HEARTBEATTABLE specification {0}.
Invalid DELETE HEARTBEATTABLE specification.
Action:
None
OGG-14052: No Heartbeat entries with [{0}], none deleted.
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.
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.
Detailed lag report from heartbeat table requires DBLOGIN.
Action:
Log into the database to view detailed lag report.
OGG-14055: Successfully created {0} "{1}".
Heartbeat object has been created. Informational only.
Action:
None
OGG-14056: Successfully deleted {0} "{1}".
Heartbeat object has been deleted. Informational only.
Action:
None
OGG-14057: Could not retrieve heartbeat table frequency interval.
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 dblogin command using a login with more privileges or contact Oracle Support.
OGG-14058: Could not retrieve heartbeat table purge frequency interval.
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 dblogin command using a login with more privileges or contact Oracle Support.
OGG-14059: Could not retrieve heartbeat table retention time interval.
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 dblogin command using a login with more privileges or contact Oracle Support.
OGG-14060: Invalid INFO HEARTBEATTABLE specification {0}.
Invalid INFO HEARTBEATTABLE specification.
Action:
None
OGG-14061: Datastore uses LMDB environment files.
The datastore uses LMDB files for its environment resources.
Action:
No action required.
OGG-14062: Dblogin required before exttrail in parameter file to enable heartbeats.
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.
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}).
Undefined
Action:
Undefined
OGG-14065: Heartbeat table "{0}" does not exist in "{1}".
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}".
Heartbeat entries with the given process name were deleted from heartbeat table. Information only.
Action:
None
OGG-14068: Schema is required for commandtable : "{0}".
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 commandtable name (with schema) for the COMMANDTABLE parameter, or mention GGSCHEMA in GLOBALS.
OGG-14069: Catalog login required to add command tables.
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.
Catalog login required to delete command tables.
Action:
Login to a pdb and retry the command.
OGG-14071: Catalog login required to alter COMMANDTABLE.
Catalog login required to alter COMMANDTABLE.
Action:
Login to a pdb and retry the command.
OGG-14072: Catalog login required to delete commandentry.
Catalog login required for command 'DELETE COMMANDENTRY'.
Action:
Login to a pdb and retry the command.
OGG-14073: "{0}" exists already.
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}".
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}.
Invalid ADD COMMANDTABLE specification.
Action:
None
OGG-14076: Invalid ALTER COMMANDTABLE specification {0}.
Invalid ALTER COMMANDTABLE specification.
Action:
None
OGG-14077: Invalid DELETE COMMANDTABLEENTRY specification {0}.
Invalid DELETE COMMANDTABLEENTRY specification.
Action:
None
OGG-14078: The ADD COMMANDTABLE option: {0} is ignored.
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.
The command table name specified with COMMANDTABLE in the GLOBALS file cannot contain a wildcard.
Action:
Specify a non-wildcarded name.
OGG-14080: Datastore uses Metrics Service Datastore.
The datastore uses Metrics Service Datastore.
Action:
No action is required.
OGG-14081: This Operation is Invalid For Metrics Service Datastore.
The Operation is invalid for the Metrics Service Datastore.
Action:
No action is required.
OGG-14082: Purge Complete, {0} Messages Removed, {1} Status Changes Removed.
The data store has been purged.
Action:
No action is required.
OGG-14083: Datastore Purge Failed.
The data store purge failed.
Action:
No action is required.
OGG-14084: Invalid or Missing Number of Days.
Invalid or missing value for max monitoring days.
Action:
No action is required.
OGG-14085: Successfully enabled partitioning for heartbeat history table "{0}".
Partitioning enabled on heartbeat table. Information only.
Action:
No action is required.
OGG-14086: Successfully disabled partitioning for heartbeat history table "{0}".
Partitioning disabled on heartbeat table. Information only.
Action:
No action is required.
OGG-14087: Successfully disabled supplemental logging for heartbeat seed table "{0}".
Disabled supplemental logging for heartbeat seed table. Information only.
Action:
None
OGG-14088: Successfully disabled supplemental logging for heartbeat table "{0}".
Disabled supplemental logging for heartbeat table. Information only.
Action:
None
OGG-14089: Successfully tracking extract restart position with heartbeat table "{0}".
Tracking extract restart position with heartbeattable. Information only.
Action:
None
OGG-14090: Invalid UPGRADE HEARTBEATTABLE specification {0}.
Invalid UPGRADE HEARTBEATTABLE specification.
Action:
None
OGG-14091: Supplemental logging for the heartbeat seed table "{0}" failed.
Supplemental logging for heartbeat seed table failed.
Action:
None
OGG-14092: Enabling supplemental logging for the heartbeat table "{0}" failed.
Supplemental logging for heartbeat table failed.
Action:
None
OGG-14093: Disabling supplemental logging for heartbeat table "{0}" failed.
Disabling supplemental logging for heartbeat table failed.
Action:
None
OGG-14095: Failed to disable supplemental logging for the heartbeat seed table {0}.
Disabling supplemental logging for heartbeat seed table failed.
Action:
None
OGG-14096: Upgrade heartbeattable failed. Database error {0,number,0} ({1})
Upgrade heartbeattable failed
Action:
No action is required.
OGG-14097: Insert into heartbeat object "{0}" failed.
Insert into heartbeat object failed.
Action:
None
OGG-14098: Update into heartbeat object "{0}" failed.
Update into heartbeat object failed.
Action:
None
OGG-14099: command 'Alter Heartbeattable' is ignored.
Alter Heartbeattable is not supported for Delivery Only DBs like TD, hence command is ignored.
Action:
None
OGG-14101: Successfully added heartbeat table.
ADD HEARTBEATTABLE command executed successfully.
Action:
None
OGG-14102: Successfully deleted heartbeat table.
DELETE HEARTBEATTABLE command executed successfully.
Action:
None
OGG-14103: Successfully upgraded heartbeat table.
UPGRADE HEARTBEATTABLE command executed successfully.
Action:
None
OGG-14104: Successfully altered heartbeat table.
ALTER HEARTBEATTABLE command executed successfully.
Action:
None
OGG-14105: Frequency not applicable for target only heartbeat table.
Scheduler job for updating heartbeat tables does not exist as heartbeat tables are target only.
Action:
Do not alter frequency for targetonly heartbeat tables.
OGG-14106: Scheduler job "{0}" does not exist.
Scheduler job for purging heartbeat history table does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the scheduler job.
OGG-14107: Heartbeat history table "{0}" does not exist.
Heartbeat history table does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the heartbeat tables.
OGG-14108: Catalog login required to upgrade heartbeat tables.
Catalog login is required to upgrade heartbeat tables.
Action:
Login to a pdb and retry the command.
OGG-14109: On Autonomous database, heartbeat table operations require dblogin to GGADMIN schema.
GGADMIN schema login is required for using heartbeat table in ADB.
Action:
Login to GGADMIN.
OGG-14110: Invalid frequency for heartbeat table. Frequency must be between between 0 and 7999.
Invalid input for repeat interval.
Action:
Specify a valid frequency between 0 and 7999.
OGG-14111: Invalid retention time for heartbeat table. Retention time must be between 1 and 2147483646.
Invalid input for retention time.
Action:
Allowed values for retention time are 1 to 2147483646.
OGG-14112: Invalid purge frequency for heartbeat table. Purge frequency must be between between 0 and 199.
Invalid input for repeat interval.
Action:
Specify a valid frequency between 0 and 199.
OGG-14500: ({0}) line {1}: Parsing error, parameter [{2}]: {3}
Parameter specification is invalid.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-14501: Parameter file {0} has unicode byte order mark and CHARSET parameter.
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.
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.
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-14504: Unable to locate the parameter definitions file.
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.
This parameter is not applicable to the running process database version.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-14550: The number of trail/file definitions exceeded maximum allocated {0, number, 0}.
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.
Loading AES library failed.
Action:
Contact Oracle Support.
OGG-14600: Specifying EXCLUDETAG + in conjunction with EXCLUDETAG NULL is not allowed.
EXCLUDETAG + and EXCLUDETAG NULL are mutually exclusive.
Action:
Verify the EXCLUDETAG option. See the Oracle GoldenGate reference documentation.
OGG-14602: Specifying EXCLUDETAG + in conjunction with other EXCLUDETAG options.
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}.
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}].
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})
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}
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}
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}
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-15054: Java executable is not found in the search path.
The Java executable can not be found or loaded.
Action:
Make sure that the Java executable is in the search path (PATH environment variable). In Linux, the Java executable is located under $(JAVA_HOME)/bin/java. In Windows, java.exe is under %JAVA_HOME%\bin\java.exe.
OGG-15055: Failed to execute shell command '{2}': ({0,number,0} {1})
The shell command can not be executed or returns a non-zero exit code.
Action:
Check the shell command's syntax and argument. If the syntax is correct, find out if there is a problem with the file system or operating system that prevents the command from succeeding.
OGG-15056: The definition for target table {0} is derived from the source table {1}.
The definition for the target table is derived from the source table.
Action:
None
OGG-15057: The definition for table {0} is obtained from the metadata provider.
The definition for the specified table is obtained from the metadata provider.
Action:
None
OGG-15101: Cannot support hierarchy-enabled tables with not-null ACL/Owner. object id: {0}
Cannot support hierarchy-enabled tables with not-null ACL/Owner.
Action:
Do not use HETs with not-null ACL/Owner with GoldenGate.
OGG-15102: Credential store created.
Credential store has been created. Informational only.
Action:
None
OGG-15103: Unable to create a new credential store.
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.
A credential store has already been created. Informational only.
Action:
None
OGG-15105: Credential store location was not found.
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.
Credential store has been deleted. Informational only.
Action:
None
OGG-15107: Unable to delete credential store.
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.
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.
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.
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.
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.
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.
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.
Credential store has been altered. Informational only.
Action:
None
OGG-15115: Reading from credential store:
The credential store is being read. Informational only.
Action:
None
OGG-15116: No information found in credential store.
Credential store at the specified location is empty. Informational only.
Action:
None
OGG-15117: Unable to retrieve information from credential store.
There was a problem retrieving information from the credential store.
Action:
Contact Oracle Support.
OGG-15118: Missing table name specification.
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}.
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}.
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 table {0}. Detail: {1}.
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}.
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}'.
The specified preparecsn mode is not valid.
Action:
Refer to the Reference for Oracle GoldenGate for Windows and UNIX for the proper specification.
OGG-15124: Table {0} does not exist.
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.
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}.
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}.
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}
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}
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.
Informational only.
Action:
None
OGG-15131: Logging of supplemental redo log data is already enabled for table {0}.
Informational only.
Action:
None
OGG-15132: Logging of supplemental redo data enabled for table {0}.
Informational only.
Action:
None
OGG-15133: TRANDATA for scheduling columns has been added on table {0}.
Informational only.
Action:
None
OGG-15134: TRANDATA for all columns has been added on table {0}.
Informational only.
Action:
None
OGG-15135: TRANDATA for instantiation CSN has been added on table {0}.
Informational only.
Action:
None
OGG-15136: TRANDATA for instantiation CSN has been disabled on table {0}.
Informational only.
Action:
None
OGG-15137: TRANDATA is already disabled for table {0}.
Informational only.
Action:
None
OGG-15138: Failed to disable TRANDATA for table {0} due to {1}.
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}.
Informational only.
Action:
None
OGG-15140: TRANDATA for all columns has been disabled on table {0}.
Informational only.
Action:
None
OGG-15141: Logging of supplemental redo log data is already disabled for table {0}.
Informational only.
Action:
None
OGG-15142: Logging of supplemental redo log data disabled for table {0}.
Informational only.
Action:
None
OGG-15143: No command was specified.
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.
There was an attempt to send a command to an unsupported OGG application.
Action:
See the Oracle GoldenGate reference documentation for the supported programs that can receive and interpret remote commands.
OGG-15146: Manager not currently running.
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.
The command could not be sent to the target program because it is not currently running.
Action:
Start the target application process.
OGG-15148: Application {0} not currently running.
The command could not be sent to the application because it is not currently running.
Action:
Start the application process.
OGG-15149: {0} {1} is initializing, please try the command later.
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.
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.
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}.
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.
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.
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.
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 group {2} is not integrated.
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-15158: Coordinated Replicat thread {0} is not running.
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}.
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}.
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 application {0} group {1}. Detail: {2}.
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}).
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 application {0}, group {1}, detail: ({2}).
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}
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.
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.
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.
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.
Informational only.
Action:
None
OGG-15169: Could not process the tracing command due to the error: {0}
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}
Informational only.
Action:
None
OGG-15171: Tracing command operation successfully processed.
Informational only.
Action:
None
OGG-15173: Could not skip the specified transaction due to the next error: {0}
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 command is being processed and will complete shortly. Detail: {0} For Oracle database, if you intend to stop Extract now, wait until the recovery checkpoint SCN from INFO EXTRACT SHOWCH is updated to greater than the start SCN of this transaction. Otherwise, the transaction is still present in the Extract.
Informational only.
Action:
None
OGG-15175: Transaction [{0}] not found.
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}".
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}".
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.
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.
The collection profiles for performance metrics have been loaded successfully.
Action:
None
OGG-15180: Not enabled.
The collection profiles for performance metrics are disabled and cannot be loaded.
Action:
Enable the collection profiles and try again.
OGG-15181: Not loaded.
The collection profiles for performance metrics could not be loaded correctly.
Action:
Contact Oracle Support.
OGG-15182: Invalid JSON formatted response.
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.
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.
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.
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.
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}.
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.
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}.
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.
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}.
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}.
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}.
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.
The specified directory does not exist yet in the Oracle GoldenGate environment.
Action:
Create the directory using the CREATE SUBDIRS command.
OGG-15195: AUTO_CAPTURE operation is not supported for this DB version.
AUTO_CAPTURE operation is not supported on the current version of the database.
Action:
Upgrade to a supported Oracle Database release.
OGG-15196: Keyword {0} is unsupported in RDBMS version running with AUTO_CAPTURE capability.
The specified keyword is not supported with the command when the running RDBMS version supports AUTO_CAPTURE capabilities.
Action:
None
OGG-15197: An operation with inconsistent data encountered where table '{0}' has the partition segment id {1} the same as the table object id {2}, with scn={3}, threadid={4}
This is usually associated with bug 30397100 where piece-wise LOB update generated the segment id using the base table id.
Action:
Contact Oracle Support.
OGG-15198: STOP request will be executed immediately (Recovery canceled).
Informational only.
Action:
None
OGG-15199: STOP request will be executed immediately (Current transaction canceled).
Informational only.
Action:
None
OGG-15200: Data target not specified
The Oracle GoldenGate Extract (capture) 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-15201: Extract group {0} not currently running.
The command could not be sent to the Extract group because it is not currently running.
Action:
Start the Extract group process.
OGG-15202: Replicat group {0} not currently running.
The command could not be sent to the Replicat group because it is not currently running.
Action:
Start the Replicat group process.
OGG-15203: Missing or invalid Kafka producer configuration, details: {0}
A Kafka producer configuration is missing or invalid.
Action:
Specify a valid Kafka producer configuration.
OGG-15204: Kafka producer returns error: {0}
An error occurred in the Kafka producer.
Action:
Resolve the problem based on the error that is shown in this message.
OGG-15205: Missing or invalid Kafka topic configuration for topic {0}, details: {1}
A Kafka topic configuration is missing or invalid.
Action:
Specify a valid Kafka topic configuration.
OGG-15300: GLOBALS file GGSCHEMA parameter must be specified.
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}.
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}.
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.
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}.
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}.
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.
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.
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}.
The specified catalog name will be used for the sequence specification.
Action:
None
OGG-15309: Sequence schema {0} does not exist.
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.
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}.
Informational only.
Action:
None
OGG-15312: Cannot obtain database version information because verification of database login failed with next error: {0}.
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}.
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}).
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 Replicat group {0}. This action is valid only for integrated, coordinated, or parallel Replicat.
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 an integrated, coordinated, or parallel Replicat process.
OGG-15316: Could not perform the Replicat synchronization operation.
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.
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-15330: FORCETRANS command is being processed and will complete shortly. Detail: {0} For Oracle database, if you intend to stop Extract now, wait until the recovery checkpoint SCN from INFO EXTRACT SHOWCH is updated to greater than the start SCN of this transaction. Otherwise, the transaction is still present in the Extract.
Informational only.
Action:
None
OGG-15331: Transaction [{0}] not found.
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.
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.
The specified command could not be executed because it is not valid for this process type.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15334: Command [{0}] is not supported by Replicat.
The specified command could not be executed because it is not valid for this process type.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15335: {0} request processed.
The specified SEND request was successfully processed.
Action:
None
OGG-15336: Could not process the TRANLOGOPTIONS request due to the next error: {0}
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.
Informational only.
Action:
None
OGG-15338: Timestamp mismatch between source and target. Accurate Lag Information Unavailable.
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.
The specified parameters for the command are invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15340: Invalid THREAD/THREADS specification.
The specified parameters for the command are invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15341: Invalid THREADRANGE specification.
The specified parameters for the command are invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15342: Table specification {0} is invalid. {1}
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.
Informational only.
Action:
None
OGG-15344: No tables found matching {0} to set {1} for {2}.
Informational only.
Action:
None
OGG-15345: Missing or invalid INTEGRATEDPARAMS options {0}.
The specified parameters for the command are invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15346: Error parsing INTEGRATEDPARAMS parameters: {0}.
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.
There are no remote host connections configured for this Extract process.
Action:
None
OGG-15348: Missing end quote for VAMMESSAGE.
The VAM message received by extract is not formatted correctly.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15349: Could not process the VAM request due to the next error: {0}
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.
There was a problem processing the VAM command.
Action:
Contact Oracle Support.
OGG-15351: Bounded recovery is off.
Informational only.
Action:
None
OGG-15352: Command [{0}] not recognized.
The specified BR command is invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15353: Bounded recovery is already running.
Informational only.
Action:
None
OGG-15354: Bounded recovery is already stopped.
Informational only.
Action:
None
OGG-15355: Unknown command {0}.
The specified command is invalid.
Action:
Verify the syntax and then issue the command again. For help, see the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax.
OGG-15356: Not enough memory to execute command.
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.
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}
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}.
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}.
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}.
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
The specified value is not a valid one for REPORTRATE.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax of the command.
OGG-15363: Invalid STATS request: {0}.
The specified option is not a valid one for STATS command.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax of the command.
OGG-15364: No active replication maps.
Informational only.
Action:
None
OGG-15365: No active extraction maps.
Informational only.
Action:
None
OGG-15366: Successfully reset statistics.
Informational only.
Action:
None
OGG-15367: Fully qualified table name {0} is not found in the Oracle GoldenGate configuration.
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.
Informational only.
Action:
None
OGG-15369: TCP stats reset.
Informational only.
Action:
None
OGG-15375: Invalid command: {0}.
The specified PROBE command is invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15376: Missing options: {0}.
There is a missing required option for the specified PROBE command.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15377: Probe is dumped to {0}.
The PROBE command result was dumped to the specified file.
Action:
None
OGG-15378: Failed to dump probes to {0}.
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 successfully loaded.
The PROBE configuration was correctly loaded from the specified file.
Action:
None
OGG-15380: Failed to load probe configuration {0}.
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 <PARAM_ID> {0}.
The specified parameter id is not valid and will be ignored.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command. If you cannot resolve the problem, contact Oracle Support.
OGG-15382: Failed to retrieve parameter information due to next error: {0}
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 <PARAM_ID> {0}.
The specified parameter id is not recognized.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct parameter syntax. If you cannot resolve the problem, contact Oracle Support.
OGG-15384: Param '{0}' is not loaded into dictionary.
The specified parameter name cannot be found in the parameter dictionary.
Action:
Contact Oracle Support.
OGG-15385: File '{0}' could not be opened.
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.
The VAM message received by extract is not formatted correctly.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
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.
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).
The STOP request will be executed after finishing processing the pending transaction.
Action:
None
OGG-15389: STOP request pending completion of recovery mode.
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.
The STOP request will be executed after the pending fetch is finished.
Action:
None
OGG-15391: Error retrieving {0} next checkpoint.
There was a problem obtaining the process checkpoint information.
Action:
Contact Oracle Support.
OGG-15392: Invalid checkpoint type.
Oracle GoldenGate was not able to recognize the process checkpoint type.
Action:
Contact Oracle Support.
OGG-15393: Unknown checkpoint error.
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).
The last value of the process lag is invalid.
Action:
Contact Oracle Support.
OGG-15395: Low watermark position not available.
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.
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.
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.
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}
Informational only.
Action:
None
OGG-15400: Could not process the STOP command due to the next error: {0}
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.
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}
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}'.
The specified command parameter is invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15404: Unrecognized parameter '{0}'.
The specified command parameter is invalid.
Action:
See the Reference for Oracle GoldenGate for Windows and UNIX for the correct syntax for the command.
OGG-15405: The container list for REGISTER EXTRACT cannot be empty.
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. For help, see the GGSCI help or the Reference for Oracle GoldenGate for Windows and UNIX.
OGG-15406: Missing opening parenthesis in container list for REGISTER EXTRACT command.
A parenthesis is missing from the container list specification for REGISTER EXTRACT command.
Action:
Add the parenthesis. For help, see the Reference for Oracle GoldenGate for Windows and UNIX.
OGG-15407: Missing closing parenthesis in container list for REGISTER EXTRACT command.
A parenthesis is missing from the container list specification for REGISTER EXTRACT command.
Action:
Add the parenthesis. For help, see the Reference for Oracle GoldenGate for Windows and UNIX.
OGG-15408: Cannot specify both '{0}' and '{1}' at the same time.
Mutually exclusive command arguments were specified.
Action:
Remove one of the arguments and try again. For help, see the Reference for Oracle GoldenGate for Windows and UNIX.
OGG-15409: Alias '{0}' not found in credential store domain '{1}'.
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}'.
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}
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.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-15413: Failed to bind SSL functions with TLSAdapter.
An internal error occurred.
Action:
Contact Oracle Support.
OGG-15414: Missing archive log file for Thread {0} Seqnum {1}, SCN 0x{2}.
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}'.
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.
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}'.
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.
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.
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: Maximum size of standby redo logs {0} must not be less than online redo logs {1}.
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}.
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.
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.
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.
One or more table specifications contain wildcard character(s). 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.
Replicat tasks cannot be altered once created.
Action:
To alter a replicat task, delete the task and re-create it.
OGG-15426: Extract group {0} started.
The specified Extract group was started.
Action:
None
OGG-15427: Redo transport experienced a lag of {0}secs at thread {1}.
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.
Redo transport lag at thread returned to acceptable levels.
Action:
No action required.
OGG-15430: No database connection was initialized while getting database information.
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.
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.
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.
Online redo logs are needed in the source database to support realtime downstream mining.
Action:
Verify that the source database has valid online redo logs configured.
OGG-15434: One of the following required parameter values is missing from the param file: EXTRACT, REPLICAT, SOURCEISTABLE, SPECIALRUN.
One of the following parameter values is required in the param file: EXTRACT, REPLICAT, SOURCEISTABLE, SPECIALRUN.
Action:
Add one of the following parameter values to the param file: EXTRACT, REPLICAT, SOURCEISTABLE, SPECIALRUN.
OGG-15435: Logical replication has been disabled on table {0}.
Informational only.
Action:
None
OGG-15436: Logical replication can not be disabled for table {0} because Oracle Goldengate replication is not enabled.
The enable_goldengate_replication system parameter is not set to true in the database. This parameter is required to support the attempted operation.
Action:
Set enable_goldengate_replication system parameter to true.
OGG-15437: Failed to disable Logical Replication for table {0} due to {1}.
There was a problem disabling the logical replication for the specified table.
Action:
Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.
OGG-15438: Enabling logical replication (with all keys) on auto capture table {0}.
Informational only.
Action:
None
OGG-15439: Logical Replication has been enabled (with non validated keys) on table {0}.
Informational only.
Action:
None
OGG-15440: Oracle GoldenGate user part of resource group {0} with resource limits.
Oracle GoldenGate user is configured as part of resource group which has resource limits.
Action:
Move Oracle GoldenGate user to a different user group.
OGG-15441: DDL is missing mapping target information.
Target Object and Schema for mapping DDL is missing.
Action:
Check that the MAP parameter contains both source and the target object information needed for mapping.
OGG-15442: Partition filter rules applied to auto capture table {0}
Partition name filter can be used on auto capture tables to include or exclude specific partitions.
Action:
Contact Oracle Support.
OGG-15443: Extract is enabled for Auto Capture.
Extract can be used to replicate auto-capture enabled tables.
Action:
None
OGG-15444: Extract is disabled for Auto Capture.
Extract will not replicate auto-capture enabled tables.
Action:
None
OGG-15445: Replicat group {0} started.
The specified Replicat group was started.
Action:
None
OGG-15446: Extract configured as {0} resource group.
Extract was configured as a part of specified resource group.
Action:
None
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.
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.
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.
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.
The timer for temporarily disabling the HANDLEDLFAILOVER parameter expired. Re-enable HANDLEDLFAILOVER.
Action:
None
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.
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.
Extract failed to determine the character set of the mining database.
Action:
Contact Oracle Support.
OGG-25092: Sequence update did not succeed, error: {0}.
Replicat failed to update the sequence value.
Action:
Examine the errors and contact Oracle Support if necessary.
OGG-25093: Invalid command format.
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.
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.
The shared pool is full and cannot allocate more resources.
Action:
Avoid creating numerous distpaths.
OGG-25102: Too many requests for distpath '{0}' are in the queue.
Too many requests were sent for the same distpath in a short period of time.
Action:
Avoid sending too many requests at once for the same distpath to distsvc.
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})
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})
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})
File access failed at the operating system level.
Action:
Correct Oracle Support.
OGG-25106: Failed to create checkpoint file {0}
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
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}
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
The specified value of the tag is reserved for Internal use.
Action:
Please choose another value for the SETTAG option.
OGG-25110: The database role {0} is unsupported
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
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}
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
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}.
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.
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 application {0}, group {1}, detail: ({2}).
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}'.
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.
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.
Creating directories failed.
Action:
Manually create all the directories.
OGG-25124: Parameter {0} is not supported by Parallel Replicat
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}.
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}')
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}'.)
Error detected on the remote side, too many (greater or equal to 1000) paths have been started.
Action:
Distribution Service will terminate the path.
OGG-25128: RESOLVECONFLICT is not supported when the target table is enabled for Automatic Conflict Detection and Resolution
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.
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.
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.
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.
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.
The process cannot use a schema name that is greater than the maximum zOS DB2 schema name length.
Action:
Use a remote schema name that is not longer than the maximum length of a zOS DB2 schema name.
OGG-25134: The EXCLUDEUSER value in the TRANLOGOPTIONS line in the EXTRACT param file cannot be longer than {0} characters.
The process cannot use a user name that is greater than the maximum zOS DB2 user name length.
Action:
Use a user name that is not longer than the maximum length of a zOS DB2 user name.
OGG-25135: This transaction cannot be forced to extract trail because of PL/SQL error. Please check log for more information.
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 file because the feature does not support CDB mode of Oracle Database prior to release 18.1.0.0
The request of SEND EXTRACT FORCETRANS failed because the feature does not support CDB mode of Oracle Database prior to release 18.1.0.0.
Action:
Use a CDB mode Oracle Database with a release equal to or later than 18.1.0.0.
OGG-25137: Missing file name (and optionally DETAIL)
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)
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.
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:
Please 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
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
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)
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 to force transaction {0} to trail file (y/n)?
Double-check before you force the transaction.
Action:
Input y to force this transaction to trial or n to stop the force operation.
OGG-25145: Extract is currently in recovery mode (reading transactions from trail file). Please try again in a few minutes
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
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)
The THREAD option not applicable to this Extract configuration.
Action:
Check THREAD option and extract configuration.
OGG-25149: THREAD value not a valid number (1, 2, 3...)
The THREAD number is not valid.
Action:
Check the THREAD number.
OGG-25151: Missing value for DURATION option
Missing a value for the DURATION option.
Action:
Please input a value for DURATION option
OGG-25152: Missing value for COUNT option
Missing a value for the COUNT option.
Action:
Please input a value for COUNT option.
OGG-25153: COUNT value not a valid number (1, 2, 3...)
The COUNT value is not a valid number.
Action:
Please check COUNT value.
OGG-25154: Long transaction report finished on {0}
Long transaction report finished.
Action:
None
OGG-25155: Starting long transaction report on {0}
Long transaction report finished.
Action:
None
OGG-25156: No transactions found
No transactions found.
Action:
None
OGG-25157: Transaction {0} is being forced to trail file.
The transaction is being forced to the trail file.
Action:
None
OGG-25158: Transaction {0} is being skipped.
The transaction is being skipped.
Action:
None
OGG-25159: COUNT option cannot be used with transaction ID
The COUNT option cannot be used with transaction ID.
Action:
Delete the COUNT option.
OGG-25160: DURATION option cannot be used with transaction ID
The DURATION option cannot be used with transaction ID.
Action:
Delete the DURATION option.
OGG-25161: TABULAR option cannot be used with transaction ID
The TABULAR option cannot be used with transaction ID.
Action:
Delete the TABULAR option
OGG-25162: File {0} could not be opened
The file could not be opened.
Action:
Check the file name.
OGG-25164: Writing transaction report to file.
Writing transaction report to file.
Action:
None
OGG-25165: Unrecognized option {0}
Unrecognized option.
Action:
Check option.
OGG-25166: Query for this request returned no data
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}.
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 the user does not have permission to use it. Update the GLOBALS file to specify a valid database schema for GGSCHEMA or create the schema in the database and assign the correct permissions to use it.
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 schema coinciding with GGSCHEMA with proper permissions for the Oracle GoldenGate database user.
OGG-25169: {0}
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
The process could not find the required Oracle GoldenGate objects in the current database.
Action:
Ensure that the Oracle GoldenGate required local objects exist in the database for the given table. If objects are missing, then ADD TRANDATA for the table to create the Oracle GoldenGate objects.
OGG-25171: Checkpoint LSN: {0} Timestamp: {1} ({2})
Display the startup checkpoint information.
Action:
None
OGG-25172: Auxiliary table information, error {0} table {1}.{2}
The Extract process could not add system table information to its internal memory structure. See the error text for more information.
Action:
Address the error specified in the message.
OGG-25173: LRSN {0}
Display an LRSN or RBA value.
Action:
None
OGG-25174: For LRSN {0}, the QWHSTYP value should = QWHSHS01 which is = 1
Display the value of the RBA where the QWHSTYP value caused a logic error.
Action:
Contact Oracle Support.
OGG-25175: For LRSN {0}, the QWHSNSDA value should = 2
Display the value of the RBA where the QWHSNDA value caused a logic error.
Action:
Contact Oracle Support.
OGG-25176: The LRSN became too high when searching for a position in the log.
An LRSN or RBA, that is to high, was calculated using the date and time specified for positioning in the log.
Action:
Modify the starting date and time so that the Extract can find a starting point in the log.
OGG-25177: The LRSN exceeded the maximum limit when searching for a position in the log.
An LRSN or RBA calculated using the date and time specified for positioning in the log, exceeded the maximum size limit.
Action:
Modify the starting date and time so that the Extract can find a starting point in the log.
OGG-25178: The LRSN became too small when searching for a position in the log.
An LRSN or RBA, that is to low, was calculated using the date and time specified for positioning in the log.
Action:
Modify the starting date and time so that the Extract can find a starting point in the log.
OGG-25179: Specified start time: {0} ({1})
Display the specified timestamp position used to start reading the log.
Action:
None
OGG-25180: Log record timestamp: {0} ({1})
Display the log record timestamp at the position processing started.
Action:
None
OGG-25181: {0} ECSA memory at {1} for length {2}.
Report shared ECSA memory allocation and deallocation information returned from DB2.
Action:
Reported so that shared ECSA memory can be released, if memory deallocation does not occur.
OGG-25182: {0}
Display a DB2 or other system trace message.
Action:
None
OGG-25183: Using DB2 subsystem {0} In data sharing group {1}
Display the DB2 subsystem and the data sharing group.
Action:
None
OGG-25184: Using DB2 subsystem {0}
Display the non-datasharing DB2 Subsystem being used.
Action:
None
OGG-25185: Failed to add LOB chunk number {0,number,0}, size {1,number,0} for PSID {2}. Cause: {3}
The process could not add LOB chunk to memory possibly due to it having a large size or other limitation.
Action:
Add the FETCHMODCOLS configuration to the TABLE statement and restart the Extract process.
OGG-25186: Using default redo buffer size {0}
Display the configured redo buffer size.
Action:
None
OGG-25187: GRANT <privileges> TO <user-list> IDENTIFIED BY <password-list> DDL replication is not supported for Classic Extract.
A DDL record that combines creating users and granting privileges to the users is not supported by Classic Extract.
Action:
Split the DDL into separate commands: (1) creating the users, (2) granting privileges to the users.
OGG-25188: TRANLOGOPTIONS DB2ZV11COMPATIBILITYMODE specified connecting to unsupported database version. Option will be ignored.
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.
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.
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.
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.
OGG-25192: Trail file '{0}' is remote. Only local trail allowed for this extract.
This extract can only write to a local trail file.
Action:
Replace the RMTTRAIL parameter with an EXTTRAIL parameter.
OGG-25193: {0} is a deprecated parameter and it is no longer in use.
The NOUSESUBDIRS│USESUBDIRS parameter is deprecated and was specified.
Action:
Contact Oracle Support to obtain the current version. Remove the NOUSESUBDIRS│USESUBDIRS parameter from the command line.
OGG-25194: Error accessing auxiliary table information, reason: {0}
The Extract process cannot access some system table information. See reason information for details.
Action:
Address the error specified in the reason information.
OGG-25195: In-Database row archival is supported in Integrated Capture mode only and requires trail format RELEASE 12.2 or later. Any mismatch in row archival settings on source and target databases may result in process abend or divergence.
In-Database row archival is supported in Integrated Capture mode only and requires trail format RELEASE 12.2 or later. Any mismatch in row archival settings between source and target database may result in process abend or divergence.
Action:
Undefined
OGG-25196: In-Database row archival is enabled for {0}. Any mismatch in row archival settings on source and target databases may result in process abend or divergence.
In-Database row archival is supported in Integrated Capture mode only and requires trail format RELEASE 12.2 or later. Any mismatch in row archival settings between source and target database may result in process abend or divergence.
Action:
Undefined
OGG-25197: The DB2 member node is restarting. Restart extract or connect to a different member in case of PureScale. db2ReadLog error [{0}] [{1}]
db2ReadLog() returned an error indicating that the DB2 member node is being restarted.
Action:
If the node is back online then restart extract or reconnect to a different member in case of PureScale.
OGG-25199: OUTPUTFORMAT XML _AUDIT_VAULT is not supported until database version 12.2
The parameter file contains the OUTPUTFORMAT parameter with the _AUDIT_VAULT option, which is not supported for database versions prior to 12.2.
Action:
Remove the _AUDIT_VAULT option.
OGG-25200: Error initializing the Oracle Key Vault environment context.
There was a problem initializing the Oracle Key Vault context. Possible causes include a network connection problem or an invalid configuration file.
Action:
Verify the logs and look for any error during the Oracle Key Vault context initialization and connection setup. Verify that the Oracle Key Vault client configuration file has been properly specified. Also, make sure that the Oracle Key Vault server is running. If you cannot resolve the problem, contact Oracle Support.
OGG-25201: Error retrieving the UID for object {0} from Oracle Key Vault server.
There was a problem finding the Unique Identifier for the object with the specified name in Oracle Key Vault server. The name may be incorrect, the object no longer exists, or the host does not have the right permissions with the server.
Action:
Verify that the key name is spelled correctly. Verify that the object exists in the server. Also, make sure that the Oracle GoldenGate host has the appropriate permission with Oracle Key Vault server to retrieve the specified key.
OGG-25202: Error retrieving the cryptographic key '{0}' with UID {1} from Oracle Key Vault server.
There was a problem retrieving the encryption key from the Oracle Key Vault server. Possible causes include invalid permissions with the server.
Action:
Verify that the key name is spelled correctly. Verify that the object exists in the server. Also, make sure that the Oracle GoldenGate host has the appropriate permission with Oracle Key Vault server to retrieve the specified key.
OGG-25203: Key in state '{0}' cannot be used to encrypt data.
The specified master encryption key cannot be used for encryption operations because of its state.
Action:
Specify a different master encryption key or change the key state.
OGG-25204: Error retrieving the cryptographic key '{0}' with UID {1} from Oracle Key Vault server. The state of the key is '{2}'.
The encryption key has been destroyed.
Action:
Specify a different cryptographic key.
OGG-25205: Error retrieving the state of cryptographic key '{0}' with UID {1} from Oracle Key Vault server.
There was a problem retrieving the state of the encryption key from the Oracle Key Vault server. Possible causes include invalid permissions with the server.
Action:
Make sure that the Oracle GoldenGate host has the appropriate permission with Oracle Key Vault server to retrieve the specified key.
OGG-25206: Size of master encryption key {0} is {1} bytes. Expected size is {2}.
The specified master encryption key size is invalid.
Action:
Specify a different master encryption key with a valid size as indicated by this error message.
OGG-25207: Loading master encryption key from Key Management System '{0}'
The specified master encryption key will be loaded using the provided Key Management System configuration. This is an informational message.
Action:
None
OGG-25208: Key Management System using configuration file {0}.
The specified master encryption key will be loaded using the provided Key Management System configuration. This is an informational message.
Action:
None
OGG-25209: Retrieved master encryption key {0} version {1} with state {2}.
The master encryption key with specified attributes was loaded for encryption operations. This is an informational message.
Action:
None
OGG-25210: Error retrieving the version of cryptographic key '{0}' with UID {1} from Oracle Key Vault server.
There was a problem retrieving the version of the encryption key from the Oracle Key Vault server. Possible causes include invalid permissions with the server.
Action:
Make sure that the Oracle GoldenGate host has the appropriate permission with Oracle Key Vault server to retrieve the specified key.
OGG-25211: Error performing master encryption key operation in the local wallet while KMS is in use.
Unable to perform master encryption key operations in the local wallet while KMS is in use.
Action:
Disable KMS.
OGG-25212: Could not obtain active transaction(s) and the current scn information because verification of database login failed with next error: {0}.
A request for information about active transactions and the current SCN was attempted without first issuing a DBLOGIN command or establishing a database connection.
Action:
Provide the correct database login details, and then retry this operation.
OGG-25214: The SSL certificate: {0} can not be loaded. {1}
The certificate may be corrupted or the way it is generated is not correct.
Action:
Verify that the generated certificate is working correctly using the standalone Cassandra connector binary, and then retry. Contact Oracle support for Cassandra connector binary.
OGG-25215: The PEM formatted private key file used to verify the client's certificate is missing. For two-way handshake or if ENABLECLIENTAUTH is set, then it is mandatory to set PEMCLIENTPRIVATEKEYFILE in your Oracle GoldenGate GLOBALS file or in the Extract parameter file.
PEMCLIENTPRIVATEKEYFILE is not set to enable two-way handshake.
Action:
Set "CPPDRIVEROPTIONS SSL PEMCLIENTPRIVATEKEYFILE filename.pem" in your Oracle GoldenGate GLOBALS or in the Extract parameter file.
OGG-25216: The PEM formatted public key file used to verify the client's certificate is missing. For two-way handshake or if ENABLECLIENTAUTH is set, then it is mandatory to set PEMCLIENTPUBLICKEYFILE in your Oracle GoldenGate GLOBALS file or in Extract parameter file.
PEMCLIENTPUBLICKEYFILE is not set to enable two way handshake.
Action:
Set "CPPDRIVEROPTIONS SSL PEMCLIENTPUBLICKEYFILE filename.pem" in your Oracle GoldenGate GLOBALS file or in the Extract parameter file.
OGG-25217: The PEM formatted public key file used to verify the peer's certificate is missing. If SSL is enabled, then it is must to set PEMPUBLICKEYFILE in your Oracle GoldenGate GLOBALS file or in Extract parameter file.
PEMPUBLICKEYFILE is not set for SSL handshake.
Action:
Set "CPPDRIVEROPTIONS SSL PEMPUBLICKEYFILE filename.pem" in your Oracle GoldenGate GLOBALS file or in the Extract parameter file.
OGG-25219: Can not open the SSL certificate: {0}.
The certificate may not exist or there is some problem in the user permissions.
Action:
Check the existence and permissions of the given certificate. Also, check its absolute path with the qualified name.
OGG-25220: No secondary truncation point was set at startup. If a log backup should occur before any replicable transactions are processed, then Extract is not be able to restart and must be manually positioned to the new start of the transaction log.
No truncation point was at startup.
Action:
If extract is restarted reposition extract to the start of the online transaction log.
OGG-25221: Processing transaction (XID: {0}, Seqno: {1,number,0}, RBA: {2,number,0}) larger than eager size ({3})
IR has encountered a transaction larger than eager size.
Action:
IR has encountered a transaction larger than eager size.
OGG-25222: Large transaction completed. Total records: {0}
IR has completed a transaction larger than eager size.
Action:
IR has completed a transaction larger than eager size.
OGG-25224: PureScale members unavailable or Automatic Client Reroute (ACR) is not configured in the db2dsdriver.cfg file. DB2 error {0}
All PureScale members are unavailable or Automatic Client Reroute (ACR) is not configured in the db2dsdriver.cfg file.
Action:
Check if there are unavailable PureScale members and that ACR is configured properly in the db2dsdriver.cfg file.
OGG-25225: PureScale member that Extract is connected to is not available. Retrying db2ReadLog as connection will be rerouted by DB2 driver.
The PureScale member that Extract is connected to may be down or unavailable. The connection should get rerouted automatically to an available member.
Action:
No action required because the connection is automatically rerouted to an available member.
OGG-25227: Unsupported datatype '{1}' for table '{0}'. Column will not be captured or replicated.
The table contains an unsupported column.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25228: Unsupported datatype '{1}' in key column for table '{0}'. Table '{0}' will not be captured.
The table contains an unsupported column as primary key.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25229: Table '{0}' contains no supported datatypes. Table '{0}' can not be captured.
All columns of the table are unsupported.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25230: Unsupported datatype '{1}' used with '{2}' in table '{0}'.
An unsupported column cannot be used with the specified parameter.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25231: Unsupported datatype '{1}' used with '{2}' in table '{0}'.
An unsupported column cannot be used with the specified parameter.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25232: Unsupported datatype '{1}' in table '{0}'. The target column is not nullable, please specify a default value of the column in the database or use Oracle GoldenGate COLMAP to exclude the column.
An unsupported column should be nullable at target.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25233: Unsupported datatype '{2}' used for '{1}' in table '{0}'.
An unsupported column cannot be used with the specified parameter.
Action:
See Using Oracle GoldenGate for Oracle Database for more information.
OGG-25234: Column value for column {1} is missing in the target table {0}
The column value is missing for the target table.
Action:
If you are working with an Oracle GoldenGate developer, then contact that person. Otherwise, contact Oracle Support.
OGG-25252: The extract DB2 stored procedure major version is {0} and the Minor version is {1}.
The version number used to verify DB2 stored procedure and function compatibility. The minor version is never verified. This is an informational message.
Action:
None
OGG-25253: The major initialization stored procedure version is {0} and may not be supported. (The minor version is {1}).
The DB2 initialization stored procedure may not be compatible with this version of Oracle GoldenGate and the Extract may have reduced functionality or may cease to function properly.
Action:
Install the proper initialization stored procedure in the DB2 subsystem identified in the Extract report.
OGG-25254: The major log reading user defined function version is {0} and may not be supported. (The minor version is {1}).
The DB2 initialization stored procedure may not be compatible with this version of Oracle GoldenGate and the Extract may have reduced functionality or may cease to function properly.
Action:
Install the proper log reading user defined function in the DB2 subsystem identified in the Extract report.
OGG-25255: The Extract does not have the fix for Bug 28520557
The Extract does not have fix for bug 28520557
Action:
Upgrade Extract to have patch for fix of bug 28520557
OGG-25256: DATA CAPTURE CHANGES enabled for SYSIBM.SYSCOLUMNS. This may allow the capture of table alterations when SYSIBM.SYSTABLES is also set for data capture and the DDL parameter is specified.
If DATA CAPTURE CHANGES is enabled for SYSIBM.SYSCOLUMNS and SYSIBM.SYSTABLES, then log information can be used to capture log records with tables alter information if the DDL parameter is also specified.
Action:
Enable DATA CAPTURE CHANGES for both SYSIBM.SYSCOLUMNS and SYSIBM.SYSTABLES in DB2 if alter table log record processing is desired. Data capture for SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS must be on, and the DDL parameter must be specified to enable this feature.
OGG-25257: System information from SYSIBM.SYSTABLES is unavailable to the Extract. The Extract may not be able to process drop table and some alter table log records.
If the Extract does not have permissions for SYSIBM.SYSTABLES or the table is inaccessible for other reasons, the table should be made available so the Extract can process system information.
Action:
Enable SYSIBM.SYSTABLES in DB2 if alter table log record processing is desired. Both sysibm.systables and sysibm.syscolumns must be on to enable this feature.
OGG-25258: System information from SYSIBM.SYSCOLUMNS is unavailable to the Extract. The Extract may not be able to process some alter table log records.
If the Extract does not have permissions for SYSIBM.SYSCOLUMNS or the table is inaccessible for other reasons, the table should be made available so the Extract can process alter table information.
Action:
Enable SYSIBM.SYSCOLUMNS if alter table log record processing is desired. Both SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS must be on to enable this feature.
OGG-25259: SYSIBM.SYSCOLUMNS is queued in the list of database and table IDs that may be used with APIFILTER.
If APIFILTER is enabled and DATA CAPTURE CHANGES is enabled for SYSIBM.SYSCOLUMNS, then the SYSIBM.SYSCOLUMNS database and table ID is added to the list of APIFILTER IDs.
Action:
Enable DATA CAPTURE CHANGES for SYSIBM.SYSCOLUMNS. 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-25260: Attempted to register {0} {1} to process status file with unknown protocol.
The protocol the process is trying to use is not supported by Oracle GoldenGate.
Action:
Contact Oracle Support.
OGG-25261: Host connection string is using unsupported protocol: {0}.
A connection string read from a process status file is specifying an unsupported protocol.
Action:
Contact Oracle Support.
OGG-25262: Process was configured to use an unsupported network protocol.
Configuration for the process indicated the usage of a protocol that is not supported on the platform on which it is running.
Action:
Contact Oracle Support.
OGG-25263: The command {0} is not supported.
The command is not supported.
Action:
Check and correct the command.
OGG-25264: Invalid transaction id {0}.
The Transaction id is not valid.
Action:
Check and correct the transaction id.
OGG-25265: Error code {0}, detail: {1} while retrieving item ({2}) for transaction.
Internal error. Cannot find the requested first or next record in a transaction.
Action:
Contact Oracle Support.
OGG-25266: There is a mismatch between number of columns detected, {0}, and the information fetched for table {1}.{2}
There is an inconsistency in retrieving column information for a table.
Action:
Contact Oracle Support.
OGG-25267: There was an error processing a database statement related to DDL processing. Processing will continue using classic method. {0}
There is a problem reading or writing to the DDL history table.
Action:
Check the previous message. Ensure that the DDL history table is set up correctly.
OGG-25268: Column {0} was not found while searching the DDL history table.
A column is missing from the DDL history table.
Action:
Ensure that the DDL history table is set up correctly. Ensure that extract spans entire history of the table.
OGG-25269: Expecting qualified name in format 'SCHEMA.TABLE' and found {0}
The name representing a table was found in an unexpected format.
Action:
Contact Oracle Support.
OGG-25270: Expecting change column subtype for:{0} but encountered end.
There is an inconsistency in the database or a program logic error.
Action:
Contact Oracle Support.
OGG-25271: Unrecognized encoding, {0} was encountered while processing alter column.
There is an inconsistency in the database or a program logic error.
Action:
Contact Oracle Support.
OGG-25272: Failed to retrieve metadata history version {0} for column {1} in table {2} while processing log record with LSN {3}.
There is an inconsistency in the database or a program logic error.
Action:
Contact Oracle Support.
OGG-25273: Unexpected change column subtype, {0}, encountered while processing column {1}.
There is an inconsistency in the database or a program logic error.
Action:
Contact Oracle Support.
OGG-25274: Metadata history version {0} for table {1} was not found (current range {2} to {3}) while processing log record with LSN {4}.
Version was out of range of values in the table history.
Action:
Ensure that the DDL history table is set up correctly. Ensure that extract spans entire history of the table.
OGG-25275: Version {0} for table {1} was not found in the table history while processing record with LSN {2}.
No corresponding version was found in the table history.
Action:
Ensure that the DDL history table is set up correctly. Ensure that extract spans entire history of the table.
OGG-25276: Unable to invalidate table {0} after DDL change
Unable to invalidate a table entry due to a previous error.
Action:
See previous messages.
OGG-25277: Oldest LRI required to restart Extract is: {0}.{1}
The SHOWTRANS command was executed.
Action:
None
OGG-25278: LSN to restart Extract is: {0}
The SHOWTRANS command was executed.
Action:
None
OGG-25279: ------------------------------------------------------------ UOW (XID): {0} Items: {1} LRI (LFS.LSN): {2} Status: {3} Log Stream: {4}
The SHOWTRANS command was executed.
Action:
None
OGG-25280: ------------------------------------------------------------- URID(XID): {0} Items: {1} Start time: {2} LSN: {3}
The SHOWTRANS command was executed.
Action:
None
OGG-25281: UOW (XID) Items LRI(LFS.LSN) Status Log Stream ----------------------------------------------------------------------------------------------------
The SHOWTRANS output should be in tabular format.
Action:
None
OGG-25282: XID Items Extract Status ----------------------------------------------------------------------------------------------------
The SHOWTRANS output should be in tabular format.
Action:
None
OGG-25283: Error retrieving redo log io checkpoint.
Could not retrieve the Extract redo log checkpoint position. The Extract checkpoint may be corrupted.
Action:
Contact Oracle Support.
OGG-25284: The Extract is configured for DDL processing and will capture table changes when SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS have data capture changes enabled.
The DDL parameter can be used in conjunction with SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS enabled for change data capture when processing of table alterations is wanted.
Action:
Specify the DDL parameter in the parameter file to enable this feature when SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS have changed data capture enabled.
OGG-25285: The Extract is configured for DDL processing. System information from SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS must have data capture changes enabled or the Extract cannot process DDL alter and create table log records.
If SYSIBM.SYSTABLES or SYSIBM.SYSCOLUMNS does not have change data capture enabled, these table should be altered to have change data capture allowing the Extract to process system information when DDL is configured.
Action:
Enable change data capture for SYSIBM.SYSTABLES and SYSIBM.SYSCOLUMNS in DB2 if alter table log record processing is desired. Both tables must have this value enabled for alter and create table processing.
OGG-25286: Possible erroneous negative lag ({0} ms) has been detected and ignored.
Negative lag has been detected.
Action:
If lag is reported normally, then you can ignore this; if lag is always being reported as 0, then check the date/time at the source and target.
OGG-25287: Oldest journal position to restart extract is: Journal : {0} Journal Receiver : {1} Journal Sequence number : {2}
The SHOWTRANS command was executed.
Action:
None
OGG-25301: DB2 transaction log is not available. Retrying db2ReadLog.
API db2ReadLog() returned error SQLU_RC_MISSING_EXT. A DB2 transaction log may be unavailable temporarily. Retrying db2ReadLog().
Action:
No action required.
OGG-25302: Unable to create KMS "{0}".
The specified KMS configuration is invalid or not supported.
Action:
Verify that the KMS options are supported and spelled correctly in the GLOBALS parameter file or the encryption profile. If you cannot resolve the problem, contact Oracle Support.
OGG-25303: The GGSCHEMA value in the GLOBALS file cannot be longer than {0} characters.
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-25304: Detected gap in metadata history at version {0} for table {1} while processing log record with LSN {2}.
There may have been some DDL executed for the table that was not captured by Extract.
Action:
The situation may not present a problem as the program will fall back to the previous way of processing records. If a problem does occur, then try replaying Extract over the time span of the DDL.
OGG-25305: Encryption Profile {0} does not exist.
The given encryption profile does not exist.
Action:
Use a valid encryption profile.
OGG-25306: A default encryption profile has not been set
A default encryption profile has not been set
Action:
Set a profile as default.
OGG-25307: Missing entry in configDataDescription for encryption profile {0}.
A missing entry in configDataDescription.
Action:
Add an entry in configDataDescription for the encryption profile.
OGG-25308: Master encryption key name '{0}' in trail file does not match encryption profile master encryption key name '{1}'.
The master encryption key name in the trail file does not match the master encryption key name in the encryption profile being used.
Action:
Make sure that the correct master encryption key is configured in the encryption profile.
OGG-25309: Operation not allowed for '{0}'.
This operation is not allowed.
Action:
Perform only those operations that are allowed on the encryption profile.
OGG-25310: Only one output trail allowed when OUTPUTFORMAT XML _AUDIT_VAULT is specified.
The parameter file contains multiple Extract trails when OUTPUTFORMAT XML _AUDIT_VAULT is specified.
Action:
Remove the _AUDIT_VAULT option or specify only one EXTTRAIL statement in the parameter file.
OGG-25311: SQL Server CDC does not support column-level collations. Column '{1}', in table '{0}', with collation '{2}' is different from database collation '{3}'. Some characters may not be translated properly. Use a Unicode datatype, remove the column-level collation, or use FETCHMODCOLS to fetch the value from the source table.
The table column has a different collation from database collation.
Action:
Use a Unicode data type or remove the column-level collation.
OGG-25312: Keyspace {0} does not exist in the database.
The specified keyspace does not exist in the database, but it is specified in the Oracle GoldenGate configuration.
Action:
None
OGG-25313: Keyspace {0} does not exist in the database.
The specified keyspace does not exist in the database, but it is specified in the Oracle GoldenGate configuration.
Action:
None
OGG-25314: Table {0} does not exist in the database.
The specified table does not exist in the database but is specified in the Oracle GoldenGate configuration.
Action:
None
OGG-25315: Unexpected error while fetching row
The fetch through cpp driver resulted in an error for one or more rows in the result set.
Action:
Attempt to resolve the error by using lower fetchbatchsize. If you cannot resolve the problem, contact Oracle Support.
OGG-25316: TRANLOGOPTIONS MIXEDENDIAN enabled. It is assumed that the database and Oracle GoldenGate are running on different endian servers. Necessary conversions will be performed.
DB2 LUW and Oracle GoldenGate are running on different Endian servers. Necessary conversions will be performed.
Action:
None
OGG-25317: Table {0} column {1} : the fractional part of the captured timestamp will be truncated from {2} to {3} digits.
The timestamp column has higher granularity than the maximum supported fraction digits. The captured timestamp data will be truncated.
Action:
None. Extract will process the timestamp data with less granularity.
OGG-25319: Detected DB2 LUW and Oracle GoldenGate to be running on different Endian servers. DB2 LUW is running on {0}. Necessary conversions will be performed.
DB2 LUW and Oracle GoldenGate are running on different Endian servers. Necessary conversions will be performed.
Action:
None
OGG-25320: DB2 LUW version is 10.1. Detection of the byte order of the database server is not supported. Assuming the database byte order matches environment where the Extract is running.
Cannot detect the database server OS architecture type from the catalog tables of DB2 LUW v10.1.
Action:
If this is a cross Endian capture then, specify TRANLOGOPTIONS MIXEDENDIAN ON in the Extract parameter file.
OGG-25321: Could not retrieve active transaction(s) and the current scn details; because of the following OCI error: {0}-{1}.
An OCI error prevented Oracle GoldenGate from getting information about active transactions and the current scn.
Action:
Fix the OCI error and then retry the operation. If the OCI error cannot be resolved, contact Oracle Support.
OGG-25330: The hexadecimal LRSN Delta value is {0} bytes long. When it is specified on the lrsntimedelta parameter it must be 20 bytes long.
The delta value should be cut and pasted from the DB2 subsystem Bootstrap Dataset (BSDS) for an accurate result and must contain the full 20 byte hexadecimal string.
Action:
Check the length of the delta value and recopy it from the Bootstrap Dataset (BSDS) report.
OGG-25331: The LRSN delta value must be a valid hexadecimal string but contains at least one invalid two byte combination at position {0} (beginning at 0).
The hexadecimal value may not have been copied from the Bootstrap Dataset (BSDS) report correctly.
Action:
Check the Bootstrap Dataset (BSDS) report and reenter the LRSN delta value.
OGG-25332: The Extract is using LRSN delta value: {0} This delta is used to adjust operation timestamp values.
Informational only.
Action:
None
OGG-25333: Sourcedb {0} accessed from {1} changed, cannot deallocate ECSA memory at {2} for length {3}.
The configured DB2 z/OS name is different than the name from the previous Extract process. Recovery cannot deallocate this memory and it should be deallocated independent of the Extract process.
Action:
Reported so that shared ECSA memory can be released in case the ECSA memory was allocated on a different DB2 z/OS mainframe.
OGG-25334: The Extract will deallocate the previous Extract's ECSA memory at {0} for length {1}.
Report shared ECSA memory will be released automatically by the Extract because it was not deallocated due to the abnormal termination of the previous Extract process.
Action:
Reported to indicate that previously allocated shared ECSA memory will be released by the current Extract process.
OGG-25335: The SSL certificate authority {0} specified in the prm file not found.
The path of the SSL certificate authority (CA) specified in the the Oracle GoldenGate parameter file is not accessible.
Action:
Verify that the paths of the SSL certificate authority (CA) specified in the parameter file is not accessible.
OGG-25336: The SSL client certificate {0} specified in the prm file not found.
The path of the SSL client certificate specified in the the Oracle GoldenGate parameter file is not accessible.
Action:
Verify that the path of the SSL client certificate specified in the Oracle GoldenGate parameter file is not accessible.
OGG-25337: The SSL client private key {0} specified in the prm file not found.
The path of the SSL client private key specified in the the Oracle GoldenGate parameter file is incorrect.
Action:
Verify that the path of the SSL client private key specified in the Oracle GoldenGate parameter file is correct.
OGG-25338: The workaround for the Teradata's deferred LOB issue is enabled and might have an impact on the performance.
Teradata database returns "deferred lob is used more than once" when replicat attempts to set a LOB column to NULL as part of an ALL-AMP UPDATE operation. The DBOPTIONS parameter _ENABLEDEFERREDLOBWORKAROUND enables a workaround that assigns an inline NULL value to the LOB columns instead of using parameterized query.
Action:
The DBOPTIONS parameter _ENABLEDEFERREDLOBWORKAROUND might have an impact on the performance. If the LOB column(s) are never intended to be SET to NULL, then this parameter should not be used.
OGG-25339: Connected to database {0}, CPU information not available.
The Oracle GoldenGate is not able to collect CPU information of the data base server or the user does not have the correct level of permissions to determine the CPU information.
Action:
None
OGG-25340: Database Version: {0}
Report DB version.
Action:
None
OGG-25341: Database Language and Character Set: {0}
Report DB language and character set.
Action:
None
OGG-25342: Found a non-nesting XML start element {0}, in an existing context while parsing {1}.
XML obtained from parsing context is malformed.
Action:
None
OGG-25343: Found a terminating XML element {0} with no corresponding begin while parsing {1}.
XML obtained from parsing context is malformed.
Action:
None
OGG-25344: Found an unexpected XML element {0} while parsing {1} to obtain {2}.
XML obtained from parsing context is malformed.
Action:
None
OGG-25345: SAX error, {0}, while parsing {1}.
XML obtained from parsing context is malformed.
Action:
None
OGG-25346: SAX fatal error, {0}, while parsing {1}.
XML obtained from parsing context is malformed.
Action:
None
OGG-25347: SAX warning, {0}, while parsing {1}.
XML obtained from parsing context is malformed.
Action:
None
OGG-25348: Table {0} was not found while building the optional APIFILTER Object ID list. The Extract will filter without using an Object ID list.
The DB2 catalog query for the specified table failed and the Extract was unable to obtain an ID to use in the DB2 APIFILTER Object ID list.
Action:
No action is needed. The APIFILTER option can be used without an Object ID List. The table might have been dropped or it does not exist yet. When the table is created, the Extract will process any log records found for this table.
OGG-25349: No metadata was found for {0}
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle GoldenGate Support.
OGG-25350: Extract group {0} must first be deleted before it can be registered/unregistered.
A REGISTER/UNREGISTER EXTRACT command was issued for an Extract group that was not added/deleted.
Action:
Delete the Extract group, and then retry the command.
OGG-25351: Extract group name was not found.
Logical programming error.
Action:
Contact Oracle GoldenGate Support.
OGG-25352: The replication slot name '{0}' used in the REGISTER/UNREGISTER EXTRACT command must not exceeds the maximum(64 characters) allowed length.
The replication slot name used in REGISTER/UNREGISTER EXTRACT command exceeds the maximum(64 characters) allowed length.
Action:
Contact Oracle GoldenGate support.
OGG-25353: The replication slot '{0}' for group '{1}' already exist in the database '{2}'.
The given replication slot already exists in the connected database.
Action:
No action required.
OGG-25354: The replication slot '{0}' for group '{1}' does not exist in database '{2}'.
The given replication slot does not exist in the connected database.
Action:
No action required.
OGG-25355: Successfully created replication slot '{0}' for Extract group '{1}' in database '{2}'.
Successfully created replication slot.
Action:
No action required.
OGG-25356: Successfully dropped the replication slot '{0}' for Extract group '{1}' in database '{2}'.
Extract successfully dropped the replication slot.
Action:
No action required.
OGG-25357: Cannot register or unregister Extract group {0} because the Extract is currently running. Stop the Extract and retry the command.
REGISTER/UNREGISTER EXTRACT command was issued without first stopping the process.
Action:
Stop the Extract process, then issue a DBLOGIN command, and then the REGISTER EXTRACT or UNREGISTER EXTRACT command.
OGG-25358: Extract {0} cannot be registered as it is a pump
The REGISTER EXTRACT command is being run on a pump Extract.
Action:
Do not run the REGISTER EXTRACT command on a pump Extract.
OGG-25359: Could not connect to server with database '{0}', host '{1}', port '{2,number,0}' and user name '{3}'. Error Message: {4}.
The connection to the database has failed.
Action:
Check the credentials including user name, password, host name, port number and follow the error message string to resolve the error or contact Oracle GoldenGate support.
OGG-25360: Database error occurred.Error Message:{0}.
The database has thrown an error.
Action:
Contact Oracle GoldenGate support.
OGG-25361: Could not determine server setting for integer DATETIME.
The server integer DATETIME setting is not determined during the connection.
Action:
Contact Oracle GoldenGate support.
OGG-25362: Integer DATETIME compile flag does not match with the server integer DATETIME.
The server integer DATETIME compile flag does not match with the connected server.
Action:
Contact Oracle GoldenGate support.
OGG-25363: Could not send replication command 'IDENTIFY_SYSTEM' to server - {0}.
The replication command sent to the server was not accepted.
Action:
Contact Oracle GoldenGate support.
OGG-25364: Could not identify system, got rows{0} and fields{1}, expected {2} rows and {3} or more fields.
The number of rows and fields received after the replication command was sent to the server are not correct.
Action:
Contact Oracle GoldenGate support.
OGG-25365: Could not parse write ahead location {0}.
There is a problem in parsing the write ahead location.
Action:
Contact Oracle GoldenGate support.
OGG-25366: Unexpected termination of replication stream. Error Message:{0}.
The Replication stream has terminated unexpectedly.
Action:
Contact Oracle GoldenGate support.
OGG-25367: Invalid socket when receiving network data: {0}.
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:
Check the network connectivity between the source and target systems. Verify that the number of connections has not exceeded the operating system limitation. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25368: Select socket failed when receiving network data. Detail: {0}.
Socket select failed while receiving the data from the network.
Action:
Check the network connectivity between the source and target systems. Verify that the number of connections has not exceeded the operating system limitation. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25369: Failure while reading the copy stream. Detail: {0}.
Failure happened while receiving data from the socket over the network.
Action:
Check the network connectivity between the source and target systems. Verify that the number of connections has not exceeded the operating system limitation. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25370: Could not receive data from write ahead log stream{0}.
Failure happened while receiving the data from the write ahead log stream.
Action:
Contact Oracle GoldenGate support.
OGG-25371: The streaming header length {0} is too small to process.
The header length received from the socket is too small to determine any valid record.
Action:
Contact Oracle GoldenGate support.
OGG-25372: The streaming header'{0}' received cannot be recognized.
The header data received from the write ahead log stream cannot be recognized.
Action:
Contact Oracle GoldenGate support.
OGG-25373: The write ahead log current location (EOF) not found.Error Message{0}.
There is a problem in database result set.
Action:
Contact Oracle GoldenGate support.
OGG-25374: The replication slot '{0}' for group '{1}' does not exist in the database '{2}'.
The given replication slot does not exist in the connected database or there is a problem in retrieving the result set.
Action:
Run the DBLOGIN command and then register the Extract group name to create the replication slot.
OGG-25375: The commit timestamp{0} received from the log is converted to julian timestamp{1} is a not a valid timestamp.
There is a parsing error while converting the string timestamp.
Action:
Contact Oracle GoldenGate support.
OGG-25376: Oracle GoldenGate capture '{0}' running with replication slot '{1}', slot type '{2}', plugin name as '{3}' attached with database '{4}' with slot restart LSN as '{5}', flush LSN as '{6}' and its current TXID as '{7}'.
This is an informational message.
Action:
No action required.
OGG-25377: Positioning to end of file (EOF) location'{0}'.
This is an informational message..
Action:
No action required.
OGG-25378: Positioning to the log sequence number(LSN)'{0}'.
This is an informational message.
Action:
No action required.
OGG-25379: The position by the given log sequence number(LSN)'{0}' does not fall between the replication slot position'{1}' and the current write ahead log position'{2}'.
The start position provided by the user does not fall between the current slot position and the write ahead log position.
Action:
Provide any LSN, which lies between the replication slot and write ahead log position.
OGG-25380: Could not send the feedback packet.Error message:{0}.
The feedback packet was not delivered to the server during the COPY_IN state.
Action:
Check the network connectivity between the source and target systems. Verify that the number of connections has not exceeded the operating system limitation. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25381: Positioning at Log Sequence Number (LSN) '{0}', with record TimeStamp (TS) as {1,date} {1,time} and Transaction ID as'{2}'.
This is an informational message.
Action:
No action required.
OGG-25382: The column name '{0}' received from the log record does not exist in the existing metadata for the given table'{1}'.
Possible cause could be DDL changes for the given table.
Action:
Restarting the capture process may resolve this problem. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25383: Metadata changes detected for table'{4}'. Log received column'{0}' and datatype'{1}' while existing metadata has column'{2}' and datatype'{3}'.
Possible cause could be DDL changes for the given table.
Action:
Restarting the capture process may resolve this problem. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25384: Extract group '{0}' must be added prior to running REGISTER EXTRACT command.
Extract group is not added and user is trying to run REGISTER command.
Action:
Add the Extract group first and then run the REGISTER command.
OGG-25385: Extract '{0}' cannot be unregistered as it is a pump Extract type
The UNREGISTER EXTRACT command is being run on a pump Extract.
Action:
Do not run the UNREGISTER EXTRACT command on a pump Extract type.
OGG-25386: Extract {0} cannot be registered as it is a pump Extract type
The REGISTER command is being run on a pump Extract.
Action:
Do not run the REGISTER EXTRACT command on a pump Extract type.
OGG-25387: Extract {0} cannot be unregistered as it is a pump Extract type
The UNREGISTER command is being run on a pump Extract.
Action:
Do not run the UNREGISTER EXTRACT command on a pump Extract type.
OGG-25388: Memory could not be allocated for parsing the WAL record.
Memory could not be allocated for parsing the WAL record.
Action:
Contact Oracle Support.
OGG-25389: Parsing of the WAL record failed. {0}
Parsing of the WAL record failed.
Action:
No action is needed.
OGG-25390: An unsupported operation is encountered. The WAL record could not be processed and is ignored.
An unsupported operation is encountered. The WAL record could not be processed and is ignored.
Action:
Please refer to Oracle GoldenGate documentation for operations that are supported with OGG Capture from PostgreSQL.
OGG-25391: Database is not identified in the logical replication system.
The server cannot identify the database in the logical replication system.
Action:
Contact Oracle GoldenGate Support.
OGG-25392: Trying to get the valid log record from the socket, but could not get it in Maxretries '{0}' count and so stopping the process.
Extract may have parsed unrecognized header or the header length is very small to process the record. It tries maximum number of times specified with the retry count option.
Action:
Correct the problem that caused the error, and then restart Extract. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25393: The metadata for table '{0}' does not exist in the database but the record(s) of the given table does exist in commit log. Extract is filtering its record(s).
The table metadata does not exist in the database but the records of the table does exist in commit log. Extract is filtering its record(s).
Action:
It is a warning. A user can ignore this or can create the corresponding missing table.
OGG-25394: Database error - severity:'{0}', state:'{1}' msg:'{2}'.
The database has thrown an error.
Action:
Contact Oracle GoldenGate support.
OGG-25395: The wildcarded catalog specification '{0}' is unsupported for the TABLE parameter in the Extract or Replicat parameter file.
The wildcarded catalog is not supported.
Action:
Remove the catalog part name from the Extract or Replicat parameter file and then retry.
OGG-25396: The wildcarded schema specification is missing for the TABLE parameter in the Extract or Replicat parameter file.
The wildcarded schema specification must be added for the qualified TABLE name in the Extract or Replicat parameter file.
Action:
Add the schema name as part of qualified TABLE name in the Extract or Replicat parameter file and then retry.
OGG-25397: The object id for table '{0}' not found.
It is a programming error.
Action:
Contact Oracle GoldenGate Support.
OGG-25398: Unexpected end of Copy Stream.
Unexpected end of copy stream.
Action:
Check the network connectivity between the source and target systems. Verify that the number of connections has not exceeded the operating system limitation. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25399: GGDataBufferGetHandle() returned with invalid handle or zero length: table name '{0}', column name '{1}', transaction id '{2}'.
The Vendor Access Module call interface returned an unexpected error to Extract when it tries to get the LOB handle.
Action:
Contact Oracle GoldenGate support.
OGG-25400: Parameter {0} is only compatible with an integrated or parallel integrated replicat.
The specified option is only valid in integrated Replicat configurations.
Action:
Remove the incompatible option from the Replicat parameter file.
OGG-25401: Option {0} is required for parameter ACDR.
The specified option is required for the ACDR parameter.
Action:
Add the missing option to the ACDR parameter.
OGG-25402: ACDR SITE_PRIORITY requires database/container name or '*'.
The specified option is required for the ACDR parameter.
Action:
Add the missing option to the ACDR parameter.
OGG-25403: Invalid container/database name "{0}" is specified for ACDR SITE_PRIORITY.
The container or database name specified for the ACDR SITE_PRIORITY is invalid.
Action:
Specify the correct site name.
OGG-25404: Invalid container/database name "{0}" is specified for ACDR SITE_PRIORITY. '*' can only be used as complete container/database name, i.e. matching all container/database names
Wildcard '*' is not allowed except as the complete name, matching all container/database names.
Action:
Use exact container or database name or wildcard '*' as the entire string/name.
OGG-25405: Site priority action missing - possible values are OVERWRITE and IGNORE
Site priority action is missing.
Action:
Provide site priority action - OVERWRITE or IGNORE.
OGG-25406: Site priority action {0} is invalid - possible values are OVERWRITE and IGNORE
Site priority action is invalid.
Action:
Provide site priority action - OVERWRITE or IGNORE.
OGG-25407: Site Priority unsupported for Oracle Version {0}
Site priority is unsupported for versions prior to Oracle Database 20c.
Action:
Upgrade to Oracle Database 20c.
OGG-25408: Site Priority set for all pdbs
All_pdbs specified for pdb name.
Action:
Informational - no action is necessary.
OGG-25500: Credential store backup is empty. Not restoring; removing invalid backup.
A Credential store file restore operation was requested with the current backup file reporting empty. The restoration operation was canceled with the Credential store file unaltered. Please check filesystem space availability.
Action:
Restore the Credential store from from a manual backup. Contact Oracle Support for help.
OGG-25501: A Credential store file restore operation failed to restore from backup. Error {0} : {1}
Restoring the Credential store backup to the Credential store file failed. Please check filesystem space availability and check that the Credential store file has write permissions set.
Action:
Remove unneeded files from the filesystem or extend the filesystem's capacity.
OGG-25502: The credential store file does not exist after the restore operation completed.
A Credential store file is expected but not found after having been restored from the backup. Please check filesystem space availability.
Action:
Remove unneeded files from the filesystem or extend the filesystem's capacity.
OGG-25503: The credential store file is reporting empty after the restore operation completed.
A Credential store file is reporting empty, a filesize of 0, after having been restored from the backup. Please check filesystem space availability.
Action:
Remove unneeded files from the filesystem or extend the filesystem's capacity.
OGG-25504: A credential store backup exists. Current backup operation has been canceled.
A Credential store backup was found while attempting to create a new backup file. A Credential store backup file will be present if a prior update operation to the Credential store file was unsuccessful.
Action:
If the current Credential store file is not empty and the store file and backup file are the same size, remove the backup file. If the current Credential store file is not empty and the backup file is empty, remove the backup file. If the current Credential store file is empty and the backup is not empty, replace the Credential file with the backup file. If the both current Credential store file and backup file are not empty but differ in size. Archive both files. Replace the Credential store file with the archived Credential store file. Resume if operation is restored and the registered users validated. Otherwise replace the Credential store file with the archived backup file. Resume if operation is restored and the registered users validated. Contact Oracle Support.
OGG-25505: Failed to create Credential store backup. Credential store file unaltered. Error {0} : {1}
Failed to create Credential store backup file. Please check filesystem space availability and check that the output directory for the Credential store backup has write permissions set.
Action:
Remove unneeded files from the filesystem or extend the filesystem's capacity.
OGG-25506: The Credential store backup reports empty after backup operation. Removing invalid backup file.
Creation of the backup file resulted in an empty backup file. The empty backup file was removed. Please check filesystem space availability.
Action:
Remove unneeded files from the filesystem or extend the filesystem's capacity.
OGG-25507: Failed to cleanup and remove the Credential store backup (Error Code: {0}).
Cleanup and removal of the backup file failed. Please check that filesystem has write permissions set.
Action:
Manually remove the backup file or Contact Oracle Support for help.
OGG-25510: The column index {0} is out of range.Error: {1}.
An internal logic error occurred in the VAM module in Extract.
Action:
Contact Oracle GoldenGate Support.
OGG-25511: The specified filter table {0} is not found in the database.
The specified filter table is not found in the database.
Action:
Specify the correct filter table name or create one using ADD CHECKPOINTTABLE.
OGG-25512: Using filter table {0} for bi-directional loop detection.
Extract to identify the Replicat transaction that has operated on the filter table.
Action:
None
OGG-25513: The Replica identity setting for table '{1}' is set to '{0}' which is not compatible to process the Extract parameters such as NOCOMPRESSUPDATES or NOCOMPRESSDELETES. Set the Replica identity setting to FULL using the ADD TRANDATA '{1}',ALLCOLS command.
The Replica identity setting for the table is either USING INDEX or DEFAULT, which is not compatible to process the Extract parameters such as NOCOMPRESSUPDATES or NOCOMPRESSDELETES.
Action:
Change the Replica identity setting for the given table to FULL using ADD TRANDATA with ALLCOLS command and re-initiate the DML in the source database.
OGG-25514: Replica identity setting for the processing table '{1}' is set to '{0}' which is not compatible to process Oracle GoldenGate Extract parameter such as UPDATERECORDFORMAT FULL/COMPACT or GETUPDATEBEFORES or GETBEFORECOLS.
Replica identity setting for the table is either USING INDEX or DEFAULT which is not compatible to process Oracle GoldenGate Extract parameter such as UPDATERECORDFORMAT FULL/COMPACT or GETUPDATEBEFORES or GETBEFORECOLS.
Action:
Change the replica identity setting to FULL thorough GGSCI ADD TRANDATA command and re-initiate the DML again in the source database.
OGG-25515: The replication table '{2}' has '{0}' columns that do not match with the total columns '{1}' that exist in the VAM metadata.
Possible cause could be DDL changes for the given table.
Action:
Restarting the capture process may resolve this problem. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-25516: Oracle GoldenGate capture using LIBPQ client library version as {0} which is incompatible with the connected PostgreSQL server version {1} for streaming the log record. The LIBPQ client library version must be the same as or bigger than, that of the connected PostgreSQL server library version.
The LIBPQ client library version is not compatible with the connected PostgreSQL server library version. The LIBPQ client version must be the same as or bigger than, that of the connected PostgreSQL server library version.
Action:
Download the LIBPQ client library version which is same as or bigger than the PostgreSQL server version and point to the library path correctly, and then restart Extract.
OGG-25517: An issue in getting the max_replication_slots from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25518: The minimum replication slot must be 1 if there is one Extract capture session, otherwise depending upon the number of Extract capture sessions, the slot must be increased.
The max_replication_slots is not set to a minimum value in server configuration (postgresql.conf) file.
Action:
The max_replication_slots value must be set depending upon the number of Extract capture session. If there are 2 Extract capture sessions then max_replication_slots must be set to 2 or more.
OGG-25519: The minimum replication slot must be 1 if there is one Extract capture session, otherwise depending upon the number of Extract capture sessions, the slot must be increased.
The max_replication_slots is not set to a minimum value in server configuration (postgresql.conf) file.
Action:
The max_replication_slots value must be set depending upon the number of Extract capture session. If there are 2 Extract capture sessions then max_replication_slots must be set to 2 or more.
OGG-25520: An issue in getting the track_commit_timestamp from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25521: The track_commit_timestamp should be set to 'on' to get the timestamp for each of the record in the transaction.
The track_commit_timestamp is set to 'off' in the server configuration (postgresql.conf) file.
Action:
Set the track_commit_timestamp minimum value to 'on'.
OGG-25522: An issue in getting the wal_level from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25523: The wal_level must be set to 'logical' so that the write ahead log can be polled.
The wal_level is not set to 'logical' in the server configuration (postgresql.conf) file.
Action:
Set the wal_level to 'logical'.
OGG-25524: An issue in getting the ssl setting from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25525: The SSL connection is currently not supported.
The SSL connection is configured in server configuration (postgresql.conf) file.
Action:
Disable the SSL to continue replication.
OGG-25526: An issue in getting the wal_sender_timeout setting from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25527: An issue in getting the wal_receiver_status_interval setting from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25528: An issue in getting the server_encoding setting from the connected server: {0}
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25529: An issue in getting the lc_collate setting from the connected server. [0]
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25530: Table {0} has a column {1} of type {2} with unsupported length {3}. Column data is truncated to maximum supported length(4000).
The length of bit/varbit column exceeded the maximum supported length of 4000. Column data gets truncated if its length is more than the maximum supported length.
Action:
To avoid truncation, the length of bit/varbit columns must be less than or equal to maximum supported length(4000).
OGG-25531: Job table "{0}" does not exist.
Job table for heartbeat does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the job table.
OGG-25532: Job table "{0}" dropped.
Job table for heartbeat dropped. Informational only.
Action:
None
OGG-25533: Job procedure "{0}" does not exist.
Job procedure for heartbeat history table does not exist.
Action:
Use the command 'ADD HEARTBEATTABLE' to add the heartbeat job procedure.
OGG-25534: Job procedure "{0}" dropped.
Job procedure for heartbeat table dropped. Informational only.
Action:
None
OGG-25535: Successfully created heartbeat job table "{0}".
Heartbeat job table has been created. Information only.
Action:
None
OGG-25536: Supplemental logging for heartbeat table "{0}" is not enabled.
The supplemental logging for the heartbeat table is not enabled.
Action:
Follow the PostgreSQL database error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25537: 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.
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-25538: Successfully populated heartbeat job table.
Heartbeat job table populated. Informational only.
Action:
None
OGG-25539: Successfully created heartbeat job procedure "{0}".
Heartbeat job table has been created. Informational only.
Action:
None
OGG-25540: Positioning to replication slot restart location '{0}'.
This is an informational message..
Action:
No action required.
OGG-25541: GETTRUNCATES is not valid with OGG EXTRACT on PostgreSQL database version {0}.{1}. PostgreSQL database supports capture of TRUNCATE operations starting from version 11.
GETTRUNCATES can not be supported. The support for capturing TRUNCATE operations is available in PostgreSQL 11 and later versions.
Action:
You can either remove GETTRUNCATES from the EXTRACT param file to silently ignore the truncate operations, or contact Oracle Support for help.
OGG-25542: Error in retrieving the database version information.
Error in retrieving the database version information.
Action:
None
OGG-25543: An error occurred while converting the data of the bit/bit varying column {1} of the table {0}.
An error occurred while converting the data of the bit/bit varying column during initial load.
Action:
None
OGG-25545: Extract tried {3,number,0} times to reserve the replication slot '{0}' in database '{1}', but failed. A wal sender process is actively using it. Database reported {2}. Terminate the wal sender process and restart extract.
Extract could not reserve the replication slot.
Action:
User can perform one of the following steps and then restart Extract: 1)Increase the wal_sender_timeout values in postgresql.conf file. 2)Terminate the process id reported in the error message, which is using the given slot.
OGG-25546: The wal_sender_timeout parameter in postgres.conf is disabled. This will prevent the termination of inactive wal sender processes. Extract will use the default wal_sender_timeout of {0,number,0} seconds when attempting to reserve a replication slot.
The wal_sender_timeout parameter is not enabled in postgresql.conf file.
Action:
Enable the wal_sender_timeout parameter in postgresql.conf file.
OGG-25547: An error occurred while getting the HostName and/or the PortNumber information from the ODBC configuration file.
Could not retrieve the host name and/or port number details from the ODBC configuration file.
Action:
Contact Oracle Support.
OGG-25549: Replica identity setting for the processing table {0} is set to 'DEFAULT' which is not compatible to process DELETE operation.
Replica identity setting for the table is set to DEFAULT, which is not compatible to process DELETE operation.
Action:
Disable the reported table name from the Extract parameter file and then restart Extract process.
OGG-25550: Error setting client encoding to {0}: {1}
There could be a permission issue for the connected user.
Action:
Follow the PostgreSQL error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-25551: Failed to parse the {0} transaction record. Could not parse the 'TXN_ID' token in the received WAL record with LSN '{1}'.
An issue occurred in parsing the Txn ID from the WAL record at corresponding LSN.
Action:
Please evaluate the WAL record at the given LSN and check if it is supported. Contact Oracle GoldenGate support, if required.
OGG-25552: Failed to parse the COMMIT transaction record with transaction ID {1}. Could not parse the 'COMMIT_TIMESTAMP' token in the received WAL record with LSN '{0}'.
An issue occurred in parsing the Txn COMMIT_TIMESTAMP from the WAL record at corresponding LSN.
Action:
Please evaluate the WAL record at the given LSN and check if it is supported. Contact Oracle GoldenGate support, if required.
OGG-25553: Failed to parse the Table record. Could not parse the '{1}' token in the received WAL record with LSN '{0}'.
An issue occurred in parsing the SchemaName/ObjectName from the WAL record at corresponding LSN.
Action:
Please evaluate the WAL record at the given LSN and check if it is supported. Contact Oracle GoldenGate support, if required.
OGG-25554: Failed to parse the record for the Table '{0}.{1}'. Could not parse the 'OPERATION_TYPE' token in the received WAL record with LSN '{2}'.
An issue occurred in parsing the Operation Type from the WAL record at corresponding LSN.
Action:
Please evaluate the WAL record at the given LSN and check if it is supported. Contact Oracle GoldenGate support, if required.
OGG-25555: An unsupported operation '{0}' is encountered for the table '{1}.{2}' and will be ignored. Unsupported operation type is found in the received WAL record with LSN '{3}'. Please refer to Oracle GoldenGate documentation for the supported operation types.
The operation type of the WAL record with the corresponding LSN is not supported.
Action:
Please refer to Oracle GoldenGate documentation for the supported operation types. Contact Oracle GoldenGate support, if required.
OGG-25556: Failed to parse the column information in the {0} record for the table '{1}.{2}'. Could not parse the '{4}' token in the '{5}' image section in the received WAL record with LSN '{3}'.
An issue occurred in parsing the Column Information from the WAL record at corresponding LSN.
Action:
Please evaluate the WAL record at the given LSN and check if it is supported. Contact Oracle GoldenGate support, if required.
OGG-25557: Failed to parse the {0} operation of the table '{1}.{2}'. Could not parse the '{4}' token of the column '{5}' in the {6} image section in the received WAL record with LSN '{3}'.
An issue occurred in parsing the Column Information from the WAL record at corresponding LSN.
Action:
Please evaluate the WAL record at the given LSN and check if it is supported. Contact Oracle GoldenGate support, if required.
OGG-25558: Table {0} has an identity always column {1} which is not supported by PostgreSQL Replicat. The user must change the identity always column to identity default to continue the replication.
Replicat found a table with an identity always column that is not supported for PostgreSQL.
Action:
One of the following action user can take - 1. Remove the table which has identity always column from the Oracle GoldenGate configuration. 2. Change the table which has identity always column to identity default.
OGG-25559: Column being added already exists in table.
The LOGBSN columns already exist in the heartbeat table.
Action:
It is an informational message only.
OGG-25560: Oracle GoldenGate capture connected to PostgreSQL server library version {1} using LIBPQ client library version {0} and streaming protocol version {2}.
Informational only.
Action:
None
OGG-25561: The DDLTABLE value in the GLOBALS file cannot be longer than {0} characters.
The process cannot use a DDL table name that is greater than the maximum DB2 z/OS table name length.
Action:
Use a remote DDL table name that is not longer than the maximum length of a DB2 z/OS table name.
OGG-25562: The Extract for DB2 zOS is configured to use the DDL history table {0}.
The process has been configured to use a DDL history table to track and use DDL changes when they are detected in the log records.
Action:
Use a remote DDL table name to track DDL changes in the Extract.
OGG-25565: Unrecognized Parameter {0}. expected {1}
Invalid input for dblogin. Either Sourcedb or Useridalias(for MSA db login ) is missing with dblogin command. dblogin sourcedb ... MSA: dblogin useridalias ...
Action:
Specify a valid dblogin command.
OGG-25566: ODBC Connection Creation failed.
ODBC Connection creation failed.
Action:
None
OGG-25575: JT400 method call for function {0} failed. Subfunction failed: {1}. Check message log for more info.
JT400 method call for function {0} failed.\nSubfunction failed: {1}.\n Check message log for more info.
Action:
Check the error message. Verify that DB2 for i Java libraries are present in the install location. Contact Oracle Support if you cannot resolve the issue.
OGG-25576: GLOBALS file GGSCHEMA parameter must be specified.
Specify GGSCHEMA in the GLOBALS file for the DB2 for i Remote capture build.
Action:
Edit the GLOBALS file and supply the GGSCHEMA.
OGG-25577: JVM failed to load for DB2i remote capture build
JVM failed to load for DB2 for i remote capture build.
Action:
Check the previous error messages. Verify that DB2 for i Java libraries are present in the install location. Contact Oracle Support if you cannot resolve the issue.
OGG-25578: JVM created successfully
Successfully created JVM. Informational only.
Action:
None
OGG-25601: Unable to open wallet at location '{0}'.
The Oracle wallet used to store certificate(s) cannot be opened.
Action:
Verify that the directory exists and has appropriate file permissions on the wallet file.
OGG-25602: Unable to save the wallet at location '{0}'.
There was a problem saving the Oracle wallet to disk.
Action:
Verify that the directory exists and has appropriate file permissions on the wallet file.
OGG-25603: Unable to add content to the wallet at location '{0}'.
There was a problem adding information to the Oracle wallet at the specified location.
Action:
Verify that the directory exists and has appropriate file permissions on the wallet file.
OGG-25604: Unable to retrieve contents from the wallet at location '{0}'.
Unable to retrieve contents from the Oracle wallet file.
Action:
Check file permissions on the wallet file.
OGG-25605: No information found in the Oracle wallet.
The Oracle wallet has no entries for the specified element. Informational only.
Action:
None
OGG-25606: Certificate and Private Key do not match in the Oracle Wallet.
Certificate could not be added to the Oracle wallet as the private key provided or previously stored in the wallet does not match.
Action:
Add a matching private key to the Oracle wallet.
OGG-25607: Certificate has been successfully added to the Oracle wallet.
Successfully added a certificate to the Oracle wallet. Informational only.
Action:
None
OGG-25608: Certificate has been successfully updated in the Oracle wallet.
Oracle wallet has been successfully updated. Informational only.
Action:
None
OGG-25609: Certificate has been successfully deleted from the Oracle wallet.
Successfully removed a certificate from Oracle wallet. Informational only.
Action:
None
OGG-25610: Unable to delete content from the wallet at location '{0}'.
There was a problem deleting information from the Oracle wallet at the specified location.
Action:
Verify that the directory exists and has appropriate file permissions on the wallet file.
OGG-25612: Invalid value of query parameter '{0}'.
Certificate data in the request is missing begin or end certificate token.
Action:
Verify that the certificate data is included in the request.
OGG-25613: Successfully added authorization profile '{0}' in deployment '{1}'
Successfully added the authorization profile in the determined deployment.
Action:
None
OGG-25614: The authorization profile '{0}' has been deleted from the deployment '{1}'
Successfully deleted authorization profile in deployment.
Action:
None
OGG-25615: The authorization profile '{0}' in deployment '{1}' could not be deleted because it is currently enabled or is undeletable.
An authorization profile that is currently set or is undeletable in the specified deployment tried to be deleted.
Action:
Disable the profile profile before trying to delete it, or check if it is undeletable.
OGG-25616: Could not access authorization profiles from deployment '{0}'
The profile list could not be found or values could not be properly loaded.
Action:
Check that the deployment directory is correct and authorization profile formatting is correct.
OGG-25617: Attempted to use external Identity Provider authorization functionality but not enabled
Attempted to use functionality or access an endpoint that is only enabled for external Identity Provider authorization, but an Identity Provider profile is not enabled.
Action:
Enable an Identity Provider authorization profile to use this functionality.
OGG-25618: Invalid or incorrect Auth Code received
The Authorization Token received is invalid or incorrect and could not be processed.
Action:
Check logs for more information.
OGG-25619: Test connection failed for profile '{0}' in deployment '{1}'
Connection and configuration tests failed for the profile.
Action:
Check response for failing test.
OGG-25620: The authorization profile file or directory '{0}' do not exist or their content is not properly formed.
File does not exist or the content is not properly formed.
Action:
Check if the file exists, that it contains only JSON content and that the IDP profile section exists.
OGG-25621: Error loading enabled profile '{0}' into service.
Could not load profile into service.
Action:
Check other messages or logs for more information.
OGG-25622: Test connection passed for profile '{0}' in deployment '{1}'.
Connection and configuration test passed.
Action:
None
OGG-25623: Values in configuration file cannot be loaded into service for profile '{0}' from deployment '{1}'.
Values are incorrectly formatted or invalid.
Action:
Check that configuration values are correctly formatted.
OGG-25624: Could not get Application information from Identity Provider for profile '{0}' in deployment '{1}'.
Request to Identity Provider for Application Information could not be completed.
Action:
Check logs for further information.
OGG-25625: Returned Identity Provider Application does not match Application described by profile '{0}' from deployment '{1}'.
Identity Provider returned application(s) that did not match requested application.
Action:
Check profile and/or Identity Provider application.
OGG-25626: No matching Application was returned by Identity Provider using values from profile '{0}' from deployment '{1}'.
No matching Application was returned by Identity Provider when filtered by Client ID.
Action:
Check that Application exists in the Identity Provider and that it is queriable.
OGG-25627: Unknown error occurred when performing a connection and configuration test on the profile '{0}' in deployment '{1}'.
Unknown Error.
Action:
Check logs.
OGG-25628: Could not complete authorization profile configuration. Stopping Service.
Error occurred while configuring authorization profile.
Action:
Check logs for specific error.
OGG-25629: Profile creation request for '{0}' in deployment '{1}' does not contain minimum fields.
The profile creation request did not contain minimum fields of client id and secret, type, tenant discovery uri, and group to role mapping.
Action:
Add missing fields.
OGG-25630: Profile alter request for '{0}' in deployment '{1}' contains unalterable fields or invalid values
The alter request contains fields that cannot be altered like name or type.
Action:
Remove unalterable fields from request.
OGG-25631: Request to Identity Provider was rejected - invalid user credentials.
Request to Identity Provider failed due to incorrect username or password.
Action:
Check the username or password.
OGG-25632: The previous way of implicit authentication method definition is deprecated
The previous method of specifying domain and alias or implicit certificate authentication is deprecated.
Action:
Explicitly specify the authentication method in the distribution path endpoint definition.
OGG-25633: Request to Identity Provider was rejected - invalid client credentials.
Connection request to Identity Provider was unauthorized due to incorrect client id or client secret.
Action:
Check that the authorization profiles's client id or client secret are valid for the Identity Provider.
OGG-25634: No authorization code was present in request. Returned error: {1}
No Authorization code was present in request.
Action:
Check error from Identity Provider attached in message.
OGG-25635: User cannot be granted access.
User does not have necessary groups.
Action:
Check logs for issue.
OGG-25700: CACHEMGR: File {0} is still open
An open file was found during cleanup.
Action:
None
OGG-25701: The file caching thread was shutdown. Thread ID: {0,number,0}.
The filecaching thread was shutdown.
Action:
None
OGG-25702: Bounded recovery is not running.
Informational only.
Action:
None
OGG-25703: Invalid time value {0}
The specified time value is invalid.
Action:
Specify a valid time value in the command.
OGG-25704: Object pool {0} {1}: {2} active items, {3} deferred deleted {4}
Informative message during BR on the items in the persisted object pool.
Action:
None
OGG-25705: Bounded Recovery is not used. Normal recovery is only used due to mining DB version changed.
When mining DB versions change between IE runs, BR data must be discarded during startup because the persisted PDBUID may not match the one from the current run. Extract will use Normal Recovery for the current run and then turn on Bounded Recovery after the recovery is complete.
Action:
None
OGG-25706: Bounded Recovery is not used. Normal recovery is only used due to BRRESET parameter.
BRRESET parameter is set. Extract will use Normal Recovery for the current run and then turn on Bounded Recovery after the recovery is complete.
Action:
None
OGG-25707: Bounded Recovery is not used. Normal recovery is only used due to BRDIR changed.
BRDIR changed. Extract will use Normal Recovery for the current run and then turn on Bounded Recovery after the recovery is complete.
Action:
None
OGG-25708: Bounded Recovery error: {0,number,0}.
Fatal error encountered during Bounded Recovery.
Action:
Contact Oracle support.
OGG-25709: CACHEMGR: object co: 0x{0} co_uid: 0x{1} already persisted.
Attempted double persist of an object already persisted.
Action:
Contact Oracle Support.
OGG-25710: Lock free stack: full, items: 0x{0}.
The lock free stack is full.
Action:
Contact Oracle Support.
OGG-25711: Object pool {0} {1}: {2} stale objects deleted.
Informative only.
Action:
None
OGG-25712: CACHEMGR: Cannot commit for use virtual memory addr: 0x{0}, len 0x{1} Error code {2,number,0} ({3})
Failed to commit for using virtual memory for CACHEMGR.
Action:
Contact Oracle Support.
OGG-25713: CACHEMGR: Cannot uncommit usage on virtual memory addr: 0x{0}, len: 0x{1} Error code {2,number,0} ({3})
Failed to uncommit using virtual memory for CACHEMGR.
Action:
Contact Oracle Support.
OGG-25714: CACHEMGR: CACHESIZE parameter {0} can not exceed the CONTAINER MEM_LIMIT {1}
CACHEMGR CACHESIZE parameter can not exceed the current setting of CONTAINER MEM_LIMIT parameter.
Action:
Reduce the setting on CACHEMGR CACHESIZE parameter and verify that CONTAINER MEM_LIMIT is set appropriately.
OGG-25715: CACHEMGR: No Swap environment and parameter CONTAINER MEM_LIMIT not set
Parameter CONTAINER MEM_LIMIT is not set in an environment without swap space.
Action:
Set CONTAINER MEM_LIMIT and adjust the CACHEMGR CACHESIZE parameter to a value that is either equal to or lower than it.
OGG-25716: CACHEMGR: No Swap environment and parameter CACHESIZE not set
Parameter CACHESIZE is not set in an environment without swap space.
Action:
Set CACHEMGR CACHESIZE parameter to a value lower than or equal to CONTAINER MEM_LIMIT.
OGG-25717: CACHEMGR: parameter CONTAINER MEM_LIMIT {0} set is exceeding physical ram {1}
Parameter CONTAINER MEM_LIMIT is exceeding physical ram on the machine.
Action:
Reduce CONTAINER MEM_LIMIT to a value lower than the physical ram on the machine.
OGG-25718: BOUNDED RECOVERY: Current br mmap grain {0,number,0} is not matching the value in BR Checkpoint file {1,number,0}
Parameter CONTAINER MEM_LIMIT limit changed, while Bounded Recovery was performed using a different mmap granularity.
Action:
No action is required, as the existing BR files will not be used.
OGG-25719: BOUNDED RECOVERY: Current br file grain {0,number,0} is not matching the value in BR Checkpoint file {1,number,0}
Parameter CONTAINER MEM_LIMIT limit changed, while Bounded Recovery was performed using a different file granularity.
Action:
No action is required, as the existing BR files will not be used.
OGG-25720: No-swap system detected
Informative only.
Action:
None
OGG-25721: Memory limit set to {0}
Informative only.
Action:
None
OGG-25800: A length of {0} was returned while querying value {1} for column {2} which is out of range of 1 - {3}. Current log position is {4}
A logic error has occurred while querying values from the DB2 system tables.
Action:
Contact Oracle support.
OGG-25801: Could not map Oracle native JSON column {0} to non-native JSON target column
The target column is not using the Oracle native JSON type.
Action:
Remove the table from the Oracle GoldenGate configuration or remove BINARY_JSON_FORMAT from Extract parameter file.
OGG-25802: Unexpectedly ran out of JSON descriptors while applying JSON column
Replicat ran out of JSON descriptors.
Action:
Contact Oracle support
OGG-25803: Database error ({0}). Heartbeat table is already upgraded.
Upgrade not needed as heartbeattable is already upgraded.
Action:
No action is required.
OGG-25804: Database error ({0}). Heartbeat History table is already upgraded.
Upgrade not needed as heartbeat history table is already upgraded.
Action:
No action is required.
OGG-25805: Could not find JSON column {0} during lobrow processing.
Missing expected JSON column in lobrow.
Action:
Contact Oracle support
OGG-25806: Could not find LOBROW object containing JSON column {0}.
Missing expected lobrow object containing JSON column.
Action:
Contact Oracle support
OGG-25807: Failed to allocate Json descriptor
Failed to allocate JSON descriptor.
Action:
Contact Oracle support
OGG-25808: Failed to load Json descriptor
Failed to open JSON descriptor.
Action:
Contact Oracle support
OGG-25809: Failed to convert Json column
Failed to convert JSON column from text and binary format.
Action:
Contact Oracle support
OGG-25810: Failed to open OraStream for Json conversion
Failed to open OraStream to do JSON conversion.
Action:
Contact Oracle support
OGG-25811: Parameter BINARY_JSON_FORMAT is not supported during initial load. Extract will ignore the parameter.
Extract is trying to fetch JSON column with BINARY_JSON_FORMAT enabled during initial load, which is not supported. This parameter is ignored.
Action:
Take out BINARY_JSON_FORMAT parameter.
OGG-25812: Parameter BINARY_JSON_FORMAT is not supported with FETCHCOLS/FETCHMODCOLS on Json columns on table {0}. Extract will ignore the parameter and keep Json in text format.
Extract is trying to fetch JSON column with BINARY_JSON_FORMAT enabled. This parameter is ignored.
Action:
Take out BINARY_JSON_FORMAT parameter.
OGG-25814: Parameter BINARY_JSON_FORMAT is not supported when OUTPUTFORMAT is set to text, SQL, or XML formats. Extract will ignore the parameter.
Output trail is using text encoding so the parameter BINARY_JSON_FORMAT is ignored.
Action:
Take out BINARY_JSON_FORMAT parameter.
OGG-25815: Partial LOB operation to Oracle native JSON column {0} is not supported.
Partial LOB operation to Oracle native JSON is not supported.
Action:
In Extract use FETCHPARTIALLOB option for TRANLOGOPTIONS or FETCHMODCOLS/FETCHCOLS option for the column that will be mapped to JSON in the target.
OGG-25816: Cannot convert Oracle native JSON column {0} to text format.
Oracle native JSON column cannot be evaluated as text.
Action:
Take out BINARY_JSON_FORMAT parameter from Extract configuration.
OGG-25817: Cannot use Oracle native JSON column {0} as argument to column function {1}.
Oracle native JSON column cannot be evaluated as text.
Action:
Take out BINARY_JSON_FORMAT parameter from Extract configuration.
OGG-25820: Error while trying to encrypt using Oracle Cloud Infrastructure Key Management service using encryption profile '{0}'.
Failed to encrypt with Oracle Cloud Infrastructure Key Management service.
Action:
Look for additional error messages.
OGG-25821: Error while trying to decrypt using Oracle Cloud Infrastructure Key Management service using encryption profile '{0}'.
Failed to decrypt with Oracle Cloud Infrastructure Key Management service.
Action:
Look for additional error messages.
OGG-25822: Error while trying to decode the API Signing key.
Invalid API Signing key, must be Base64 encoded.
Action:
Make sure that the encryption profile has a valid Signing Key.
OGG-25823: Error while trying to sign the request. Oracle Security Toolkit encountered error: {0}.
Invalid API signing key.
Action:
Make sure that the encryption profile has a valid API Signing Key.
OGG-25824: Error while trying to hash the payload.
Failed to hash using the Oracle Security Toolkit.
Action:
Contact Oracle support.
OGG-25826: Unexpected value for KMS type.
Unexpected value for KMS type.
Action:
Make sure that the encryption profile has a valid KMS type.
OGG-25827: Changing the type of an existing profile is not allowed.
Attempt to modify the type of an encryption profile.
Action:
Don not change the type of an existing profile.
OGG-25828: Failed to validate the Signing Key, expected RSA pattern.
The given key does not match the expected RSA pattern.
Action:
Specify a valid RSA KEY.
OGG-25829: Regular expression error while trying to validate the API signing key.
Exception raised while trying to complete a regular expression operation.
Action:
Contact Oracle support.
OGG-25830: OCI HTTP request failed. Server replied 'UNAUTHORIZED'.
Unable to authorize against the Oracle Cloud Infrastructure.
Action:
Make sure that the Oracle Cloud credentials are valid.
OGG-25831: OCI HTTP request failed. Server replied: Not Found
The requested resource does not exist.
Action:
Specify a valid resource.
OGG-25832: OCI HTTP request failed. Network error: {0}.
Unable to connect to the Oracle Cloud Infrastructure.
Action:
Check your network settings.
OGG-25833: OCI Server replied with an invalid HTTP code: {0} - {1}
Oracle Cloud Infrastructure replied with an unexpected HTTP code.
Action:
Look at the description of the Oracle Cloud Infrastructure error code for more details.
OGG-25834: Could not complete HTTP request. Reason: {0}.
Could not complete HTTP request.
Action:
Look at the response reason for more details.
OGG-25835: OCI HTTP request failed. Invalid Argument: {0}.
Could not complete HTTP request.
Action:
Contact Oracle Support.
OGG-25836: HTTP request to the Oracle Cloud Infrastructure failed. Timeout: {0}.
Timeout while trying to connect to the Oracle Cloud Infrastructure.
Action:
Check if the Oracle Cloud Infrastructure can be reached from the source server.
OGG-25837: Master encryption key not found in the KMS vault.
The given master encryption key does not exist in the KMS vault.
Action:
Make sure that the master encryption key name OCID is valid.
OGG-25838: Oracle Cloud Infrastructure replied with code: {0} - {1}.
Oracle Cloud Infrastructure replied with an error code.
Action:
Look at the Oracle Cloud Infrastructure error code for more details.
OGG-25839: HTTP request to the Oracle Cloud Infrastructure failed. Server replied 'BAD REQUEST'.
Request was not constructed correctly.
Action:
Look at the Oracle Cloud Infrastructure error code for more details.
OGG-25840: HTTP request to the Oracle Cloud Infrastructure failed. Server replied 'CONFLICT'.
Oracle Cloud Infrastructure replied 'CONFLICT'.
Action:
Look at the Oracle Cloud Infrastructure code message for more details.
OGG-25841: Validation for encryption profile {0} succeeded.
Encryption Profile validation succeeded.
Action:
None
OGG-25842: Validation for encryption profile {0} failed.
Encryption Profile validation failed.
Action:
Look for additional error messages for more details.
OGG-25843: Master encryption key is in an invalid state.
The given master encryption key is in an invalid state.
Action:
Look at the Oracle Cloud Infrastructure error code for more details.
OGG-25844: Changing value for property '{0}' is not allowed.
Some properties can not be changed after the profile is created.
Action:
Please take a look at the documentation to get the list of allowed properties that can be changed.
OGG-25845: Decrypted text does not match original text.
Encrypt and decrypt functions did not generate the same original string.
Action:
Contact Oracle support.
OGG-25846: Regular expression exception raised: '{0}'
An exception was raised while using regex.
Action:
Contact Oracle support.
OGG-25847: Required property '{0}' is missing from the request.
A required property is missing from the request.
Action:
Please take a look at the documentation to get the list of required properties.
OGG-25848: Invalid property '{0}' for profile type '{1}'.
Invalid property found in the request.
Action:
Please take a look at the documentation related to encryption profiles.
OGG-25849: Encryption Profile {0} does not exist.
The given encryption profile does not exist.
Action:
Use a valid encryption profile.
OGG-25850: Make sure the OKV endpoint software is installed on the system.
Failed to initialize the OKV context.
Action:
Register an endpoint in the Oracle Key Vault and install the endpoint software. Specify the location of the OKV endpoint software installation in the encryption profile.
OGG-25851: Using encryption profile '{0}'.
Using encryption profile.
Action:
None
OGG-25852: KMS type '{0}' in trail file does not match type '{1}' in the encryption profile.
KMS type mismatch between trail file and encryption profile.
Action:
Verify that the correct encryption profile is being used.
OGG-25900: The maximum count of {0} entries was exceeded in the Extract or Replicat configuration file for parameter {1}.
Too many entries for the given parameter in the Extract or Replicat configuration file.
Action:
Remove some entries for the parameter in the Extract or Replicat configuration file.
OGG-25999: Running Extract in classic mode is no longer supported. Switch to running Extract in Integrated mode.
Classic Extract is no longer supported.
Action:
Run Extract in Integrated mode.
OGG-26000: Key columns are different between source and target in mapping for table {0}.
The set of key columns is different in the source and target tables.
Action:
None
OGG-26001: Update on table {0} at (Seq#: {1,number,0}, RBA: {2,number,0}) is a primary key update on target but not in source.
This update changes columns that are keys in the target table but not in the source table.
Action:
Ensure that this update is processed by Integrated Replicat or Parallel Replicat.
OGG-26002: Schema: "{0}" is blocked.
This schema is not allowed to issue SCHEMATRANDATA.
Action:
Avoid applying ADD SCHEMATRANDATA on this schema.
OGG-26003: Index {1} not found for ddl history table {0}. Please run ddl_delete_dups.sh to rectify.
An older version of the ddl history table without a unique index was encountered.
Action:
Run the ddl_delete_dups.sh to ensure that there are no duplicate records and add the unique index.
OGG-26004: Heartbeat functionality requires the GGSCHEMA parameter to be set to a valid database schema. Add the GGSCHEMA parameter and valid database schema to the GLOBALS file.
GGSCHEMA must be included in the GLOBALS file to enable supplemental logging for HEARTBEATTABLE.
Action:
Edit the GLOBALS file and specify GGSCHEMA with a valid database schema.
OGG-26005: The specified HEARTBEATTABLE schema name '{0}' in the GLOBALS file does not exist in the database or you do not have the permission to use it. Update the GLOBALS file to specify a valid database schema for HEARTBEATTABLE or create the schema in the database and assign the correct permissions to use it.
The HEARTBEATTABLE schema 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 HEARTBEATTABLE schema in the database with proper permissions for the Oracle GoldenGate database user.
OGG-26006: Heartbeat functionality requires the HEARTBEATTABLE parameter to include a valid database schema when GGSCHEMA is not specified. Update the GLOBALS file to specify GGSCHEMA or a fully-qualified HEARTBEATTABLE name.
HEARTBEATTABLE parameter must include a valid database schema in the GLOBALS file when GGSCHEMA is not specified.
Action:
Update the GLOBALS file to specify GGSCHEMA or a fully-qualified HEARTBEATTABLE name.
OGG-26007: Heartbeat functionality requires the GLOBALS file GGSCHEMA parameter set to a valid database schema or the HEARTBEATTABLE parameter set to a valid fully-qualified table name. Edit the GLOBALS file to specify GGSCHEMA or a fully-qualified HEARTBEATTABLE name.
GLOBALS must include either GGSCHEMA or a fully-qualified HEARTBEATTABLE name.
Action:
Edit the GLOBALS file to specify GGSCHEMA or a fully-qualified HEARTBEATTABLE name.
OGG-26008: An issue found with ODBC configuration. Please make sure to connect to PostgreSQL and to set the InstallDir attribute in the ODBCINI file to the directory where Oracle GoldenGate for PostgreSQL was installed.
Either the connection is not established to a PostgreSQL database or the InstallDir attribute in ODBCINI file is not set to the directory where Oracle GoldenGate for PostgreSQL was installed.
Action:
Make sure to connect to PostgreSQL database and to set the InstallDir attribute in the ODBCINI file to the directory where Oracle GoldenGate for PostgreSQL was installed.
OGG-26009: Oracle GoldenGate Capture from PostgreSQL does not support the IntervalStyle '{0}'.
Unsupported IntervalStyle is configured on the PostgreSQL database.
Action:
Set the IntervalStyle configuration parameter in the postgresql.conf file to one of the supported variants. Please refer to the Oracle GoldenGate documentation for details on supported IntervalStyle variants.
OGG-26010: Table '{0}' has a column '{1}' with unsupported interval type '{2}'.
The interval type of the column is not supported.
Action:
Please check the Oracle GoldenGate documentation for the supported interval types.
OGG-26011: An error occurred while formatting the {2} interval data '{3}' of column '{1}' in table '{0}'.
An error occurred while formatting the data of the interval column.
Action:
Contact Oracle Support.
OGG-26012: Cannot convert the interval data '{2}' of column '{1}' in table '{0}' to the Oracle GoldenGate internal format.
A conversion error occurred while processing the data of the interval column.
Action:
Contact Oracle Support.
OGG-26013: An issue found while getting the intervalstyle setting from the connected server. {0}
There could be a permission issue for the connected user.
Action:
Follow the postgresql error message to resolve the issue. Contact Oracle GoldenGate support, if required.
OGG-26014: Cannot capture mixed sign interval data '{2}' of column '{1}' in table '{0}'. Use 'DBOPTIONS ALLOWNONSTANDARDINTERVALDATA' to capture the mixed signed interval data as character string.
Capturing mixed sign interval data is not supported with this OGG version.
Action:
Use 'DBOPTIONS ALLOWNONSTANDARDINTERVALDATA' to capture the mixed signed interval data as character string.
OGG-26015: Target column '{1}' does not support non-standard interval data. Map the source column '{0}' to a char/binary column on the target database.
Applying non-standard interval data onto a target interval type column is not supported with this OGG version.
Action:
Map the source interval column containing non-standard interval data to a target char/binary column.
OGG-26016: Cannot capture interval data '{2}' of column '{1}' in table '{0}' due to its unsupported length. Use 'DBOPTIONS ALLOWNONSTANDARDINTERVALDATA' to capture the interval data as character string.
The length of the internally formatted interval data exceeds the supported length.
Action:
Use 'DBOPTIONS ALLOWNONSTANDARDINTERVALDATA' to capture the interval data as character string.
OGG-26017: RESOLVECONFLICT or HANDLECOLLISIONS is not supported when the target table is enabled for Automatic Conflict Detection and Resolution
The target table has been configured with Automatic Conflict Detection and Resolution and is incompatible with RESOLVECONFLICT or HANDLECOLLISIONS mapping options.
Action:
Either remove Automatic Conflict Detection and Resolution on the target object or the conflicting RESOLVECONFLICT or HANDLECOLLISIONS mapping options.
OGG-26018: DIAGNOSTIC: {0}
The local diagnostic is in progress and diagnostic information will be displayed in the report using this message.
Action:
No action is needed. A development engineer is replaying customer logs. This message will only be displayed during a diagnostic Extract run.
OGG-26019: The current log record is: {0}
An error occurred when processing a log record.
Action:
Contact Oracle support if you are unable to resolve the issue.
OGG-26020: zOS DB2 Statistics: {0}
The zOS DB2 Extract is ending and DB2 statistics will be displayed in the Extract report file.
Action:
No action is needed.
OGG-26023: OCI Error {1} (status = {0,number,0}), Check privilege for dictionary tables <{2}>
An error occurred in OCI.
Action:
Resolve the problem by checking privileges for dictionary tables listed in this message. If you cannot resolve the problem, contact Oracle Support.
OGG-26024: ALLOWNULLABLEKEYS should not be used with Integrated Replicat.
ALLOWNULLABLEKEY allows nullable key columns. Nullable keys may not identify unique rows.
Action:
It is advised not to use ALLOWNULLABLEKEYS parameter in the Replicat.
OGG-26025: Database Unique Name: {0}
Report DB unique name.
Action:
None
OGG-26026: The DbUniqueName token is not available in the trail header for Heterogeneous databases. DBUNIQUENAME will be treated as a synonym of DBNAME for this source.
Heterogeneous Databases do not provide a unique database name.
Action:
No action needs to be taken.
OGG-26027: The DbUniqueName token is not available in the source trail header. DBUNIQUENAME will be treated as a synonym of DBNAME.
The source trail was written by an OGG processes that does not support the DbUniqueName token.
Action:
Upgrade source OGG deployment if you require the DbUniqueName trail header token.
OGG-26028: The Extract for DB2 zOS is using the difference between the DB2 ({0}) and the local Extract ({1}) timezone variance in microseconds ({2})
The remote DB2 subsystem may be in a different timezone than the Extract. The Extract is using the DB2 timezone variance to resolve timestamp differences between DB2 and local Extract timestamps.
Action:
None
OGG-26029: The PostgreSQL server LC_MONETARY setting of {0} is not supported.
The PostgreSQL server LC_MONETARY setting is not supported.
Action:
Please install the required additional language support and verify it using localectl list-locales.
OGG-26030: Heartbeat frequency adjusted from {0} seconds to {1} seconds. Frequency values are between 60 and 3600 seconds in 60 second increments, or in 3600 second increments above 3600.
Invalid input for repeat interval.
Action:
Specify a valid frequency.
OGG-26032: Invalid heartbeat retention time {0} days entered. Valid values are from {1} to {2} days.
Invalid input for retention_time.
Action:
Specify a valid retention_time within valid range.
OGG-26034: Invalid heartbeat purge frequency {0} days entered. Valid values are from {1} to {2} days.
Invalid input for purge frequency.
Action:
Specify purge frequency within valid range.
OGG-27999: Column Index {0}, Column name {2} in Table {1} is not nullable. A null data is seen for not nullable column in operation {3} at log sequence number {4}.
A null value was passed to the VAM API by the VAM module for a column whose metadata marked it as not nullable.
Action:
Contact Oracle Support or, if you are working with an Oracle GoldenGate developer, contact that person.
OGG-30000: A critical certificate processing error has occurred. {0}.
An unexpected critical certificate processing error has occurred. The error may be recoverable.
Action:
Review the request along with the error details and retry the request if possible. Contact Oracle GoldenGate support, if required.
OGG-30001: The Certificate Administration service has not been initialized.
Incorrect or missing initialization attempted to use the Certificate Administration service before it has been initialized.
Action:
Attempt to restart the service. Contact Oracle GoldenGate support, if required.
OGG-30002: Unable to complete request. The {0} certificate name '{1}' already exists.
Specified certificate name already exists.
Action:
Specify an unused name for the certificate and retry.
OGG-30003: Unable to complete request. The {0} certificate name '{1}' does not exist.
The specified certificate name does not exist.
Action:
Specify the name of an existing certificate and retry the request.
OGG-30005: Failed to read the {0} PEM portion of the certificate bundle.
Unable to read and decode the specified portion of the certificate bundle.
Action:
Review the specified portion of the certificate bundle and correct as needed. The data should be in a properly encoded PEM format include the starting and ending marker texts.
OGG-30006: Processing of the {0} PEM portion of the certificate bundle resulted in zero (0) {0} objects.
The read and decode processing of the specified portion of the certificate bundle produced zero (0) objects. The PEM format is correct but the data may be invalid.
Action:
Review the specified portion of the certificate bundle and correct as needed. The PEM envelope should contain valid DER encoded data.
OGG-30007: Processing of the {0} PEM portion of the certificate bundle resulted in more than one (1) {0} objects.
The read and decode processing of the specified portion of the certificate bundle produced more than one (1) objects. More than one PEM encoded object is present in the data.
Action:
Review the specified portion of the certificate bundle and correct as needed. Only a single PEM encoded object is expected.
OGG-30008: Encountered a non-array type in the {0} PEM portion of the certificate bundle.
The specified portion of the certificate bundle contained unexpected datatype. The expected datatype is an array of zero or more string values.
Action:
Review the specified portion of the certificate bundle and correct as needed. The datatype of CA Certificates should be an array.
OGG-30009: Encountered a non-string type array member in the {0} PEM portion of the certificate bundle.
The specified portion of the certificate bundle contained unexpected array member datatype. The expected datatype should be of string type.
Action:
Review the specified portion of the certificate bundle and correct as needed. The datatype of caCertificates array members should a string.
OGG-30010: More than 1 managed non-default server certificate found at {0}.
More than 1 managed server certificates found with no default specified.
Action:
There should only be one server certificate present or a default server certificate should be defined. Either remove all unneeded server certificates leaving only 1 server certificate or label a valid server certificate as default. Please see Oracle Security documentation for details.
OGG-30011: More than 1 legacy server certificate found at {0}.
More than 1 legacy server certificate found with no default specified.
Action:
There should only be one legacy server certificate present. Remove all unneeded server certificates leaving only 1 legacy server certificate. Please see Oracle Security documentation for details.
OGG-30012: No {0} certificate found at specified store location {1}.
There were no managed or legacy server certificates found at the specified storage location.
Action:
There should either be a on 1 legacy server certificate, 1 managed server certificates of a default managed server certificate present. Please see Oracle Security documentation for details.
OGG-30013: The certificate found at specified store location {0} is in an invalid storage format.
The storage format of the certificate found at storage location {0} was invalid.
Action:
Remove and re-add the certificate.
OGG-30014: Certificate at specified store location {0} could not be read.
Certificate at the specified store location could not be read. Access permissions is denied.
Action:
Check the access and read permission on the storage location and the certificate filesystem object.
OGG-30015: Certificate at specified store location {0} could not be written.
Certificate at the specified store location could not be Written. Access or write permission is denied.
Action:
Check the access and write permission on the storage location and the certificate filesystem object.
OGG-30016: Certificate at specified store location {0} could not be opened.
Open operation on certificate in specified store location failed.
Action:
Verify that the certificate data is properly formatted and valid for the certificate type.
OGG-30017: Failed to import certificate named '{0}', a {1} certificate.
The import operation of an existing certificate at the specified location as a named certificate failed.
Action:
Verify that the source certificate data is properly formatted and valid for the certificate type.
OGG-30018: Match operation failed comparing the expected issuer name '{0}' with the certificate's subject name '{1}'.
The name matching operation comparing subject name and issuer name failed.
Action:
Internal compare failure. Contact Oracle GoldenGate support.
OGG-30019: Failed to create persona for certificate named '{0}'.
Unable to create the certificate's persona with the provided data.
Action:
Internal create failure. Contact Oracle GoldenGate support.
OGG-30020: Failed to store persona for certificate named '{0}' at '{1}'.
Unable to store the certificate's persona.
Action:
Internal store failure. Contact Oracle GoldenGate support.
OGG-30021: The private-key does not belong to the certificate.
The private key's identifier could not be matched with certificate private key identifier. The key is not the private key of certificates.
Action:
Locate the correct matching private key for the certificate and try again.
OGG-30022: Failed to acquire persona for certificate named '{0}' at '{1}'.
Unable to acquire the certificate's persona.
Action:
Internal store failure. Contact Oracle GoldenGate support.
OGG-30023: The certificate store specified for this deployment is missing or not available.
The location of the certificate store could not be found.
Action:
Verify the the configured location for the deployment's certificate store is correct, that the specified location exists, is available and has the appropriate access permissions set. Please see Oracle Security documentation for details.
OGG-30024: The certificate store's permissions deny read access.
The specified certificate store location could not be read due to permission settings that deny read access.
Action:
Check the access and read permission on the certificate storage location. Please see Oracle Security documentation for details.
OGG-30025: The certificate store's permissions deny write access.
The specified certificate store location could not be written due to permission settings that deny write access.
Action:
Check the access and write permission on the certificate storage location. Please see Oracle Security documentation for details.
OGG-30026: The certificate store specified for this deployment is not configured to store certificates.
If using filesystem storage, the location specified is not a directory. If using an object-store, the location specified is not configured to contain certificates.
Action:
Verify that the certificate store location is configured to contain certificate. Please see Oracle Security documentation for details.
OGG-30027: The certificate store's path or specification appears invalid.
The certificate store location provided does not resolve to valid fully qualified path.
Action:
Verify that the certificate store's location refers to valid storage location. Please see Oracle Security documentation for details.
OGG-30028: There is less than 1% space available for the certificate store: Space available {0}, total space {1}.
The space for creating and storing certificates at the storage location provided has fallen below 1% availability. Errors administering certificates may occur due to lack of storage space.
Action:
Increase the space available at the certificate storage location. Please see Oracle Security documentation for details.
OGG-30029: Unable to complete request. The {0} certificate {1} exists but contains no certificate, private-key or trustpoint data.
The indicated certificate was located but is empty. No certificate, private-key or trustpoint data could be found.
Action:
Remove and reinstall the certificate. Please see Oracle Security documentation for details.
OGG-30030: No {0} certificate named '{1}' found.
There were no certificates of the specified type found at the certificate storage location.
Action:
Verify the certificate is present in the certificate store. Please see Oracle Security documentation for details.
OGG-30031: The {0} certificate named '{1}' has an invalid storage format.
The storage format of the certificate was not in the expected format.
Action:
Remove and re-add the certificate.
OGG-30032: The {0} certificate named '{1}' could not be read because of storage permission settings.
The permissions associated with the certificate do not allow read access.
Action:
Check the access and read permission on the storage location and the certificate filesystem object. Please contact your administrator for guidance.
OGG-30033: The {0} certificate named '{1}' could not be written because of storage permission settings.
The permissions associated with the certificate do not allow write access.
Action:
Check the access and write permission on the storage location and the certificate filesystem object. Please contact your administrator for guidance.
OGG-30034: The {0} certificate named '{1}' could not be opened.
Open operation on certificate in specified store location failed.
Action:
Verify that the certificate data is properly formatted and valid for the certificate type.
OGG-30035: Unable to complete request. The certificate type '{0}' is invalid. Valid certificate types are 'server', 'client' and 'truststore'.
The certificate type specified is invalid.
Action:
Review the type of certificate specified.
OGG-30036: The CA certificates contained in the certificate bundle have been added to the certificate store as separately named truststore certificates.
CA certificates added as part of a certificate bundle are stored as separately named truststore certificates. The allows administrators to review and administer each truststore certificate individually. Please see Oracle Security documentation for details on the naming conventions for generated truststore names.
Action:
Informational message. No action is needed. Please see Oracle Security documentation for details on certificate administration.
OGG-30037: Deleting the {0} certificate named '{1}' is not allowed.
Certain certificates, such as the 'default' server certificate, cannot be deleted.
Action:
Try replacing the certificate instead of deleting and re-creating it.
OGG-30038: Adding non-CA certificates to the truststore is not allowed.
The certificate specified for adding to the truststore is not a Certificate Authority (CA) certificate.
Action:
Only Certificate Authority (CA) certificates are allowed in the truststore.
OGG-30039: Adding the {0} certificate named '{1}' without a valid certificate chain is not allowed.
End entity certificates, such as client and server certificates, must be accompanied by a valid certificate chain.
Action:
Include a valid set of the CA certificates in the request and try again.
OGG-30051: Encountered a commit log record with xid {2}, commit timestamp {3} and a commit CSN: {1}, which is less than the highest CSN already processed: {0}. All the records under this xid {2} are skipped.
Extract processed a transaction that has a begin CSN value which is less than the highest CSN already processed. All transactions from the write ahead log are skipped until a begin CSN is found which is greater than or equal to the previous CSN that was already processed.
Action:
None
OGG-30052: Extract started with CSN {1} and positioned to CSN {0}.
CSN shows the exact position of the Extract from where it will start processing the records.
Action:
None
OGG-30053: The Extract for DB2 zOS may receive an ODBC error and further information may be available on the system console.
The remote DB2 subsystem data is accessed using ODBC, SQL and remote procedures. For some issues the procedures may not be able to return some information. If an issue cannot be understood from the Extract report messages, it may help to look at any messages provided by the remote system.
Action:
None
OGG-30054: Could not delete Extract for {0} {1} ({2})
Deleting Extract requires dblogin unless it's forced using override '!'!
Action:
Perform dblogin before deleting Extract or force delete using override '!'
OGG-30055: Database error {0,number,0} ({1})
The specified database error occurred.
Action:
Resolve the error. If the problem persists, contact Oracle Support.
OGG-30057: The log reading user-defined function major version is {0} and is not supported. (The minor version is {1}).
The DB2 log reading user-defined function is not compatible with this version of Oracle GoldenGate and the Extract.
Action:
Install the proper log reading user-defined function in the DB2 subsystem identified in the Extract report.
OGG-30058: The remote diagnosis value of {0} is not a string value of NONE or of TRACE, MINIMUM, DETAIL, VERBOSE or one of those four strings preceded by INIT or READ. The default value is NONE. INIT and READ are specified in order to diagnose only initialization or reading. This parameter will be ignored.
An invalid value was specified for the REMOTEDIAG parameter. The value should be NONE or TRACE, MINIMUM, DETAIL, VERBOSE or one of those four strings preceded by INIT or READ. The default value is NONE.
Action:
None
OGG-30059: The wildcard table mapping {0} does not have DATA CAPTURE CHANGES turned on for table DBID {1} OBID {2} : Table will be ignored
DATA CAPTURE CHANGES is not enabled for the specified table and Extract is ignoring it because TRANLOGOPTIONS includes IGNOREDATACAPTURECHANGES. If DATA CAPTURE CHANGES is enabled, then the table will not be ignored.
Action:
None
OGG-30060: The wildcard table mapping {0} added {1} database and object IDs to the list of table IDs used to filter log records by ID.
When a table matches the filtering by ID criteria for a table-defined wildcard in the Extract parameter file, all currently existing table IDs matching the definition are added to the list of table IDs, used by DB2 for filtering log records by ID. If a table matching this criteria is added later, then its IDs will also be added to the list.
Action:
None
OGG-30061: The Extract initialize and utility remote stored procedure has encountered a option of {0} that is not valid. and cannot be processed.
When the initialization and utility remote stored procedure that is an older version is invoked, Extract abends considering it as an invalid option.
Action:
Check to see if the proper remote initialization and utility procedure is installed in the remote DB2 z/OS subsystem. If you cannot resolve the problem, contact Oracle GoldenGate Support.
OGG-30062: {0} is not supported.
A connection was made to an unsupported variant of the Database.
Action:
Connect to a supported variant of Database. See the Oracle GoldenGate reference documentation for more details.
OGG-30063: The table mapping {0}, with database ID {1} and object ID {2}, has been added to the list of table IDs used to filter log records by ID.
When filtering by ID, any table that matches a table defined in the Extract parameters file will be added to the list of table IDs DB2 uses to filter log records.
Action:
None
OGG-30064: The database ID {0} and object ID {1} that was dropped but was not defined to the Extract has been removed from the list of table IDs used to filter log records by ID.
When filtering by ID, any dropped table that is not defined to the Extract will have its IDs removed from the list of table IDs DB2 uses to filter log records if the IDs are in the list.
Action:
None
OGG-30065: The database ID {0} and object ID {1} that was dropped and was defined to the Extract has been removed from the list of table IDs used to filter log records by ID.
When filtering by ID, any dropped table defined to the Extract will be removed from the table definitions, and its table IDs will be removed from the list of table IDs DB2 uses to filter log records.
Action:
None
OGG-30066: Cannot map the Source column '{0}' to the Target bit/varbit column '{1}' because the target column accepts only string of 0s and 1s.
The Bit/Varbit column in the PostgreSQL database can only accept data in the form of 0s and 1s.
Action:
Map the target PostgreSQL bit/varbit column to a source column containing data in the form of 0s and 1s.
OGG-30067: Opened trail file {0}, RBA: {2} at {1}.
Trail file has been opened.
Action:
None
OGG-30068: Table {0}.{1} has a default sequence column which is not supported.
Extract found a table with a default sequence column that is not supported.
Action:
Remove the table with the default sequence column from the Oracle GoldenGate configuration.
OGG-30069: Partial metadata for column {1}, column ordinal position {2,number,0} is not available for table {0}.
There was an internal error in the metadata processing. The partial metadata for the column is not available.
Action:
Contact Oracle GoldenGate Support.
OGG-30072: Call to {0} produced the following recoverable error: {1}
A call to a system stored procedure failed with message returned.
Action:
Examine the returned message to determine the cause of the failure.
OGG-30073: Call to {0} produced recoverable error without a message.
A call to a system stored procedure failed.
Action:
Examine the previous messages and the system log. If you cannot determine and resolve the problem, contact Oracle Support.
OGG-30075: IBM i Job {0}
IBM i Job
Action:
None
OGG-30076: DDL history table {0} was not found. Please ensure that ddl_create.sh script as been run and the corresponding schema has been specified in GLOBALS.
No DDL history table was found.
Action:
Run the ddl_create.sh to create the table. Ensure that GGSCHEMA in the GLOBALS parameter file points to the schema where the DDL history table was created.
OGG-30077: The SQL CALL statement could not be processed. Verify the WLM is properly setup for the GET_SYSTEM_INFO stored procedure. The GET_SYSTEM_INFO stored procedure runs in a WLM-established stored procedures address space where all STEPLIB libraries must be APF-authorized and the WLM must run with the TCB=1 parameter.
A call to system stored procedure GET_SYSTEM_INFO failed.
Action:
Examine all associated messages and the system log. If you cannot determine and resolve the problem, contact Systems personnel to verify the stored procedure is properly set up.
OGG-30078: The GET_CONFIG stored procedure runs in a WLM-established stored procedures address space. Verify that the WLM is set up properly for the GET_CONFIG stored procedure. Also check that the DBRM OR PACKAGE NAME for this procedure is set up and the user has EXECUTE privilege to call this procedure.
A call to system stored procedure GET_CONFIG failed.
Action:
Examine all associated messages and the system log. If you cannot determine and resolve the problem, contact Systems personnel to verify the stored procedure is properly set up.
OGG-30079: DDL Mismatch Detected. Table {0} has column {1} whose offset in before image is out of sync at LRI {2}.{3}.
Variable Length Columns were added to the specified table after it is created. The Before image does not have records of new added columns.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it with the target table. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30080: Error in KEYCOLS clause, key does not exist or key cannot be determined. {0}. {1}
There has been an error in the KEYCOLS clause.
Action:
Examine KEYCOLS in mapping statement.
OGG-30081: Error in {0} clause, key does not exist or key cannot be determined. {1}. {2}
There has been an error in the clause.
Action:
Examine mapping statement.
OGG-30082: The DBOPTIONS _rollbacktransactiononerror is enabled. This causes the transaction to get rolled back in case of any error. The CDR, HANDLECOLLISIONS and REPERROR features will not work in presence of this parameter.
ODBC DSN attribute TransactionErrorBehavior is internally set to 2 for supporting CDR, HANDLECOLLISIONS and REPERROR features. This setting will have an impact on performance. If the user is not interested in any of these features, user can specify the DBOPTIONS _rollbacktransactiononerror in the parameter file to avoid unnecessary performance degradation.
Action:
Remove the DBOPTIONS _rollbacktransactiononerror parameter from the REPLICAT parameter file if the user is interested in any of the CDR, HANDLECOLLISIONS and REPERROR features.
OGG-30083: System call {0} failed with errno = {1,number,0}, {2}
There has been a failure in a system call.
Action:
Examine error message.
OGG-30084: The parameter filename in the checkpoint file {0} was automatically changed from a non-existent file to one with the same name in the same relative directory under the current installation.
The parameter filename in the checkpoint file is no longer correct and has automatically been changed to the correct name.
Action:
None, the parameter filename in the checkpoint file has automatically been corrected.
OGG-30085: The parameter filename in the checkpoint file {0} was automatically cleared because the current value is the same as the default value.
The parameter filename in the checkpoint file has automatically been cleared as the the current value is the same as the default value.
Action:
None, the parameter filename in the checkpoint file has automatically been cleared.
OGG-30086: The parameter filename in the checkpoint file {0} references a file that does not exist.
The parameter filename in the checkpoint file refers to a file that does not exist.
Action:
Change the parameter filename in the checkpoint to a file that exists, for example "alter replicat rep1 params validfilename"
OGG-30087: TimesTen Driver Manager connection type is {0}. For best performance, use Direct mode when connecting to a local TimesTen instance and Client/Server mode for a remote instance. Refer to TimesTen Driver Manager user guides to configure a Direct or ClientServer connection.
Reports the TimesTen Driver Manager connection type : Direct/Client-Server.
Action:
None
OGG-30088: Java or JNI exception: {0}
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-30089: Error occurred while retrieving member details for file {1}/{0} in remote journal configuration.
Error occurred while retrieving member details for file {1}/{0} in remote journal configuration. Could not retrieve member names. Additional error details: {2}.
Action:
Look for other messages in the process report and error log that provide more context for this failure. If you cannot determine and resolve the problem, contact Oracle Support.
OGG-30090: DDL Mismatch Detected. After image record at LRI {1}.{2} does not match the current metadata for Table {0}.
Columns in the table were added or dropped after it is created. The number of columns in the after image does not match the current table metadata.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it with the target table. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30099: Table {0} has column {1} whose offset is zero but length {4} is non-zero at lri {2}.{3}. There could possibly be a DDL Mismatch issue.
The current column has a NULL value but either its offset or length is not NULL.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30100: Table {0} has column {1} whose offset is zero but length {4} is non-zero at lri {2}.{3}. There could possibly be a DDL Mismatch issue.
The current column has a NULL value but either its offset or length is not NULL.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30101: Table {0} has column {1} whose value is null but either the current offset {4} or current length {5} is not-null at lri {2}.{3}. There could possibly be a DDL Mismatch issue.
Current column is NULL but either its offset or length is not NULL.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30102: Parallel Replicat thread {0} exited unexpectedly. Please check the report file of {0} for more details.
The Main process of the Parallel Replicat group received an unexpected thread disconnect event.
Action:
Contact Oracle Support if you cannot determine the cause after viewing the report file for the specified thread.
OGG-30103: Invalid heartbeat frequency {0} seconds entered. Valid values are from {1} to {2} seconds.Alter heartbeat frequency to 0 to disable heartbeat updates.
Invalid input for repeat interval.
Action:
Specify frequency within valid range.
OGG-30104: The startup transaction ID or URID is {0}. The startup log record RBA or LINK is {1}. This is the actual RBA in non-datasharing and the back chain (LINK) RBA in datasharing.
Display the DB2 z/OS log record URID and the actual RBA or LINKRBA once we are positioned and log record processing has started. The back chain or LINKRBA is the only log record RBA available in datasharing and it points to the previous log record in the transaction. Both RBA types can be used to find the actual starting log record in log record dumps.
Action:
None
OGG-30105: Direct Connect mode requires TimesTen Server version 18.1.4.8 or higher. Use Client/Server mode or upgrade the server to 18.1.4.8 or higher.
Direct Connect Mode requires TimesTen Server version 18.1.4.8 or higher.
Action:
Use Client/Server mode or upgrade the server to 18.1.4.8 or higher.
OGG-30106: Failed to disable the idle transaction session timeout in libpq connection {0}.
Idle transaction session timeout is not set in the libpq connection.
Action:
Contact Oracle Support.
OGG-30107: Table {0} has column {1} whose length {4} does not match the current metadata column length {5} at LRI {2}.{3}. There could possibly be a DDL Mismatch issue.
The column has more data in the current record buffer compared to the current column metadata length. The column length has been changed since its creation.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it with the target table. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30108: Table {0} has column {1} whose length {4} does not match the current metadata column length {5} at LRI {2}.{3}. There could possibly be a DDL Mismatch issue.
The column has more data in the log record buffer compared to the current column metadata length. The column length has been changed since its creation.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30109: Table {0}, column {1}, at offset {4} plus length {5} of the log record is beyond the range of the total record length starting from the record fixed section start offset at LRI {2}.{3}. There could possibly be a DDL Mismatch issue.
The column offset plus the length is longer than the current record length from log the record fixed section start point.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30110: Table {0}, column {1}, at offset {4} plus length {5} of the log record is beyond the range of the total record length starting from the record fixed section start offset at LRI {2}.{3}. There could possibly be a DDL Mismatch issue.
The column offset plus the length is longer than the current record length from log record fixed section start point.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30111: Table {0} has column {1} whose offset {4} is less than the previous column's {5} offset {6} plus its length {7} at LRI {2}.{3}.There could possibly be a DDL Mismatch issue.
The variable length column offset is less than the previous variable column offset + length.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30112: Table {0} has column {1} whose offset {4} is less than the previous column's {5} offset {6} plus its length {7} at LRI {2}.{3}.There could possibly be a DDL Mismatch issue.
The variable length column offset is less than the previous variable column offset + length.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30113: Table {0} has column {1} whose value is null but either the current offset {4} or current length {5} is not-null at lri {2}.{3}. There could possibly be a DDL Mismatch issue.
The current column has NULL value but either its offset or length is not NULL.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30114: DDL Mismatch detected. Table {0} has column {1} data in after image but not in before image at LRI {2}.{3}.
The column data is available in the after image but not in the before image. The column has been added to the table after its creation.
Action:
Exclude this table from the Oracle GoldenGate configuration, stop user activity on it, and then resynchronize it. Add it back to the Oracle GoldenGate configuration, and then restart the processes.
OGG-30115: An unavailable resource was encountered at position {0}. The DB2 z/OS message is: {1}.
The process is trying to read a log file that is no longer available.
Action:
If the Extract start position was specified using a date or LSN, it is possible to use a position that is not available in the current active or archive logs. If Extract is configured properly, contact Oracle Support.
OGG-30116: A log record for the requested checkpoint LRSN time {0} was not found. The DB2 z/OS message is: {1}.
The Extract is positioning in the log by time and a log record with the requested time is not available.
Action:
If the Extract start position was specified using a date and or time, it is possible to use a position that is not available in the current active or archive logs. If Extract is configured properly, contact Oracle Support.
OGG-30117: Invalid numeric data detected. Error converting numeric from Oracle to ASCII format for column {0}, table {1}, row length {2,number,0}, rowdata: {3}
Invalid numeric data was detected while converting from the Oracle native type to Oracle GoldenGate ASCII for the specified column.
Action:
Restart Extract. If the problem persists, exclude this table from the Extract configuration so that processing continues, and then contact Oracle Support.
OGG-30118: Reached STOPATLRI value requested {0}.{1}
This message is reported when Extract is running in a diagnostic mode under the direction of Oracle Support.
Action:
None
OGG-30119: LRI requested ({0}.{1}) was not found in the the DB2 log files, using next available LRI at ({2}.{3})
Extract was positioned to start at the specified LRI, but it does not exist in the log files. Extract is positioned to the closest next LRI that exists in the log files.
Action:
None
OGG-30120: DPF Detected: Number of nodes in database is {0} and current node number is {1}.
A properly detected DPF configuration will have its node configuration reported.
Action:
If the current DB set-up is DPF and DPF set up is not reported, the database must be explicitly activated by running DB2 command DB2 ACTIVATE DB DB_NAME.
OGG-30121: The initialization and utility stored procedure major version is {0} and is not compatible with this Extract. (The minor version is {1}).
The DB2 initialization and utility stored procedure is not compatible with this version of Oracle GoldenGate and the Extract. Install the stored procedure that was supplied with this Extract.
Action:
Install the proper initialization stored procedure in the DB2 subsystem identified in the Extract report.
OGG-30122: Attempt to resolve the object {0} failed. Check the object {0} exists in the system.
Review the previous error logs.
Action:
Check if the object {0} exists in the system. Contact Oracle support if the object exists in the system and the error persists.
OGG-30123: Invalid journal name {0}.
The journal name is in invalid format.
Action:
Specify the journal name in correct format.
OGG-30125: Object not found: {0}/{1}
Object {0}/{1} not found in the system.
Action:
Check if the object {0}/{1} exists in the system.
OGG-30126: DB2 zOS version 10.1 is no longer supported for this OGG version.
Extract no longer supports DB2 z/OS version 10.1.
Action:
Oracle GoldenGate for DB2 z/OS will need to be upgraded to a version supported by Oracle and IBM before using the Extract process.
OGG-30127: The Replica identity setting for the table '{0}' is set to 'DEFAULT' which is not sufficient to process the DELETE operation for table without a primary key. Set the Replica identity setting to FULL using the ADD TRANDATA '{0}', ALLCOLS command and re-initiate the DML in the problematic table.
The Replica identity setting for the table is set to DEFAULT, which is not compatible to process the DELETE operation for a table without a primary key.
Action:
Set the Replica identity setting to FULL using the ADD TRANDATA with ALLCOLS command and re-initiate the DML in the problematic table.
OGG-30128: TRANSDISCARD cannot be used with GROUPTRANSOPS.
REPERROR TRANSDISCARD option applies an error-handling action to an entire transaction. It honors the boundaries of the source transaction. However, GROUPTRANSOPS in the parameter file may affect the error-handling logic or outcome because it alters the transaction boundaries.
Action:
Remove one of the parameters, depending on the required Oracle GoldenGate configuration. For help, see the Oracle GoldenGate reference documentation.
OGG-30152: TRANDATA cannot be added/deleted for non-physical file {0} ({1})
There was a problem with deleting the supplemental log for the specified table.
Action:
Correct the problem based on the error message. If you cannot resolve the problem, contact Oracle Support.
OGG-30153: Journaling for object {0} ({1}) is enabled to journal {2}
Journaling enabled for specified table.
Action:
None
OGG-30154: Journaling for object {0} ({1}) is disabled
Journaling disabled for specified table.
Action:
None
OGG-30155: Journaling for object {0} ({1}) is enabled to journal {2}, however it is not journaled with before images. It is recommended that you delete and add trandata on the object or extract cannot process it.
The table is not journalled with before images.
Action:
Perform 'DELETE TRANDATA' and 'ADD TRANDATA' on the tables where the warining is issued.
OGG-30156: Journaling for object {0} ({1}) is already enabled to journal {2}. If you wish to change the journaling, first perform delete trandata on the table and then perform add trandata.
Journaling already enabled for specified table.
Action:
Perform 'DELETE TRANDATA' and 'ADD TRANDATA' on the table if you wish to change the journaling.
OGG-30157: No JOURNAL specified for ADD TRANDATA. Use either the JOURNAL keyword or specify a journal with the DEFAULTJOURNAL command.
No JOURNAL specified for ADD TRANDATA.
Action:
Use either the JOURNAL keyword or specify a journal with the DEFAULTJOURNAL command and re-run ADD TRANDATA.
OGG-30158: The Extract remote memory manager stored procedure task {0} started with return code 0.
The IBM DB2 z/OS stored procedure ADMIN_TASK_ADD started successfully and the remote memory manager task is running.
Action:
None
OGG-30159: The Extract remote memory manager stored procedure received a return code of {0} at startup. The startup message is: {1}.
The IBM DB2 z/OS stored procedure ADMIN_TASK_ADD failed to start and the the remote memory manager task could not be run.
Action:
Extract failed to start the memory manager with a bad return code. Check the remote_memory_options parameter for accuracy. Also check that the OGGTASKM stored procedure is set up correctly. Contact Oracle GoldenGate support if the problem persists.
OGG-30160: The Extract remote memory manager stored procedure is configured to release shared memory after {0} hours and {1} minutes if the Extract remains inactive.
The IBM DB2 z/OS remote memory manager stored procedure will detect inactivity and shut down after the specified time.
Action:
None
OGG-30161: Replicat has stopped the inbound server {0}. {1}
Integrated Replicat has stopped the inbound server.
Action:
None
OGG-30162: Failed to find routine {0}.{1}. Please ensure that DBOPTIONS REMOTESCHEMA is correctly specified in the parameter file for replicat or extract and that the remote routines are correctly installed on the Db2 subsystem. See other messages for further details
The Oracle GoldenGate process could not find and execute the specified remote routine.
Action:
Correct the problem with the parameter file or installation, and then restart the process.
OGG-30163: APIFILTER is filtering to send only change data capture and transactions when reading log records.
If APIFILTER is enabled and no ID list is available, then APIFILTER will be used to only return change data capture and transaction log records.
Action:
None
OGG-30164: Failed to enable the bytea_output to hex in libpq connection {0}.
Setting bytea_output to hex in the libpq connection.
Action:
Contact Oracle Support.
OGG-30165: Moving BR data to new directory.
Informative only.
Action:
None
OGG-30166: Moving BR data incomplete. Using original setup.
Informative only.
Action:
None
OGG-30167: Removing BR data incomplete at {0}.
Informative only.
Action:
None
OGG-30168: Duplicate directory found {0}. Using last specification.
Informative only.
Action:
None
OGG-30169: Duplicate entry for table {0} is found in the internal metadata cache.
This is an internal error. The internal object metadata cache is in inconsistent state.
Action:
If this message continues to appear, contact Oracle Support.
OGG-30171: The server has ended the streaming connection.
The PostgreSQL server has shutdown.
Action:
Startup the PostgreSQL server and check that it's up and running. Then restart the Extract.
OGG-30173: Using TCP instead of UDS as the underlying protocol for ER interprocess communication.
The process couldn't validate if it is running on Solaris 11.3 or above.
Action:
If UDS is necessary, upgrade to Solaris 11.3 or above.
OGG-30174: Using UDS as the protocol for ER interprocess communication on Solaris 11.3 may lead to an undesired behaviour
A UDS-related bug fix introduced in Solaris 11.3.27.4.0 is required to use Unix Domain Sockets as the communication protocol for ER processes. The process can't verify the system's update level.
Action:
Ensure that current Solaris version is 11.3.27.4.0 or above. You can choose TCP instead of UDS as the communication protocol by setting _communication_protocol parameter.
OGG-30177: Persisted data mismatch on '{0}'. Has the BR version been updated?
Informative only.
Action:
None
OGG-30178: Parallel Replicat is not supported on this platform
ADD REPLICAT command failed because parallel Replicat is not supported on this platform.
Action:
Create a new Replicat that is not a Parallel Replicat.
OGG-30200: The recovery checkpoint position of Sequence {0,number,0}, RBA {1,number,0}, from the checkpoint table is older than the checkpoint file position of Sequence {2,number,0}, RBA {3,number,0}.
A mismatch between the database checkpoint position and the file checkpoint position may occur if the target database is recovered from a backup, or if a non-durable commit is not persisted prior to a database failure.
Action:
If the database was recovered from a backup, or if the database supports non-durable commits, then no action is required. Otherwise, investigate the cause of the mismatched checkpoint positions.
OGG-40000: Path conflict. Redefinition of environment variable found: {0} vs. {1}. Ignoring {0} misspelled. Using {1}.
Path conflict. Redefine the environment variable.
Action:
Remove or unset one of the environment variables. Only use one environment variable.