Oracle 11g2.2.1错误代码详解：GoldenGate for Windows/UNIX

需积分: 43 17 浏览量更新于2024-07-21 收藏 676KB PDF 举报

Oracle 11g Release 2 (11.2.1.0.0) 的 GoldenGate for Windows 和 UNIX Error Messages 是一份专门针对 Oracle 数据库管理员设计的文档，提供了在处理 Oracle 数据库时可能遇到的各种错误代码和解决方案。E24874-01 是其中的一个错误代码示例，它可能是与 GoldenGate 服务、数据复制或者数据同步相关的错误。Oracle GoldenGate 是一款强大的数据集成工具，用于实时或异步地在不同的数据库系统之间传输数据。这份文档包含了详细的错误代码描述，如 E24874-01，它可能会指示问题的具体性质，例如数据传输失败、配置错误或是网络连接问题。对于这个特定错误，用户可以根据提供的信息来诊断问题，可能涉及检查网络设置、源和目标数据库的状态，或者确认 GoldenGate 配置是否正确无误。错误代码文档还强调了版权和许可限制，指出该软件受到法律保护，未经许可不得擅自使用、复制或修改。除非在许可证协议中明确允许，或者法律规定为了实现兼容性而进行逆向工程，否则禁止对软件进行反编译。此外，文档提醒用户，信息可能存在变更且不保证无误，如有发现错误，请提交书面报告。对于政府用户或代表政府接收此软件的个人，文档还提及了适用的美国政府许可条款，这可能包括特定的安全合规性和使用规定。 Oracle 11g2.2.1 的 GoldenGate 错误代码文档是数据库管理员必备的参考资料，帮助他们快速定位和解决在维护Oracle环境中的技术问题，确保数据的完整性和一致性。

Oracle

GoldenGate For Windows and UNIX Error Messages 11g Release 2 (11.2.1)

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00105: {0}: Table lookup in database has either not taken place or failed:

Check return code of GGAttrSet for GG_ATTR_OBJECT_NAME

Cause: The VAM module is attempting to continue processing the metadata for a

table after the VAM API returned an error code on a previous call.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00106: {0}: Adding column before operation type set

Cause: A column value is being passed to the VAM API by the VAM module

before the operation type was set for the record.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00107: GG_OBJ_RECORD: Invalid VAM operation type {0,number,0}

Cause: The operation type attribute being passed to the VAM API by the VAM

module for the VAM API record object is unknown.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00108: GG_OBJ_RECORD: No transaction ID was given in DCI interface call

Cause: No transaction identifier was given in the Direct Call Interface call when

the VAM module was sending a record via the VAM API.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00109: {0} requires maximum protection mode

Cause: This message is specific to the Teradata VAM implementation. The VAM

module sent a prepare transaction record via the VAM API in maximum

performance mode. This is only allowed in maximum protection mode.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00110: {0}: VAM session using local ASCII format timestamps for position

time: Integer format Julian GMT timestamps invalid.

Cause: The VAM module is sending timestamps in a Julian format as an integer

value while the session protocol is to use ASCII timestamps.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00111: {0}: VAM session using integer format Julian GMT timestamps for

position time: Local ASCII format timestamps invalid.

Cause: The VAM module is sending timestamps in an ASCII format while the

session protocol is to use a Julian format passed as an integer.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00112: GG_OBJ_RECORD: {0} must be set before {1}

Cause: A required attribute in the VAM API record object was not set in the right

order by the VAM module.

OGG-00001 to OGG-05502 15

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00113: GG_OBJ_RECORD: GG_ATTR_BEFORE_AFTER can only be used

with GG_OPTYPE_UPDATE

Cause: The VAM module tried to add a before key for a record that is not a

primary key update.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00115: GG_OBJ_RECORD: Attribute {0,number,0}: Null pointer passed for

value

Cause: No buffer was given for the VAM kernel to retrieve the value when the

VAM module is setting an attribute value via the VAM API.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00116: VAMMessage error returned by VAM

Cause: A call from GGSCI to the VAMMessage function implemented by the user

in the VAM module returned with an error.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00117: VAMMessage called before VAM module initialized]

Cause: A call from GGSCI to the VAMMessage function was made before the

VAM module was initialized by a call to VAMInitialize.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00118: {1}: Index {0,number,0} is not in sequential order

Cause: A column was sent out of sequential order by the VAM module when

sending the columns for an insert, update or delete record.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00119: {1}: Index {0,number,0} is out of range of columns added to record

Cause: A column index was sent by the VAM module that is greater than the

number of columns available for the table, when sending the columns for an

insert, update or delete record.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00120: The maximum length allowed for LOB row ID was exceeded

Cause: The maximum size of the buffer available to hold the unique ID generated

for a LOB column was exceeded by the length of the ID that was generated.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00121: {1}: Invalid VAM action {0,number,0}]

Cause: An invalid action type was passed by the VAM module when generating

an informational, warning or error message to be sent to and output by the VAM

API.

Oracle

GoldenGate For Windows and UNIX Error Messages 11g Release 2 (11.2.1)

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00122: Large column support is not implemented in this release

Cause: The maximum column size was exceeded for the column value sent by the

VAM module by the VAM API.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00123: No columns given in DCI interface call

Cause: An insert, update or delete record was sent in the Direct Call Interface call

to the VAM API but no columns for the record were received.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00124: Input data format must be set to zero

Cause: The data format type was set by the VAM module for an attribute passed

to the VAM API that does not possess a data type. The data format value should

be set to zero in this case.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00125: Object {0,number,0}: Attribute {1,number,0}: Column values can not be

set directly

Cause: An attempt was made to use one of the deprecated column attributes that

were originally used to set column values directly.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00126: Object {0,number,0}: Attribute {1,number,0}: String does not contain a

value

Cause: An attribute value was sent by the VAM module as a null-terminated

string, but the null-terminated string has a length of zero instead of a value

(required).

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00127: Object {0,number,0}: Attribute {1,number,0}: Maximum length allowed

exceeded

Cause: The attribute value set by the VAM module for the transaction identifier in

the VAM API record object exceeds the maximum length allowed for transaction

identifier.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00128: Large column processing in progress: invalid data format

Cause: An invalid data format type was passed by the VAM module when

processing large and LOB columns that are sent in blocks across the VAM API.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00129: Adding column before metadata retrieved

OGG-00001 to OGG-05502 17

Cause: The VAM module is sending the column values for a table via the VAM

API before the metadata exchange for that table has taken place.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00130: Table {0}: Column {1} has invalid type for a key column

Cause: The data type of the primary key of this table is not supported by Oracle

GoldenGate as a key.

Action: Specify an alternate key by using a KEYCOLS clause in the parameter file.

For more information, see the Oracle GoldenGate reference documentation. For

supported data types in keys, see the Oracle GoldenGate installation and setup

documentation for your database.

OGG-00133: GG_OBJ_METADATA: {0} returned an error

Cause: There was an error trying to retrieve metadata with the specified VAM

function.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00134: VAM attempting retrieve GG_ATTR_MD_KEYCOLS when GG_

ATTR_MD_KEYCOLS_COUNT is set to zero and there are no key columns to

return

Cause: During the table metadata exchange the VAM module is attempting to

retrieve the value of the KEYCOLS array specified in the Extract parameter file

when there are no KEYCOLS values to retrieve.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00135: GG_OBJ_METADATA: Table {0} has no key columns specified and no

columns that can be used as key columns

Cause: The specified table contains no defined key columns and no other columns

that Oracle GoldenGate can use as key columns. Oracle GoldenGate will attempt

to use all of the columns as a key, or you can specify a KEYCOLS clause in the

source TABLE and target MAP parameters. For more information, see the Oracle

GoldenGate reference documentation.

Action: None

OGG-00136: {0} is a deprecated VAM API function and is longer in use

Cause: An incompatible version of the VAM API module is being used.

Action: Contact Oracle Support to obtain the current version.

OGG-00137: GG_OBJ_COLUMN: Invalid integer type {0,number,0}

Cause: An invalid integer was passed by the VAM module when sending the

columns for an insert, update or delete record via the VAM API.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00138: A SORTTRANLOG extract requires either a TERADATA or a

VAMTRD pre-processor define to build successfully

Cause: This message is specific to the Teradata VAM implementation. The

executable was built without the defines that are required in order to enable the

functionality being requested.

Oracle

GoldenGate For Windows and UNIX Error Messages 11g Release 2 (11.2.1)

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00139: Extract was not built with VAM functionality included

Cause: This Extract build does not include a VAM module.

Action: Obtain the correct Extract build for your database from Oracle.

OGG-00140: Error {0,number,0}, source {1,number,0} - {2}

Cause: Inter-process communication failed. This error is related to the Oracle

GoldenGate vendor access module (VAM).

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00141: {1} Invalid VAM type:{0,number,0}

Cause: The Extract type was not given in the TRANLOGOPTIONS clause in the

Extract parameter file for the Teradata implementation of the VAM API.

Action: Specify the correct Extract type, either COMMITTEDTRANLOG,

CREATETRANLOG, or SORTTRANLOG. If the problem persists, contact Oracle

Support.

OGG-00142: {0}: Adding column before table owner set

Cause: The VAM module sent a column through the VAM API for an insert,

update or delete operation before it set the required record attribute that specifies

the object owner of the record.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00143: {0}: Adding column before table name set

Cause: The VAM module sent a column through the VAM API for an insert,

update or delete operation before it set the required record attribute specifying the

object name of the record.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00144: Fatal error reported by VAM reader thread

Cause: A fatal error was reported in another thread in the multi-threaded VAM

Extract, and this thread terminated because of that error.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00145: VAM function {0} returned unexpected value, {1,number,0}

Cause: One of the VAM API functions implemented in the VAM module returned

an unknown status on completion of the call to that function in the VAM kernel.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

OGG-00146: VAM function {0} returned unexpected result: error {1,number,0} - {2}

Cause: One of the VAM API functions implemented in the VAM module returned

an error status on completion of the call to that function in the VAM kernel, after

previously reporting a fatal error in the call.

Action: Contact Oracle Support or, if you are working with an Oracle GoldenGate

developer, contact that person.

剩余219页未读，继续阅读

山姆大叔De小屋

粉丝: 0
资源: 3

Oracle 11g2.2.1错误代码详解：GoldenGate for Windows/UNIX

ora 错误全集 全部 ora0000-ora32999

ORACLE ORA错误大全

oracle ora06550表达式类型错误

oracle ora-01830

oracle ora 00279,ORA-01113 、ORA-00279

oracle ora-00980

oracle ORA-00921

oracle ora-01555

Oracle ORA-28547

oracle19c ora65096

最新资源

ora 错误全集全部 ora0000-ora32999