Parallel Database Extensions (PDE) Message 13805 - 13805 - 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
- Required node not available for vproc %d.
- Explanation
- The VConfig GDO specifies that the virtual processor run on a particular node, and that node is not currently running.
- Generated By
- PDE Initialization.
- For Whom
- System Support Representative.
- Notes
- The specified vproc is not started, but PDE initialization otherwise continues normally. However, the lack of this vproc may lead to other problems during DBS startup.
- Remedy
- When the required node for a vproc is back up, force a TPA restart to get the vproc running again. Verify that the vproc actually requires a specific node; if not, use vconfig utility to alter the vproc definition to make it movable. This could also be due to corruption of the VConfig or VprocConfig GDO. Run vconfig -x and vprocgdo to display these GDOs. If they are not correct, rerun vconfig and force a TPA restart.