This topic describes how to use HostChecker to configure SAP ASE environments.
What is HostChecker?
Please note that HostChecker does not communicate changes made to hosts back to the Delphix Engine. If you reconfigure a host, you must refresh the host in the Delphix Engine in order for it to detect your changes.
You can run the tests contained in the HostChecker individually, or all at once. You must run these tests on both the source and target hosts to verify their configurations. As the tests run, you will either see validation messages that the test has completed successfully, or error messages directing you to make changes to the host configuration.
The procedure Delphix administrators need to perform to validate target database servers using Hostchecker can be found at Using HostChecker to Validate Target Database Servers.
- Make sure that your source and target environments meet the requirements specified in SAP ASE Support and Requirements.
Download the HostChecker tarball matching the host's operating system from https://download.delphix.com/ (for example: hostchecker_linux_x86.tar).
Create a working directory and extract the HostChecker files from the HostChecker tarball.
mkdir dlpx-host-checker cd dlpx-host-checker/ tar -xf hostchecker_linux_x86.tar
Change to the working directory and enter this command. Note that for the target environments, you would change
$ cd hostchecker $ ./hostchecker.sh Extracting the JDK from the tarball jdk.tar.gz. Please enter whether this machine is a source or a target:target 1: Check ASE environment 2: Check all ASE instances 3: Check all the Oracle installations 4: Check homedir permissions 5: Check Linux Performance Settings 6: Check mkdir and rmdir 7: Check the MySQL installation 8: Check network port access 9: Check the Oracle CRS home 10: Check for ssh connectivity 11: Check sshd_config for timeout configuration 12: Check user sudo privileges 13: Check toolkit path all: Execute all checks quit: Exits Please select an option:
Don't Run as Root
Don't run the HostChecker as root; this will cause misleading or incorrect results from many of the checks.
Select which checks you want to run. We recommend you run all checks (excluding Oracle and MySQL) if you are running Hostchecker for the first time.
- Pass in the arguments the checks ask for.
Read the output of the check.
- The error or warning messages will explain any possible problems and how to address them. Resolve the issues that the HostChecker describes. Don't be surprised or undo your work if more errors appear the next time you run HostChecker, because the error you just fixed may have been masking other problems.
- Repeat steps 3–7 until all the checks return no errors or warnings.
|Check ASE environment||X||X|
|Check All ASE instances||X||X|
Attempts to connect to each running ASE instance via "isql_r64" (utilizing the $SYBASE/interfaces file) and execute the following queries:
|Check all the Oracle installations||N/A||N/A|
|Check homedir permissions||X||X|
Check that the home directory, the ~/.ssh directory, and the ~/.ssh/authorized_keys file exist, that they are owned by the user invoking this check, and that they are not 'group' or 'other' writable.
|Check <OS> Performance Settings||X||Check target's kernel settings necessary to optimize performance. See Target Host OS and Database Configuration Options|
|Check mkdir and rmdir||X||Tests that the user can mkdir and rmdir under both the toolkit directory and the specified mount path.|
|Check the MySQL installation||N/A||N/A|
|Check network port access||X||X||Can be used to test access to specified ports on the Delphix Engine. See Network and Connectivity Requirements for SAP ASE Environments for a list of ports.|
|Check the Oracle CRS home||N/A||N/A|
|Check Oracle DB Instance||N/A||N/A|
|Check for ssh connectivity||X||X||Verifies that the environment is accessible via SSH|
|Check sshd_config for timeout configuration||X||Check that sshd_config does not contain ClientAliveInterval or ClientAliveCountMax entries.|
|Check toolkit Path||X||X||Verifies that the toolkit installation location has the proper ownership, proper permissions, and enough free space.|
|Check user sudo privileges||X||X||Verifies that the operating system user can execute certain commands with necessary privileges via |