Teradata SQL Error and Failure Codes from Error 9103 To 9111

SQLServerF1_Header_Small

9103 Invalid Period value constructor. %VSTR
Explanation: An error was generated during Period Data Type Construction. The exact message is given within VSTR.
a) If only the beginning bound is specified in the construction of a period, the beginning bound must be less than the maximum
of the element type.
b) For the construction of a period, the beginning bound must be less than the ending bound. For an element of type TIME
or TIMESTAMP, the beginning bound must be less than the ending bound in its UTC form.
Generated By: Period constructor function.
For Whom: End User.
Remedy: Correct the bound values and re-submit.

9104 Invalid Period arithmetic operation. %VSTR
Explanation: An error was generated during Period arithmetic operation. The exact message is given within VSTR. a)
For arithmetic operation where one operand has PERIOD(TIME) and the other operand is an interval, the result beginning
bound must be less than the result ending bound. For example, this can occur when adding or subtracting an interval that
causes one element of the result to go past 24 hours and be modulo 24 hours but the other element of the result does not.
b) For period of element type DATE/TIMESTAMP the resulting ending bound value of a period arithmetic operation must
not be equal to the UNTIL_CHANGED value.
Generated By: Period constructor function.
For Whom: End User.
Remedy: Correct the Period arithmetic expression/bound values and re-submit.

9105 %VSTR
Explanation: The Period operands of the P_INTERSECT operator must overlap.
Generated By: Period operator P_INTERSECT.
For Whom: End User.
Remedy: Correct the operands and re-submit.

9106 %VSTR result in UDF/XSP/UDM %DBID.%TVMID.
Explanation: The Period value returned from an UDF/UDM is invalid.
Generated By: Period check value function.
For Whom: End User.
Remedy: Correct the returned period value in UDF/UDM and re-submit.

9107 MultiLoad not allowed: table %TVMID does not have a primary index.
Explanation: MultiLoad is not supported on a table that does not have a primary index.
Generated By: AMP MLOAD step.
For Whom: End User.
Remedy: Use FastLoad to load a table that does not have a primary index.

9108 Table Header pertains field 10.
Explanation: This is an internal status error created for verifying field 10 of table header in tablerebuild.
Generated By: RbdGetD
For Whom: End User
Remedy: Rebuild will handle the table according to the status of the field 10.

9109 Source row with access lock is deleted while statistical function is in progress.
Explanation: This error may be reported during following condition :
– STAT function on a table with an access lock is in progress – another transaction modifying the same table
Though this is not an invalid operation, still the DBS found it difficult to continue even after lots of retrying to proceed with
the STAT function. At this moment, DBS decides to gracefully abort the transaction. In future releases, this problem may be
corrected by implementing a better solution.
Generated By: AMP Software(STPSTATFN).
For Whom: End User.
Remedy: Resubmit the transaction.

9110 Maximum number of select statements exceeded.
Explanation: This error is returned when a fastexport utility has submitted more select statements then the maximum
allowed. The maximum number of select statements that can be submitted through one fastexport is 1024.
Generated By: LCT Modules.
For Whom: End User.
Remedy: Reduce the number of select statements and resubmit the request. Alternatively the select statements can be
broken into multiple fastexport jobs.

9111 The DATE has reached 9999-12-31 23:59:59.
Explanation: It is returned by the evlbuild logic to the AMP when the UNTIL_CHANGE value (9999-12-31) is encountered
which is either an input date or a date which is obtained by performing an arithmetic operation in the evlexpand
logic. When this code is returned in the sutexpand algorithm, the expansion loop breaks and the next row is read for expansion. This code is used as a graceful exit in the algorithm. This is not intended for the end user and is used for internal logic
purpose only.
Generated By: EVL (evlexpand)
For Whom: sutexpand (To gracefully exit from the expansion loop).
Remedy: NA.

Above are list of Teradata Errors or Failure Codes from Error 9103 To 9111 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.

Thanks,
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 *