Teradata Database Message 9103 - 9103 - Analytics Database - Teradata Vantage
Teradata® VantageCloud Lake - Analytics Database Messages
- Edition
- Lake
- Product
- Analytics Database
- Teradata Vantage
- Published
- October 2022
- Language
- English (United States)
- Last Update
- 2024-02-26
- dita:mapPath
- tzr1629746512312.ditamap
- dita:ditavalPath
- ft:empty
- dita:id
- vza1585613049811
- lifecycle
- latest
- Product Category
- Teradata® Vantage™
- Message
- 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. c) If the session transaction mode is ANSI or the temporal behavior is ANSI Temporal behavior then TEMPORAL_TIMESTAMP generated in the parser is used for timestamping the TransactionTime column by default. When concurrent transactions are happening, if one transaction started early and another transaction started later, the later transaction modifies a row and the earlier transaction tries to modify the same row then it may result in begin value greater than the end value for the TransactionTime column. The same behavior can occur when the session TTGranularity is set to the transaction level and the session transaction mode is either ANSI or Teradata and the session temporal behavior is either ANSI Temporal behavior or Teradata Temporal behavior. This problem will not happen when the request comes through UNITY since timestamping of the TransactionTime column happens at the request level always.
- Generated By
- Period constructor function.
- For Whom
- End User.
- Notes
- None
- Remedy
- Correct the bound values and re-submit. If the problem is due to timestamping of the TransactionTime column at transaction level then set the session TTGranularity to logical row level.