- The SAP HANA lifecycle manager (HLM) is installed and configured on the SAP HANA system.
- Read the SAP HANA Update and Configuration Guide.
- For offline update, Make sure that all the necessary installation files for the individual components available in the repository.
- Make sure that a valid, permanent SAP license for the SAP HANA database is applied.
- Take the necessary backups for the SAP HANA database and the other components (including config files).
- Stop all processes.
- Perform an automated Update with the SAP HANA lifecycle manager (HLM).
- Update the depending components.
- Perform the post-update steps.
- Restart all processes.
Please note the following:
- Do NOT under any circumstances upgrade from maintenance revision 69.01 to SP revision 70.00 (SPS 07) due to the incompatibility of these 2 versions.
- In SAP HANA Database Revisions 64 – 66 due to a programming error it is possible that an inconsistency between main and delta of column store tables can occur. So you need to follow these instructions.
- Prevent the inconsistencies from happening again by running the python script(SAP note 1919033).
- There is the python script keepTransaction.py attached to the note 1919033
- Download the python script and start it on your system. Therefore, login as sidadm user and execute the following command:
nohup python -u <path_to_python_script>keepTransaction.py <master indexserver host> 3<instanceid>15 <username> <password> &
- The database user provided as input parameter for the script needs at least the roles “PUBLIC” and “MONITORING”.
2. Before upgrading the system ,merge all tables to repair potential inconsistencies as described in SAP Note
- There are 4 files attached to the SAP note 1919034 including several SQL Statements and procedures. Additionally, there are explanations for each statement and procedure in the files.
- Make sure that the script keepTransaction.py is running.
- In the attribute.ini section idattribute set parameter check_duplicates_on_merge = on
- Execute all statements in preparation-1.sql as SYSTEM user. This creates a temporary schema, helper procedures, tables and views.
- Check with the statements provided in preparation-2.sql which users own schemas and need to grant privileges to user SYSTEM. Additionally, there is the option to adjust the tables which will be merged. This adjustment is not recommended because all tables should be merged before upgrading the system.
- Each user which was found in the above step needs to adjust and run the SQL statements in preparation-3.sql to allow SYSTEM user to merge the tables (details can be found in the file).
- As SYSTEM user check with the statements provided in execution.sql if all rights have been granted and start the merge process by calling procedure MERGE_ALL_TABLES.
- When the procedure has finished successfully, upgrade the system to SP7 or any newer revision..
- Set the parameter check_duplicates_on_merge back to default value.
- If the system cannot be upgraded immediately after performing above steps, the script keepTransaction.py needs to be running until the upgrade.
Important SAP Notes: