Replica node is: 2 initialGci: 2 numCrashedReplicas = 0 nextLcpNo = 1 LcpNo[0]: maxGciCompleted: 1 maxGciStarted: 2 lcpId: 1 lcpStatus: valid LcpNo[1]: maxGciCompleted: 0 maxGciStarted: 0 lcpId: 0 lcpStatus: invalid -------Stored Replica---------- Replica node is: 3 initialGci: 2 numCrashedReplicas = 0 nextLcpNo = 1 LcpNo[0]: maxGciCompleted: 1 maxGciStarted: 2 lcpId: 1 lcpStatus: valid LcpNo[1]: maxGciCompleted: 0 maxGciStarted: 0 lcpId: 0 lcpStatus: invalid ------ Fragment with FragId: 1 -------- Preferred Primary: 3 numStoredReplicas: 2 numOldStoredReplicas: 0 distKey: 0 LogPartId: 1 -------Stored Replica---------- Replica node is: 3 initialGci: 2 numCrashedReplicas = 0 nextLcpNo = 1 LcpNo[0]: maxGciCompleted: 1 maxGciStarted: 2 lcpId: 1 lcpStatus: valid LcpNo[1]: maxGciCompleted: 0 maxGciStarted: 0 lcpId: 0 lcpStatus: invalid -------Stored Replica---------- Replica node is: 2 initialGci: 2 numCrashedReplicas = 0 nextLcpNo = 1 LcpNo[0]: maxGciCompleted: 1 maxGciStarted: 2 lcpId: 1 lcpStatus: valid LcpNo[1]: maxGciCompleted: 0 maxGciStarted: 0 lcpId: 0 lcpStatus: invalid 

## 23.4.20 ndb_print_schema_file — Print NDB Schema File Contents 

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 NDB Cluster Data Node File System Directory. 

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_print_schema_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. 

## 23.4.21 ndb_print_sys_file — Print NDB System File Contents 

ndb_print_sys_file  obtains diagnostic information from an NDB 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_ # _fs/D # / DBDIH/P # .sysfile . In each case, the #  represents a number (not necessarily the same number). For more information, see NDB Cluster Data Node File System Directory. 

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 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. 

