Parameterized Connector Errors

Parameterized connector errors are shown as follows:

&H3101 -- 12545 LCFAIL_INVALID_METADATA -- Metadata object ['METADATA'] does not exist

The value provided for the "Metadata" property is not a valid metadata object in the external system. The invalid metadata name will generally be provided. Ensure that a valid value is being provided; common errors include misspellings, incorrect capitalization in case-sensitive systems, and being connected to the wrong database.

&H3102 -- 12546 LCFAIL_TYPE_MISMATCH -- Type mismatch [for field 'FIELDNAME'] [; Connector: TYPE1] [, External: TYPE2]

Data type mismatch. Implicit data conversion is supported only within a data type "class": number, stream, or datetime. When mapping is attempted between data types in different classes (for example, INT to TEXT; or DATETIME to NUMERIC), this error is generated. The fieldname and data types are generally provided in the error text. Ensure that the data types being mapped are members of the same data type class.

&H3103 -- 12547 LCFAIL_DUPLICATE Duplicate object ['NAME']

For database-specific connectors such as Sybase, Oracle, and DB2®, this error indicates that an object of the same name already exists. Select a different name for the object. This error can occur when creating an API object or an external system object, such as creating a new metadata object where one of the same name already exists. Note that if using ODBC, LCFAIL_EXTERNAL would occur in this scenario instead of LCFAIL_DUPLICATE.

&H3104 -- 12548 LCFAIL_FIELD_COUNT_MISMATCH -- Field count mismatch [; Connector: COUNT1, External: COUNT2]

The number of fields did not match between a connector and an external system. In some cases, this problem can be resolved automatically (for example, when writing fields to a external system that supports more fields than provided). In other cases, this error will be generated (for example, when writing 5 fields to a external system which supports 3 fields). To avoid this error, fields can be removed from a fieldlist on a per-operation basis by using field flags.

&H3105 -- 12549 LCFAIL_KEY_COUNT_MISMATCH -- Key count mismatch [; Connector: COUNT1, External: COUNT2]

The number of keys did not match two systems. In cases where keys must be specified for two systems, the same number of keys must be provided for both systems.

&H3106 -- 12550 LCFAIL_STAMPFIELD_TYPE -- Timestamp field ['FIELDNAME'] must be type Datetime [; Actual: TYPE]

A timestamp field provided for the "StampField" property of a connector must represent an external field of type datetime. This error is returned when it is a number or stream data type.

&H3107 -- 12551 LCFAIL_FIELD_TYPE -- Type mismatch for field ['FIELDNAME'] used in this context [; Expected: TYPE1 [, Actual: TYPE2]]

Specific functionality requested of a connector requires that a field be of a particular data type. This error is generated when a specific data type is expected for a particular field, but an incompatible data type is provided.

&H3108 -- 12552 LCFAIL_MERGE_FIELD -- Field mapping failed due to a missing field ['FIELDNAME']

When using the methods LCFieldlist.Merge or MergeVirtual, there was a mismatch between the fieldlists. Either a field in the namelist had no match in the data list, or vice-versa. If such a mismatch occurs and the merge flag LCMERGEF_NAME_LOSS or LCMERGEF_DATA_LOSS is not specified to indicate that loss of fields is allowed, then this error is generated. Ensure that the field indicated in the error has a corresponding field in the other fieldlist.

&H3109 -- 12553 LCFAIL_MISSING_PROPERTY -- No value supplied for required property ['PROPERTY']

The indicated property requires a value for the requested operation, but none was provided. Supply a valid value for the property. Check the documentation for the connector or the method being called (for example, when using the LCConnection.Create method to create an index, the property "Index" is required, and if no value was given, this error would be generated).

&H310A -- 12554 LCFAIL_PROPERTY_CONFLICT -- Conflicting values for properties ['PROPERTY1' and 'PROPERTY2']

The values provided for the two indicated properties conflict with one another. Check the connector documentation for information regarding conflicting property values for this connector.

&H310B -- 12555 LCFAIL_INVALID_PROPERTY -- Invalid property ['PROPERTY']

The attempt to get or set the indicated property failed because it is not supported by the connector. Check the connector documentation for more information on supported properties for this connector.

&H310C -- 12556 LCFAIL_PROPERTY_VALUE -- Invalid property value [for property 'PROPERTY']

The value provided for the indicated property is not a valid value. Check the connector documentation for information on valid property values for this connector.

&H310D -- 12557 LCFAIL_INVALID_CHARSET -- The text format provided ['CHARSET'] is not a valid connector character set indicator

An attempt to indicate a character set by it's textual representation failed due to an invalid string. Check the documentation for a list of supported character set strings.

&H310E -- 12558 LCFAIL_READ_ONLY_PROPERTY -- Cannot change the value of read-only property ['PROPERTY']

The indicated property is read-only for this connector and an attempt to set it's value was made. For example, the "TextFormat" property of some connectors cannot be assigned, so will generate this error on any such attempt.

&H310F -- 12559 LCFAIL_MISSING_CONNECTORLCX -- Cannot load Connector LCX Library ['CONNECTOR']

The connector library .LCX file could not be loaded. Ensure that a valid connector was specified and that the connector is available on the system. A common mistake which produces this error is to not have any client files installed to support the connector. For example, use of the Connector for DB2® requires that a DB2® client product be installed.

&H3110 -- 12560 LCFAIL_INVALID_CONNECTORLCX -- Invalid Connector LCX Library ['CONNECTOR']

The connector library .LCX file was located and loaded, but was not a valid connector. Contact HCL or the connector vendor for a valid connector library.