Parallel Database Extensions (PDE) Message 13906 - 13906 - Analytics Database - Teradata Vantage
Analytics Database Messages
- Deployment
- VantageCloud
- VantageCore
- Edition
- Enterprise
- IntelliFlex
- VMware
- Product
- Analytics Database
- Teradata Vantage
- Release Number
- 15.xx,16.xx,17.xx
- Published
- June 2022
- ft:locale
- en-US
- ft:lastEdition
- 2023-01-05
- dita:mapPath
- sfx1628096178347.ditamap
- dita:ditavalPath
- ft:empty
- dita:id
- B035-1096
- lifecycle
- latest
- Product Category
- Teradata Vantageā¢
- Message
- %s
- Explanation
- An "impossible" condition has been detected in PdeMain or PdeLib. PDE code contains a number of assertions for conditions that should never occur. The occurrance of one of these conditions is known as an assertion failure. Catching assertion failures at the point where they occur can be useful for debugging on development and test systems. In a production environment, though, stopping the program at the point where an assertion fails is not useful, and may seem to cause Teradata to hang inexplicably. Therefore, by default, when an assertion fails, this message is logged to note the fact that the error occurred, and the programs that detected the error tries to continue running. The result of doing this is generally unpredictable. Depending on the exact condition being asserted, this may range from an immediate fatal error at one extreme, to having no apparent affect at the other extreme. In other cases, Teradata will continue to run, but with unexpected results. In a debugging environment, asserts can be made to cause a dialog box to pop up, stopping the program at the point where the error occurred so that it can be debugged. To enable this, put a line containing: set pdeassert 1 in the startup.txt file in the PDE configuration file directory.
- Generated By
- PDE initialization.
- For Whom
- System Support Representative.
- Notes
- None
- Remedy
- Contact the Global Support Center.