Teradata SQL Error and Failure Codes from Error 9247 To 9256


9247 One or more objects reconciled to an earlier or same date or timestamp.
Explanation: The newly resolved date and/or timestamp value evaluated when ALTER TABLE TO CURRENT is issued
is earlier than the last resolved date and/or timestamp value for a table or join index whose PPI is defined with
CURRENT_DATE or CURRENT_TIMESTAMP. This may be possible either due to a clock drift, a clock reset, or time zone
differences for data.
Generated By: OPD modules
For Whom: End user
Remedy: Resubmit the ALTER TABLE TO CURRENT statement later. If problem persists check if there are issues with
the system clock.

9248 Object is not associated with CURRENT_DATE or CURRENT_TIMESTAMP.
Explanation: For an ALTER TABLE statement with the TO CURRENT clause, the table or join index must use
Generated By: OPD modules
For Whom: End user
PRIMARY INDEX must be used.

9249 The altering of RANGE_N definition with CURRENT_DATE/CURRENT_TIMESTAMP is not allowed.
Explanation: On a table that has PPI defined using CURRENT_DATE or CURRENT_TIMESTAMP, only ALTER TABLE
<tablename> TO CURRENT can be submitted to alter the PPI definition using a new date or timestamp. ALTER TABLE
with ADD or DROP RANGE clause must not be used in this case.
Generated By: OPD modules
For Whom: End user
Remedy: Use ALTER TABLE <tablename> TO CURRENT.

9250 External Stored Procedure “%VSTR” in language “%FSTR” does not exist.
Explanation: The user referenced an external stored procedure created in a different language in the database.
Generated By: RES/OPD modules.
For Whom: End User.
Remedy: Check the language of the external stored procedure. Correct the request and resubmit it.

9251 Source table field list did not match with Target table field list.
Explanation: This error occurs when Source table field list differ with Target table field list in number of columns or data types.
Generated By: opdctat.c
For Whom: End User.
Remedy: Correct the statement or give fields that matches correspondingly and resubmit the request.

9252 An invalid statement was attempted on a table without a primary index: %VSTR.
Explanation: The following statements are not allowed on a table without a primary index:- CREATE TABLE as queue table – CREATE TABLE as error table – CREATE TABLE with permanent journal – CREATE
UPDATE and DELETE into a replicated NoPI table
Generated By: Resolver.
For Whom: End User.
Remedy: Remove the invalid statement or clause.

9253 Invalid range specified for partitioning expression caused numeric overflow.
Explanation: For a CREATE TABLE or ALTER TABLE statement, the RANGE_N partitioning expression contains a
range boundary which is larger than can be expressed by the data type of the test value.
Generated By: OPT modules.
For Whom: End User.
Remedy: Examine the DDL statement and verify that it is correct. Modify the partitioning expression such that none of
the range boundaries in the RANGE_N expression is larger or smaller than can be represented by the data type of the test

9254 Internal error: Intermediate file not created while compiling stored procedure.
Explanation: This error is returned when creation of or writing into (i.e., fopen() or fwrite() system calls) intermediate
file(s) fails during stored procedure creation.
Generated By: Parser module.
For Whom: System Administrator.
Remedy: Check the free space in C:Program FilesTERADATATdatTdTempTDSPTemp on windows (installed directory
instead of C:) or /var/opt/teradata on linux where intermediate files are created. Create more space in this directory and
retry compiling the stored procedure.

9255 Recreate the join index in order to reflect the base table compression changes to the join index.
Explanation: This is only a warning but not error. Join index column compression is enabled implicitly when a join
index is created. Join index column compression is limited by the available table header space, and stops when the available
table header space is exhausted. Implicit join index column compression is restricted from the following join index columns:
i) Join index columns defined using the functions SUM, COUNT, or EXTRACT ii)(Join index columns that are part of
the partitioning expression for that index iii)Join index primary index columns iv)Join index columns in either the
column_1 or column_2 column So if the base table compression is modified, If Join index is defined on the base table Then
the Join index compression should also modified.
Note: The request is still processed despite the warning.
Generated By: OPD
For Whom: End User.
Remedy: Recreate the join index if the modified compressed column is eligible for the above rules.

9256 FastExport No Spooling mode is not supported for Select statement.
Explanation: The FastExport No Spooling mode is not supported for the SELECT statement.
Generated By: OPH modules.
For Whom: End User.
Remedy: Use a FastExport mode that will spool the results.

Above are list of Teradata Errors or Failure Codes from Error 9247 To 9256 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *