ogg 真的太多bug了，不穩定，太坑Action: Contact Oracle Support.
OGG-01043: Terminate on fetch result = {1} ({2,number,0}) (table: {0})
Cause: 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 {2}"
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01051: Reverting to overwrite recovery mode at user's request...
Cause: 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)
Cause: No trail exists to recover.
Action: None
OGG-01053: Recovery completed for target file {0}, at RBA {1,number,0}
Cause: Extract completed its recovery.
Action: None
OGG-01054: Recovery completed for target file {0}, at RBA {1,number,0}, CSN {2}
Cause: Extract completed its recovery.
Action: None
OGG-01055: Recovery initialization completed for target file {0}, at RBA {1,number,0}
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01071: {0} cannot be used with stored data
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01072: {2}: Buffer overflow, needed: {1,number,0}, allocated: {0,number,0}
Cause: 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
Cause: An array element in an XML message exceeded the defined limit.
Action: Contact Oracle Support.
OGG-01074: Invalid case statement, value {0,number,0} in {1}
Cause: This message is deprecated.
Action: None
OGG-01075: The table object ID cannot be used to look up the table entry if the tables were added via a SOURCEDEFS file
Cause: 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
Cause: This message is deprecated.
Action: None
OGG-01077: Error closing file, handle: 0x{0}, err: {1,number,0} - {2}
Cause: 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}
Cause: 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.
Cause: 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
Cause: 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
Cause: 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 {0} function from {2} failed with return code {1,number,0}
Cause: An API error occurred.
Action: Contact Oracle Support.
OGG-01083: The call to the {0} function from {1} failed with return code {2,number,0} ({3})
Cause: 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})
Cause: 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: {0} received window closed event
Cause: 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: {0} received system shutdown event
Cause: 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: {0} received user logoff event
Cause: 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.}
Cause: 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
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01100: Unrecoverable XML configuration error
Cause: 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 build IPC message from XML node
Cause: 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})
Cause: This message is deprecated.
Action: Contact Oracle Support.
OGG-01103: missing err property in xml msg message
Cause: This message is deprecated.
Action: None
OGG-01104: Unknown error starting remote program {0}
Cause: 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})
Cause: 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})
Cause: 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})
Cause: 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})
Cause: The IPC message could not be decompressed.
Action: Contact Oracle Support.
OGG-01109: error compressing IPC message ({1}, inlen={0,number,0})
Cause: 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}
Cause: 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
Cause: This is an internal error.
Action: Contact Oracle Support.
OGG-01112: Unexpected condition in {0} at line {1,number,0}
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01113: Unexpected condition in {0} at line {1,number,0}
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01114: invalid reply ({0})
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01115: Function {0} not implemented.
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01116: Marker fragment and current fragment out of sync
Cause: This message is deprecated.
Action: None
OGG-01117: Received signal: {1} ({0,number,0})
Cause: 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}
Cause: Oracle GoldenGate encountered a non-recoverable processing exception.
Action: Contact Oracle Support.
OGG-01119: XML error: {0}
Cause: 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}
Cause: 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
Cause: 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}]
Cause: 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}]
Cause: 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)
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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})
Cause: 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})
Cause: The process cannot position in the trail file.
Action: Contact Oracle Support.
OGG-01134: Cannot find executable file '{0}'
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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}
Cause: An internal error occurred.
Action: Contact Oracle Support.
OGG-01143: before image missing from key update for table {0}
Cause: A primary key was updated, but the before image is not in the Oracle redo log record. Supplemental logging for this table was not enabled before starting capture of its data.
Action: First, make certain that database-level supplemental logging is enabled. Next, do the following, without delay between steps, so that Extract lag is kept to a minimum: Stop Extract, then remove the table from the TABLE parameter, then restart Extract. Next issue ADD TRANDATA for the table. Stop activity on the table, and resynchronize it with the target. Stop Extract, then add the table back to the TABLE parameter. Start Extract and enable user activity on the table.
OGG-01144: Error mapping source hex-string data into a native floating-point format, col: {0}, input: [{1}]
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: The mapping specification contains an invalid timestamp or date 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-01151: Error mapping from {0} to {1}
Cause: 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
Cause: 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 {0} to {1} {3}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: There was an internal error converting a timestamp value.
Action: Contact Oracle Support.
OGG-01159: Value ({0}) exceeds minimum value of column.
Cause: 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.
Cause: 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}.
Cause: 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}).
Cause: 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}.
Cause: 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}.
Cause: 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
Cause: 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.
Cause: 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
Cause: 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.
Cause: 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
Cause: 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
Cause: 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-01171: Failed to process MBU record.
Cause: Extract could not link multi-block undo records.
Action: Make certain that supplemental logging is enabled. If the problem persists, remove the table from the Oracle GoldenGate configuration.
OGG-01172: Discard file ({0}) exceeded max bytes ({1,number,0})
Cause: 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}])
Cause: 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}
Cause: 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
Cause: Enscribe auditcomp records are not supported by Oracle GoldenGate.
Action: Remove these record types from the Extract configuration on the NonStop system.
OGG-01176: Error converting data to ascii format
Cause: 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 {0} at {1}
Cause: This message is deprecated.
Action: None
OGG-01178: New record version encountered (data may be missing) in {0} at {1}
Cause: This message is deprecated.
Action: None
OGG-01179: Mismatched record version/bad data in {0} at {1}
Cause: 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.txt 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
Cause: 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
Cause: 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}
Cause: The trail record header does not contain the IO 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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...
Cause: 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...
Cause: 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})
Cause: 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}]
Cause: 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
Cause: 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}).
Cause: 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
Cause: 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 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}
Cause: 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}>
Cause: 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}>
Cause: 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}>
Cause: 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}>
Cause: 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
Cause: Extract stopped the initial-load Replicat after the load completed successfully. Informational only.
Action: None
OGG-01201: Error reported by MGR : {0}
Cause: 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
Cause: 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
Cause: 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 recognised by receiving process
Cause: 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}
Cause: 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]
Cause: This message is deprecated.
Action: None
OGG-01207: The length given for the unique row identifier required for LOBROW is zero
Cause: 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}
Cause: 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]
Cause: 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]
Cause: 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
Cause: 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})
Cause: The size of the LOB chunk exceeds the maximum allowed limit.
Action: Contact Oracle Support.
OGG-01213: Unexpected error allocating LOB column memory structure
Cause: While storing a LOB chunk in memory, the process detected that the transaction information is missing.
Action: Contact Oracle Support.
OGG-01214: oldest uncommmitted transaction has no tran_hdr data
Cause: 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)
Cause: 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})
Cause: 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})
Cause: 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})
Cause: This message is deprecated.
Action: None
OGG-01220: Could not establish host TCP/IP address
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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})
Cause: 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} ...
Cause: The process is waiting to connect to the specified listening port. Informational only.
Action: None
OGG-01228: Timeout in {0,number,0} seconds
Cause: The process connection will timeout in the specified time frame.
Action: None
OGG-01229: Connected to {0}:{1,number,0}
Cause: 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}
Cause: Oracle GoldenGate recovered from a TCP error. Informational only.
Action: None
OGG-01231: Remote host TCP params error: {0}
Cause: 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}
Cause: 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}
Cause: 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 recognised by receiving process
Cause: 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
Cause: A TCP command was not permitted by the receiving Manager process.
Action: Contact Oracle Support.
OGG-01236: Trace file {0} opened
Cause: The specified trace file was opened by the process. Informational only.
Action: None
OGG-01237: Trace file {0} closed
Cause: The specified trace file was closed by the process. Informational only.
Action: None
OGG-01239: {0}
Cause: 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}
Cause: 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
Cause: This message is deprecated.
Action: None
OGG-01244: {0}
Cause: 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}
Cause: The DEF parameter is missing the record name detail.
Action: Add the record name to be used in the DEF file output.
OGG-01246: DEFINITION {0} was not defined
Cause: The FILE input record was not found in the COBOLDEFSFILE.
Action: Correct the FILE entry to match the source DDL record name.
OGG-01247: Error processing {0} params: {1}
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}"
Cause: This message is deprecated.
Action: None
OGG-01255: Missing entry for data type {0}
Cause: 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}
Cause: 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.
Cause: 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: ERROR: INVALID CACHE MEMORY VALUES
Cause: 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}.
Cause: 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-01262: The call to the {0}() function from line {2,number,0} in {3}() failed with reason '{1}'
Cause: 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: The call to the {0}() function from line {1,number,0} in {2}() returned an unexpected value
Cause: 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-01264: The call to the {0}() function from line {1,number,0} in {2}() returned an unexpected value
Cause: 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-01266: {0}
Cause: 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-01268: {2}: exceeded maximum allocation attempts ({0,number,0}): {1}
Cause: The Oracle GoldenGate cache manager failed to allocate virtual memory for transaction data after the maximum permissible number of retries. There is not sufficient free virtual memory, based on the implicit or explicit CACHESIZE setting of the CACHEMGR parameter, to satisfy new memory requests. Data will be paged to disk, if eligible. For more information, see the CACHEMGR parameter in the Oracle GoldenGate reference documentation.
Action: None
OGG-01269: The call to the {0}() function for address 0x{1}, size 0x{2} from line {3,number,0} in {4}() returned an unexpected value
Cause: 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: {1}: Bad Parameter: {0}
Cause: The CACHEMGR parameter contains invalid syntax, or is not supported for the database type.
Action: Check the CACHEMGR reference documentation to verify that the database is supported. If true, then correct the syntax and then restart the process.
OGG-01271: {1}: Bad Parameter Argument: {0}
Cause: 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 Oracle GoldenGate Reference.
OGG-01273: {1}: INVALID ARGUMENT SYNTAX: {0}
Cause: The CACHEMGR parameter contains invalid syntax.
Action: Correct the syntax and then restart the process. For syntax and usage of CACHEMGR, see the Oracle GoldenGate Reference.
OGG-01274: {1}: Duplicate Argument: {0}
Cause: The CACHEMGR parameter contains duplicate syntax.
Action: Correct the syntax and then restart the process. For syntax and usage of CACHEMGR, see the Oracle GoldenGate Reference.
OGG-01275: EXCEEDED ARGUMENT COUNT FOR: {0} max allowed: {1,number,0}
Cause: There are too many arguments in the CACHEMGR parameter, such as: CACHESIZE 16G 64G, when only one size should be specified.
Action: Fix the parameter, and then restart the process.
OGG-01276: {1}: BAD DIRECTORY PARAMETER: {0}
Cause: The CACHEMGR parameter contains a CACHEDIRECTORY option that has invalid syntax.
Action: Specify a directory path and a maximum directory size for each CACHEDIRECTORY entry, and separate each CACHEDIRECTORY entry with a comma, as in: CACHEDIRECTORY /ogg1/temp 2GB, CACHEDIRECTORY /ogg2/temp 2GB
OGG-01277: {2}: INVALID DIRECTORY SIZE SPEFICICATION: {1} ({0})
Cause: 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: {2}: cm_memdir_add: {0} size: {1}
Cause: The disk space that is allocated to the CACHEMGR paging directories and specified with the CACHEDIRECTORY option was exceeded.
Action: Add disk space if needed, and change the CACHEDIRECTORY option to allocate more space to the cache directories.
OGG-01279: {1}: max # of directories allocated: {0,number,0}
Cause: 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: {1}: Duplicate CACHEDIRECTORY: {0}
Cause: The CACHEDIRECTORY option of the CACHEMGR parameter contains one or more duplicate entries.
Action: Remove the duplicate entries.
OGG-01281: {0}
Cause: This is a generic Event Marker Infrastructure informational message. It may be useful for operational, performance, or diagnostic purposes.
Action: None
OGG-01282: {0}
Cause: 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}
Cause: 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 aborted)
Cause: The parameter file contains the EVENTACTIONS parameter with the STOP option. The process stopped immediately and aborted 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}
Cause: 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}
Cause: 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}'
Cause: 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}
Cause: 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: Aborting process due to {0} event {1}{2}
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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>...])
Cause: 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})
Cause: 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
Cause: 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.
Cause: The specified trail is not a valid Oracle GoldenGate trail.
Action: Contact Oracle Support.
OGG-01334: Error mapping data from {0} to {1}.{2} in function {3}
Cause: 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}
Cause: 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}
Cause: 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})
Cause: 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.
Cause: The specified service started successfully. Informational only.
Action: None
OGG-01339: {1}: Failed to start the {0} service, error code {2,number,0} ({3}).
Cause: 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, operation [{0}], start {1} [{2}], DDL seqno [{3}]
Cause: 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}
Cause: A restart failed.
Action: Contact Oracle Support.
OGG-01344: Restart notification failure. status = {0}.
Cause: A restart notification failed.
Action: Contact Oracle Support.
OGG-01348: Invalid CHARSET and A2E character set configuration
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: 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
Cause: Oracle GoldenGate is converting character data. Informational only.
Action: None
OGG-01356: CHAR/VARCHAR: {0}
Cause: Character data is in the format of the specified character set. Informational only.
Action: None
OGG-01357: CHAR/VARCHAR: Default
Cause: Character data is in the format of the default character set. Informational only.
Action: None
OGG-01358: NCHAR/NVARCHAR: UTF-16/UTF-8
Cause: 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 {0}.
Cause: 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.
Cause: This is an informational message to indicate the mode of a group.
Action: None
OGG-01364: No opening parenthesis was found for the {0} {1} parameter.
Cause: 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.
Cause: 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.
Cause: 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 precedure 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}
Cause: 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})
Cause: 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}]
Cause: 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}.
Cause: 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.
Cause: 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}
Cause: 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}
Cause: 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.
Cause: 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.
Cause: 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}.
Cause: 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.
Cause: 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}]
Cause: 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}.
Cause: 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.
Cause: 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
Cause: 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}.
Cause: 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.
Cause: 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}.
Cause: 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-01385: This command is not supported for VAM DDL implementation
Cause: The DDLDUMP command is not supported for the current database type.
Action: None
OGG-01386: Value for {0} must be between {1} and {2}.
Cause: 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.
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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}
Cause: 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.
Cause: 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}.
Cause: 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 Support.
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.
Cause: 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.
Cause: 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
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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)
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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 {0}
Cause: 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 {0}
Cause: 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.
Cause: 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 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.
Cause: 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}
Cause: 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.
Cause: 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.
Cause: 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: tran id: 0 length memtran: 0x{0}
Cause: A primary key or unique identifier is not present in the captured data.
Action: Open a support case with Oracle GoldenGate.
OGG-01415: CACHEMGR: secondary tran id: 0 length tran id: {0}
Cause: A secondary key or unique identifier is not present in the captured data.
Action: Open a support case with Oracle GoldenGate.
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.
Cause: 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 proces, 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: {1} primary key: {0}
Cause: 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 data type {0} ({1,number,0}) found in UDT attribute {2}.
Cause: An NCLOB, NCHAR, or NVARCHAR2 data type 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.
Cause: 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}
Cause: 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
Cause: 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: no secondary key primary key: {0}
Cause: 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-01424: Event processing not supported for Teradata maximum performance mode.
Cause: 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}'
Cause: 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}
Cause: The specified user exit excluded the specified DDL. This is informational only.
Action: None
OGG-01427: {1} ignored when {0} is used
Cause: 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}
Cause: 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: Aborted grouped transaction on {0}, Mapping error
Cause: 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: Aborted grouped transaction on {0}, Filter not passed
Cause: There was an error in the filter logic.
Action: Fix the filter specification in the parameter file, and then restart the process.
OGG-01433: Failed to validate table {0}. The table is compressed and Extract will not be able to Extract data from Oracle logs
Cause: Oracle GoldenGate does not support tables created with table compression or OLTP table compression.
Action: Remove the table from the Extract and Replicat configurations, and then restart the processes.
OGG-01434: {0}
Cause: 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})
Cause: Internal warning. A memory mapping operation failed.
Action: Verify that the installation directory is on a file system that supports memory mapped files.
OGG-01436: Detected and skipped incomplete log write at end of Oracle log with sequence# of {0,number,0} and log write starting rba of {1,number,0}
Cause: The end of the file was reached before the log writer buffer was completed.
Action: Add the TRANLOGOPTIONS parameter with the OPENARCHIVEIMMEDIATE option to the Extract parameter file, so that the process uses the archive log immediately.
OGG-01437: Failed to modify trail record image prior to write to trail file {0}
Cause: 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}
Cause: 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).
Cause: 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}]
Cause: 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
Cause: 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.
Cause: 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
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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}
Cause: 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.
Cause: 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}.}
Cause: 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.
Cause: 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.
Cause: 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}
Cause: 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}
Cause: 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
Cause: 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
Cause: 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})
Cause: 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}.
Cause: 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}.
Cause: 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.
Cause: 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.
Cause: 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}.
Cause: 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.
Cause: 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.
Cause: 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.
Cause: 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 - DDL 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.
Cause: 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-01474: Cannot automatically start {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.
Cause: 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-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.
Cause: 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.
Cause: 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}
Cause: 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}.
Cause: 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}
Cause: This message is deprecated.
Action: None
OGG-01482: DDL object type is not supported, type {0}
Cause: 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.
Cause: 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 LSN={4,number,0}, length={5,number,0}.
Cause: 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}]
Cause: 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}]
Cause: 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}]
Cause: 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}
Cause: The process could not find a valid trail during the initial phase of recovery.
Action: Contact Oracle Support.
OGG-01498: Aborting BATCHSQL transaction{0,choice,0#|1# in batch error mode}. Database error {1,number,0} ({2}).
Cause: 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: Aborting 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.
Cause: 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: Aborting 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.
Cause: 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 TPKU.) Replicat will revert to normal processing to apply this transaction.
Action: None
OGG-01502: Aborting BATCHSQL transaction{0,choice,0#|1# in batch error mode}. Database error {1,number,0} ({2}). Override of duplicate failed.
Cause: 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: Aborting BATCHSQL transaction{0,choice,0#|1# in batch error mode}. Mapping error.
Cause: The batched transaction is being aborted, and Replicat will revert to normal processing.
Action: None
OGG-01504: Aborting BATCHSQL transaction{0,choice,0#|1# in batch error mode}. Filter not passed.
Cause: The batched transaction is being aborted 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}
Cause: 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}.
Cause: 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}.
Cause: 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.
Cause: 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.
Cause: 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})
Cause: 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})
Cause: 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
Cause: 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}
Cause: Extract is positioning to the specified sequence number.
Action: None
OGG-01514: Positioning to start
Cause: 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}
Cause: The process is being positioned to start at the specified timestamp.
Action: None
OGG-01516: Positioned to {0}, {1,date} {1,time}
Cause: 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}
Cause: 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.
Cause: 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.
Cause: 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.
Cause: 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}
Cause: 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
Cause: 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})
Cause: 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}'
Cause: 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.
Cause: Undefined
Action: Undefined
OGG-01528: Cannot access configuration file '{0}', error {1,number,0} ({2})
Cause: 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.
Cause: Undefined
Action: Undefined
OGG-01530: MaxFileSize of '{0}' in configuration file, '{1}', must be between zero and 4GB
Cause: 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'.
Cause: 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}'
Cause: 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
Cause: Undefined
Action: Undefined
OGG-01534: Error parsing XML configuration file, '{2}', at line {0,number,0}: {1}
Cause: 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
Cause: 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}'
Cause: 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}'
Cause: 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}'
Cause: 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}'
Cause: 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}'
Cause: 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}'
Cause: 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-01545: Table {0} column {1,number,0} : DATA CORRUPTION may result from the use of "NOT FOR REPLICATION" on a check constraint and OLE DB.
Cause: Alerts you that the check constraint in the specified table is set to NOT FOR REPLICATION. In this mode, the target database does not check constraints when the operation is applied by Replicat. The assumption is that the constraint checking was performed by the source database.
Action: None
OGG-01546: Table {0} column {1,number,0} : DATA CORRUPTION may result from the use of "NOT FOR REPLICATION" on a trigger when OLE DB is being used.
Cause: The trigger in the specified table is set to NOT FOR REPLICATION. In this mode, the target database does not fire the trigger when the operation is applied by Replicat operating as the Replication agent. The assumption is that the triggered operations from the source are captured and Replicated.
Action: Verify 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-01547: Table {0} column {1,number,0} : DATA CORRUPTION may result from the use of "NOT FOR REPLICATION" on a foreign key when OLE DB is being used.
Cause: The foreign key in the specified table is set to NOT FOR REPLICATION. The target database does not enforce the constraint when the operation is applied by Replicat operating as the 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: Verify that the referenced tables are included in the Replication configuration with the referencing table; otherwise, there will be no errors to alert you to integrity violations, such as if a row gets inserted into a table that contains a foreign key to a non-Replicated table.
OGG-01548: Table {0} : To improve performance, consider switching to OLE DB.
Cause: The ODBC API is being used by Replicat, but IDENTITY columns have NOT FOR REPLICATION enabled.
Action: To take advantage of NOT FOR REPLICATION and have Replicat use the better-performing OLE DB API, configure Replicat to connect as the SQL Server Replication user by using the DBOPTIONS parameter with the USEREPLICATIONUSER option. See the Oracle GoldenGate for SQL Server documentation for more information.
OGG-01552: Connection String: {0}
Cause: This is an informational message that indicates the OLE DB connect string (with the password masked) that Replicat used to connect to the target database.
Action: None
OGG-01554: The DBOPTION USEODBC and USEREPLICATIONUSER are mutually exclusive.
Cause: USEODBC and USEREPLICATIONUSER are both specified in the DBOPTIONS parameter.
Action: To have Replicat perform DML through ODBC, remove USEREPLICATIONUSER. To have Replicat perform DML as the SQL Server Replication user, remove USEODBC.
OGG-01555: OLE DB Error: Incompatible driver error DSN '{0}' SQL Server {1} requires {2}
Cause: The DSN that is specified with TARGETDB in the Replicat parameter file does not specify a connection driver that is compatible with the selected SQL Server in that specification.
Action: Make certain the correct DSN is specified for TARGETDB and, if so, make certain that the driver and the database server that are specified in the DSN definition are compatible.
OGG-01557: OLE DB Error: Cannot open data source. Error code 0x{0} Detail: {1}
Cause: Replicat failed to connect to the target database with the OLE DB connection.
Action: Check the TARGETDB parameter to make certain that the correct DSN is specified. If that value is correct, examine the DSN definition itself, to make certain that all of the required connection information is present and valid.
OGG-01558: Database operation failed: OLE DB Error 0x{0}
Cause: The Replicat OLE DB operation failed, but no error information can be retrieved from the driver.
Action: Check the process report file for any warning or error messages that occurred prior to this error message, and then contact Oracle Support.
OGG-01560: Positioned to {0}
Cause: Extract positioned to the specified sequence number.
Action: None
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/30393770/viewspace-2783738/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- jivejdon太坑爹了，原始碼類路徑不對啊！！！。2013-08-04原始碼
- go 代理穩定不卡頓2020-06-16Go
- 太任性！因為美女太多，這所學校設定了三個計算機類學院2019-08-26計算機
- 程式設計師真的“編碼太多沒時間思考”了嗎2012-03-05程式設計師
- 愛了愛了！豐巢智慧政務櫃真的太實用了2021-02-19
- 伺服器不穩定因素2022-07-29伺服器
- 怎麼測試伺服器穩不穩定2022-08-25伺服器
- 不經歷太多2024-03-29
- 程式碼Bug太多？給新人Code Review頭都大了？快來試試SpotBugs2023-04-03View
- 沒太多坑的微信支付2015-12-10
- 這個Bug的排查之路，真的太有趣了。2021-03-16
- 伺服器不穩定的原因2023-02-06伺服器
- 目標檢測框不穩定不連續？2021-02-04
- Java22重磅釋出！！！！卷不動了，真的卷不動了。。。。2024-03-21Java
- 太極限了，JDK的這個BUG都能被我踩到2022-05-10JDK
- 網路 adb 不穩定咋辦？2020-05-14
- 企業網路的不穩定因素2022-04-12
- 理解mouseover和mouseout“不穩定”的原因2015-08-17
- Linux 發行版 Ultimate Edition 3.9 太坑爹了2014-04-16Linux
- Topic太多！RocketMQ炸了！2023-03-28MQ
- MySQL的這個bug，坑了多少人？2020-04-06MySql
- 蘋果手機的月亮圖示有什麼功能？原來這麼好用，不會真的太浪費了2020-01-19蘋果
- 樂視eui 重新定義了--“穩定版”2016-07-30UI
- AndroidStudio升級3.x之後太坑了2019-03-03Android
- [譯]為何前端開發如此不穩定2018-06-22前端
- [譯] 為何前端開發如此不穩定2018-06-12前端
- 執行計劃不穩定的原因分析2012-02-14
- 強大的CSS：focus-visible偽類真的太6了！2019-05-22CSS
- iOS Bug 太多，蘋果終於坐不住了！2020-01-12iOS蘋果
- 圍觀：iOS 8 Bug太多被編小曲2014-09-26iOS
- ORACLE RAC 11.2.0.4 FOR LINUX TO ORACLE 11.2.0.3 OGG部署巨坑集錦2018-02-28OracleLinux
- Flutter JsonToDart Mac版 lei了，真的不mark嗎2019-07-08FlutterJSONDartMac
- 聊聊spring事務失效的12種場景，太坑了2021-09-04Spring
- 諾基亞要推 Android 機了，「某軟」實在太坑2015-11-27Android
- 為什麼前端開發這麼不穩定？2019-06-25前端
- Oracle中的並行系列（二）：你設定的並行真的生效了嗎？2019-01-14Oracle並行
- 前端介面做得是夠炫了 可是後端不穩2013-06-09前端後端
- 爆火的ChatGPT太強了！寫程式碼、改bug，網友：可取代Stack Overflow了2022-12-05ChatGPT