Recommended Servers for MySQLThe world's most popular open source database
- Documentation Library
- Table of Contents
- MySQL 6.0 Reference Manual
- MySQL 5.1 Reference Manual
- MySQL 5.0 Reference Manual
- MySQL 3.23/4.0/4.1 Manual
- Table of Contents
- 15.10 MySQL Cluster Utility Programs
- 15.10.1 ndb_config — Extract NDB Configuration Information
- 15.10.2 ndb_cpcd — Automate Testing for NDB Development
- 15.10.3 ndb_delete_all — Delete All Rows from NDB Table
- 15.10.4 ndb_desc — Describe NDB Tables
- 15.10.5 ndb_drop_index — Drop Index from NDB Table
- 15.10.6 ndb_drop_table — Drop NDB Table
- 15.10.7 ndb_error_reporter — NDB Error-Reporting Utility
- 15.10.8 ndb_print_backup_file — Print NDB Backup File Contents
- 15.10.9 ndb_print_schema_file — Print NDB Schema File Contents
- 15.10.10 ndb_print_sys_file — Print NDB System File Contents
- 15.10.11 ndb_select_all — Print Rows from NDB Table
- 15.10.12 ndb_select_count — Print Row Counts for NDB Tables
- 15.10.13 ndb_show_tables — Display List of NDB Tables
- 15.10.14 ndb_size.pl — NDBCLUSTER Size Requirement Estimator
- 15.10.15 ndb_waiter — Wait for Cluster to Reach a Given Status
ndb_print_sys_file obtains diagnostic information from a cluster system file.
Usage:
ndb_print_sys_file file_name
file_name is the name of a cluster
system file (sysfile). Cluster system files are located in a
data node's data directory (DataDir); the
path under this directory to system files matches the pattern
ndb_.
In each case, the #_fs/D#/DBDIH/P#.sysfile# represents a
number (not necessarily the same number). For more
information, see
Cluster Data Node FileSystemDir Files.
Like ndb_print_backup_file and
ndb_print_schema_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_print_backup_file
must be run on a cluster data node, since it accesses the data
node filesystem 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.