LOAD_DATA_ERRORS

On this page

This table is where the errors are logged when the LOAD DATA command is used with the ERRORS HANDLE clause.

To access this table, users may have the INSERT, or SHOW METADATA permissions.

information_schema.LOAD_DATA_ERRORS Schema

Column Name	Description
`DATABASE_NAME`	The name of the database associated with the error.
`HANDLE`	The string value specified in the `LOAD DATA ... ERRORS HANDLE <string>` statement that caused the error.
`ERROR_UNIX_TIMESTAMP`	The time of the error event in Unix timestamp format.
`ERROR_TYPE`	Specifies what type of error occurred. `Error` is used when `LOAD DATA` returned the error to the client application. `Warning` is used when `LOAD DATA` did not return the error to the client application and instead skipped or ignored the error. Note: If `LOAD DATA ... ERRORS HANDLE` returns a duplicate key error to the client application, the error is not logged to `information_schema.LOAD_DATA_ERRORS`.
`ERROR_CODE`	The error code for the error.
`ERROR_MESSAGE`	The message associated with the error. This value contains contextual information about the error that can be used for debugging purposes, including a stack trace if the error was caused by a transform failure.
`LOAD_DATA_LINE`	The text of a `LOAD DATA` statement that caused a parsing error while attempting to load data into the destination table. Load errors are typically caused by malformed CSV data or attempting to write invalid schema types into a column, such as a `NULL` value into a non-nullable column.
`LOAD_DATA_LINE_NUMBER`	The line number of a `LOAD DATA` statement that caused a parsing error while attempting to load data into the destination table. A `LOAD DATA` statement may consist of many lines, and this value indicates the specific invalid line. This line number can be correlated with the value of `LOAD_DATA_LINE`, which contains the invalid line’s text. This value may be empty or `NULL` if a `LOAD DATA` statement wasn’t associated with the error event.
`HOST`	The hostname or host IP address for the leaf node that processed the erroneous line of the input file.
`PORT`	The port number of the node that processed the erroneous line of the input file.
`PARTITION`	Specifies the partition ID on the leaf node that processed the erroneous line of the input file. This value is NULL if the aggregator processed the line.

Last modified: July 8, 2025

Was this article helpful?

Verification instructions

Note: You must install cosign to verify the authenticity of the SingleStore file.

Use the following steps to verify the authenticity of singlestoredb-server, singlestoredb-toolbox, singlestoredb-studio, and singlestore-client SingleStore files that have been downloaded.

You may perform the following steps on any computer that can run cosign, such as the main deployment host of the cluster.

(Optional) Run the following command to view the associated signature files.
Shell
```
curl undefined
```
Download the signature file from the SingleStore release server.
- Option 1: Click the Download Signature button next to the SingleStore file.
- Option 2: Copy and paste the following URL into the address bar of your browser and save the signature file.
- Option 3: Run the following command to download the signature file.
  Shell
```
curl -O undefined
```

After the signature file has been downloaded, run the following command to verify the authenticity of the SingleStore file.

Shell

echo -n undefined |
    cosign verify-blob --certificate-oidc-issuer https://oidc.eks.us-east-1.amazonaws.com/id/CCDCDBA1379A5596AB5B2E46DCA385BC \
      --certificate-identity https://kubernetes.io/namespaces/freya-production/serviceaccounts/job-worker \
      --bundle undefined \
      --new-bundle-format -

Verified OK