HP NonStop SQL/MX Messages Manual page 102

SQL/MX MXCMP Messages (2000 through 2999)
SQL 2017
2017 Server process name could not be created on node - no
more processes (PCBs) available.
Where name is the server process name.
Cause. NonStop SQL/MX was unable to create server process name, because no
more process control blocks (PCBs) were available.
Effect. NonStop SQL/MX does not create the server process because too many
processes are running to allow more to be created.
Recovery. Do not attempt recovery. Contact your service provider.
SQL 2018
2018 Server process name could not be created on node -
library conflict.
Where name is the server process name.
Cause. NonStop SQL/MX was unable to create server process name because of a
library conflict. The process you are trying to create has a different library than the one
that is already running.
Effect. The operation fails.
Recovery. Do not attempt recovery. Contact your service provider.
SQL 2019
2019 Server process name could not be created on node -
unable to allocate virtual memory.
Where name is the server process name.
Cause. NonStop SQL/MX was unable to create server process name because it was
unable to allocate enough virtual memory to start the process.
Effect. The operation fails.
Recovery. Do not attempt recovery. Contact your service provider.
HP NonStop SQL/MX Messages Manual—640324-001
4 -6