Checking System After Configuration

the postcheck command helps capture critical node health states and metrics after the {{ocient}} configuration process you can run the command as shown in this example the flags included after the precheck command are optional see /#flags for command execution for descriptions $ sudo /usr/local/bin/postcheck dsn ocient //ur sql0 4050/system;user=admin\@system;password=admin the command invokes a script from the command line on operating systems supported by ocient the script sends output to standard output (stdout) and standard error (stderr) with the option to send a text file or a json file to specify the file option, use this flag logfile location \<directory> where \<directory> is the directory where the postcheck command creates the log file before you begin, ensure that all steps in the docid 4005nflvguw4fqfqa1spu process are complete prerequisites the script requires java® and the ocient jdbc jar to run in most cases, you should use this script on client servers rather than database nodes to get the post check script onto a client, perform the scp operation on the wheel onto the server and run python3 m pip install no index \<path to wheel>/postcheck whl , and replace \<path to wheel> with the path to the directory of the wheel file on your server flags for command execution use the postcheck command to run the script that checks the system configuration after you configure ocient you can execute the command using these flags flag name required values default description example dsn yes many not applicable data source name (dsn) the script prompts for your credentials dsn ocient //host\ port/path connects you to the specified cluster where host is the host name, port is the port number, and path is the path on the host for the connection logfile location no non empty string /var/opt/ocient/log name of directory that contains the log file created from the execution of the script logfile location /user/query/logs generates a log file in the /user/query/logs directory if this directory does not exist, the command issues a warning print level no verbose or silent verbose denotes the level of detail in the output see the “outputs” section print level verbose provides a detailed report with information about the checks that ocient performs print level silent provides the overall status from the check of the system timeout no any integer 3 denotes the default timeout (in seconds) for running any command line command in the script in most cases, the default is enough, so you do not need to specify this setting timeout 4 runs checks with a timeout of 4 seconds for each command jar path no non empty string /opt/ocient/current/ocient jdbc4 jar denotes the path to the ocient jdbc jar the default value is the usual location of the jar file on an ocient system this path must be accurate for the postcheck command to run correctly jar path /opt/ocient/test dir/jdbc jar uses the jar at /opt/ocient/test dir/jdbc jar to run jdbc commands for the postcheck command json no not applicable false if you specify the json flag, the command prints output in json format to stdout if you do not specify this flag, the command prints human readable output to stdout json prints output in json format to stdout command output the command has two types of output, silent or verbose, which you can specify by using the print level flag at the command line silent the silent value for the print level flag only produces a status code the code is 0 for success, 1 for error, and 2 for warning verbose the verbose value for the print level flag prints either human readable output by default or output in json format (if you specify the json flag) the output contains all status details this example shows human readable output warnings \ foundation nodes storage are non uniform os configuration ok \================ huge page settings ok isolcpus settings ok memory ok \====== foundation nodes 1024 gb sql nodes 1024 gb loader nodes 1536 gb total dram 123120 gb this example shows output in json format {"status" 2, "components" { "firmware" { "status" 0, "message" "success nvme drive firmware is consistent across nodes " } "symmetry" { "status" 2, "message" "warning non uniform configuration " "storage" { "status" 2, "foundation" { "status" 0, "message" "success storage consistent across foundation nodes " "foundation1" 16tb, } } } related links docid 4005nflvguw4fqfqa1spu docid\ nneedy7yn8g1pennmamng