CREATE ERROR TABLE (OFS) Error Handling VantageCloud Lake - Handling Errors - Teradata VantageCloud Lake

Lake - Working with SQL

Deployment
VantageCloud
Edition
Lake
Product
Teradata VantageCloud Lake
Release Number
Published
February 2025
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
jbe1714339405530.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
jbe1714339405530

As there are changes for the field sizes of BLOB (32000) and CLOB(32000) to Varbyte(64000) and Varchar(64000) respectively, you may encounter an error while executing Basic Teradata Queries (BTEQ) or SQL queries. You can resolved the error by enabling the record mode. The following is an example of the same:

BTEQ -- Enter your SQL request or BTEQ command:
sel ErrorBinaryRecord from antares_overstock_small.ET_BI_CUST_parquet;
*** Failure 3798 A column or character expression is larger than the max size..
Statement# 1, Info =0
*** Total elapsed time was 1 second.

In the previous case, the query execution failed with an error Failure 3798.

With record mode enabled, the syntax is:

 BTEQ -- Enter your SQL request or BTEQ command:
.set recordmode on
sel ErrorBinaryRecord from antares_overstock_small.ET_BI_CUST_parquet;
*** Success, Stmt# 1 ActivityCount = 0
*** Query completed. No rows found.
*** Total elapsed time was 1 second.

The query runs successfully.