SQL/MX 2.x Messages Manual (H06.10+, J06.03+)

SQL/MX MXCMP Messages (2000 through 2999)
HP NonStop SQL/MX Messages Manual—544518-011
4-6
SQL 2017
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. Rebalance the system or add hardware.
SQL 2018
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. Check your process configuration.
SQL 2019
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. You might need to rebalance the system.
2017 Server process name could not be created - no more
processes (PCBs) available.
2018 Server process name could not be created - library
conflict.
2019 Server process name could not be created - unable to
allocate virtual memory.