Thursday, March 23, 2017

HANA Database 1.0 - Update from SPS11 to SPS12


1.       You have installed SAP HANA Database 1.0 SPS11
2.       You have installed one of the following OS versions:
SLES 11 (SP3 or SP4)
SLES 12 (SP1)
RHEL 6.7
RHEL 7.2

3.       You have SAP Host Agent version 7.21.11 or newer

Attention! More complete information about supported operation systems, you can find in SAP Note 2235581 – SAP HANA: Supported Operating Systems.
Attention! Before update process has been started, recommended complete backup database.

Update Process:

For update, we will use the SAP HANA database lifecycle manager (hdblcm) in console or native GUI mode. For update, we will use user ROOT !!!
Step 1
Unpack the archive in to the extraction directory, passing the option –manifest SIGNATURE.SMF to SAPCAR

SAPCAR -xvf IMDB_SERVER100_122_7-10009569.SAR -manifest SIGNATURE.SMF

p.s. Another case you will get the following error:

File 'SIGNATURE.SMF' cannot be found in the SAP HANA Database installation kit. You can ignore this error and continue with the execution by passing the ignore option 'check_signature_file' to hdblcm, started as root. See SAP note 2078425, section 'How to prepare SAP HANA packages for installation or update' for instructions how to prepare packages for update or implications of ignoring this error.

Step 2
Run the hdblcm tool. You can find it in the extracted directory (SAP_HANA_DATABASE)

Choose the index number 1
Next, choose the index number 2 (server), and enter password for <sid>adm and SYSTEM users.

After this, we will see summary:

After finished update process, we will get confirm message:

SAP HANA components updated

Attention! Please check the created log file, in our case '/var/tmp/hdb_TST_hdblcm_update_2017-03-16_16.47.30/hdblcm.log' 

Possible Problems:

In update process, you can face with different problems. For example, you have installed an additional components, in our case is AFL (Application Function Libraries), and this component is incompatible with new version on HANA database you will want to install. In result you will get the same error message:

For issues this problem you need reinstallation this component as follows:
       1.  Uninstall the AFL component
You can uninstall components by using hdblcm tool. Start the hdblcm tool by super user (root):

[root@<server_name> ~]# /hana/shared/<SID>/hdblcm/hdblcm

Choose the index number 7 (uninstall) and then choose the component for uninstall (for our case is number 3).

      2.  After uninstallation has been completed, you can continue the update of HANA database.
      3.  After HANA database update process has been completed, you must install additional component uninstalled on step 1:

You can install components by using hdblcm tool. Start the hdblcm tool by super user (root):

[root@<server_name> ~]# /hana/shared/<SID>/hdblcm/hdblcm -component_dirs=<component_dir_path>

Choose the index number 14

Then you choose the component you will want to install. In our case Index 2 and after you will input <sid>adm user password, the component will be installed.

Now, all looks like fine!

Good luck! 

Tuesday, May 6, 2014

BDLS. Performance Problem

Every SAP Basis faced with creating test system with another ID. In that case we must use BDLS for changing logical names in database tables. The BDLS processing may take very long time. And increasing the time will depend on the size growth of the database.
How can we reduce the BDLS processing time?
For the answer for this question I have write this article.

So… First key point is “Test run” option. We must always perform the changing of logical names in two steps. The first step is perform with enabled “Test run” option. The test run enables create the tables list to be converted (remember not all tables must have the converted), and speed up the real run, because no longer has to check every table. Below, you may see example pic:

In my case, “Test run” takes longer time unlike real update mode. After the test run was completed, you can find in BDLSS the report with tables which to be updated. Now you can run in real update mode.

Using this simple method i can change the logical names for four hours, on the system with size about 5,5 Tb.
But, we can reduce this time. For this, we must turn to report (BDLSS) and mark the tables with many rows for update, there we find the column names with existing the rows for update. With this information we can manually update some tables using simple SQL expression. Below I explain how you can change the logical names with manually correction with maximum reduction of time.   

Every time you update the test system, you must change the logical names in the same SAP tables (not Z tables, their number can change)!!! So, you can create the list of tables which you want to update using SQL expression. These tables you must put in exception list, transaction BDLSC:

Now BDLS will ignore these tables in both mode test and update mode. While BDLS is running, you can manually update them using SQL. How can you see, is very simple.   

I apologize in advance for my english