SQL2800N CREATE, DROP, or CHANGE NODE failed. Reason code "<reason-code>".
Cause: The utility failed to add, drop, or change the node because the input parameters specified are invalid as indicated by the following reason codes:
Action: The action corresponding to the reason code is:
SQL2801N The syntax of the DB2NCRT command is incorrect.
Cause: The DB2NCRT utility creates a new node in a partitioned database system.
DB2NCRT /n:node [/h:host]
[/m:machine]
[/p:port]
[/i:instance]
[/u:username,password]
The command options are:
Action: Issue the DB2NCRT command with one of the valid command options.
SQL2802N The syntax of the DB2NCHG command is incorrect.
Cause: The DB2NCHG utility changes or updates node configuration for a given node in a partitioned database system.
DB2NCHG /n:node [/h:host]
[/m:machine]
[/p:port]
[/i:instance]
[/u:username,password]
The command options are:
Action: Issue the DB2NCHG command with one of the valid command options.
SQL2803N The syntax of the DB2NDROP command is incorrect.
Cause: The DB2NDROP utility drops a node from a partitioned system.
DB2NDROP /n:node [/i:instance]
The command options are:
Action: Issue the DB2NDROP command with one of the valid command options.
SQL2804N The syntax of the DB2NLIST command is incorrect.
Cause: The DB2NLIST utility list all nodes in a partitioned system.
DB2NLIST [/i:instance]
[/s]
The command options are:
Action: Issue the DB2NLIST command with one of the valid command options.
SQL2805N A service error has occurred. Reason code "<reason-code>".
Cause: A service error has occurred during CREATE, DROP or ADD NODE processing as indicated by the following reason codes:
Action: The action corresponding to the reason code is:
If the problem persists, examine the db2diag.log for problem determination information and contact an IBM Service Representative for assistance.
SQL2806N Node "<node>" not found for instance "<instance>".
Cause: DB2NDROP failed because the node does not exist.
Action: Ensure the node number is correct and reissue the command.
SQL2807N Node "<node>" already exists for instance "<instance>".
Cause: DB2NCRT failed because the node already exists.
Action: Ensure the node number is correct and reissue the command.
SQL2808W Node "<node>" for instance "<instance>" has been deleted.
Cause: The DB2NDROP processing has completed successfully.
Action: No further action is required.
SQL2809W Node: "<node>" added to instance: "<instance>" {Host: "<host-name>" Machine: "<machine-name>" Port: "<port-num>"}
Cause: The DB2NCRT processing has completed successfully.
Action: No further action is required.
SQL2810W Node: "<node>" changed in instance: "<instance>" {Host: "<host-name>" Machine: "<machine-name>" Port: "<port-num>"}
Cause: The DB2NCHG processing has completed successfully.
Action: No further action is required.
SQL2811N The command is invalid because the instance is not a partitioned database instance.
Cause: The command is only valid if the instance is a partitioned database instance.
Action: Ensure that the specified instance name is valid. If the instance name is not specified on the command line, ensure that the DB2INSTANCE environment is set to a valid partitioned database instance.