【ogg 】Error Messages（OGG-02563 to OGG-03520）
OGG-02563: Internal LCR column {0} formating error: {1}.
Cause: Internal LCR column format error.
Action: Contact Oracle Support.
OGG-02564: Invalid opcode {0} {1} to format.
Cause: Internal LCR column format error. Invalid operation code found.
Action: Contact Oracle Support.
OGG-02565: Failed to add GGS token for LOB erase on column {0}.
Cause: Internal LCR column format error. Failed to add GGS token.
Action: Contact Oracle Support.
OGG-02566: Failed to add GGS token for LOB trim on column {0}.
Cause: Internal LCR column format error. Failed to add GGS token.
Action: Contact Oracle Support.
OGG-02567: Failed to add GGS token for XMLDIFF on column {0}.
Cause: Internal LCR column format error. Failed to add GGS token.
Action: Contact Oracle Support.
OGG-02568: Failed to add GGS token for XMLUDT on column {0}.
Cause: Internal LCR column format error. Failed to add GGS token.
Action: Contact Oracle Support.
OGG-02569: Failed to add GGS token for XMLUDT on column {0}.
Cause: Internal LCR column format error. Failed to add GGS token.
Action: Contact Oracle Support.
OGG-02570: Invalid numeric data detected. Error converting numeric from Oracle to ASCII on column {0}, raw length {1}, raw data: {2}.
Cause: Internal LCR column format error. Failed to convert numeric data to ASCII format.
Action: Contact Oracle Support.
OGG-02571: Error converting timestamp from Oracle to ASCII format for column {0}.
Cause: Internal LCR column format error. Failed to convert timestamp data to ASCII format.
Action: Contact Oracle Support.
OGG-02572: Error converting day to second interval from Oracle to ASCII format for column {0}.
Cause: Internal LCR column format error. Failed to convert day to second interval data to ASCII format.
Action: Contact Oracle Support.
OGG-02573: Error converting year to month interval from Oracle to ASCII format for column {0}.
Cause: Internal LCR column format error. Failed to convert year to month interval data to ASCII format.
Action: Contact Oracle Support.
OGG-02574: Error converting rowid from Oracle to ASCII format for column {0}.
Cause: Internal LCR column format error. Failed to convert rowid data to ASCII format.
Action: Contact Oracle Support.
OGG-02575: Failed to add lob piece to lobmem.
Cause: Internal error. Failed to add lob piece to lobmem.
Action: Contact Oracle Support with detailed error information.
OGG-02576: Failed to find transaction in COM {0} for LONG_CHUNK with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02577: Failed to retrieve lob lcr from COM {0} with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02578: Failed to find end piece of LONG_CHUNK in COM {0} with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02579: Interleaved pieces of LONG_CHUNK in COM {0} with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02580: Incomplete LONG_CHUNK in COM {0} with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02581: No thread local storage.
Cause: Internal error.
Action: Contact Oracle Support.
OGG-02582: No OCI handle for fetch in thread local storage.
Cause: Internal error.
Action: Contact Oracle Support.
OGG-02583: No Active Data Guard standby database with source-less Extract.
Cause: No Active Data Guard standby database configured for source-less Extract.
Action: Check Oracle GoldenGate and database configurations for valid Active Data Guard standby database.
OGG-02584: Query to Active Data Guard standby database to retrieve applied SCN failed.
Cause: Failed to query applied SCN from Active Data Guard standby database.
Action: Check Oracle GoldenGate and database configurations for valid Active Data Guard standby database.
OGG-02585: Query to source db to retrieve applied SCN of the target standby database failed.
Cause: Failed to query applied SCN of the target standby database.
Action: Check Oracle GoldenGate and database configurations for valid target standby database.
OGG-02586: No applied SCN information available on source database or Active Data Guard.
Cause: Applied SCN information no available on source database or Active Data Guard.
Action: Check Oracle GoldenGate and database configurations for valid standby database.
OGG-02587: No longer able to retrieve applied SCN on source database or Active Data Guard.
Cause: Could not retrieve applied SCN on source database or Active Data Guard.
Action: Check health of standby database.
OGG-02588: Failed to find PLSQL tran in COM {0} with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02589: Failed to retrieve PLSQL large arg lcr from COM {0} with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02590: Failed to get LCR: {0}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02591: Error (%hd, string) adding LCR item to transaction {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02592: Failed to find transaction in COM {0} for LONG_CHUNK with xid {1}.
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02593: Extra items in COM (row_count={0}; chunk_count={1})
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02594: Found gap in LOB (expected offset={0}; LCR offset={1})
Cause: Internal LCR transfer error.
Action: Contact Oracle Support.
OGG-02595: Missing decryption key, failed to process command table {0}.
Cause: Command table found in the AES encrypted file, but the decryption key is missing.
Action: Configure the right decryption key at the default or specified location or configure the command table to pass-thru mode. Contact Oracle Support if assistance is needed.
OGG-02596: ALTID can not be specified with wildcard TABLE specification. {0}.
Cause: The TABLE clause option ALTID PARTITIONOBJID, is specified with wildcard TABLE specification, which is not allowed.
Action: Remove the ALTID PARTITIONOBJID option or use a non-wildcard TABLE specification.
OGG-02597: A database login was not established before {0} clause.
Cause: The [SOURCEDB | TARGETDB] USERID parameter to login to the database was not specified before the TABLE/MAP/PROCEDURE/SEQUENCE clause.
Action: Add the [SOURCDB] USERID parameter before the TABLE/MAP/PROCEDURE/SEQUENCE clause.
OGG-02598: File {0}, with trail format release {1}, is not compatible with the current software version's trail file format release {2}. Modify the file writer's parameter file to generate the appropriate format using the FORMAT RELEASE {2} option.
Cause: The trail version must be the equal to or greater than that of the reader process. LEVEL is an internal option that specifies a compatibility level that is independent of the Oracle GoldenGate software release, which only changes when new functionality is added to a release that affects the trail format. A value of 1 or greater specifies a format that is supported by Oracle GoldenGate release 10.0 and later. A value of 0 specifies a format that is supported by Oracle GoldenGate releases prior to 10.0.
Action: Edit the parameter file to set the EXTFILE, EXTTRAIL, RMTFILE, or RMTTRAIL parameter FORMAT RELEASE option to write a trail version that is backward compatible with the reader process. Next, issue the issue the ALTER EXTRACT command with the ETROLLOVER option in GGSCI. The rollover creates a new trail file in the specified format. Start Extract to begin writing to the new trail file. For more information, see the Oracle GoldenGate reference documentation for the trail or file parameters.
OGG-02599: ALTID can not be specified in a MAP statement if DDL is enabled.
Cause: The MAP clause option ALTID PARTITIONOBJID is specified when DDL is enabled. DDL capture and Replication is not supported when using the clause ALTID option.
Action: Remove either the ALTID PARTITIONOBJID option or the DDL parameter in the Capture parameter file.
OGG-02600: OCI error ({0,number,0}-{1}) when validating checkpoint table {2}, SQL: {3}. The table may not exist. To add it, use the ADD CHECKPOINTTABLE command.
Cause: Validation of the checkpoint table failed, possibly because the checkpoint table does not exist.
Action: Add the checkpoint table by using the ADD CHECKPOINTTABLE command in GGSCI. For help, see the ggsci online help or the Oracle GoldenGate reference documentation.
OGG-02601: OCI error ({0,number,0}-{1}) when validating supplemental checkpoint table {2}, SQL: {3}. The table may not exist. If you upgraded from Oracle GoldenGate 11.2.1.0.0 or earlier, add this table with the UPGRADE CHECKPOINTTABLE command.
Cause: Validation of the supplemental checkpoint table failed, possibly because the table does not exist. This table is required for upgrades from version 11.2.1.0.0 or earlier.
Action: Add the supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI after an upgrade from release 11.2.1.0.0 or earlier. For help, see the ggsci online help or the Oracle GoldenGate reference documentation.
OGG-02602: Unable to determine the supplemental checkpoint table name from the checkpoint Table.
Cause: The process could not determine the name of the supplemental checkpoint table.
Action: Make sure you used valid connection credentials to log into the database with the DBLOGIN command in GGSCI.
OGG-02603: Checkpoint table {0} does not exist. Create this table with the ADD CHECKPOINTTABLE command.
Cause: The checkpoint table does not exist.
Action: Use the ADD CHECKPOINTTABLE command in GGSCI to create the table. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02604: Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command if you have upgraded from release 11.2.1.0.0 or earlier.
Cause: Supplemental checkpoint table does not exist.
Action: Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02605: The use of a checkpoint table is not supported for {0}.
Cause: Oracle GoldenGate does not support the use of a checkpoint table for the specified target database.
Action: None
OGG-02606: Error retrieving information on checkpoint table: {0}. Database error: {1}. Create the checkpoint table with the ADD CHECKPOINTTABLE command.
Cause: Validation of the Checkpoint table failed, possibly because the checkpoint table was not created.
Action: Create the checkpoint table with the ADD CHECKPOINTTABLE command in GGSCI. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02607: Error reading status from the checkpoint table: {0}. Database error: {1}.
Cause: An error occurred while reading status information from the checkpoint table.
Action: Re-create the checkpoint table by using the ADD CHECKPOINTTABLE command in GGSCI. For more information, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02608: Error reading row from checkpoint table: {0}. Database error: {1}.
Cause: An error occurred while reading row data from the checkpoint table.
Action: Re-create the checkpoint table by issuing the ADD CHECKPOINTTABLE command in GGSCI. For more information, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02609: Error allocating statement handle for validating checkpoint table operations. Checkpoint table: {0}. Database error: {1}.
Cause: A statement handle could not be allocated to access the checkpoint table.
Action: Fix the database connectivity problem according to the error message.
OGG-02610: Error retrieving information on checkpoint table: {0}. SQL Statement: {1}. Database error: {2}.
Cause: Validation of the checkpoint table failed, possibly because the table was not created.
Action: Create or re-create the table with the ADD CHECKPOINTTABLE command in GGSCI. For more information, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02611: Error ({0,number,0}-{1}) when validating supplemental checkpoint table {2}, SQL: {3}. The table may not exist. If you upgraded from Oracle GoldenGate 11.2.1.0.0 or earlier, add this table with the UPGRADE CHECKPOINTTABLE command.
Cause: Validation of the supplemental checkpoint table failed, possibly because the table does not exist. This table is required for upgrades from version 11.2.1.0.0 or earlier.
Action: Add the supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI after an upgrade from release 11.2.1.0.0 or earlier. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02612: Supplemental checkpoint table does not exist. Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command if you have upgraded from release 12.1.1.0.0 or earlier.
Cause: The supplemental checkpoint table does not exist.
Action: Create a supplemental checkpoint table with the UPGRADE CHECKPOINTTABLE command in GGSCI. For help, see the GGSCI online help or the Oracle GoldenGate reference documentation.
OGG-02613: Error ({0}) while updating DB checkpoint.
Cause: An error occurred in the database server while updating the database checkpoint table.
Action: Resolve the database error and restart Replicat.
OGG-02615: Login to the database as user {0} failed because of error {1}
Cause: Logon to the database failed because of the reported error.
Action: Correct the error, and then restart the process.
OGG-02616: Unable to initialize database connection because of error {0}
Cause: Logon to the database was successful, but the connection could not be initialized because of the reported error.
Action: Correct the error, and then restart the process.
OGG-02617: A default source catalog name is not specified for the SOURCECATALOG parameter.
Cause: The SOURCECATALOG parameter does not contain a specification for the default source catalog name.
Action: Specify the default source catalog name or remove the SOURCECATALOG parameter.
OGG-02618: The SOURCECATALOG parameter is not supported for this database version.
Cause: The parameter file contains the SOURCECATALOG parameter, which is not supported for the database that is configured as the Oracle GoldenGate datasource.
Action: Remove the SOURCECATALOG parameter from the parameter file.
OGG-02619: Wildcards are not supported for the default source catalog name "{0}" in the SOURCECATALOG parameter.
Cause: The SOURCECATALOG parameter specifies a wildcarded name as the default source catalog name. Wildcards are not permitted for the default catalog name.
Action: Specify the full default source catalog name or remove the SOURCECATALOG parameter.
OGG-02620: The source catalog name for table {0} cannot be wildcard because no catalog name or non-wildcard catalog name is specified for target table {1} in TABLE/MAP.
Cause: The source catalog in the TABLE/MAP parameter is wildcarded, but a catalog is not specified or non-wildcard catalog name is specified for the target table. In this case, the source wildcard cannot be resolved to the correct target catalog.
Action: Edit the TABLE/MAP parameter to specify the full source catalog name, or keep the source wildcard but also specify a wildcard catalog name for the target table.
OGG-02621: A catalog name is specified for source table {1} in the TABLE/MAP parameter, but no schema name is specified for target table {0}.
Cause: In the TABLE/MAP specification, a catalog is specified for the source table, but a schema name is not specified for the target table.
Action: Specify a schema name for the target table in the TABLE/MAP statement.
OGG-02622: A catalog name is specified for target table {1} in the TABLE/MAP parameter, but no schema name is specified for source table {0}.
Cause: In the TABLE/MAP specification, a catalog is specified for the target table, but a schema name is not specified for the source table.
Action: Specify a schema name for the source table.
OGG-02623: Default source catalog name {0} will be used for source table name {1} mapping.
Cause: A default source catalog name is specified with the SOURCECATALOG parameter and will be used when mapping the specified source table.
Action: None
OGG-02624: Default source catalog name {0} is specified but schema name is not specified for the source table name {1}.
Cause: A default source catalog name is specified with the SOURCECATALOG parameter, but schema name is not specified for the source table name.
Action: Remove SOURCECATALOG parameter or specify schema name for the source table name.
OGG-02625: Invalid TARGET wildcard table name {0} is specified.
Cause: The wildcard resolution failed because question mark is specified for the target table name or more than one wildcard was specified for a name part.
Action: Fix the syntax. A target wildcarded specification can have only one asterisk (like rpt.* or rpt.tab*). For more information, see TABLE and MAP in the Oracle GoldenGate reference documentation.
OGG-02626: Processing more than {0} direct load rollback records from redo thread# {1} with xid {2,number,0}.{3,number,0}.{4,number,0} (0x{5}.{6}.{7})
Cause: Extract is processing a rollback operation that resulted in more than the stated number of direct load rows being rolled back.
Action: None
OGG-02627: Object with object number {0} is compressed. Table compression is not supported by classic capture.
Cause: Table compression is not supported by Extract in a classic capture configuration.
Action: None
OGG-02628: Missing exclusion specification for {0} parameter.
Cause: An exclusion object specification for TABLEEXCLUDE, SCHEMAEXCLUDE or CATALOGEXCLUDE is not specified.
Action: Specify an object name in the parameter or remove the parameter.
OGG-02629: Wildcarded schema names are not supported for this database. Ignoring SCHEMAEXCLUDE parameter.
Cause: The SCHEMAEXCLUDE parameter is specified for a database that does not support wildcarded schema names.
Action: Remove the SCHEMAEXCLUDE parameter.
OGG-02630: Catalog names are not supported for this database. Ignoring CATALOGEXCLUDE parameter.
Cause: The CATALOGEXCLUDE parameter is specified for a database that does not support wildcarded catalog names.
Action: Remove the CATALOGEXCLUDE parameter.
OGG-02631: NORENAME option is not supported for CATALOGEXCLUDE parameter.
Cause: The CATALOGEXCLUDE parameter does not support a NORENAME option.
Action: Remove the NORENAME option from the CATALOGEXCLUDE parameter.
OGG-02632: Invalid exclusion specification {0} is specified for {1} parameter.
Cause: The parameter contains an invalid exclusion specification.
Action: Specify a valid exclusion specification. For help, see the Oracle GoldenGate reference documentation.
OGG-02633: Exclusion specification {0} for parameter {1} excludes all objects.
Cause: The parameter contains an invalid exclusion specification that excludes all objects from mapping.
Action: Specify a valid exclusion specification. For help, see the Oracle GoldenGate reference documentation.
OGG-02634: Default source catalog name {0} will be used for table exclusion specification {1}.
Cause: A default source catalog name is specified with the SOURCECATALOG parameter and will be used for the table exclusion specification.
Action: None
OGG-02635: The database does not support catalog names. Ignoring SOURCECATALOG parameter {0} specified for TABLE clause '{1}'.
Cause: The source database does not support catalog names.
Action: Remove the SOURCECATALOG parameter.
OGG-02636: The TABLE specification '{0}' for the source table {1} does not include a catalog name. The database requires a catalog name.
Cause: The source table name in the TABLE statement does not include a catalog name. The database requires a catalog name.
Action: Add a catalog name to the source table specification of the TABLE/MAP statement.
OGG-02637: The target catalog name for table {0} cannot have a wildcard because no catalog name is specified for source table {1} in the MAP parameter.
Cause: The target catalog in the MAP parameter is wildcarded, but a catalog is not specified for the source table. The source wildcard cannot be resolved to the correct target catalog.
Action: Edit the MAP parameter to specify the full target catalog name, or keep the target wildcard and specify a catalog name for the target table.
OGG-02638: No schema is specified for table {0} in the MAP clause '{1}'. Schema is required.
Cause: The table specification does not include an explicit schema name.
Action: To specify a schema other than the default login schema, edit the parameter file to specify the correct schema.
OGG-02639: The table specification {0} in the MAP parameter '{1}' includes a catalog name, but the database does not support catalog names.
Cause: The name of the target table in the TARGET clause of the MAP statement includes a catalog name, but the target database does not support catalog names.
Action: Remove the catalog from the table specification.
OGG-02640: The format of trail file {0} does not support catalog names. Remove the catalog name from table specification {1} in TABLE clause '{2}'.
Cause: The trail file format specified by FORMAT RELEASE/LEVEL does not support catalog names, but the table specification includes a catalog name.
Action: Remove the catalog name from the target table specification.
OGG-02641: Source table name {0} in TABLE clause '{1} ' has a wildcarded catalog name. The format of trail file {2} does not support catalog names.
Cause: The trail file format specified by FORMAT RELEASE/LEVEL does not support catalog names. The source table name is being written to the trail file without the catalog name.
Action: Specify a non-wildcarded source catalog name, or specify a trail format that supports catalog names.
OGG-02642: Trail file {0} format does not support catalog names. The catalog name of the source table {1} specified in TABLE clause '{2}' will be removed.
Cause: The trail file format specified by FORMAT RELEASE/LEVEL does not support catalog names. The source table name is being written to the trail file without the catalog name.
Action: None
OGG-02643: Wildcarded catalog name of source table specification {0} cannot be mapped to target table specification {1} that has no catalog name in TABLE clause '{2}'.
Cause: The source table name includes a wildcarded catalog name and is being mapped to a target table name that does not include a catalog name. This is not supported.
Action: Specify a non-wildcarded source catalog name, or specify a target table name that includes a catalog name.
OGG-02644: The catalog portion of source table name {0} in TABLE clause '{1}' will not be written to trail file {2}.
Cause: The catalog portion of the source table name will be removed before being written to the trail, because the source table name is explicitly mapped to a target table name that does not include a catalog name.
Action: None
OGG-02645: Source table name {0} that does not include a catalog name cannot be mapped in TABLE clause '{2} to target table {1} that has a wildcarded catalog na me.
Cause: A source table specification that does not include a catalog name is mapped to a target table specification that includes a wildcarded catalog name.
Action: Specify a non-wildcarded target catalog name, or include a catalog name in the source table specification.
OGG-02646: Source table specification {0} in TABLE clause {1} has no catalog name and will be mapped to target table {2} specification that has a catalog name.
Cause: A source table specification that does not include a catalog name is mapped to a target table specification that includes a catalog name.
Action: None
OGG-02647: Cannot specify table clause '{0}' for trail file {1} because the trail specifies a different target table name format.
Cause: A table name with a catalog name and one without a catalog name cannot be output to the same trail file. A different target table name format is specified by the table clause for the specified trail file.
Action: Remove the catalog name from the TABLE clause or add a catalog name to the TABLE clause, or output the table to a different trail file.
OGG-02648: Table name {0} specified in TABLE/MAP clause '{1}' contains a wildcarded schema or catalog. The database does not support wildcards for those objects.
Cause: Wildcarded schemas or catalogs are not supported by this database.
Action: See the rules for schema and catalog wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.
OGG-02649: Source wildcard specification {0} includes a catalog name, but the source table name {1} does not include a catalog name.
Cause: A catalog name is specified for the source wildcard specification, but the source table name does not include a catalog name.
Action: Remove the catalog name from the source wildcard specification.
OGG-02650: Source wildcard specification {0} does not include a catalog name, but the source table name {1} includes a catalog name.
Cause: A catalog name is not specified for the source wildcard specification, but the source table name includes a catalog name.
Action: Add a catalog name to the source wildcard specification.
OGG-02651: Parameter {0} syntax error: {1}
Cause: The syntax of the specified parameter is incorrect.
Action: Check for spelling errors, or see the Oracle GoldenGate reference documentation for the correct syntax.
OGG-02652: Missing interval value.
Cause: The interval value was not specified.
Action: Specify the interval value.
OGG-02653: Invalid interval value {0} was specified.
Cause: An invalid interval value was specified.
Action: Specify the correct interval value.
OGG-02654: Missing time qualifier in interval specification.
Cause: The time/interval value was specified without a time qualifier such as DAYS, HOURS, MINUTES, or SECONDS.
Action: Specify the time qualifier.
OGG-02655: Invalid time qualifier {0} was specified. Time qualifier must be either DAYS, HOURS, MINUTES or SECONDS.
Cause: An invalid time qualifier was specified for the time/interval value.
Action: Specify a valid time qualifier.
OGG-02656: The specified interval value {0} is out of range. The value must be between {1} and {2}.
Cause: The specified interval value is out of range.
Action: Specify a valid interval value.
OGG-02657: No schema is specified for table exclusion specification '{0}'.
Cause: A schema was not explicitly specified for the TABLEEXCLUDE parameter and there was no default schema.
Action: Edit the parameter file to specify the correct schema, or use the default schema by adding DBLOGIN to the parameter file.
OGG-02658: No schema is specified for table exclusion specification '{0}'. Using default schema {1}.
Cause: A schema was not explicitly specified for the TABLEEXCLUDE parameter. The process is using the default login schema.
Action: To use a schema other than the default login schema, edit the parameter file to specify the correct schema.
OGG-02659: Could not retrieve logon catalog name
Cause: A database error may be preventing the process from retrieving the logon catalog name.
Action: Contact Oracle Support.
OGG-02660: Retrieving table definition for table specification {0} is prohibited when logged on to database {1}.
Cause: An attempt to retrieve the table definition failed because the process is not logged on to the root level database.
Action: Either log on to the root database or specify a catalog name in the logon to the current database.
OGG-02661: Replicat is not allowed to log on to the root level database.
Cause: Replicat logged into the root level database.
Action: Modify the Replicat parameter file so that Replicat logs on to a pluggable database, not the root database.
OGG-02662: Exclusion specification {0} specified for {1} parameter has a catalog name, but catalog names are not supported by this database.
Cause: The parameter contains an exclusion specification that specifies a catalog name, but the database does not support catalogs.
Action: Remove the catalog name from the exclusion specification.
OGG-02663: Missing catalog name in exclusion specification {0} specified for {1} parameter.
Cause: The catalog name is missing from the exclusion specification.
Action: Specify a catalog name in the exclusion specification, or specify a default catalog name with the SOURCECATALOG parameter.
OGG-02664: Exclusion specification {0} specified for {1} parameter has a wildcarded schema, but the wildcarded schema name is not supported for the database.
Cause: Wildcarded schemas are not supported for this database.
Action: See the rules for schema wildcarding in the Oracle GoldenGate documentation or contact Oracle Support.
OGG-02665: Login catalog name {0} will be used for target table name {1} mapping.
Cause: A catalog name is not specified for the target table for the database. Login catalog will be used when mapping the specified target table.
Action: None
OGG-02666: Could not retrieve default catalog name
Cause: A database error may be preventing the process from retrieving the default catalog name.
Action: Contact Oracle Support.
OGG-02667: Default catalog name {0} will be used for table exclusion specification {1}.
Cause: A default catalog name will be used for the table exclusion specification.
Action: None
OGG-02668: Default catalog name {0} will be used for source table name {1} mapping.
Cause: A default catalog name will be used when mapping the specified source table.
Action: None
OGG-02669: Default catalog name {0} will be used for target table name {1} mapping.
Cause: A default catalog name will be used when mapping the specified target table.
Action: None
OGG-02670: Default source catalog name {0} will be used for schema exclusion specification {1}.
Cause: A default source catalog name is specified with the SOURCECATALOG parameter and will be used for the schema exclusion specification.
Action: None
OGG-02671: A database login was not established to retrieve a table definition.
Cause: The [SOURCEDB | TARGETDB] USERID parameter to login to the database was not specified before the TABLE parameter.
Action: Add the [SOURCDB] USERID parameter before the TABLE parameter.
OGG-02672: No DB login established to retrieve a definition for table {0}
Cause: The [SOURCEDB | TARGETDB] USERID parameter must be specified in order to retrieve a definition from the database.
Action: Add the [SOURCDB | TARGETDB] USERID parameter before the TABLE or MAP parameter.
OGG-02678: Unrecognized GLOBALS parameter {0} is ignored. Parameter could be misspelled or unsupported.
Cause: The parameter is either specified incorrectly or is not valid for this version of Oracle GoldenGate.
Action: Check the GLOBALS parameter file for the correct syntax, spelling, and any required terminators such as the semi-colon. Also make certain the parameter is supported for this version of Oracle GoldenGate. To do both of those things, check the reference documentation for your version of Oracle GoldenGate.
OGG-02679: The Replicat process logged on to database {0} and can only apply to that database.
Cause: Replicat can only apply to the database it logged on to, and cannot apply to any other database. Informational only.
Action: None
OGG-02680: ENABLECATALOGNAMES parameter is specified, enabling catalog name support.
Cause: ENABLECATALOGNAMES parameter is specified in GLOBALS and the catalog name is supported.
Action: None
OGG-02681: The catalog name is missing. Fully qualified name for table {0} is required for root database
Cause: The process logged on to the root level database, but the table name was specified without a catalog name. A three-part name is required to log onto the root database.
Action: Add a catalog name to the table specification.
OGG-02682: Cannot execute a command to catalog {0} while logged in to catalog {1}
Cause: A process can only execute a command to its login catalog.
Action: Specify a catalog that is the same as the login catalog or log in to the root level database.
OGG-02683: Invalid schema specification "{0}" for ADD/INFO/DELETE SCHEMATRANDATA.
Cause: An invalid schema was specified for the ADD/INFO/DELETE SCHEMATRANDATA command.
Action: Specify a valid schema.
OGG-02684: Table definition output {0} {1} is specified but the output format level {2} is already specified.
Cause: Table definition file output format is specified twice or more in different output format using FORMAT LEVEL/RELEASE parameter.
Action: Specify table definition file output format only once.
OGG-02685: Ignoring SOURCECATALOG parameter {0} specified for TABLE parameter '{1}' which contains a catalog specification.
Cause: The TABLE clause already specifies a catalog name for the specified source table.
Action: Remove the SOURCECATALOG parameter or remove the catalog name from the source table name.
OGG-02686: Default catalog name {0} will be used for schema exclusion specification {1}.
Cause: A default catalog name will be used for the schema exclusion specification.
Action: None
OGG-02687: Invalid catalog name "{0}" is specified for SOURCECATALOG parameter.
Cause: The catalog name specified for the SOURCECATALOG parameter is invalid.
Action: Specify the correct catalog name.
OGG-02688: Table definition output character set {0} is specified, but the output character set {1} is already specified.
Cause: Multiple CHARSET parameters exist and specify different values for the output character set of the definitions file.
Action: Specify only one CHARSET definition for the character set of the DEFGEN output file.
OGG-02689: The NOCATALOG parameter is specified after the TABLE parameter.
Cause: NOCATALOG parameter is specified after TABLE parameter.
Action: Specify the NOCATALOG parameter before any TABLE parameters.
OGG-02690: Wildcard catalog name {0} is incompatible with the NOCATALOG parameter.
Cause: A catalog name is specified in a TABLE parameter, but the NOCATALOG parameter is specified for that TABLE parameter.
Action: Remove the NOCATALOG parameter or remove the catalog specification from the TABLE specification.
OGG-02691: Cannot specify TABLE parameters with diffre ntcatalog names when Defgen parameters NOCATALOG or FORMAT LEVEL 3 or less is specified.
Cause: The NOCATALOG parameter or FORMAT LEVEL 3 or less is being used in the Defgen parameter file to prevent the output of catalog names to the definitions file, but the TABLE parameters specify different catalog names.
Action: Remove the NOCATALOG or FORMAT LEVEL parameter to allow three-part names from different catalogs to be written to the definitions file. To keep those parameters, specify TABLE parameters that all have the same catalog name.
OGG-02692: Cannot specify format level of {0} for definitions file {1} that already has a format level of {2}.
Cause: The output mode of DEFGEN is set to APPEND mode, and the specified format level is different from the current format level of the existing definitions file. In APPEND mode, the existing file and new output must be the same format level.
Action: Remove the FORMAT parameter.
OGG-02693: The checkpoint table name cannot contain a wildcard.
Cause: The checkpoint table name specified with CHECKPOINTTABLE in the GLOBALS file cannot contain a wildcard.
Action: Specify a non-wildcarded name.
OGG-02694: ASCII trail format does not support DDL.
Cause: The DDL option is enabled for one or more trails that are configured for FORMATASCII, FORMATSQL or FORMATXML output.
Action: Remove the DDL option or do not specify FORMATASCII, FORMATSQL or FORMATXML as the trail format.
OGG-02695: ANSI SQL parameter syntax is used for parameter parsing.
Cause: Default parameter syntax is used.
Action: None
OGG-02696: NON-ANSI SQL parameter syntax is used for parameter parsing.
Cause: NOUSEANSISQLQUOTES parameter is specified for compatibility with legacy parameter syntax.
Action: None
OGG-02697: LOB write failed. LOB exceeds the supported size. LOB offset: {0}
Cause: The LOB write operation failed because the size of the LOB is equal to or greater than that maximum supported size of 4GB.
Action: Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02698: LOB trim failed. LOB exceeds the supported size. LOB offset: {0}
Cause: The LOB trim operation failed because the size of the LOB is equal to or greater than that maximum supported size of 4GB.
Action: Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02699: LOB erase failed. LOB exceeds the supported size. LOB offset: {0}, length: {1}
Cause: The LOB erase operation failed because the size of the LOB is equal to or greater than that maximum supported size of 4GB.
Action: Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02700: LOB size exceeds the maximum supported size {0} bytes. LOB offset: {1}, length: {2}
Cause: The LOB size exceeds the Oracle GoldenGate maximum allowed size.
Action: Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02701: LOB size exceeds the maximum supported size {0} bytes after character set conversion. LOB offset: {1}, length: {2}
Cause: The LOB size exceeds the Oracle GoldenGate maximum allowed size after character set conversion.
Action: Remove the specified LOB column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02702: VARCHAR2 size exceeds the maximum supported size 4000 bytes. Table: {0}, Column: {1}
Cause: The VARCHAR2 size exceeds the Oracle GoldenGate Extract maximum allowed size. It is only supported by Integrated Extract and initial data load.
Action: Use Integrated Extract or remove the specified VARCHAR2 column or the table that contains it from the Oracle GoldenGate configuration.
OGG-02703: The trail or definitions file is format level {0} and does not support database character set {1}.
Cause: The specified database character set is not supported by the previous release of Oracle GoldenGate. An older version of Replicat may not be able to apply the data properly.
Action: Contact Oracle Support.
OGG-02704: Failed to read entire LOB column "{0}" of table {1}. Expected length was {2} characters. Only {3} bytes was read.
Cause: Internal LOB read error.
Action: Contact Oracle Support.
OGG-02705: Invalid value given for the DDLOPTIONS parameter {0}
Cause: The specified value is not a valid one for DDLOPTIONS.
Action: See the Oracle GoldenGate reference documentation for further information.
OGG-02706: Unable to set the USE_PASSWORD_VERIFIER_LEVEL to {0} as the requested verifier was not provided in the password.
Cause: The password verifier that was requested was not present in the password string that was generated by the database.
Action: Change the SQLNET.ALLOWED_LOGON_VERSION_SERVER setting to generate the requested password verifier.
OGG-02707: UDT LOB buffer overflow, needed: {0}, allocated: {1}.
Cause: Not enough UDT read buffer was allocated.
Action: Allocate a larger LOB read buffer using the DBOPTIONS LOBBUFSIZE parameter.
OGG-02708: UDT LOB write error: {0}.
Cause: OCI error occurs when writing UDT LOB.
Action: Check the error message detail and resolve the error as described.
OGG-02750: The definition for table {0} from the target database overrides the table metadata from the trail.
Cause: ASSUMETARGETDEFS OVERRIDE was used to override the table metadata from the trail.
Action: None
OGG-02751: Unable to generate metadata record for table {0} because its definition is obtained from an earlier release definitions file, {1}.
Cause: The provided definitions file was generated using format release prior to 12.1.
Action: Regenerate the definitions file using format release 12.1 or later and restart the process.
OGG-02752: The definition for table {0} from definitions file {1} overrides the table metadata from the trail.
Cause: A SOURCEDEFS file was specified with OVERRIDE option to override the table metadata from the trail.
Action: None
OGG-02753: Unable to generate table metadata records because there are no table definitions in {0}.
Cause: Data pump was unable to generate the table metadata when the specified input trail file contained no table metadata.
Action: Perform one of the following steps: Specify a SOURCEDEFS file containing the correct definitions of all the tables in the input trail; 2) Add NO_OBJECTDEFS to the RMTTRAIL option to generate an output trail with no metadata records; 3) Remove the PASSTHRU option from the data pump's parameter file if it's specified.
OGG-02754: Initial load Extract does not support more than 65535 tables.
Cause: Initial load Extract does not support more than 65535 tables.
Action: Reduce the number of tables in the TABLE option.
OGG-02755: Unable to process metadata record for {0} from trail seq# {1,number,0} at RBA {2,number,0}.
Cause: An error occurred when deserializing the metadata record at the specified position in the trail file. This may be due to incorrect encryption key or algorithm provided to the process.
Action: None
OGG-02756: The definition for table {0} is obtained from the trail file.
Cause: The definition for the specified table is obtained from the trail file.
Action: None
OGG-02757: Trail file {0} contains no table definition for {1}.
Cause: Data pump or Replicat encountered a trail file with no table definitions after the definition for the specified table was Extracted from a previous file sequence.
Action: If SOURCEDEFS is specified in the parameter file then verify the source definitions file contains the correct definitions for all the tables in the specified trail file then restart the application. If SOURCEDEFS is not specified then add a SOURCEDEFS option with a correct definitions file then restart the application.
OGG-02758: The definition for table {0} is obtained from definitions file {1}.
Cause: The definition for the specified table is obtained from a source definitions file.
Action: None
OGG-02759: The definition for table {0} is obtained from the target database.
Cause: The definition for the specified table is obtained from the target database.
Action: None
OGG-02760: ASSUMETARGETDEFS is ignored because trail file {0} contains table definitions.
Cause: Replicat ignored ASSUMETARGETDEFS because the table definitions from the specified trail file were more reliable.
Action: Perform one of these actions: * Remove the ASSUMETARGETDEFS parameter. * Append OVERRIDE to the ASSUMETARGETDEFS parameter if you want the process to use the table definitions from the target database. Note that doing this may result in data corruption if the target table definitions are not in sync with the trail records.
OGG-02761: Source definitions file, {0}, is ignored because trail file {1} contains table definitions.
Cause: Data pump and Replicat ignored the source definitions files because the table definitions from the specified trail file were more reliable.
Action: Perform one of these actions: * Remove the SOURCEDEFS parameter. * Append OVERRIDE to the SOURCEDEFS parameter if you want the process to use the source definitions file. Note that doing this may result in data corruption if the source definitions file is not in sync with the trail records.
OGG-02762: NO_USE_TRAILDEFS is specified. All table definitions from trail files are ignored.
Cause: The global parameter, NO_USE_TRAILDEFS, was specified when the trail file contains table definitions."
Action: Remove NO_USE_TRAILDEFS from the GLOBALS parameter file to use the table definitions from the trail and avoid this message.
OGG-02763: Unable to retrieve catalog metadata: {0}.
Cause: The query to retrieve catalog metadata did not complete successfully.
Action: Make sure the Extract user has privileges to query catalog metadata.
OGG-02764: OBJECTDEFS is ignored when the input trail file does not have full table metadata or NO_USE_TRAILDEFS is specified.
Cause: Pump ignored the OBJECTDEFS option and generated metadata records with no table definition when the table definitions from the input trail file were not available or not used.
Action: None
OGG-02765: Trail format version must be 12.2 or higher to Extract changes from multiple catalogs with mixed character sets or time zones.
Cause: The trail format release is prior to Oracle GoldenGate 12c (12.2.1)
Action: None
OGG-02766: Unrecognized metadata record type {2}.
Cause: This process encountered an unsupported metadata record type. This is likely because the input trail was generated from a later Oracle GoldenGate release.
Action: Re-generate the input trail using a lower FORMAT RELEASE version or upgrade existing GoldenGate.
OGG-02767: The metadata for {0} is obtained from the target database as the records for this table are mapped based on the TARGETDETS from a different database type.
Cause: Replicat assumed the metadata from the target database for the specified table because the metadata in the trail was based on a target defs file generated by a database of a type different from the source.
Action: Avoid using TARGETDEFS by moving the mapping parameters from Extract to Replicat.
OGG-02768: All SOURCEDEFS statements must have the same OVERRIDE option.
Cause: You cannot define multiple SOURCEDEFS statements with different OVERRIDE options.
Action: Modify the SOURCEDEFS statements to use the same OVERRIDE option.
OGG-02800: Parameter {0} can only be used when Extract is connected to a standby database.
Cause: This parameter was used when Extract was connected to the primary database. It must only be used when Extract connects to a standby database.
Action: Remove the parameter from the parameter file or move Extract to the standby database.
OGG-02801: Parameter MINEFROMACTIVEDG can only be used when the database is in READ ONLY mode.
Cause: The parameter MINEFROMACTIVEDG was used with a database that is not in READ ONLY mode.
Action: Remove the parameter or alter the database to READ ONLY mode.
OGG-02802: Classic Extract failed to retrieve the current system SCN from database.
Cause: The database is in a corrupted or unstable state.
Action: Resolve the database issue.
OGG-02803: Encountered a Data Guard role transition. Alter Extract to SCN {0} and restart Extract, or recreate Extract with the correct number of threads at SCN {0}.
Cause: Extract detected a role transaction.
Action: If the new thread number matches the original thread number after the switch, alter to specified SCN and restart Extract with proper parameter setting. If the old and new thread numbers do not match, recreate Extract from the specified SCN.
OGG-02804: Failed to fetch current resetlogs_id from database view.
Cause: An error occurred when fetching current resetlogs_id from the database view.
Action: Contact Oracle support.
OGG-02805: Resetlogs_id from file header {0} doesn't match expected value of {1}.
Cause: resetlogs_id from Oracle redo log files does not match expected value.
Action: Make sure old abandoned logs are deleted from system views on logs or archived log.
OGG-02806: Extract is waiting for logs to become available based on time {0} from incarnation with relogs_id of {1}.
Cause: Extract cannot find logs from said incarnation based on timestamp given.
Action: Make sure log transporter is running and logs are being transferred.
OGG-02807: Extract is waiting for logs to become available based on SCN {0} from incarnation with relogs_id of {1}.
Cause: Extract cannot find logs from said incarnation based on scn value given.
Action: Make sure log transporter is running and logs are being transferred.
OGG-02808: Standby database is not running. Start it, then start Extract again.
Cause: The Extract process tried to capture from a standby database that is not running.
Action: Start the standby database.
OGG-02809: Oracle Managed Redo Process(MRP) is not running on the Standby database.
Cause: Oracle Managed Redo Process (MRP) is not running.
Action: Start the Oracle Managed Redo Process (MRP).
OGG-02810: A relative timestamp, such as NOW, was used as starting position for Extract on an Oracle Active Data Guard standby database.
Cause: A relative value was specified as the start position for this Extract. However, only an SCN or timestamp value can be used when capturing data from an Oracle Active Data Guard standby database.
Action: Start Extract at a specific SCN or timestamp. For help with START EXTRACT syntax, issue the HELP command in GGSCI, or see the Oracle GoldenGate reference documentation.
OGG-02811: Resetlogs change# does not match expected value. Expecting {0} or {1}, retrieved {2}.
Cause: Extract attempted to capture data from a database incarnation that does not match the prior branch. This may be due to multiple role transitions or other database recovery operations.
Action: Contact Oracle Support.
OGG-02812: The USEPREVRESETLOGSID parameter is specified for this process, but the standby database has not been reset.
Cause: The USEPREVRESETLOGSID parameter is specified in the Extract parameter file. However, the standby database was not reset and there is no data from the previous incarnation to capture. This parameter should only be used to capture data from a previous incarnation of the database.
Action: Remove the USEPREVRESETLOGSID parameter from the Extract parameter file.
OGG-02813: Cannot access database {0} to capture table {1}. Verify database name and login privileges.
Cause: The specified container database does not exist or the login user does not have sufficient privileges to access the container database.
Action: Specify the correct container database name or make certain the Oracle GoldenGate user has sufficient privileges to access the container database. Consult the Oracle GoldenGate documentation for Oracle Database. If the problem persists, contact Oracle Support.
OGG-02814: DDLOPTIONS ADDTRANDATA is not supported on read only database
Cause: This parameter leads to an attempt to ADD TRANDATA on new object and is not allowed.
Action: Delete or comment out the DDLOPTIONS ADD TRANDATA parameter.
OGG-02815: Detecting thread {0} is down at primary database when positioning based on SCN {1}.
Cause: Extract detects that a thread on the primary database is down.
Action: Ensure that this down thread is intended.
OGG-02816: In ADG mode, ADGTIMEOUT value {0} must be greater than ADGAPPLYCHECKFREQ value {1}
Cause: Value for ADGTIMEOUT parameter (default is 30 seconds), must be greater than value for ADGAPPLYCHECKFREQ (default is 3 seconds).
Action: Increase ADGTIMEOUT value, or decrease ADGAPPLYCHECKFREQ value.
OGG-02817: DBOPTIONS FETCHTIMEOUT value {0} must be greater than FETCHCHECKFREQ value {1}
Cause: Value for FETCHTIMEOUT parameter (default is 30 seconds), must be greater than value for FETCHCHECKFREQ (default is 3 seconds).
Action: Increase FETCHTIMEOUT value, or decrease FETCHCHECKFREQ value.
OGG-02900: Replication of UDT and ANYDATA from redo logs is disabled. Trail FORMAT RELEASE must be 12.1 or later. Use fetch instead.
Cause: Trail FORMAT RELEASE must be 12.1 or later.
Action: To support Replication of UDT and ANYDATA from redo logs, you must set FORMAT RELEASE to release 12.1 or later.
OGG-02901: Replication of UDT and ANYDATA from redo logs is not supported with the Oracle compatible parameter setting. Using fetch instead.
Cause: Replication of UDT and ANYDATA from redo logs requires Oracle compatible parameter 12.0.0.0.0 or later.
Action: See the Oracle GoldenGate documentation for help with required Oracle database compatible parameter setting requirements.
OGG-02902: Replication of UDT and ANYDATA from redo logs is not supported because the patch required for Oracle database is missing. Use fetch instead.
Cause: The patch that is required to Replicate UDT and ANYDATA from redo logs cannot be found.
Action: Apply Oracle Patch 18038108 to the source database.
OGG-02903: Replication of UDT and ANYDATA from redo logs is not supported because the Oracle database version is not release 12.1 or later.
Cause: Replication of UDT and ANYDATA from redo logs requires Oracle 12.1.0.1 or higher version.
Action: Upgrade to Oracle Database release 12.1.0.1 or later. For Oracle Database release 12.1.0.1, apply Oracle Patch 18038108 to the target database.
OGG-02904: Replication of PARTIAL XML containing NCHAR/NVARCHAR/NCLOB data may cause divergence.
Cause: Full support to NCHAR/NVARCHAR/NCLOB in PARTIAL XML requires Oracle Database release 12.1.0.1 or later versions. For Oracle Database release 12.1.0.1, apply Oracle Patch 18038108 to the target database.
Action: The workaround is to use the FETCHPARTIALXML option in Extract so that Replicat does not encounter PARTIAL XML. Contact Oracle support.
OGG-02905: Replication of OID column in object tables may diverge.
Cause: Extract is not configured to capture DML from CREATE TABLE AS SELECT statement.
Action: Configure Extract to capture DML from CREATE TABLE AS SELECT statement, and then restart the process.
OGG-02906: Replication of UDT and ANYDATA from redo logs requires Replicat 12.1.2.1.0 or later.
Cause: Replication of UDT and ANYDATA from redo logs may diverge if Replicat 12.1.2.1.0 or later is not used.
Action: Make sure that Replicat 12.1.2.1.0 or later is used. Ignore this message if you are using the right version.
OGG-02907: User provided parameters conflict.
Cause: _LOGMINER_GET_CTAS_DML and GETCTASDML cannot conflict.
Action: Change _LOGMINER_GET_CTAS_DML or GETCTASDML.
OGG-02908: CTAS not supported with DDL trigger metadata.
Cause: You cannot CTAS parameter while running with DDL metadata trigger.
Action: Remove GETCTASDML from your parameter file or run with no DDL metadata trigger.
OGG-02909: CTAS not supported with Replicat versions lower than 12.1.2.1.0.
Cause: CTAS functionality must be used with Replicat versions at or above 12.1.2.1.0.
Action: Ensure that the trail files produced with CTAS enabled are not consumed by Replicat versions less than 12.1.2.1.0.
OGG-02910: Sequence {0} not processed, sequence values are synchronized at run-time
Cause: SEQUENCE capture is not supported by initial load capture, and is ignored.
Action: None
OGG-02911: Processing table {0}
Cause: Inital load capture is processing the table.
Action: None
OGG-02912: Patch 17030189 is required on your Oracle mining database for trail format RELEASE 12.2 or later.
Cause: The patch that is required by Integrated Dictionary cannot be found.
Action: Either apply Oracle Patch 17030189 to the mining database, or change the trail format to RELEASE 12.1 (or earlier). If neither of these options are viable, as a temporary workaround you may apply script prvtlmpg.plb (included in the Oracle GoldenGate installation directory) to the mining database.
OGG-02913: Metadata format of the definitions file for table {0} does not match trail format.
Cause: The definitions file uses a metadata format that is incompatible with the trail format.
Action: Regenerate the definitions file using the correct metadata format then restart the application.
OGG-02914: Unsupported XML storage option encountered for table {0}, column {1}.
Cause: The specified XML column uses a storage option that is not supported.
Action: Exclude the table from the TABLE or MAP parameter. For supported storage options, see the Oracle GoldenGate documentation.
OGG-02915: Extract is configured with multiple incompatible trail formats.
Cause: Extract is configured with multiple trail formats that are not compatible with each other.
Action: Configure Extract to use compatible trail formats. For compatibility of different trail formats, see the Oracle GoldenGate documentation.
OGG-02916: Global commit serialization is specified, {0} cannot be specified for a specific catalog without specifying no commit serialization for it.
Cause: Global commit serialization is specified for all PDB's, which is not compatible with apply_parallelism which is specified for a specific PDB.
Action: When doing override, no commit serialization needs to be specific first.
OGG-02917: LONG and partial LOB updates written as UNIFIED UPDATE records require Replicat 12.3.0.1.0 or later.
Cause: Extract is configured to write LONG and partial LOB updates as UNIFIED UPDATE records.
Action: To avoid downstream Replicat failures, validate that all Replicats consuming this trail are at version 12.3.0.1.0 or later.
OGG-02918: Monitoring parameters in the GLOBALS file are ignored in Microservices Architecture mode.
Cause: Monitoring parameters in the GLOBALS file are not recognized or used in Microservices Architecture mode.
Action: Remove monitoring parameters from the GLOBALS file in Microservices Architecture mode.
OGG-02919: Parameter [enablemonitoring] has unrecognized keyword or extra value "{0}".
Cause: The specified data store type is not valid.
Action: Correct the data store type.
OGG-02920:Parameter TRANLOGOPTIONS SOURCE_OS_timezone must be specified, but it is not.
Cause: The OS time zone of the source database must be specified if it is different from the OS time zone of the Extract process.
Action: Specify the OS time zone of the source database using the TRANLOGOPTIONS SOURCE_OS_timezone parameter.
OGG-02921:Invalid TRANLOGOPTIONS SOURCE_OS_timezone value: {0}
Cause: Parameter TRANLOGOPTIONS SOURCE_OS_timezone is set to an invalid value.
Action: Specify a valid value. For more information, see the Oracle GoldenGate reference documentation.
OGG-03000: Table {0} has a lower case ASCII, non-ASCII character or special character such as white space or dot that is not supported when NOEXTATTR option is specified.
Cause: DEFGEN was run with the NOEXTATTR parameter, and the specified table contains a lower case ASCII, non-ASCII or special character.
Action: Exclude the table from the DEFGEN parameter file, or run DEFGEN without the NOEXTATTR parameter.
OGG-03001: Column {0} of table {1} has a lower case ASCII, non-ASCII character or special character that is not supported when NOEXTATTR option is specified.
Cause: DEFGEN was run with the NOEXTATTR parameter, and the column of the specified table contains a lower case ASCII, non-ASCII or special character, such as a white space or dot.
Action: Exclude the table from the DEFGEN parameter file, or run DEFGEN without the NOEXTATTR parameter.
OGG-03002: Target table {0} does not exist. Inexact wildcard match table {1} is being used for target table.
Cause: No table name exactly matches the target wildcard specification. A table with a name that is an inexact match was used as the target.
Action: None required.
OGG-03003: Target table {0} has a lower case ASCII, non-ASCII or special character, such as white space or dot, that is incompatible with trail format level {1}.
Cause: The name of the target table is incompatible with a trail format that is prior to the 11.2.1 release format.
Action: Exclude or rename the table that is in the TARGET clause, or specify 11.2.1 or later for the FORMAT RELEASE option the of EXTTRAIL, RMTTRAIL, EXTFILE, or RMTFILE parameters.
OGG-03004: Unknown source column character set. Cannot map source column {0} to target column {1}
Cause: The trail file is written by Extract version 11.1 or earlier, but the _TRAILCHARSET parameter is specified.
Action: Specify the _TRAILCHARSET parameter or do not map a CHAR/VARCHAR column to an NCHAR/NVARCHAR column.
OGG-03005: Unable to find matching parenthesis for token {0} at location {1}.
Cause: There is a syntax error in the parameter file.
Action: Fix the syntax error in the token specification that contains incomplete parentheses.
OGG-03006: Source database character set or Target client character set is missing. OGG character set conversion is disabled.
Cause: Source database character set or Target client character set is missing.
Action: Set up character set or Target client character set.
OGG-03007: Invalid or unsupported character set {0} specified with {1} parameter.
Cause: An invalid or unsupported character set is specified with the _TRAILCHARSET parameter.
Action: Specify a valid character set, and then restart Replicat.
OGG-03010: Performing implicit conversion of column data from character set {0} to {1}.
Cause: Oracle GoldenGate is performing character set conversion because source data character set differs from target data character set.
Action: None required.
OGG-03014: Source column {0} has more characters than target column {1} can hold. Some source characters will not be mapped during conversion from source character set {2} to target character set {3}.
Cause: The source column has more characters than the target column can hold.
Action: Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03015: Character set conversion failure occurred between source column {0} and target column {1} when converting from source character set {2} to target character set {3}. Error code: {4}
Cause: An internal error occurred during character set conversion.
Action: Save the error message and contact Oracle GoldenGate Support.
OGG-03017: Target column {1} length becomes zero when converting from source column {0} character set {2} to target character set {3}.
Cause: This message is for sanity checking and should not occur in a production environment.
Action: Contact Oracle Support.
OGG-03018: Alternative format data found (code = {0}). Character set conversion was not performed.
Cause: Data of an alternative format was processed. Examples are binary XML, XML diff, or partial LOB.
Action: None
OGG-03019: The column that is being used to evaluate the WHERE clause or FILTER clause is missing in table {0}.
Cause: The column that is being used to evaluate the WHERE clause or FILTER clause is missing, and the process cannot perform the necessary filtering of the data.
Action: Edit the WHERE or FILTER specification in the parameter file to specify a column that cannot contain a missing value.
OGG-03020: Trail character set {0} is specified.
Cause: _TRAILCHARSET parameter is specified.
Action: None
OGG-03021: Trail character set {0} is specified with REPLACEBADCHAR option. Invalid characters will be replaced by substitute character.
Cause: _TRAILCHARSET parameter is specified with REPLACEBADCHAR option.
Action: None
OGG-03022: Unexpected return code {1} received while attempting to retrieve the {0} CCSID values.
Cause: SQLFetch returned an unexpected return code from select getvariable() for specified CCSID values.
Action: Contact Oracle Support with the details from this message.
OGG-03023: {0} CCSID {1} is not recognized.
Cause: The CCSID value obtained from DB2 is not recognized by Oracle GoldenGate.
Action: Contact Oracle Support with the details from this message.
OGG-03024: Character data marked as MIXED CCSID was encountered, but no TRAILCHARSET option was specified.
Cause: Character data marked as MIXED CCSID was encountered, but no TRAILCHARSET option was specified.
Action: Add either TRAILCHARSETASCII, TRAILCHARSETEBCDIC, or TRAILCHARSETUTF8 in the Extract parameter file.
OGG-03025: The {0} character set specified for the A2E parameter in the GLOBALS file does not match the database CCSID.
Cause: The character set specified for the A2E parameter in the GLOBALS file does not match the database CCSID.
Action: Either correct the CHARSET specification for the A2E parameter in the GLOBALS file or edit the TABLE specification in the Extract parameter file to avoid processing tables with this native encoding.
OGG-03026: Unexpected return code {0} received while attempting to retrieve the APPLICATION ENCODING SCHEME.
Cause: An attempt to select the APPLICATION ENCODING SCHEME failed. This function is not supported prior to DB2 V9.1.
Action: Ensure that the DEFAULT APPLICATION ENCODING SCHEME is EBCDIC.
OGG-03027: The DEFAULT APPLICATION ENCODING SCHEME is {0}. Only EBCDIC is supported.
Cause: The APPLICATION ENCODING SCHEME was determined to be a value other than EBCDIC.
Action: Either change the value specified for CURRENTAPPENSCH in the ODBC initialization file to EBCDIC or remove the CURRENTAPPENSCH parameter.
OGG-03028: Table {0}, with {1} encoding, cannot be processed with {2} parameter specification.
Cause: A table was encountered with encoding that cannot be processed with the specified TRAILCHARSET parameter.
Action: Correct the parameter file to either eliminate this table from processing or change the TRAILCHARSET specification to a value that supports the data in this table.
OGG-03029: Invalid source table name "{0}" specified.
Cause: An invalid source table name is specified in the TABLE/MAP parameter.
Action: Specify the correct source table name.
OGG-03030: Invalid target table name "{0}" specified.
Cause: An invalid target table name is specified in the TABLE/MAP parameter.
Action: Specify the correct target table name.
OGG-03031: Character set conversion is not supported in a data pump. Incoming ASCII data will not be converted to EBCDIC.
Cause: The character set of the input file does not match the character set of the platform on which the data pump is running.
Action: Note that column data is ASCII and any attempt to process it as EBCDIC will likely fail.
OGG-03032: Character set conversion is not supported in a data pump. Incoming EBCDIC data will not be converted to ASCII.
Cause: The character set of the input file does not match the character set of the plat form on which the data pump is running.
Action: Note that column data is EBCDIC and any attempt to process it as ASCII will likely fail.
OGG-03033: Character set conversion is not supported in a data pump.
Cause: The parameter EBCDICTOASCII was specified in the data pump parameter file.
Action: Remove the parameter EBCDICTOASCII from the data pump parameter file.
OGG-03036: Database character set identified as {0}. Locale: {1}
Cause: The process verified the character set of the database. Informational only.
Action: None
OGG-03037: Session character set identified as {0}.
Cause: The process verified the character set of the database connection. Informational only.
Action: None
OGG-03038: Table {0}, column {1}, data type: {2} supported only for Unicode tables.
Cause: The data type shown is currently only supported for Unicode tables.
Action: Exclude this table from Extract processing, either by removing its explicit specification in the TABLE parameter, or by using the TABLEEXCLUDE parameter if it was included as the result of a wildcard specification.
OGG-03039: Database character set {0} is not supported.
Cause: Database character set is not supported.
Action: Contact Oracle Support.
OGG-03040: Session character set {0} is not supported.
Cause: Session character set is not supported.
Action: Contact Oracle Support.
OGG-03041: Post-DDL command successful: {0}
Cause: Replicat is executing a post-DDL command.
Action: None
OGG-03042: Character set value is not specified for defgen CHARSET parameter.
Cause: No value is specified for the DEFGEN CHARSET parameter.
Action: Specify a character set for the CHARSET parameter in the DEFGEN parameter file.
OGG-03043: Character set value {0} specified for defgen CHARSET parameter is ignored.
Cause: The CHARSET parameter and the NOEXTATTR parameter are both specified in the DEFGEN parameter file. The CHARSET parameter is ignored.
Action: Remove either NOEXTATTR or CHARSET.
OGG-03044: Invalid character set {0} is specified for defgen CHARSET parameter.
Cause: An invalid character set is specified for the Defgen CHARSET parameter.
Action: Specify the correct character set for CHARSET.
OGG-03045: Character set {0} specified for defgen CHARSET parameter is not supported.
Cause: An unsupported character set is specified for the Defgen CHARSET parameter.
Action: Specify a supported character set.
OGG-03046: The definitions file {0} is a version that does not support the extended attributes of character encoding and locale.
Cause: DEFGEN is in APPEND mode, and the existing contents are of an older format that does not include the extended attributes for character encoding and locale. For consistency, appended definitions will not have extended attributes.
Action: Specify the DEFGEN parameter NOEXTATTR to cause DEFGEN to omit the extended attributes, or re-run DEFGEN for all tables to a new file if you want to include attributes that support character encoding and locale. See the Oracle GoldenGate documentation for more information on globalization support.
OGG-03047: Existing defs file {0} has extended attribute. NOEXTATTR parameter is ignored.
Cause: DEFGEN is in APPEND mode, and the existing contents are of the format that includes the extended attributes for character encoding and locale. For consistency, appended definitions will have extended attributes, and NOEXTATTR is being ignored.
Action: Remove the NOEXTATTR parameter from the Defgen parameter file.
OGG-03048: Existing definitions file {0} is written in character set {1}. New definitions are being appended in the same character set.
Cause: DEFGEN APPEND mode is specified. For consistency, the new definitions are being appended in the same character set as those in the existing file.
Action: None
OGG-03049: Existing defs file {0} is written in character set {1}. CHARSET parameter value {2} is ignored.
Cause: Defgen APPEND mode is specified. The character set specified by the CHARSET parameter is different from the one used in the existing definitions file and is being ignored.
Action: None
OGG-03050: Existing definitions file {0} has invalid character set name or the file is corrupted.
Cause: The existing definitions file has an invalid character set. The character set tag may be incorrect, or the file may be corrupted.
Action: Fix the character set tag if it is wrong, or create a new definitions file to replace to corrupt one.
OGG-03051: Invalid character set {0} is specified for defgen UPDATECS parameter.
Cause: An invalid character set is specified for the Defgen UPDATECS parameter.
Action: Specify the correct character set.
OGG-03052: Definitions file is encoded in character set {0}. No character set update is necessary.
Cause: The definitions file is already encoded in the character set specified by the DEFGEN UPDATECS parameter.
Action: None
OGG-03053: Cannot open the definitions file {0} to update the character set. Check file attributes and user permissions.
Cause: The definitions file may be read-only, or the Defgen user does not have permission to modify the file.
Action: Change the attributes of the file or give the DEFGEN user write permission.
OGG-03054: The character set of definitions file {0} was updated from {1} to {2}.
Cause: The DEFGEN parameter UPDATECS is specified, and the character set of the definitions file was updated successfully.
Action: None
OGG-03055: Failed to update character set of definitions file {0} from {1} to {2}. {3}
Cause: The disk may be full or the Defgen user does not have permission to write to the definitions file.
Action: Make sure there is enough disk space for the definitions file, and make sure the DEFGEN user has full permissions on the file.
OGG-03056: Source table {0} column {1} data size exceeds the maximum target table {2} column {3} size. Automatic truncation is enabled for all tables/columns without further warnings.
Cause: The source column data size exceeds the maximum target column size.
Action: Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03057: Unexpected error code {0} while converting column {1} of table {2} from {3} to {4}.
Cause: An unexpected error was encountered during character set conversion.
Action: Contact Oracle Support.
OGG-03058: Cannot identify the character set of the operating system.
Cause: The character set of the operating system is not properly configured.
Action: Check the operating system character set and locale configuration.
OGG-03059: Operating system character set identified as {0}.
Cause: The process verified the character set of the operating system. Informational only.
Action: None
OGG-03060: Source column {0} has more characters than target column {1} can hold. Some source characters will not be mapped during source column character validation of character set {2}.
Cause: The source column has more characters than the target column can hold.
Action: Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03061: Character validation failure occurred between source column {0} and target column {1} when validating source column data that is in character set {2}. Error code: {3}
Cause: An internal error occurred during character validation.
Action: Save the error message and contact Oracle GoldenGate Support.
OGG-03062: Source column {0} contains an invalid character. Cannot write to XML file to convert from source character set {1} to XML encoding {2}.
Cause: The source column contains an invalid character and cannot be converted to XML file encoding.
Action: Do any of the following: Specify another XML encoding, fix the source database data, or use the REPLACEBADCHAR parameter to replace the invalid character.
OGG-03063: Cannot write source column {0} to XML file during conversion from source character set {1} to XML encoding {2}. The source character set is not supported.
Cause: The specified column could not be written to an XML file because Oracle GoldenGate does not support the source character set.
Action: Contact Oracle Support.
OGG-03064: Character set conversion failure occurred between source column {0} and XML file when converting from source character set {1} to XML encoding {2}. Error code: {3}
Cause: An internal error occurred during character set conversion.
Action: Save the error message and contact Oracle GoldenGate Support.
OGG-03065: Source column {0} has more characters than the maximum number of characters that target column {1} can hold. Some source characters will not be mapped during conversion from source character set {2} to target character set {3}.
Cause: The source column has more characters than the target column can hold.
Action: Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03066: Source column {0} has more characters than the maxmum number of characters that target column {1} can hold. Some source characters will not be mapped during source column character validation of character set {2}.
Cause: The source column has more characters than the target column can hold.
Action: Specify another target column or make the target column size equal to, or greater than, the source column size.
OGG-03067: Source Oracle database character set {0} is not supported.
Cause: The source Oracle Database character set is not supported for this database and platform.
Action: Contact Oracle Support.
OGG-03068: Could not initialize large object memory pool.
Cause: This is internal error, failed to initialize memory pool object for large object (LOB).
Action: Contact Oracle Support.
OGG-03069: Unexpected LOB chunk ({0}) found. Expected chunk is 1.
Cause: Unexpected LOB chunk found in the trail file. Trail file may be corrupted.
Action: Check if the trail file has base DML record followed by LOB chunk 1 using logdump. Contact Oracle Support.
OGG-03070: Failed to add LOB chunk in {0}, RBA {1}.
Cause: Failed to add LOB chunk into LOB memory.
Action: Check additional error detail and contact Oracle Support.
OGG-03071: Unexpected LOB record, record fragment or out of row LOB marker in {0}, rba {1}
Cause: Unexpected LOB record found in the trail file. Trail file may be corrupted.
Action: Check additional error detail and contact Oracle Support.
OGG-03506: The source database character set, as determined from the trail file, is {0}.
Cause: The source database character set information in the trail file is being assumed as the source database character set.
Action: None
OGG-03507: The source database character set is {0} as specified by SOURCECHARSET.
Cause: The trail file version is pre-11.2.1, so the character set that is specified with the SOURCECHARSET parameter is assumed as the source database character set.
Action: None
OGG-03508: SOURCECHARSET PASSTHRU is specified. Ignoring the source database character set {1} identified in the trail file.
Cause: The SOURCECHARSET PASSTHRU parameter is specified, which directs the process to pass the data as it exists in the trail record, without performing character set conversion.
Action: None
OGG-03509: Using NLS_LANG character set {0} as the source database character set.
Cause: The version of the trail file is pre-11.2.1 and the SOURCECHARSET parameter is not specified. To assign a character set to the source data, Replicat used the character set that is specified with the NLS_LANG variable.
Action: Specify the source database character set with the SOURCECHARSET parameter.
OGG-03510: The source database character set is unknown, and the SOURCECHARSET parameter is not specified.
Cause: The trail file does not have source character set information and the SOURCECHARSET parameter is not specified. Replicat cannot map the source character data to the target database.
Action: Specify the source database character set with the SOURCECHARSET parameter.
OGG-03514: The SOURCECHARSET and _TRAILCHARSET parameters are both specified in the parameter file. SOURCECHARSET will be used and _TRAILCHARSET will be ignored.
Cause: The deprecated _TRAILCHARSET parameter and the SOURCECHARSET parameter are both specified in the same parameter file.
Action: Remove _TRAILCHARSET and specify the source database character set with SOURCECHARSET.
OGG-03515: Source character set {0} is specified with the SOURCECHARSET parameter.
Cause: The SOURCECHARSET parameter is being used to specify the character set of the source data.
Action: None
OGG-03516: The trail file is version 11.2.1 or later and contains the source character set {1}. The SOURCECHARSET {0} parameter will be ignored.
Cause: Because the trail file is version 11.2.1 or later and contains the source character set, the SOURCECHARSET parameter is unnecessary and is being ignored.
Action: Remove SOURCECHARSET the parameter.
OGG-03517: Conversion from character set {2} of source column {0} to character set {3} of target column {1} failed because the source column contains a character that is not available in the target character set.
Cause: The source column contains a character that is not available in the character set of the target column.
Action: Set the target database character set to the same set or a superset of the source database character set.
OGG-03518: Source column {0} cannot be mapped to target column {1} during conversion from source character set {2} to target character set {3}, because the source or the target character set is not supported.
Cause: Either source or target column character set is not supported.
Action: Contact Oracle Support
OGG-03519: Found NCHAR, NVARCHAR2 or NCLOB attribute in user-defined data type but the required HAVEUDTWITHNCHAR parameter is missing.
Cause: The source database has a user-defined data type with the NCHAR, NVARCHAR2 or NCLOB attribute, but the HAVEUDTWITHNCHAR parameter is not specified in the Replicat parameter file.
Action: Add the HAVEUDTWITHNCHAR parameter to the Replicat parameter file.
OGG-03520: Connecting to the Oracle database using the AL32UTF8 client character set to support a user-defined type that has an NCHAR, NVARCHAR2 or NCLOB attribute.
Cause: The HAVEUDTWITHNCHAR parameter is specified to support user-defined data types that have an NCHAR, NVARCHAR2 or NCLOB attribute.
Action: None