The action parameter specifies the check action to be performed.
To see what check actions are available, including a description of what they do, call the procedure GET_CHECK_ACTIONS by executing the following statement:
CALL GET_CHECK_ACTIONS ('CHECK_TABLE_CONSISTENCY')
To execute all available check actions in a single procedure call, specify CHECK as the action as follows:
CALL CHECK_TABLE_CONSISTENCY ('CHECK', '<schema>', '<table>')
Note
Some check actions are contained within others and are therefore not explicitly executed when you execute the CHECK action. Repair actions are also excluded from the CHECK action as they are not checks as such and make changes to the data.
The parameters schema_name and table_name are used to specify the schema(s) and table(s) to be checked. If you want to check all tables in all schemas, then specify NULL as the value for these parameters.
Example
To perform all check actions on all tables, execute the statement CALL CHECK_TABLE_CONSISTENCY ('CHECK', NULL, NULL).
Result
The procedure returns a results table with the following columns:
● SCHEMA_NAME
● TABLE_NAME
● COLUMN_NAME
● PART_ID
● ERROR_CODE
● ERROR_MESSAGE
If no errors are found, the results table is empty. If errors are found, it is recommended that you contact SAP Support to interpret the results and advise on the required action.
2.6.12 Catalog Consistency Check
The catalog consistency check is a procedure available in the SAP HANA database with which you can perform a range of consistency check actions on the database catalog. The frequency with which you do this depends on your scenario.
Recommendation
Running these database checks affects system performance. Therefore, it is recommended that you make a system copy and run the checks there instead of on your production system.
To use this procedure, you must have the system privilege DATA ADMIN or CATALOG READ.
Execution
You can call the table consistency check by executing the following statement in the SQL console of the SAP HANA studio or using the SAP HANA HDBSQL command line tool:
CALL CHECK_CATALOG_CONSISTENCY
('<action>','<schema_name>','<object_name>','<catalog_object_type>')
Input Parameters
The action parameter specifies the check action to be performed.
To see what check actions are available, call the procedure GET_CHECK_ACTIONS by executing the following statement:
CALL GET_CHECK_ACTIONS ('CHECK_CATALOG_CONSISTENCY')
To execute all available check actions in a single procedure call, specify CHECK as the action as follows:
CALL CHECK_CATALOG(CHECK,<schema_name>','<catalog_object_name>',NULL)
The parameters schema_name and object_name specify the schema(s) and object(s) to be checked. If you want to check all objects in all schemas, then specify NULL as the value for these parameters.
The parameter catalog_object_type specifies the object type(s) to be checked. However, it is not supported. You must specify NULL as the value for this parameter.
Example
To perform all check actions on all objects of all types, execute the statement CALL CHECK_CATALOG(‘CHECK’,NULL,NULL,NULL)
Result
The procedure returns a results table with the following columns:
● SCHEMA
● OBJECT
● OBJECT_TYPE
● ERROR_CODE
● ERROR_MESSAGE
If no errors are found, the results table is empty. If errors are found, it is recommended that you contact SAP Support to interpret the results and advise on the required action.
2.7 Hardware Checks for Tailored Data Center Integration
The SAP HANA HW Configuration Check Tool allows you to check the interoperability of SAP HANA with your existing enterprise storage in production environments.
In addition to SAP HANA as standardized and highly optimized appliance, SAP now offers the opportunity to run the SAP HANA server with a customer’s preferred storage solution. This option enables you to reduce hardware and operational costs through the reuse of existing hardware components and operational processes. SAP HANA server means the exact same bill of material as the certified SAP HANA appliance but without storage.
The SAP HANA HW Configuration Check Tool is a framework that provides tests and reports for new single host and scale out systems to determine if the hardware you intend to use meets the minimum performance criteria required to run SAP HANA in production use.
2.7.1 Installing the SAP HANA HW Configuration Check Tool
The SAP HANA HW Configuration Check Tool allows you to measure the performance of your hardware components to ensure they meet the criteria for running SAP HANA.
Prerequisites
● Check that you are using the latest version of the tool set.
● You should be able to run this tool set as the root user.
● When using the SAP HANA HW configuration check tool set to evaluate a distributed landscape the binaries should be available from a shared directory so every server can execute it. This means that the same version of the tool set must be installed on each server in the system.
● Check that you have Python installed. Usually this comes already installed on SLES 11.
● Ensure that you have already exchanged SSH keys between the different hosts so that the workflow can take place without passwords.
● Check that hostname resolution should work in both directions for fully qualified domain names.
Context
You can download the tool as a SAR file. For more information, see Software Download in the SAP HANA Master Guide.
We recommend that you put the binaries in a shared location, for example in a directory parallel to your main SAP HANA installation directory. This avoids any potential problems with sharing the binaries for distributed tests.
Make sure that the same version is installed on every server.
Procedure
1. Copy the SAR file to the Linux system hosting your SAP HANA server 2. Install the tool by executing this command:
SAPCAR -xvf <SAR-FILE-NAME>
Results
A new directory /hana/shared/sapcct/ is created.
Related Information
SAP HANA Master Guide
2.7.2 Using the SAP HANA HW Configuration Check Tool
The SAP HANA HW Configuration Check Tool requires a test profile to be set up describing the type of testing to be carried out.
The profile is described using JavaScript Object Notation (JSON). Before you run the profile ensure that it contains no syntax errors. The profile has two logical parts. The first part describes where to start the testing and the corresponding information required to do the testing. The second part is the actual testing itself, which needs to be described in the test array, meaning the actual combination of test modules chosen for the test.