About the Hyper-Q Error Codes
The Hyper-Q error log contains both error and informational system messages.
The error log is a comma-separated values (CSV) file, a delimited text file that uses a comma to separate values. Each line of the file is a data record. Each record consists of one or more fields, separated by commas.
For most log messages, the Message Code column contains a placeholder value that corresponds to the log severity. However, certain messages have dedicated codes which make it easier to filter the log files for these messages. Standard INFO messages use DTM1000. Other severity levels use codes in the range DTM1013–DTM1021. There are hundreds of message codes, which, while not listed here, their meaning can be easily determined by looking at the text of the log message associated with it.
The Hyper-Q error codes are organized by the following categories.
- Internal Errors
- Connections Errors
- Syntax Errors
- Unknown Keyword Errors
- License Errors
- GSS API Errors
- Miscellaneous Errors
Internal Errors
Error Code |
Description |
Troubleshooting Instructions |
Internal error Cannot recover from an internal state violation |
Critical server error. Provide full error information and query trace logs to Datometry support. |
|
Internal error. <Stacktrace> Cannot recover from an internal state violation |
Critical server error. Provide full error information and query trace logs to Datometry support. |
|
Unknown error or bad error format Triggered if no other message is found or formatting failed |
Critical server error. Provide full error information and query trace logs to Datometry support.
|
|
Process ~p unresponsive with stack~n~p Heart beat found process unresponsive |
Critical server error. Provide full error information and query trace logs to Datometry support.
|
|
Internal error. Error: <Stacktrace> Cannot recover from an internal state violation |
Critical server error. Provide full error information and query trace logs to Datometry support. |
Connections Errors
Error Code |
Description |
Troubleshooting Instructions |
Connection shut down by administrator. Process killed due to explicit request by admin |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Client shutdown connection
|
See knowledge base article: DTM1016: Client shutdown connection | |
Authentication failed. Cannot authenticate user correctly, e.g., wrong password |
Verify the user name and password are correct. If the condition persists, provide the error info and the full statement text to Datometry support for further investigations. |
|
Unsupported authentication method: '~ts'. Auth method as required by server not supported by sds |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
No valid admission policy found for host \~ts\", database \"~ts\", user \"~ts\", protocol \"~ts\" (retriable)". Cannot find appropriate mapping |
Provide the error information and the full statement text if applicable to Datometry Customer Success.
|
|
Authentication timed out. Async authentication exceeded timeout |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
DTM2005 |
Authentication method '~ts' not supported for asynchronous connect. Backend required an auth method not supported in loopback |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
Database connection error '~ts'. Server socket errored out unexpectedly |
Verify the target database connection parameters. If the condition persists, provide the error info and the full statement text to Datometry support for further investigations. | |
Database refused connection at '~ts:~B' via gateway '~ts'. Cannot connect to database at given location |
Verify the target database connection parameters. If the condition persists, provide the error info and the full statement text to Datometry support for further investigations. | |
Database refused connection due to temporarily unavailable resources. Server could not fork backend process |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
TLS not supported for connection. TLS connection is not supported |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Endpoint port 'port_number' unavailable Another process is using this port |
See the knowledge base article: DTM3021: Endpoint port '1025' unavailable: address already in use | |
Upgrading connection to TLS failed: '~p'. TLS accept did not succeed |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
The datepart tzoffset is not supported by date function datepart for data type datetime Capacity of pool '~ts' exhausted and no more waiters permitted. Pool is at capacity and all backlog slots are full |
See the knowledge base article: DTM3031 : The datepart tzoffset is not supported by date function datepart for data type datetime Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Not yet implemented for ODBC gateway: ~p. Feature not yet implemented |
Possibly observed when unsupported ODBC features are encountered. Provide full error information and query trace logs to Datometry support. |
|
Failed to connect to the underlying database: ~p. ODBC connection failed |
See the knowledge base article: DTM3102: Failed to connect to the underlying database Hyper-Q cannot connect to the target database. Verify the gateway connection string attributes (server name/address, port) and your network connectivity to the target database, and ensure that the database instance is running. |
|
Failed to run query on the underlying database: ~ts. ODBC query execution failed |
The underlying database reported an error while executing a translated query. This failure may cover a wide variety of runtime error conditions ranging from runtime errors, resource constraints, security violations, etc. Inspect the error message from the underlying database to identify the root cause of the problem and address any actionable security and resources related issues.
If the condition persists, provide the error info and the full statement text to Datometry support for further investigations. |
|
Failed to decode value: [~p, ~p, ~p]. ODBC driver failed to decode values, e.g, infinity, NaN |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
ODBC Gateway misconfigured: missing 'connection_string' field. ODBC Gateway misconfigured |
Configuration issue. Review and adjust your settings in dtm.ini. Contact Datometry support if the issue persists |
|
Failed to close the connection to the database: '~p'. ODBC disconnection failed |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Cancel requested during authentication, shutdown connection |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
ODBC port executable not found. Failed to locate the ODBC port executable |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
ODBC process received invalid request: '~p'. ODBC process received invalid request |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Connection to the underlying database closed: '~p'. ODBC connection to the c-port odbcserver closed |
Possible network configuration issues. This error code indicates that the connection from Hyper-Q to the underlying database has been terminated. These errors may also be reported when the underlying instance is brought down for maintenance or any other reason. |
|
Lost connection to underlying database
|
See knowledge base article: DTM3116: Lost connection to underlying database |
|
MDStore connection failed when retrieving metadata for ~ts: ~ts. |
Verify the Metadata store configuration and connectivity between Hyper-Q and the underlying database. If the problem persists, provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Unable to retrieve metadata for ~p from database: ~ts. Metadata interface failed with unspecified error, e.g., missing credetials, etc. |
Hyper-Q is unable to retrieve database metadata to process queries. This error may be related to connectivity or the availability of the underlying database. Verify the MDStore connection parameters. If the condition persists, please provide the error info and the full statement text to Datometry support for further investigations. |
|
Initialization of connection failed. Failure occurred before initialization of connection was completed, e.g., bad auth |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Protocol version '~p' not supported (retriable). Client tried to connect with unsupported protocol version |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Failed to extract metadata. Failed to extract metadata from ODBC results |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Unsupported reconnect request. |
Teradata client application has lost connectivity to Hyper-Q and is trying to reconnect to the session it was previously connected to. To retry the transaction, open a new connection from the client and resubmit the transaction that was interrupted by the connectivity loss. In case of frequent occurrence of connectivity loss between the client application and Hyper-Q, check firewalls and routers between client and Hyper-Q for settings that drop idle TCP connections or filter out TCP keepalive message. |
Syntax Errors
Error Code |
Description |
Troubleshooting Instructions |
Syntax error |
Syntax errors can result from invalid input statements or may be related to unsupported language features. Make sure that the statement is valid. Inspect the statement text at the line/column number specified to check for any syntax issues. You may also try running the statement against your existing Teradata system to validate it. If the statement runs successfully against Teradata, provide the error info and the full statement text to Datometry support for further investigations. |
|
Syntax error before: '~ts', at line '~p' |
Syntax errors can result from invalid input statements or may be related to unsupported language features. Make sure that the statement is valid. Inspect the statement text at the line/column number specified to check for any syntax issues. You may also try running the statement against your existing Teradata system to validate it. If the statement runs successfully against Teradata, provide the error info and the full statement text to Datometry support for further investigations. |
|
Syntax error before: ~ts, at line ~p, column ~p |
Syntax errors can result from invalid input statements or may be related to unsupported language features. Make sure that the statement is valid. Inspect the statement text at the line/column number specified to check for any syntax issues. You may also try running the statement against your existing Teradata system to validate it. If the statement runs successfully against Teradata, provide the error info and the full statement text to Datometry support for further investigations. |
Unknown Keyword Errors
Error Code |
Description |
Troubleshooting Instructions |
Unknown endpoint type: '~ts'. No suitable alpha process for endpoint type |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Unknown gateway type: '~ts'. Decoding of version string unsuccessful |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Flag '~b' unknown. Traceflag translation failed due to unknown flag |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Unknown variable '~ts'. No definition for variable found |
This error is returned when:
If the issue is not fixed then provide the error info and the full statement text to Datometry support for further investigation. |
|
Unsupported or invalid endpoint/gateway combination (endpoint:~ts, gateway:~ts). Unknown conversion requested |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Invalid query translation request (endpoint:~p, gateway:~p). Unknown conversion requested |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
An unknown character string translation was requested. |
This message displays when an unknown option was used. Execute the same statement against your Teradata system and if it works please provide the error info and the full statement text to Datometry Customer Success. |
|
Unknown incoming message type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
Unknown identifier '~ts' at line ~p, column ~p |
The error is returned when the statement contains a non-existing column or alias. Verify that your query is consistent with the current state of the schema. If the issue is not fixed then please provide the error info and the full statement text to Datometry support for further investigation. |
License Errors
Error Code |
Description |
Troubleshooting Instructions |
License for '~ts': expired. Trial license no longer valid |
Contact Datometry support to get a valid license |
|
License file '~ts' contains invalid license. License has been tampered with |
Contact Datometry support to get a valid license |
|
Process already holds lease. Process tried to lease license twice |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
License for '~ts': capacity exhausted. All seats are taken |
Contact Datometry support to review the license configuration. |
|
No licenses registered. No license loaded for this product |
Contact Datometry support to get a valid license |
|
License key incomplete. License key lacks required components |
Contact Datometry support to get a valid license |
|
Functionality not supported under present license. License SKU does not include the functionality |
Contact Datometry support to get a valid license |
|
No license key file found in directory: '~ts'. No license key found |
Configuration issue. Refer to Datomety install guide for details about provisioning license files |
|
Multiple license keys found in directory: '~ts'. Multiple license keys found |
Configuration issue. Refer to Datomety install guide for details about provisioning license files |
|
Cross-compiler module not installed or no license available (endpoint:~ts, gateway:~ts). Unknown conversion requested or all licenses already taken |
Contact Datometry support to get a valid license |
LDAP Errors
Error Code |
Description |
Troubleshooting Instructions |
LDAP: Failed to establish connection with server '~ts'. LDAP: Server is not reachable or refuses connection |
Verify your LDAP connection parameters. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP: Bind to DN '~ts' failed; no such DN or insufficient credentials. LDAP: Unsuccessful bind, e.g., non-existent DN, credentials invalid, etc |
Verify the DN exists in your LDAP schema. Make sure you have the right access level. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP: Search failed (~p). LDAP: Cannot execute search with given filter |
Verify your search syntax is valid. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP: User '~ts' is not unique. LDAP: Search produced more than one entry |
Verify that the user is unique in LDAP. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP: No such user '~ts'. LDAP: Search did not produce any records; no such user |
Verify user is valid in LDAP. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP: User name '~ts' contains invalid characters. LDAP: Search did not produce any records; invalid characters |
Verify username is valid. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP Sync: Unknown cache. LDAP Sync: Unknown cache referenced |
Validate your LDAP cache strategy. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP Sync: One or more operations failed. LDAP Sync: Operation completed with errors, |
Re-run operation. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP Sync: Modification regarding user '~ts' failed. LDAP Sync: Modification failed |
Re-run operation. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP Sync: Embedded query failed to execute or returned unrecognized format. LDAP Sync: Expected a specific format from an embedded query, |
Verify validity of your query. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
|
LDAP Sync: Role name '~ts' contains illegal characters. LDAP Sync: Role name contains invalid characters |
Verify role name characters. If the issue persists provide the error info and the full statement text to Datometry support for further investigation. |
GSS API Errors
Error Code |
Description |
Troubleshooting Instructions |
GSSAPI: ~ts. Generic GSS error; details to be filled by GSS plugin |
Provide the error information and the full statement text if applicable to Datometry Customer Success. | |
DTM2202 |
GSSAPI: Name '~ts' does not match configured realm '~ts'. Realm returned from GSSAPIs does not match configuration |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
GSSAPI: User '~ts' name does not match authenticated user '~ts'. GSS returned a different user name that was originally given |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
Miscellaneous Errors
Error Code |
Description |
Troubleshooting Instructions |
Fault injection. Explicit injection of fault; only in debug version. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
OpenSSL not found. No suitable OpenSSL library found. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Encountered malformed packet. Packet does not conform to expected protocol. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot find a module ~p for system version ~p. No suitable module found. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot load module ~p for system version ~p, reason: ~p. Invalid module name. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Out of memory. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
DTM: Invalid configuration file |
Verify Hyper-Q configuration file dtm.ini usually located at /opt/datometry/config Make sure all the property names and values are correct. |
|
Unable to resolve Kerberos service name. Cannot determine remote Kerberos service name for this operation. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot determine principal or service host. Target is not unique, e.g., multiple gateways. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Client-side socket recieved error '~p'. Client socket errored out unexpectedly. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Session timeout exceeded. Session has been idle for too long. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Transaction timeout exceeded. Session held xact lock for too long. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Data encryption not supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported parameter type '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed to decode date value. Failed to decode date value. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Incomplete header, unable to decode result. The tdf contains incomplete header. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
TDF cursor is closed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Syntax error in control command. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Object not found or insufficient privileges for operation. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected feature name: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
mdi_cache file error: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Scheduler: job ~B: bad or missing parameter '~p'. Validation of job spec failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Hyper-Q metadata manager was unable to establish connection to underlying database. Cannot login with credentials provided. |
Review and adjust your DTM.INI settings. Contact Datometry support if the issue persists |
|
Scheduler: job ~B: execution failed. Execution was terminated with an error. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No such pool: '~ts'. Cannot locate appropriate pool for incoming request. |
Review and adjust your DTM.INI settings. Contact Datometry support if the issue persists |
|
Bad parameters for tracing pool '~ts'. Parameters for persistent tracing insufficient/wrong. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot open trace file '~ts': ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No such gateway: '~ts'. Cannot locate appropriate gateway. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Type of gateway '~ts' declared as '~ts' but found to be '~ts'. Declared and actual type of gateway do not match |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Unsupported version for gateway type '~ts': found version ~ts (details: '~ts'). Gateway version not supported. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Protocol handler '~ts' missing (details: '~ts'). |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Invalid query_success_flavor '~p' in endpoint configuration. Endpoint configuration of query success flavor is invalid. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
No such user: '~ts'. Cannot locate user by name. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Failed to parse configuration file '~ts': ~ts. Cannot parse file; bad configuration. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Cannot ~ts configuration file '~ts' (~p). POSIX error when opening file. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Failed to read referenced file '~ts': ~ts. POSIX error when opening file. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Config file '~ts' corrupted. Cannot process config file; unspecified reasons. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Invalid configuration file: missing required field '~w' in entry '~ts'. Error reading configuration file. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Invalid entry in configuration file: '~ts'. Invalid entry in configuration file. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
~ts:~B: ~ts. Lexer/parser-generated error message. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Environment variable '~ts' has bad value. Env variable not usable. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
Flag '~ts' has bad value. Traceflag translation failed due to bad value. |
Review and adjust your dtm.ini settings. Contact Datometry support if the issue persists |
|
MDI interface : No valid route for the current session. Error during look up of gateway type and version by mdi interface. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
MDI interface : feature ~ts not implemented. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid MDStore table ~ts. Reason: ~ts. Invalid MDStore table definition. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Plugin not found or failed to execute (~p). Cannot find plugin in specified location or failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Plugin terminated unexpectedly with exit code '~B'. Plugin returned error code as exit. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Plugin returned unexpected value(s). Cannot make sense of plugin return values. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Plugin timed out. No answer from the plugin within timeout. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
||
Unsupported language feature or parse error. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Insufficient credentials. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid credential data. Logon string format is not supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No serialization method found for xtra: '~ts'. No serialization found for operator. |
This error is returned when the statements contain functions supported by Hyper-Q, but are not supported in the underlying database. Look into the message coming from the "No serialization method" to identify the specific function name. Try to run the same statement against your Teradata system and if it works provide the error information and the full statement text to Datometry Customer Success. |
|
No type derivation method found for '~ts' in '~ts'. No type derivation method found for operator. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected type: ~p. Operation uses unexpected type. |
Inspect the satement to ensure that it uses legitimate data types. If the issue persists, provide the error information and the full statement text to Datometry Customer Success. |
|
Type mismatch (~p/~p). Wrong type in arguments of operation. |
Inspect the satement to ensure that it uses legitimate data types. If the issue persists, provide the error information and the full statement text to Datometry Customer Success. |
|
Serialization failed: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot execute the statement in compile only mode. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No valid metadata interface defined for database '~ts'. Metadata interface definition invalid or missing. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Ambigous metadata interface configured for database '~ts'. Multiple metadata interfaces found. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Object '~ts' not found or no permission. No valid metadata found for object or no permission. |
See the knowledge base article: DTM8031: Object not found or no permission This error is returned when a statement references a non-existing or inaccessible object. Verify that the statement is either using a fully qualfied name or the database context is properly set and also verify security and access policies to ensure that the user trying to acces the object has sufficient level of access. If the object exists and is accessible, provide the error information and the full statement text to Datometry Customer Success. |
|
Unsupported or invalid aggregate function. Output contains columns not supported in aggregation. |
Hyper-Q encountered an issue interpreting a statement that uses aggregation or window functions. Verify that the statement is syntactically and semantically correct. If the error is not resolved, provide the error information and the full statement text to the Datometry Customer Success. |
|
Admin interface failed: schema ~ts not found. Admin interface failed: admin interface schema not found. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Loading object alias mapping failed: table ~ts not found. Alias mapping table not found. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Object already exists in the variable scope. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Object name '~ts' is ambiguous. |
“Object name is ambiguous” means that you are referencing an attribute or attributes that belong to more than one of the objects that are used in the query. Verify that the statement is functionally correct. If the error is not resolved, provide the error information and the full statement text to Datometry Customer Success. |
|
No function '~ts' found that matches the parameter specification. Function name incorrect or paramters of unexpected type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Schema '~ts' not found. No schema found with given name. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed to send file via client socket. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Wrong format. Unit '~ts' is not supported for trunc function. Unsupported TRUNC unit. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid input for NVL function. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Max recursion depth exceeded by ~p. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Malformed packet. Packet corrupted or of unexpected format. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Memory quota for query results exceeded. Maximally allowed result set exceeded. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Bad request. Incoming request is not of expected type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Language feature '~ts' not yet supported. Unsupported token. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Variable '~ts' ambiguous. Failed to resolve column name -- either reference or definition. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No order encoding column found for table '~ts'. Table doesn't have proper ordcol defined. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Order encoding column '~ts' is of wrong type. Ordcol defined as something else but int8. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Bad literal (~p). Modifier and value are not compatible. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Column '~ts' of unsupported external data type '~p'. Type used in database not supported in Hyper-Q. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Table '~ts' contains no columns of supported type. None of the columns are usable; or table is defined without columns. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
As-of join not applicable because right expression is keyed. Right table must not have keys. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
As-of join requires specified columns to be present and of the same type in both expressions. Columns must match by name and type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid recursive view definition: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Function '~ts' returns unsupported type. Unable to represent return type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Ungroup operator requires at least one column that contains lists. Table must have at least one column that contains lists. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Parameter value out of range. Only values in (0, 2147483647 are supported for take operator. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Window join requires specified columns to be present and of the same type in both expressions. Columns must match by name and type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Too many names specified for xcol. Number of names specified must be smaller or equal to that of the columns for xcol. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid function definition. Unable to parse the string to get function body. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Wrong number of arguments specified for function invocation. Number of arguments specified for function invocation does not match that in the function definition. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid arguments for xbar. Left side of xbar must be positive integer and right side must be numeric type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Global table feature unsupported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Table variables in request scope not supported yet. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Kerberos token has invalid format. Kerberos token got corrupted or incorrectly encoded. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Materialization of table variable failed: ~ts. Table materialization statement failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid assignment: cannot assign to 'i' in 'select' query. Invalid named assignment in 'select' query. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Key join requires that the keys of the right table be present in the left table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid variable reference '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Boolean expression required in where clause. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Column assignment required in update. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected symbol or list of symbols as left argument of operator '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected integer as left argument of operator #. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected relational expression as argument of ungroup. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid arguments for sublist. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid arguments for within. Within expression only accepts one or two arguments. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid multi-column reference. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected table expression as argument of distinct. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected table expression as argument of cols. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected table expression as argument of meta. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected symbol as argument of tables. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid table expression reference '~ts'. Invalid table reference in mci. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid select specification. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid grouping specification. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid argument to differ operator. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected non-negative integer as argument of til. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid dictionary specification. Parity mismatch between the domain and the range of the dictionary. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid q script: '~ts'. Q script must have '.q' as file extension. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid load command argument '~ts': ~ts. Invalid argument for load command. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot open script '~ts': ~ts. Cannot open q script file. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Loading failed at line ~B of '~ts': ~ts. Error occurred during loading of a statement in the q script. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid functional form specification. Parse expression must be bound to an xtra_scaop_list. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid table specification: columns expressions must have the same length. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid concatenation. Cannot concatenate table with other types. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid stdout/err argument: argument must be string type. Stdout/err accepts only string type argument. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Q's stderr logging. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Index out of bounds. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid argument for dot operator. Argument of dot operator must be symbol or integer list. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid argument for 'parse'. Parse function accepts only string argument. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid q query for 'parse'. Parse function accepts only valid q query. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Functional form of '~ts' not supported yet. Functional form does not work for certain operators. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid constraints specification. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid condition query. Condition query must have odd number of expressions. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Condition must be of boolean or integer type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid keyed table update. Update multiple rows at the same time. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Key accepts only table with key columns. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid table argument for flip. Flip accepts table with non-key columns. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid logical (and/or) arguments. Arity mismatch between the logical operator arguments. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid IN arguments. Unexpected number of columns in IN expression. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Materialization of table variable failed: admin schema not configured. Table materialization statement failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid value for parse expression. Expect to parse a serialized string of a parse expression. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid value for select topn argument. Select topn accepts integer argument only. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid delete query: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid vector conditional expression. Expression components should be scalar or list expressions, where the first component is boolean (list and the if and else components are of the same type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid functional specification. Expected three or four components. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Xcols does not apply to keyed table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid 'prepare_text' command separator. Expected char type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid high-order function definition. Cannot parse parent function body. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Encountered Q program error: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid arguments for over. Left side of over must be a function or function reference and right side must be a list expression. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Equi-join requires specified columns to be present and of the same type in both input expressions. Columns must match by name and type. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed to reconstruct the result from backend database: ~ts. Unable to construct Xtra from Rowset, most likely because the underlying database failed to execute the generated query. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed to execute statement: '~ts'. Serialization or execution failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Error: ~ts. Check type compatibility for comparison failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
SET TIMING ON' is not supported for this query. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Multiple aggregations are not supported in where clause. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Syntax error before: 'EOL'
|
See the knowledge base article: DTM8193: Syntax error before: 'EOL' |
|
Compiler error. Bad xtra. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid Date/Time/Timestamp string: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid numeric type specifications (Precision: ~p, Scale: ~p). |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Numeric overflow. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported encryption method. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Max message size is too small. Client specified message size that does not fit query results. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsuccessful decryption of message: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Message unsupported in current protocol state: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
User-generated transaction ABORT. In teradata, ROLLBACK command will generate an error response. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported window construct: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Record size must not exceed 64 KB. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid QUALIFY clause: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported group by clause: ~ts. Group by clause not supported by underlying system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Grouping operation not supported by backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid CREATE VIEW statement. Reason: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid CREATE VIEW statement: column name list ~ts than select list. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid command: there is already an active transaction. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid command: there is no active transaction. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported system procedure call: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid database name. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
SIGNAL with SQLSTATE or CONDITION name not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
SET MESSAGE_TEXT not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
RESIGNAL with SQLSTATE or CONDITION name not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported request mode in query options: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed TDF conversion. Conversion to internal result representation has failed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid calendar name '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported INSERT into a set table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported CREATE VIEW using WITH CHECK OPTION: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Database specified for function ~ts is ambiguous. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
More than ~p columns in collect stats not supported by backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Session flag ~p not supported with query override execution. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
||
Command not allowed in an active transaction. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
String replacement with negative arguments not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cols function on expressions with side effects not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Sublist function with negative arguments not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Type function on expressions with side effects not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Union join on keyed tables not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Anonymous columns not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Union all on different schemas not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Meta function on expressions with side effects not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cross compilation: '~ts' type of expression not supported in '~ts' context. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Feature '~ts' not supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported function call. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported operator '~ts'. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Row-number selection on keyed tables not yet supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplicate column symbols not supported in xcols. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Query result device is locked. Data cannot be inserted into result device. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Query result device is unlocked. Data cannot be retrieved from unlocked result device. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Cannot add unlocked result device to another device. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Query result device failed to spill data to disk. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed to access spill file '~ts'. Reason: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
response message of size '~p'. Client message size cannot be used to store results. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Client message character decoding failed '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed to access file '~ts'. Reason: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected table alias for column '~p'. Unexpected table alias. |
The query is using aliases referencing an attribute or attributes that belong to more than one of the objects. Verify that the statement is functionally correct and consider simplifying the statement to avoid forward and backward references. If the error is not resolved, provide the error information and the full statement text to Datometry Customer Success. |
|
Invalid TOP-N count '~p'. TOP-N count should be positive. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid column position '~p'. Column position should be a positive integer. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid derived table columns ~ts. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid column name ~ts. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unable to resolve column name '~ts'. Unable to resolve column name. |
This error is returned when a statement references columns that are not present in the schema. Verify that all columns referenced by the statement are present. If the error persists, provide the error information and the full statement text to Datometry Customer Success. |
|
Invalid object name '~ts'. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid grouping expression. Grouping expression can be column names, positions or expressions on columns with no aggregate functions. |
Verify that the statement is syntactically and semantically correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
insert expressions ~ts than target columns. Number of insert expressions should match target columns. |
Verify that the statement is syntactically and semantically correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid interval string '~ts'. |
Verify that the statement is syntactically and semantically correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Subquery must return only one column. |
Verify that the statement is syntactically and semantically correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected subquery expression. |
Verify that the statement is syntactically and semantically correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid HAVING clause. Columns in the HAVING clause must be either used in an aggregate function or appear in the GROUP BY clause. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplicate FROM/WHERE/GROUP BY/HAVING/ORDER BY /QUALIFY/SAMPLE clauses. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid Date/Time/Timestamp string: '~ts'. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplicate column attributes specified for column ~ts. Column attributes (not null, default etc can only be specified once except for column constraints. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Primary key column(s) must be NOT NULL. If one or more columns is specified as PRIMARY KEY, it must be specified as NOT NULL as well. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unique column(s) must be NOT NULL. If one or more columns is specified as UNIQUE, it must be specified as NOT NULL as well. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid create table syntax: '~ts'. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Specifying more than one primary index not permitted. Teradata does not allow specifying more than one primary index. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Mismatching Begin/End labels '(~ts, ~ts)'. Different labels are used for BEGIN/END of a statement block. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid statement block label '~ts'. |
Verify that the statement is functionally correct. If the error persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Object '~ts' already exists. |
A CREATE statement was run for an object that already exists. Verify the logic of your scripts if this condition is unexpected. Usually these errors can be ignored if the object definitions are static. |
|
Undefined variable '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Nested call of procedure '~ts' with output parameters and returned dynamic result sets not supported. Unsupported nested procedure call with output parameters and dynamic result sets. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid length specified for CHAR or VARCHAR type '~p'. Type modifier for CHAR or VARCHAR data type needs to be between 1 and 64000. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Illegal clause or aggregation without table accessed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid cursor variable '~ts'. Invalid variable is used in cursor operation. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid ORDER BY clause in set operation. Encountered Order By clause in the first Select of a Set operation, or non-positional Order By clause is used. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid Top N clause. Top N clause not allowed in Select expressions of Set operation. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Insert statement has invalid target columns or value expressions. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Variable '~ts' already defined. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Incorrect number arguments for function '~ts'. Function invocation with wrong number of arguments. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid precision specified for time or timestamp type '~p'. Precision for time or timestamp type needs to be between 0 and 6. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid value of argument number '~p' in function call '~ts'. Function invocation with invalid INOUT/OUT parameter. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported cursor option '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
SQLSTATE' reference outside exception handler block is unsupported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported 'SQLCODE' reference. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected expression '~p'. |
This error indicates that either an unsupported expression is provided or the statement contains multi-layer complex dependencies/clauses usage. Verify the functionality of the statement and consider simplifying it. If the error cannot be resolved, provide the error information and the full statement text to Datometry Customer Success |
|
Unsupported or invalid format string '~ts' for type '~ts'. Unsupported or invalid format string. |
Look at the message coming from "Unsupported or invalid format string" and make sure that the format of the string is supported by Teradata. If it is supported provide the error information and the full statement text to Datometry Customer Success |
|
Unable to resolve variable '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid window operation: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid operation '~ts' for cursor '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported operation '~ts' for cursor '~ts' on gateway '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid data attributes: multiple '~p' options. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplicate common table expression definition '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid argument to round function. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid sampling rate '~p'. Invalid sampling rate: Teradata requires sampling rate between 2 and 100 when collecting statistics. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Subquery output does not match required comparison. |
This message displays when the subquery output doesn't match the required comparison. Make sure that the subquery type is correct. If the error is not resolved, provide the error information and the full statement text to Datometry Customer Success. |
|
Invalid arithmetic operation (~p ~p ~p). |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported arithmetic operation (~p ~p ~p). |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Too many digits in exponent '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid float value '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid interval specification: sign '~ts', unit '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported function: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Length of object name exceeds the limit of the backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected sqlstate: ~p. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Global temporary table parse error: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Database name, if specified, must be the login user name for a volatile table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Stored procedure DDL cannot be submitted in multi-statement request. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Multi-statement request is only supported with the new pipeline. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid named expression. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplicate definition of expression '~ts'. |
This error is returned when statements contain duplicated definition of the expression. Look into the message coming from the duplicate definition of expression to identify the expression which has the duplicated definition. Try to run the same statement against your Teradata system and if it works provide the error information and the full statement text to Datometry Customer Success. |
|
Unsupported query band '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Error encountered while emulating stored procedure operation: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected one row in query results. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid statistics collection command. Reason: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected single row constant table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Case sensitivity specified for non-CHAR data. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid precision specified for interval type '~p'. Precision for interval type needs to be between 1 and 4. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Illegal or unsupported set operation inside a recursive query/view. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid length specified for byte or varbyte type '~p'. Type modifier for byte or varbyte type needs to be between 1 and 64000. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Custom ABORT message. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected argument at position '~p' when calling '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Incorrect number of arguments when calling '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid macro definition. Reason: ~p. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid interval type definition. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Expected IS NULL or IS NOT NULL to test for NULL values. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplicate option for Identity Column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Illegal usage of Identity Column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid data type for Identity Column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Some index columns are not in the table ('~ts'). Index columns must exist in the table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Index '~ts' does not exist. |
Make sure that the index which you are referring to exists. If the index exists, provide the error information and the full statement text to Datometry Customer Success |
|
Duplicate index column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Index '~ts' already exists. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid sample size '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Database '~ts' does not exist. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Conflicting CASESPECIFIC options. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Operand of EXTRACT function is not a valid data type or value. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Interval field overflow. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Statistics does not exist. |
See the knowledge base article: DTM8591: Statistics does not exist |
|
Invalid function definition. Reason: ~p. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Function reference ~ts is ambiguous. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected error: ~p. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid hexadecimal constant '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid type or precision for period base type '~p', '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Function 'greatest' called with an invalid number or type of parameters. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Function 'least' called with an invalid number or type of parameters. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Case not found for CASE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Only one ORDER BY sort key is currently supported by XMLAgg. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
The Pad Expression for TRIM has an incorrect data type or length. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
The parameter '~ts' must be given a value. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Syntax error: expecting isolation level. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid input format for type ~ts: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Value '~ts' is out of range for type ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
This statement is not allowed when the target temporary table is already materialized. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No data found. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Illegal statement following DDL statement in transaction. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
InputString or Delim length is 0; OR toknum parameter is no larger than 0. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
~ts' is not a temporary table. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed: '~ts' is not a table. Invalid SHOW statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed: '~ts' is not a view. Invalid SHOW statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid interval arithmetic operation (~p ~p). |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid Query Band Search. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed: '~ts' is not a stored procedure. Invalid SHOW statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Failed: '~ts' is not a macro. Invalid SHOW statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid input range. Value '~p' must be in range '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Column'~ts' is an index column and cannot be modified/dropped. DROP/RENAME COLUMN not allowed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Input: numeric value within range only. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Ordered Analytical Functions not allowed in GROUP BY Clause. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Regular expression '~ts' is not valid |
This message is displayed when using an an invalid regular expression. Verify that the syntax of the regular expression statement is valid. If the problem persists, provide the error information and the full statement text if applicable to Datometry Customer Success.
|
|
Function '~ts' called with an invalid number or type of parameters.
|
This message is displayed when using an an invalid number or parameter type. Verify the syntax of the statement and correct as needed. If the problem persists, provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
SAMPLE clause not allowed in SET operations. |
Sample Clause is currently not supported in set operations.
If necessary, put the sampling request in a derived table, and request that it be implemented. |
|
~B index columns exceeds maximum allowed of ~B |
Invalid number of index columns.
|
|
Invalid operation for DateTime or Interval. |
An operation that requires an appropriate DateTime or Interval data type or value, and it does not.
Correct the request and resubmit it. |
|
Cannot create a NoPI table as a SET table. |
You cannot create a no primary index (NoPI) table as a SET table. The default table type for NoPI tables in both Teradata and ANSI session modes is always MULTISET.
NoPI tables are designed for these circumstances:
In all other circumstances, it is recommended that you specify a primary index when you create a table. |
|
Invalid operation on Date or Time or Interval. |
An operation that requires an appropriate DateTime or Interval data type or value, and it does not.
Correct the request and resubmit it. |
|
~ts' statement is not supported within a stored procedure. |
The SQL statement is not supported within a stored procedure.
This error occurs in one of the following situations:
A) An unsupported SQL statement is specified in a stored procedure using the dynamic SQL feature of stored procedures. For instance, DATABASE statement, SET SQL statements, multi statement requests, CREATE USER/DATABASE statement without FROM clause, SELECT - INTO SQL or CALL SQL. This is a run-time error.
B) An unsupported SQL statement is specified in a stored procedure. For instance, DATABASE statement, SET SQL statements, INSERT EXPLAIN or a CREATE USER/DATABASE statement without FROM clause.
Correct the SQL statement and, recreate the stored procedure if necessary
|
|
A syntax error was found in the QUERY_BAND. |
The format of the Query_Band is incorrect. The syntax of each pair should be name=value;.
Correct and re-submit the statement.
|
|
An index is not supported on a ~ts column. |
Invalid index column type.
|
|
Invalid outer join: ~ts |
Invalid outer join.
|
|
Table '~ts' already exists |
Table already exists.
Delete or drop the table if it already exists.
|
|
Duplicate statistics name: ~ts" |
Duplicate statistics name.
Duplicate names are not allowed for table or constant expression statistics. You can only use COLUMN specification to recollect statistics using statistics names.
|
|
WHERE clause expects a boolean argument; instead got ~p" |
The WHERE condition does not have a boolean.
Correct the SQL statement
|
|
ORDER BY clause can have only one column. |
ORDER BY clause can have only one column.
|
|
Order by field does not belong to the index. |
Order by field does not belong to the index.
|
|
Invalid Partitioning. |
Invalid Partitioning.
A partitioning expression must be deterministic and based on one or more columns in the table (these columns are called the partitioning columns).
Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned primary index rules and resubmit the request.
|
|
Input exceeds the buffer size limit. |
Input exceeds the buffer size limit.
Enlarge the input buffer to the size returned in the information field of this FAILURE and resubmit the request.
|
|
Existing columns: ~ts, new columns: ~ts |
Number of columns are different in source and target tables.
|
|
Existing column: ~ts, new column: ~ts |
Columns are incompatible in the source and target table.
|
|
Unsupported feature '~ts'. |
This message is displayed when using an unsupported feature. Make sure that the feature is supported and provide the error information and the full statement text to Datometry Customer Success otherwise rewrite the statement. |
|
Unsupported lock type '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported lock option '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported CREATE TABLE statement: '~ts'. CREATE TABLE statement cannot be mapped to backend database. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unexpected error handler condition: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported operation to convert the format of type '~ts'. Only converting to date is supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported argument type for STDDEV_SAMP function '~ts'. Only numerical data types are supported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Query banding is unsupported. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported arithmetic operation with non-constant interval expression. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported data type '~p'. |
This message is displayed when the statement contains an unsupported data type. The type will be displayed after "Unsupported data type" message. Run the same statement against your Teradata system and if it works provide the error information and the full statement text to the Datometry Customer Success otherwise rewrite the statement. |
|
Handler for conditions '~p' is already defined. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
DML statements not supported by the backend system: '~p'. Certain DML statements (DELETE/UPDATE not supported by the backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Transaction related statements not supported by the backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported set operation by the backend system: '~p'. Certain set operations (e.g. INTERSECT, EXCEPT are not supported by the backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Stored procedures not supported for the backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid query syntax: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid 'SQLCODE' reference. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported DML operation on updatable views. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported access to system object: '~ts'. |
This message is displayed when the statement contains an unsupported system object. Try to run the same statement against Teradata system and if it works provide the error information and the full statement text to Datometry Customer Success otherwise rewrite the statement. |
|
Unsupported query element: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
DDL statements not supported by the backend system: '~p'. Certain DDL statements (e.g. CREATE INDEX not supported by the backend system. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
View ~ts is not updatable. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
View definition for view ~ts could not be parsed. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid reference to non-determinstic expression: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Creating index not supported by the backend system. |
This error is returned when trying to create an index on the backend system which does not have support for that, e.g. the error should be issued when trying to create a unique index on Redshift. Try to run the same statement against your Teradata system and if it works provide the error information and the full statement text to the Datometry Customer Success otherwise rewrite the statement. |
|
Invalid data for USING modifier: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
View definition for view ~ts could not be retrieved. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Definition of view '~ts' references itself. View definition could not be parsed because of recursive reference. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid merge statement: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported merge statement: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
MLoad job error. Reason: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
An MultiLoad job for table '~ts.~ts' is already running. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid select list. Reason :'~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Too many END TRANSACTION statements. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid UPSERT statement: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
The user cannot RENAME to a new database. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Database unspecified for '~ts'. Must specify database name. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Volatile table '~ts' not allowed in statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Column name list is not the same length as the select list. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid unicode literal: '~p'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
MLoad retry error: maximum number of errors reached. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid block number in the FastExport Initiate request. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Check constraint not satisfied for view ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid update statement: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
~ts must be empty for Fast Loading. Table must be empty for Fast Loading. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Duplication of column ~ts in a table, derived table, view, macro or trigger. Duplicate column used in object definition. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported CREATE DATABASE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported timezone specifier: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported GIVE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported SHOW STATISTICS: SHOW STATISTICS | STAT | STATS. Hyper-Q does not support 'SHOW STATISTICS | STAT | STATS' features yet |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported QUEUE TABLE statement from parser. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported DROP DATABASE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported DELETE DATABASE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported MODIFY DATABASE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported NOT NULL in CTAS column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported PERIOD FOR statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported HELP DATABASE statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Collect Statistics. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Translation of Labels in REPEAT. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Multi-character delimiters in STRTOK. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported EXPLAIN statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported feature 'Identity Column'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Transaction Command. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Update Identity Column feature. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported day_number_of_year statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Emulation of UDFs statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Non UTC Timezone statement. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Updatable view for non-Teradata endpoint. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported format string for function TO_CHAR. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported quantified subquery: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported value for the search start position: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported value for Occurrence: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported value for Match option: ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported type for Identity Column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported CREATE GLOBAL TEMPORARY TABLE inside stored procedure. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Insert into Identity Column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported Set Session Collation. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
A table may not have more than one identity column. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Invalid insert statement: '~ts'. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Stored procedure exception ~ts. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Unsupported string literal in pattern. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
MultiLoad MARK DUPLICATE INSERT (dup row). |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
MultiLoad MARK DUPLICATE UPDATE. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Distinct option is invalid with OVER phrase. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
REGEXP function parameter '~p' is not supported on backend |
REGEXP function is not supported. Due to limited support for REGEXP in the target CDW, revise the query to use string expressions or supported variants of REGEXP functions. |
|
SET QUERY_BAND PROXY_USER is not supported |
To make a proxy user connection, a middle tier application that is connected as a trusted user issues a SET QUERY_BAND request that specifies the proxy user name and an optional proxy role for that user. The reserved query band names PROXYUSER and PROXYROLE are used to specify a trusted session user name and proxy role name in the SET QUERY_BAND request, respectively. If the query band specifies PROXYUSER, Teradata validates that the current user has privileges to connect as the specified proxy user. A SET QUERY_BAND request returns an error whenever any of the following violations occur.
Reissue the SET QUERY_BAND statement with a valid proxy user. |
|
Duplicate unique primary key error in ~s table. |
Duplicate unique primary key error. The request generated a row whose prime key duplicated that of an existing row in a table with a unique prime key. Correct and resubmit the request. |
|
Duplicate row in table ~s. |
Duplicate row in table. An update or insert request generated a row that was a duplicate of an existing row. Correct and resubmit the request. |
|
Value list too long. |
Default value List is too long. Alter table query caused Default value list to exceed the maximum permissible limit.(1MB) Decrease the number of Default value columns, or split the ALTER TABLE request into multiple ALTER TABLE requests. |
|
'~s' is not a stored procedure. |
Invalid stored procedure version is invalid. The stored procedure version is not compatible with the Teradata RDBMS server release. It is either out dated or not supported in the current Teradata system release. The version mismatch may be because the stored procedure is created on a different version of the server and is being used in a server release where its behavior may be unpredictable. Recompile the stored procedure in the current Teradata system.
|
|
'~s' is not a macro. |
The specified item is a table or view and must be changed to a macro in this context. Correct the statement and resubmit the request. |
|
Failed to extract source of macro or procedure. |
Failed to extract source of macro or procedure. |
|
Column property modified: '~ts' |
Column property modified. |
|
PARTITION BY used by CREATE TABLE statement is ignored. |
PARTITION BY used by CREATE TABLE statement is ignored. |
|
SET option used by CREATE TABLE statement is ignored. |
SET option used by CREATE TABLE statement is ignored. |
|
ON COMMIT PRESERVE/DELETE ROWS option used by CREATE TABLE statement is ignored. |
ON COMMIT PRESERVE/DELETE ROWS option used by CREATE TABLE statement is ignored. |
|
Uniqueness constraint on index used by CREATE TABLE statement is ignored: '~ts' |
Uniqueness constraint on index used by CREATE TABLE statement is ignored. For a CREATE TABLE statement, a row partitioned primary index is not allowed to be unique unless all the partitioning columns are included in the set of primary index columns. For an ALTER TABLE statement, UNIQUE may only be specified if the primary index for the table is already unique, there is a unique secondary index on the same set of columns as the primary index, or the table is empty. In addition, a row partitioned primary index may only be specified as UNIQUE if all the partitioning columns are included in the set of primary index columns and altering the primary index columns of a unique primary index to not include all the partitioning columns is only allowed if NOT UNIQUE is specified. If the primary index is altered to be unique and there is a unique secondary index on the same set of columns as the primary index, the unique secondary index is dropped since it is no longer needed. Use a unique secondary index to define the columns as unique if not all the partitioning columns are included in the set of primary index columns. Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned primary index rules and resubmit the request. |
|
Unsupported TEMPORAL TABLE statement. |
Temporal operations on a table without a primary index can be done only when EnableNoPITemporal flag in the cost profile is set to 1. Set EnableNoPITemporal flag in the cost profile to 1 and re-submit the statement. |
|
Unsupported SELECT AND CONSUME statement. |
Set operations do not operate on SELECT AND CONSUME statements. |
|
Unsupported NONSEQUENCED SELECT statement. |
Unsupported NONSEQUENCED SELECT statement. |
|
Unsupported NONTEMPORAL DELETE statement. |
Unsupported NONTEMPORAL DELETE statement. |
|
Unsupported TEMPORAL column. |
Unsupported TEMPORAL column. |
|
Unsupported XML column. |
Unsupported XML column. |
|
Unsupported JSON column. |
Unsupported JSON column. |
|
Unsupported JSON COMPOSE. |
JSON_COMPOSE creates a JSON document composed of the input parameters specified. This function provides a complex composition of a JSON document when used in conjunction with the JSON_AGG function. |
|
Unsupported JSON AGG. |
The JSON_AGG function returns a JSON document composed of aggregated values from each input parameter. The input parameters can be a column reference or an expression. Each input parameter results in a name/value pair in the returned JSON document. |
|
Unsupported JSON_CHECK. |
The JSON_CHECK function checks a string for valid JSON syntax and provides an informative error message about the cause of the syntax failure if the string is invalid. |
|
Mismatch between required and specified parameters. |
The EXECUTE command for a parameterized SQL statement specifies a list of parameters. The number of parameters in that list must equal the number of parameters that appear within the SQL statement. Correct the SQL statement and resubmit. |
|
A MultiLoad DELETE Statement is Invalid. |
In a MultiLoad Complex Import Task, the user provided a DELETE statement that does not fully specify a primary index value or the values of all the partitioning columns. Or, in a MultiLoad Delete Task, the user provided a DELETE statement that specified a primary index. Correct the error and resubmit the request. In a MultiLoad Complex Import Task, the WHERE condition, including any taken from a view definition, must allow for primary index access (and, if partitioned, partition access) with possible ANDed residual conditions. It must also reference no other tables or views. In a MultiLoad Delete Task, the WHERE condition, including any taken from a view definition, must not include a primary index access. It must also reference no other tables or views. |
|
Unsupported BLOB column. |
Ordered analytical functions do not operate on the following data types:
Note that CLOB, BLOB, or UDT data types are usable inside an expression if the result is a supported data type. |
|
Unsupported GEO column. |
The target database does not support the Geospatial data type. |
|
XTRA structural_specs is not implemented. Mod: ~p" |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
SQLOP structural_specs is not implemented. Mod: ~p" |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Distribution is ignored for MSSQL |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Pick first column for distribution column due to native_multicolumn_max_cols = 1 |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Use ROUND_ROBIN for distribution due to |
Use ROUND_ROBIN distribution for tables with more than 8 columns in the primary index (default), or more than the value specified. Synapse supports only up to 8 distribution columns, whereas Teradata allows up to 64 columns in the primary index.
|
|
Pick all distribution columns. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Pick first N columns as specified by the
config parameter. |
The number of columns in Teradata Primary Index that This is only applicable if |
|
Pick only column AS-IS. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
No option is applicable, use Round-Robin for distribution. |
Use a Round Robin distribution style. |
|
IDENTITY column in distribution columns ignored. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Ignore a large column (with max size) in distribution columns. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
Use HEAP table layout for table with large (with max size) columns. |
Use HEAP table layout style. HEAP tables can be used as staging tables for large, unordered insert operations. Because data is inserted without enforcing a strict order, the insert operation is usually faster than the equivalent insert into a clustered index. |
|
Use HEAP table layout for mload work table. |
Use HEAP table layout style. HEAP tables can be used as staging tables for large, unordered insert operations. Because data is inserted without enforcing a strict order, the insert operation is usually faster than the equivalent insert into a clustered index. |
|
Use HEAP table layout due to default_table_layout config. |
The Hyper-Q hint to be used to set default table layout in CREATE TABLE statement in Azure Synapse to be HEAP instead of empty, which defaults to clustered column store index. "gateway".default_table_layout = heap |
|
No option is applicable. Use default table layout. |
Use default table layout. |
|
Renaming columns is unsupported for BigQuery. |
You can not rename columns in Google BigQuery. |
|
Unsupported Number Format ~ts |
The number format is not supported. |
|
Pick first column for distribution column due to wide columns in the table. |
Pick first column for distribution column due to wide columns in the table. |
|
DROP JOIN INDEX is ignored. -or- EXPLAIN with no option is ignored. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
EXPLAIN DATABASE is ignored. |
Provide the error information and the full statement text if applicable to Datometry Customer Success. |
|
DIAGNOSTIC statement is ignored. |
DIAGNOSTIC statement is ignored. |
|
STATS FROM option is ignored. |
STATS FROM option is ignored. |
|
FASTEXPORT spool option is ignored. |
FASTEXPORT spool option is ignored. |
|
LOCKING hint in HELP statement is ignored. |
LOCKING hint in HELP statement is ignored. |
|
DROP TABLE is ignored. |
DROP TABLE is ignored. |
|
CREATE TABLE is ignored. |
CREATE TABLE is ignored. |
|
DROP INDEX is ignored. |
DROP INDEX is ignored. |
|
CREATE INDEX is ignored. |
CREATE INDEX is ignored. |
|
ITERATE statement is ignored. |
ITERATE statement is ignored. |
|
SEQUENCE statement is ignored. |
SEQUENCE statement is ignored. |
|
MLOAD request is ignored. |
The Teradata MultiLoad request was ignored. |
|
MLOAD INSERT statement is ignored. |
The Teradata MultiLoad INSERT statement was ignored. |
|
MLOAD DELETE statement is ignored. |
The Teradata MultiLoad DELETE statement is ignored. |
|
RELEASE MLOAD is ignored. |
RELEASE MLOAD is ignored. |
|
COMMENT statement is ignored. |
COMMENT statement is ignored. |
|
DROP STATS statement is ignored. |
DROP STATS statement is ignored. |
|
COLLECT STATS is ignored. |
COLLECT STATS is ignored. |
|
EXEC DYNAMIC SQL is ignored. |
EXEC DYNAMIC SQL is ignored. |
|
SWITCH DATABASE statement is ignored. |
SWITCH DATABASE statement is ignored. |
|
CALL PROCEDURE statement is ignored. |
CALL PROCEDURE statement is ignored. |
|
UPDATE statement is ignored. |
UPDATE statement is ignored. |
|
INSERT statement is ignored. |
INSERT statement is ignored. |
|
ALTER TABLE statement is ignored. |
ALTER TABLE statement is ignored. |
|
ALTER PROCEDURE statement is ignored. |
ALTER PROCEDURE statement is ignored. |
|
BEGIN QUERY LOGGING statement is ignored. |
BEGIN QUERY LOGGING statement is ignored. |
|
END QUERY LOGGING statement is ignored. |
END QUERY LOGGING statement is ignored. |
|
REPLACE QUERY LOGGING statement is ignored. |
REPLACE QUERY LOGGING statement is ignored. |
|
FETCH CURSOR is ignored. |
FETCH CURSOR is ignored. |
|
CHECKPOINT statement is ignored. |
CHECKPOINT statement is ignored. |
|
CREATE JOIN INDEX statement is ignored. |
CREATE JOIN INDEX statement is ignored. |
|
DUMP statement is ignored. |
DUMP statement is ignored. |
|
HELP STATS is ignored. |
HELP STATS is ignored. |
|
RELEASE LOCK is ignored. |
RELEASE LOCK is ignored. |
|
SET SESSION COLLATION is ignored. |
SET SESSION COLLATION is ignored. |
|
SET SESSION TRANSACTION is ignored. |
SET SESSION TRANSACTION is ignored. |
|
BEGIN TRANSACTION is ignored. |
BEGIN TRANSACTION is ignored. |
|
COMMIT is ignored. |
COMMIT is ignored. |
|
ROLLBACK is ignored. |
ROLLBACK is ignored. |
|
UNKNOWN statement is ignored. |
UNKNOWN statement is ignored. |
|
DROP STATISTICS on PARTITION column is ignored. |
DROP STATISTICS on PARTITION column is ignored. |
|
Non-constant default value is ignored. |
Non-constant default value is ignored. |
|
Current database default value is ignored. |
Current database default value is ignored. |
|
Create index on global temporary table is ignored. |
Create index on global temporary table is ignored. |
|
DTM9199 |
Uniqueness constraint on index is ignored. index: '~ts' |
Uniqueness constraint on index is ignored. |
Create index on volatile table is ignored. |
Create index on volatile table is ignored. |
|
Create index on set table is ignored. |
Create index on set table is ignored. |
|
Create index on CREATE TABLE AS ... is ignored. |
Create index on CREATE TABLE AS ... is ignored. |
|
Create non-unique index on distribution column is ignored. |
Create non-unique index on distribution column is ignored. |
|
USING option in COLLECT STATS is ignored. |
USING option in COLLECT STATS is ignored. |
|
CREATE INDEX is ignored. Number of index columns exceeds the maximum number of allowed index columns. |
Change the index definition and resubmit the request. |
|
PRIMARY KEY CONSTRAINT '~ts' in alter table is ignored. |
PRIMARY KEY CONSTRAINT in alter table is ignored. |
|
PRIMARY KEY CONSTRAINT '~ts' is ignored because serialize_primary_key config is disabled. |
PRIMARY KEY CONSTRAINT is ignored because serialize_primary_key configuration is disabled. To serialize the PRIMARY KEY on Azure Synapse you can enable the serialize_primary_key configuration parameter. To do so, add the following to the Hyper-Q configuration file (DTM.INI). "gateway".serialize_primary_key=true |
|
Composite PRIMARY KEY CONSTRAINT is ignored. |
Composite PRIMARY KEY CONSTRAINT is ignored. |
|
Ignore a large column (with max size) for clustered index. |
Ignore a large column (with max size) for clustered index. |
|
DTM9210 |
Override table layout. Inferred: ~ts, overriden: ~ts |
Override table layout. |
Override table layout columns. Inferred: ~ts, overriden: ~ts |
Override table layout columns. |
|
Override distribution style. Inferred: ~ts, overriden: ~ts |
Override distribution style. |
|
Override distribution columns. Inferred: ~ts, overriden: ~ts |
Override distribution columns. |
|
DTM9214 |
Invalid overridden distribution style: ~ts |
Invalid overridden distribution style. |
Invalid overridden table layout: ~ts |
Invalid overridden table layout |
|
The overridden columns are not in the table columns.Override columns: ~ts, Table columns: ~ts |
The overridden columns are not in the table columns. |
|
Table layout overridden to clustered index but columns are not defined. Use primary index columns by default. Columns: ~ts |
Table layout overridden to clustered index but columns are not defined. Use primary index columns by default. |
|
No column is defined for hash distribution. |
No column is defined for hash distribution. |
|
No column is defined for clustered index. |
No column is defined for clustered index. |
|
No column is defined for hash distribution in table ~ts.~ts |
No column is defined for hash distribution in the table. |
|
Invalid column for statistics. Column: ~ts table: ~ts.~ts |
Invalid column for statistics. |
|
Unsupported regular expression pattern. |
Unsupported regular expression pattern. |
|
Unsupported DROP STATISTICS. |
Unsupported DROP STATISTICS. |
|
Dropping index not supported by the backend system: |
Dropping index not supported by the backend system. |
|
Invalid override table uniqueness option, value: ~ts, expected: |
Invalid override table uniqueness option. |
|
Invalid table options generator, value: ~ts, expected: default|smart |
Invalid table options generator. |
|
FastExport NoSpool mode finished retrieving all data chunks. |
FastExport NoSpool mode finished retrieving all data chunks. |
|
Secondary index uniqueness violation in ~s table. |
Secondary index uniqueness violation. |
|
Comparing BYTE data with other types is illegal. |
Comparing BYTE data with other types is illegal. |
|
Numeric overflow occurred during computation. |
Numeric overflow occurred during computation. |
|
Job forced to fail due to bulkload errors |
The bulkload job was forced to fail (exit code different than 0) due to entries present in the ET error table or the UV error table or both.
|
|
Bulk load copy data operation has likely reached limit. |
Bulk load copy data operation has likely reached limit. |
|
Failure parsing JSON for method: ~ts |
Failure parsing JSON. |
|
Schema or table lookup has failed. |
Schema or table lookup has failed. |
|
Existing statistics are not allowed to be recollected with a new statistics name ~ts |
Existing statistics are not allowed to be recollected with a new statistics name. |
|
Unsupported pattern for ROWNUM. |
Unsupported pattern for ROWNUM. |
|
A character string failed conversion to a numeric value. |
A character string failed conversion to a numeric value. |
|
Overflow occurred computing an expression involving ~s. |
Overflow occurred computing an expression. |
Comments
2 comments
This resource is my first stop when trying to triage an incident! Thank you Serge.
We faced an error code as below which is not in this list. can you update .
Please sign in to leave a comment.