> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ocient.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data Pipeline Loading Errors

> Reference of Ocient data pipeline error codes and messages, with parameter descriptions and recommended actions for resolving load and parsing failures.

export const Ocient = "Ocient®";

This table captures error codes and their corresponding error messages that you can encounter when you load data using data pipelines in the {Ocient} System. Also, the table contains the definitions of the parameters in the error messages, descriptions that explain the error messages, and actions you can take to resolve the errors.

| **Code** | **Error Message** | **Message Parameters** | **Description** | **Resolution** |
| - | - | - | - | - |
| OLD00 | Key `key` for class `class` must be set to a non-NULL value. Details: `details` | `key`: The key of the missing property.<br />`class`: The class that has the missing property.<br />`details`: Additional information about the error. | This error occurs when the loading process reads the pipeline definition missing a required property. | Specify a non-NULL value for the specified key in the pipeline definition. |
| OLD01 | Value `value` is not acceptable with the key `key` for class `class`. Expected `example`. Details: `details` | `value`: The value that you set for the specified pipeline definition key.<br />`key`: The pipeline definition key with an incorrect value.<br />`class`: The class that contains the property.<br />`example`: An example or description of the correct value.<br />`details`: Additional information about the error. | This error occurs when the loading process reads the pipeline definition that contains a key with an incorrect value. | Specify the correct value for the setting corresponding to the specified key in the pipeline definition. |
| OLD02 | No class with name `class` exists in the pipeline builder packages. Pipeline cannot run. | `class`: The class that cannot be found. | This error occurs when the loading process reads the pipeline definition that contains an unknown class. | Ensure that the class exists and belongs to a package specified in the `'engine.builder.packages'` configuration option. |
| OLE00 | Failed to extract record with index `index` from `sourceName`. Details: `details` | `index`: The index of the record (index starts at 1) in the source where the error occurred.<br />`sourceName`: The name of the source resource where the error occurred.<br />`details`: Additional information about the error. | This error occurs when the extraction of a record fails. | Provide the correct source data in the accurate format, extract configuration, or compression method. |
| OLE01 | `dataExtract` cannot be extracted from `sourceData`. Details: `details` | `dataExtract`: The data to extract.<br />`sourceData`: The source data for the extraction.<br />`details`: Additional information about the error | This error occurs when the extraction of data from a record fails. | Provide the correct source data in the accurate format, extract configuration, compression method, or transform configuration. |
| OLE02 | The source data has encountered invalid data or character sets. If invalid data is expected in the load, turn off the VALIDATE\_CHARACTERS option or use the REPLACE\_INVALID\_CHARACTERS option instead. | None | This error occurs when the pipeline has the VALIDATE\_CHARACTERS option turned on and the load encounters invalid data.<br /> | If you want to skip files that contain invalid data, turn on the TOLERATE file error mode. If you expect invalid data in the load, turn off the VALIDATE\_CHARACTERS option. You can replace invalid data with the REPLACE\_INVALID\_CHARACTERS option. |
| OLM00 | The <br />`message`<br /> is too large. <br />`modification` | `message`: The type of message that is too large.<br /><br />`modification`: An example or description of a modification to limit the payload size of the message. | This error occurs when an internal communication fails because the message size exceeds the maximum size set by the system.<br /> | Modify the corresponding command to limit the payload size of the message.<br /> |
| OLO00 | Failed to connect to `sourceType` source because the specified `locationType` `location` was not found. Details: `details` | `sourceType`: The type of the source.<br />`locationType`: The type of the data location argument that was not found.<br />`location`: The value of the data location argument that was not found.<br />`details`: Additional information about the error. | This error occurs when the pipeline cannot find the source data (e.g., cannot find the configured bucket or file path). | In the pipeline definition, specify an existing data location in the source. |
| OLO01 | Failed to connect to `sourceType` source because the access credentials are unauthorized. Details: `details` | `sourceType`: The type of source where access is denied.<br />`details`: Additional information about the error. | This error occurs when the pipeline cannot connect to the source due to invalid credentials. | Specify credentials in the pipeline definition with access to the specified source or configure the source to provide access to the pipeline. |
| OLO10 | File list is empty at the `sourceType` source provided. The locations searched are: `location`.<br />Details: `details` | `sourceType`: The type of the source.<br />`location`: The value of the data location argument that was not found. | This error occurs when the pipeline cannot find the source data (e.g., the file path is empty). | If an empty file list was expected, set the `expect.empty.file.list` configuration option to `true` by executing `ALTER SYSTEM ALTER CONFIG SET 'streamloader.extractorEngineParameters.configurationOption.expect.empty.file.list' = 'true';`. Then, restart the pipeline. |
| OLO50 | File `fileName` was not found. | `fileName`: The name of the missing file. | This error occurs when the pipeline is configured to fail on missing files, and it cannot find a file in the list. | Handle the missing file using your own process or configure the pipeline to skip missing files instead. |
| OLS00 | Failed to load transformed value `value` to sink after `transformName`. Details: `details` | `value`: The value that the Loader Node could not load to the sink.<br />`transformName`: The name of the executed transform.<br />`details`: Additional information about the error. | This error occurs when the Loader Node cannot load a transformed value to the sink. For example, the transformed value might be too large for the sink column. | Check that the sink column is configured correctly or check that the transforms in the column are composed properly to return values that can load to the sink. |
| OLS97 | No table with name `tableName` exists in sink at `ipAddress`:`port`. The available tables are: `existingTables`. | `tableName`: The fully specified name of the specified table.<br />`ipAddress`: The IP address for the Loader Node of the Ocient sink.<br />`port`: The external TCP port for the Loader Node of the Ocient sink.<br />`existingTables`: The list of existing tables in the same database and schema as the specified table. | This error occurs when no table with the specified name exists in the sink, but the database and schema of the table do exist. | Specify an existing table in the pipeline definition or create a table with the specified name. |
| OLS98 | The column name `columnName` does not exist. The columns available to the pipeline from the `tableName` table are: `existingColumns`. | `columnName`: The name of the column that was not found.<br />`tableName`: The table that was searched.<br />`existingColumns`: The columns in the table that are available to the pipeline. | This error occurs when the target table in the sink does not contain all the columns specified in the pipeline or a column specified as a transform target is not declared in the sink definition of the pipeline. <br />(The database ignores deleted columns. This error does not occur when you load data to a deleted column.) | Specify an existing column in the pipeline definition or add the corresponding column to the target table. |
| OLS99 | Failed to connect to sink at `ipAddress`:`port`. Check that a streamloader at that address is reachable. | `ipAddress`: The IP address for the Loader Node of the Ocient sink.<br />`port`: The external TCP port for the Loader Node of the Ocient sink. | This error occurs when the pipeline cannot connect to its Ocient sink using a Loader Node. | Check that the Loader Node at the specified host and port is reachable and that the host and port of the Ocient sink are configured properly. |
| OLT00 | Cannot perform operation `operationName` because the inputs are `inputType`. Expected inputs are `expectedType`. | `operationName`: The name of the operation that cannot be performed because its inputs are the wrong type. (usually the name of a transform)<br />`inputType`: The type of inputs that the operation received.<br />`expectedType`: The type of inputs that the operation expects to receive. | This error occurs when transforms in a column are not composed correctly. | Add, remove, or replace transforms such that each transform receives input of the correct type and that the Loader Node loads data of the correct type into the target column. |
| OLT01 | Failed to transform value `value` using `transformName`. Details: `details` | `value`: The value that was not transformed.<br />`transformName`: The name of the failed transform.<br />`details`: Additional information about the error. | This error occurs when a transformation fails. | Correct the source data or modify the transform to fit the source data. Alternatively, start the pipeline with a higher error limit so the load skips the failing record. |
| OLT02 | Value `value` is not an acceptable `parameterName` for `transformName`. Expected `example`. | `value`: The incorrect value for the specified parameter.<br />`parameterName`: The name of the specified parameter.<br />`transformName`: The name of the transform that is not configured correctly.<br />`example`: An example or description of the correct value. | This error occurs when the parameter of the transform is not configured correctly. | Correct the parameter of the transform. |
| OLT03 | Failed to transform value `value` using `transformName` because the value is `valueDescription`. Expected `example`. | `value`: The value that was not transformed.<br />`transformName`: The name of the failed transform.<br />`valueDescription`: A feature or description of the incorrect value for this transform.<br />`example`: An example or description of the correct value. | This error occurs when a transformation fails because the data is not correct for the transform. | Correct the source data, modify the transform configuration, or use a different transform. |
| OLT04 | Failed to match value `value` to format `format` in `transformName` because `valuePart` at position `valuePartPosition` does not match pattern `pattern`. Expected `example`. | `value`: The value that was not parsed with the transform format.<br />`format`: The transform format.<br />`transformName`: The name of the failed transform.<br />`valuePart`: The part of the value that was unmatched.<br />`valuePartPosition`: The position (index starts at 1) of the part unmatched in the value.<br />`pattern`: The pattern in the transform format that did not match part of the value.<br />`example`: An example or description of the correct value. | This error occurs when a transformation fails because the value does not match the specified transform format. | Correct the source data or modify the transform format to fit the source data. |
| OLTM0 | Failed to transform `value` value using `transformName`. `details`. | `value`: The value that was not transformed.<br />`transformName`: The name of the failed transform.<br />`details`: Additional information about the error. | This error occurs when an EXPLODE transformation fails. | Correct the source data or modify the transform to fit the source data. Alternatively, start the pipeline with a higher error limit so the load skips the failing record. |
| OL998 | An error occurred in library `library`: `details` | `library`: The name of the library where the error occurred.<br />`details`: Additional information about the error. | This error occurs when the Ocient System detects an error from an internal library. | Diagnose and address the error using the details provided by the library. |
| OL999 | An error occurred in class `class`: `details` | `class`: The class that threw the exception.<br />`details`: Additional information about the error. | This error occurs when the Ocient System detects a general error. | If the details of the message are not helpful for you to resolve the error, then contact Ocient Support. |

## Related Links

[Errors and Warnings](/errors-and-warnings)

[Monitor Data Pipelines](/monitor-data-pipelines)