8.2 DUMP Commands

8.2.1 DUMP Codes 1 to 999
8.2.2 DUMP Codes 1000 to 1999
8.2.3 DUMP Codes 2000 to 2999
8.2.4 DUMP Codes 3000 to 3999
8.2.5 DUMP Codes 4000 to 4999
8.2.6 DUMP Codes 5000 to 5999
8.2.7 DUMP Codes 6000 to 6999
8.2.8 DUMP Codes 7000 to 7999
8.2.9 DUMP Codes 8000 to 8999
8.2.10 DUMP Codes 9000 to 9999
8.2.11 DUMP Codes 10000 to 10999
8.2.12 DUMP Codes 11000 to 11999
8.2.13 DUMP Codes 12000 to 12999

Never use these commands on a production MySQL Cluster except under the express direction of MySQL Technical Support. Oracle will not be held responsible for adverse results arising from their use under any other circumstances!

DUMP commands can be used in the Cluster management client (ndb_mgm) to dump debugging information to the Cluster log. They are documented here, rather than in the MySQL Manual, for the following reasons:

General syntax:

ndb_mgm> node_id DUMP code [arguments]

This causes the contents of one or more NDB registers on the node with ID node_id to be dumped to the Cluster log. The registers affected are determined by the value of code. Some (but not all) DUMP commands accept additional arguments; these are noted and described where applicable.

Individual DUMP commands are listed by their code values in the sections that follow. For convenience in locating a given DUMP code, they are divided by thousands.

Each listing includes the following information:


DUMP command codes are not necessarily defined sequentially. For example, codes 2 through 12 are currently undefined, and so are not listed. However, individual DUMP code values are subject to change, and there is no guarantee that a given code value will continue to be defined for the same purpose (or defined at all, or undefined) over time.

There is also no guarantee that a given DUMP code—even if currently undefined—will not have serious consequences when used on a running MySQL Cluster.

For information concerning other ndb_mgm client commands, see Commands in the MySQL Cluster Management Client.