Messages Reference

SQL2800 - SQL2899

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:

(1) The node number is not specified
(2) The TCP/IP host name is not specified
(3) The computer name is not specified
(4) The node number is invalid.
(5) The port number is invalid.
(6) The TCP/IP host name is invalid.
(7) The port value is not defined for your instance in the services file.
(8) The port value is not in the valid range defined for your instance in the services file.
(9) The node number is not unique.
(10) The host name/port couple is not unique.
(11) The host name value has no corresponding port 0.

Action: The action corresponding to the reason code is:

(1) Ensure that the node number is specified
(2) Ensure that the TCP/IP host name is specified
(3) Ensure that the computer name is specified
(4) Ensure that the node number is between 0 and 999.
(5) Ensure that the port number is between 0 and 999.
(6) Ensure that the host name specified is both defined on the system and is operational
(7) Ensure that the TCP/IP services on your system contains an entry for your instance
(8) Ensure that you only use port values that are specified in the services file on your system
(9) Ensure that the node number specified is unique.
(10) Ensure that the new host name/port is not already defined in the db2nodes.cfg file.
(11) Ensure that the port value 0 has been defined for host name specified.

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  /u:username,password
           [/i:instance]
           [/h:host]
           [/m:machine]
           [/p:port]
           [/o:instance owning machine]
           [/g:netname]

The command arguments are:

/n Specify the node number
/u to specify the account name and password for the DB2 service.

The command options are:

/i Specify the instance if different from the default/current instance
/h Specify the TCP/IP host name if the host name is not the machine default TCP/IP host name
/m Specify the workstation name if the node is created on a remote machine
/p Specify the logical port number if this is not the first node on the machine
/o Specify the computer name of the instance owning machine when creating the first node on a machine.
/g Specify the network name or IP Address.

Action: Enter the command again using valid parameters.

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]
                    [/g:netname]

The command options are:

/h Change the TCP/IP host name
/m Change the workstation name
/p Change the logical port number
/i Specify the instance if different from the default/current instance
/u Change the Logon Account name and password
/g Specify the network name or IP Address

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:

/i Specify the instance if different from the default/current instance

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:

/i Specify the instance if different from the default/current instance
/s Display node status

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:

(1) Unable to register the service
(2) Unable to set the required User Rights Policy
(3) Unable to set the Logon Account for the service
(4) Unable to delete the service

Action: The action corresponding to the reason code is:

(1) If the workstation name is specified during DB2NCRT, ensure that the workstation name is correct.
(2) Ensure that the user name specified is valid.
(3) Ensure that the user name and the password specified are valid.
(4) If the node resides on another machine, ensure that the machine is running.

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.

SQL2812N An invalid argument was entered for the db2drvmp command.

Cause: Usage:

db2drvmp  add       node_number from_drive to_drive
          drop      node_number from_drive
          query     [ node_number ] [ from_drive ]
          reconcile [ node_number ] [ from_drive ]

Valid arguments for this command are:

add: assign a new database drive map.
drop: remove an existing database drive map.
query: query a database map.
reconcile: repair a database map drive when the registry contents are damanged.
node_number: the node number. The parameter is required for add and drop operations.
from_drive: the drive letter to map from. This parameter is required for add and drop operations.
to_drive: to drive letter to map to. This parameter is required only for add operation. It is not applicable for any other operations.

Action: Enter the command again using valid arguments.

SQL2813I The drive mapping from drive "<drive-1>" to drive "<drive-2>" was added for node "<node>".

Cause: The drive mapping was added successfully.

Action: No action necessary.

SQL2814I The drive mapping from drive "<drive>" was deleted for node "<node>".

Cause: The drive mapping was deleted successfully.

Action: No action necessary.

SQL2815I The drive mapping for node "<node>" is: "<drive-1>" - "<drive-2>".

Cause: Informational message.

Action: No action necessary

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]