- 17.4 MySQL Cluster Programs
- 17.4.1 MySQL Server Usage for MySQL Cluster
- 17.4.2 ndbd — The MySQL Cluster Data Node Daemon
- 17.4.3 ndbmtd — The MySQL Cluster Data Node Daemon (Multi-Threaded)
- 17.4.4 ndb_mgmd — The MySQL Cluster Management Server Daemon
- 17.4.5 ndb_mgm — The MySQL Cluster Management Client
- 17.4.6 ndb_config — Extract MySQL Cluster Configuration Information
- 17.4.7 ndb_cpcd — Automate Testing for NDB Development
- 17.4.8 ndb_delete_all — Delete All Rows from an NDB Table
- 17.4.9 ndb_desc — Describe NDB Tables
- 17.4.10 ndb_drop_index — Drop Index from an NDB Table
- 17.4.11 ndb_drop_table — Drop an NDB Table
- 17.4.12 ndb_error_reporter — NDB Error-Reporting Utility
- 17.4.13 ndb_print_backup_file — Print NDB Backup File Contents
- 17.4.14 ndb_print_schema_file — Print NDB Schema File Contents
- 17.4.15 ndb_print_sys_file — Print NDB System File Contents
- 17.4.16 ndbd_redo_log_reader — Check and Print Content of Cluster Redo Log
- 17.4.17 ndb_restore — Restore a MySQL Cluster Backup
- 17.4.18 ndb_select_all — Print Rows from an NDB Table
- 17.4.19 ndb_select_count — Print Row Counts for NDB Tables
- 17.4.20 ndb_show_tables — Display List of NDB Tables
- 17.4.21 ndb_size.pl — NDBCLUSTER Size Requirement Estimator
- 17.4.22 ndb_waiter — Wait for MySQL Cluster to Reach a Given Status
- 17.4.23 Options Common to MySQL Cluster Programs
ndb_print_schema_file obtains diagnostic information from a cluster schema file.
Usage:
ndb_print_schema_file file_name
file_name is the name of a cluster
schema file. For more information about cluster schema files,
see Cluster Data Node FileSystemDir Files.
Like ndb_print_backup_file and
ndb_print_sys_file (and unlike most of the
other NDB utilities that are
intended to be run on a management server host or to connect
to a management server)
ndb_schema_backup_file must be run on a
cluster data node, since it accesses the data node file system
directly. Because it does not make use of the management
server, this utility can be used when the management server is
not running, and even when the cluster has been completely
shut down.
Additional Options: None.
User Comments
Add your own comment.