Parallel Database Extensions (PDE) Message 13831 - 13831 - 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
Too many vprocs assigned to node to start vproc %d.
Explanation
The specified vproc cannot be started because the maximum allowable number of vprocs have already been started that node. This is most likely due to assigning too many vprocs to a single clique. When all nodes in the clique are up, vprocs can be distributed among them without exceeding the limit, but when only one node in the clique is up, there are too many vprocs to be migrated to that node.
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
This is probably due to an incorrect PDE configuration. 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.