Skip to Content

Situation so far


This is a follow up to the HANA replication oriented tests I’m currently playing with. 

Following tests around replication :



I will now set the situation back to where I started, but with the HDB updated from 1.0.93 to 1.0.97.



Start situation :


The primary host running the HDB is on hdbtest2

The standby host is on hdbtest1

The replication is back online ( hdbtest2-> hdbtest1 )

HDB version : 1.0.93


Target :


Primary host running the HDB will be hdbtest1

The standby host will be hdbtest2

HDB version : 1.0.97

Replication will be set back ( hdbtest1 -> hdbtest2 )


Relevant docs :




NZDT update : updating the standby host


First, I update the current standby node hdbtest1.

The following entry needs to be added to the hdbuserstore :


hdbuserstore SET SRTAKEOVER hdbtest1:30015 system <password>

hdbuserstore LIST

DATA FILE      : /usr/sap/HTL/home/.hdb/hdbtest1/SSFS_HDB.DAT

KEY SRTAKEOVER

  ENV : hdbtest1:30015

  USER: system


From the hdb software SPS directory  as root :

# ./hdblcm –action=update

SAP HANA Lifecycle Management – SAP HANA 1.00.097.00.1434028111

***************************************************************

Scanning Software Locations…

Detected components:

    SAP HANA Database (1.00.097.00.1434028111) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server

    SAP HANA AFL (Misc) (1.00.097.00.1434039685) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages

    SAP HANA LCAPPS (1.00.097.000.454405) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HANA_LCAPPS_10_LINUX_X86_64/packages

    SAP TRD AFL FOR HANA (1.00.097.00.1434039685) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_TRD_AFL_LINUX_X86_64/packages

    SAP HANA Database Client (1.00.097.00.1434028111) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client

    SAP HANA Studio (2.00.0.19.000000) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio

    SAP HANA Smart Data Access (1.00.4.004.0) in /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/SAP_HANA_SDA_10/packages

Choose system to update

  Index | System            | Database Properties

  ————————————————–

  1    | HTL (update)      | 1.00.093.00.1424770727

        |                  | hdbtest1 (worker)

        |                  |

  2    | Exit (do nothing) |

Enter selected system index [2]: 1

Choose components to be installed or updated:

  Index | Components | Description

  ————————————————————————————————————————–

  1    | all        | All components

  2    | server    | Update SAP HANA Database from version 1.00.093.00.1424770727 to version 1.00.097.00.1434028111

  3    | client    | Update SAP HANA Database Client from version 1.00.093.00.1424770727 to version 1.00.097.00.1434028111

  4    | afl        | Update SAP HANA AFL (Misc) from version 1.00.093.1.1425042048 to version 1.00.097.00.1434039685

  5    | lcapps    | Update SAP HANA LCAPPS from version 1.00.093.00.451387 to version 1.00.097.000.454405

  6    | smartda    | Update SAP HANA Smart Data Access from version 1.00.3.005.0 to version 1.00.4.004.0

  7    | studio    | Update SAP HANA Studio from version 2.00.0.11.000000 to version 2.00.0.19.000000

  8    | trd        | Update SAP TRD AFL FOR HANA from version 1.00.093.1.1425042048 to version 1.00.097.00.1434039685


Enter comma-separated list of the selected indices [2,3,4,5,6,8]: 1

Enter System Administrator (htladm) Password: ***********

Enter Database User Name [SYSTEM]:

Enter Database User (SYSTEM) Password:***********

Summary before execution:

=========================

SAP HANA Components

  Update Parameters

      Remote Execution: ssh

      SAP HANA System ID: HTL

      Database User Name: SYSTEM

      SAP HANA Database Client Installation Path: /hana/shared/HTL/hdbclient

      SAP HANA Studio Installation Path: /hana/shared/HTL/hdbstudio

  Software Components

      SAP HANA AFL (Misc)

        Update from version 1.00.093.1.1425042048 to 1.00.097.00.1434039685

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages

      SAP HANA LCAPPS

        Update from version 1.00.093.00.451387 to 1.00.097.000.454405

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HANA_LCAPPS_10_LINUX_X86_64/packages

      SAP TRD AFL FOR HANA

        Update from version 1.00.093.1.1425042048 to 1.00.097.00.1434039685

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_TRD_AFL_LINUX_X86_64/packages

      SAP HANA Database

        Update from version 1.00.093.00.1424770727 to 1.00.097.00.1434028111

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server

      SAP HANA Database Client

        Update from version 1.00.093.00.1424770727 to 1.00.097.00.1434028111

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client

      SAP HANA Studio

        Update from version 2.00.0.11.000000 to 2.00.0.19.000000

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio

      SAP HANA Smart Data Access

        Update from version 1.00.3.005.0 to 1.00.4.004.0

        Location: /hana/HANA_SPS97/EXTRACT/51049967/DATA_UNITS/SAP_HANA_SDA_10/packages

Note: Cannot verify database user (SYSTEM) password in advance: no connection available.

Note: Cannot perform license check: no connection available

Do you want to continue? (y/n):y

Updating components…

Updating SAP HANA AFL (Misc)…

  Preparing package ‘AFL’…

  Installing SAP Application Function Libraries to /hana/shared/HTL/exe/linuxx86_64/plugins/afl_1.00.097.00.1434039685_2158696…

  Installing package ‘AFL’…

Updating SAP HANA LCAPPS…

  Preparing package ‘LCAPPS’…

  Installing SAP liveCache Applications to /hana/shared/HTL/exe/linuxx86_64/plugins/lcapps_1.00.097.00.454405_4578353…

  Installing package ‘LCAPPS’…

Updating SAP TRD AFL FOR HANA…

  Preparing package ‘TRD’…

  Installing SAP TRD AFL FOR SAP HANA to /hana/shared/HTL/exe/linuxx86_64/plugins/trd_1.00.097.00.1434039685_2158696…

  Installing package ‘TRD’…

Updating SAP HANA Database…

  Extracting software…

  Updating package ‘Saphostagent Setup’…

  Updating package ‘Python Support’…

  Updating package ‘Python Runtime’…

  Updating package ‘Product Manifest’…

  Updating package ‘Binaries’…

  Updating package ‘Installer’…

  Updating package ‘Ini Files’…

  Updating package ‘Emergency Support Package’…

  Updating package ‘Documentation’…

  Updating package ‘Delivery Units’…

  Updating package ‘DAT Languages’…

  Updating package ‘DAT Configfiles’…

  Stopping system…

  Starting service (sapstartsrv)…

  Starting system…

  Importing delivery units…

Updating Resident hdblcm…

  Cleaning up old installation of Resident hdblcm…

  Installing Resident hdblcm…

Updating SAP HANA Database Client…

  Preparing package ‘Python Runtime’…

  Preparing package ‘Product Manifest’…

  Preparing package ‘SQLDBC’…

  Preparing package ‘REPOTOOLS’…

  Preparing package ‘Python DB API’…

  Preparing package ‘ODBC’…

  Preparing package ‘JDBC’…

  Preparing package ‘HALM Client’…

  Preparing package ‘Client Installer’…

  Installing SAP HANA Database Client to /hana/shared/HTL/hdbclient…

  Updating package ‘Python Runtime’…

  Updating package ‘Product Manifest’…

  Updating package ‘SQLDBC’…

  Updating package ‘REPOTOOLS’…

  Updating package ‘Python DB API’…

  Updating package ‘ODBC’…

  Updating package ‘JDBC’…

  Updating package ‘HALM Client’…

  Updating package ‘Client Installer’…

Updating SAP HANA Studio…

  Preparing package ‘Studio Director’…

  Preparing package ‘Client Installer’…

  Installing SAP HANA Studio to /hana/shared/HTL/hdbstudio…

  Updating package ‘Studio Director’…

  Updating package ‘Client Installer’…

Updating SAP HANA Studio Update repository…

Installing SAP HANA Smart Data Access…

Updating Component List…

Updating SAP HANA instance integration on local host…

  Deploying SAP Host Agent configurations…

SAP HANA components updated with warnings.

Note:

Log file written to ‘/var/tmp/hdb_hdblcm_update_2015-09-07_09.21.54/hdblcm.log’ on host ‘hdbtest1’.


So now the hdbtest1 is updated to SPS 97.

Looking at the logs we can see that the hdbtest2 system ( which is still primary )  saw the hdbtest1 going down :


/wp-content/uploads/2015/09/failback10_787251.png


On hdbtest1, the update restarts the HDB during the process :


/wp-content/uploads/2015/09/failback14_787252.png

hdbtest1 is back online as the replication database now in version 1.0.97.

The replication can go on again, the resync is triggered automatically when the standby node is restarted :

/wp-content/uploads/2015/09/failback9_787253.png

NZDT update : takeover

My standby hdbtest1 node is running on the new HANA SPS :

/wp-content/uploads/2015/09/failback16_787254.png


My primary is still on the former version :


/wp-content/uploads/2015/09/failback15_787255.png


The replication is O.K.

Now I can decide when  to switch to the new version.

I had triggered an SGEN during the update process.

Here is its current status :

/wp-content/uploads/2015/09/failback17_787256.png

We “takeover” to the new node running 097 :

hdbnsutil -sr_takeover

checking local nameserver …

done.

hdbtest1:/usr/sap/HTL/HDB00>

Note :

Now I have something I did not expect : my 2 HDBs are alive !!

/wp-content/uploads/2015/09/failback18_787257.png

on node 2 :

hdbtest2:/usr/sap/HTL/HDB00> hdbnsutil -sr_state

checking for active or inactive nameserver …

System Replication State

~~~~~~~~~~~~~~~~~~~~~~~~

mode: primary

site id: 2

site name: HTLSTBY

Host Mappings:

~~~~~~~~~~~~~~

hdbtest2 -> [HTLPRIM] hdbtest1

hdbtest2 -> [HTLSTBY] hdbtest2

done.

on node 1 :

hdbtest1:/usr/sap/HTL/HDB00> hdbnsutil -sr_state

checking for active or inactive nameserver …

System Replication State

~~~~~~~~~~~~~~~~~~~~~~~~

mode: primary

site id: 1

site name: HTLPRIM

Host Mappings:

~~~~~~~~~~~~~~

hdbtest1 -> [HTLPRIM] hdbtest1

hdbtest1 -> [HTLSTBY] hdbtest2

done.

And this is not good .

The SGEN from my HEC ECCserver is still running on the “wrong” database :

Which on a production system with actual production data being written would mean : I am currently updating the wrong DB.

/wp-content/uploads/2015/09/failback19_787258.png

Looking at the opened sessions on each HDB :

hdbnode1

/wp-content/uploads/2015/09/failback21_787259.png

hdbnode2

/wp-content/uploads/2015/09/failback20_787260.png

In this situation, where I’m updating the system, and therefore the running HDB is not crashed, I thought the sr_takeover would, in some way, kind of disable the taken over database.

I expected the HDB on hdbnode2 to be disabled. Then have my HEC ECCsystem go down, and have the HDB running on node1 ready and

waiting for connections.

Looking at my SGEN log tables I can see that something went wrong and the updates went in the “2 databases” :

Query my database on hdbnode1 : I have the following entries in table D010LINF :

/wp-content/uploads/2015/09/failback24_787261.png

Doing the same query on hdbnode 2 results in this :

/wp-content/uploads/2015/09/failback25_787262.png

/wp-content/uploads/2015/09/failback26_787263.png

I can find back my “data gap” on hdbnode2 which was supposedly taken over…

My ECC instance was still running on node hdbnode2 until I decided to “HDB stop” it, although I had performed the sr_takeover.

Then I really had 2 hdb working as primary.

But this also means that I have lost data as I am supposed to run on node1 since the takeover …

The entries written in D010LINF from 12:13 to 12:48 are now missing from my db running on hdbnode1.

Again, as a workaround, I do have to stop the hdbnode before performing the sr_takeover.

I’ll try to find the root cause of this and post it back.

I don’t know right now if I did something wrong but, as a safety measure, I’d rather stop the HDB on my currently running node and THEN perform the sr_takeover.

That said. let’ s have a look at the HDB logs on hdbnode1 :

  • This is when I trigger the sr_takeover :

[5141]{-1}[-1/-1] 2015-09-07 12:13:51.210075 i PersistenceManag DisasterRecoverySecondaryImpl.cpp(00546) : Takeover on secondary ..[5141]{-1}[-1/-1] 2015-09-07 12:13:51.210461 i PersistenceManag DisasterRecoveryProtocol.cpp(03028) : skipping preload, because last preload occurred on current spv: 8468[5141]{-1}[-1/-1] 2015-09-07 12:13:51.210504 i Logger          BackupHandlerImpl.cpp(00341) : Shutting down log backup, 0 log backup(s) pending[5141]{-1}[-1/-1] 2015-09-07 12:13:51.232039 i PersistenceManag PersistenceManagerImpl.cpp(04622) : Restart page version 1 loaded (96bytes)[5141]{-1}[-1/-1] 2015-09-07 12:13:51.232065 i PersistenceManag PersistenceManagerImpl.cpp(04647) : Initial maximum known TID after restart: 4859536[5141]{-1}[-1/-1] 2015-09-07 12:13:51.232067 i Logger          PersistenceManagerImpl.cpp(04655) : Newest known master commit position: 0x754b1c97[5141]{-1}[-1/-1] 2015-09-07 12:13:51.232070 i Logger          PersistenceManagerImpl.cpp(04665) : Known last prepare commit position on volume 1: 0x1bd2307[5141]{-1}[-1/-1] 2015-09-07 12:13:51.232072 i Logger          PersistenceManagerImpl.cpp(04665) : Known last prepare commit position on volume 3: 0x1ae3c44[5141]{-1}[-1/-1] 2015-09-07 12:13:51.232081 i PersistenceManag PersistenceManagerImpl.cpp(04719) : Known DTX volume set [1,3], 0 RTT entries[5141]{-1}[-1/-1] 2015-09-07 12:14:01.000951 i PersistenceManag PersistenceSessionRegistry.cpp(00266) : Start loading open sessions and history cleanup files[5141]{-1}[-1/-1] 2015-09-07 12:14:01.026604 i Logger          PersistenceSessionRegistry.cpp(01075) : Open session count at restart: 1/1, max known TID at restart: 4859536[5141]{-1}[-1/-1] 2015-09-07 12:14:01.026651 i PersistenceManag PersistenceSessionRegistry.cpp(00273) : Loading 1 open session(s) and 30 history cleanup file(s) finished in 0.051289 seconds;[5141]{-1}[-1/-1] 2015-09-07 12:14:01.026976 i PersistenceManag PersistenceManagerImpl.cpp(04518) : Data recovery finished.[5141]{-1}[-1/-1] 2015-09-07 12:14:01.596178 i Service_Startup  ContMgr.cc(00070) : Initializing system catalog.[5141]{-1}[-1/-1] 2015-09-07 12:14:01.927800 i Service_Startup  ContMgr.cc(00168) : Initializing system catalog done.[5103]{-1}[-1/-1] 2015-09-07 12:14:01.979122 i Service_Startup  SmFastRestart.cc(00721) : Loading RowStore segments from Persistency[5103]{-1}[-1/-1] 2015-09-07 12:14:03.004376 i RowStorePageAcce AbsolutePageAccessImpl.cpp(01137) : LoadMultiplePageBlocksAtStartup[5103]{-1}[-1/-1] 2015-09-07 12:14:03.004414 i RowStorePageAcce AbsolutePageAccessImpl.cpp(01155) : allocate 134 segments requested to load and collect information about superblocks to read…[5103]{-1}[-1/-1] 2015-09-07 12:14:05.296289 i RowStorePageAcce AbsolutePageAccessImpl.cpp(01309) : collecting information done in 2291msec.[5103]{-1}[-1/-1] 2015-09-07 12:14:05.296831 i RowStorePageAcce AbsolutePageAccessImpl.cpp(01340) : SuperblockPrefetchCalculation:        allocationLimit=47038569451



  • The HDB triggers some migration tasks as we are moving from 093 to 097 :

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.145153 i Service_Startup  mm_recovery.cc(01051) : RS: metadata & data are separated

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.184470 i Service_Startup  md_conv_util.cc(01978) : metadata version of current DB image: 205

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.184555 i Service_Startup  md_conv_util.cc(01982) : metadata version of binary: 230

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.184557 i Service_Startup  md_conv_util.cc(01986) : [metadata upgrade] start (205 -> 230)

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.184559 i Service_Startup  md_conv_util.cc(01988) : [metadata upgrade] begin of phase I (converting physical DB image)

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.184584 i Service_Startup  md_conv_util.cc(01941) : [metadata upgrade] (217 -> 218)

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.195328 i Service_Startup  md_conv_util.cc(01949) : [metadata upgrade] (229 -> 230)

[5141]{-1}[-1/-1] 2015-09-07 12:14:27.209722 i Service_Startup  md_conv_util.cc(01993) : [metadata upgrade] end of phase I (converting physical DB image)

….

[5141]{-1}[-1/-1] 2015-09-07 12:15:26.900129 i Service_Startup  catalog.cc(00595) : Auto migration started.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.484108 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_BLOCKED_TRANSACTIONS has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.512982 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CATALOG_MEMORY has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.529787 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CLIENT_VERSIONS has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.564950 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view CS_JOIN_PATHS has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.598634 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CS_COLUMNS has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.628812 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_FUZZY_SEARCH_INDEXES has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.663963 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CS_ALL_COLUMNS has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.707009 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CS_TABLES has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.736352 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CS_PARTITIONS has been changed. Its metadata is updated.

[5141]{-1}[16/-1] 2015-09-07 12:15:27.784178 i Service_Startup  catalog.cc(01916) : AutoMigration: Definition of system view M_CONNECTIONS has been changed. Its metadata is updated.

I then reconnect my HEC system to the HDB and restart.

I’m now running on HDB node 1.

The NZDT update in itself is O.K on node 1.

Note 2 :

One other thing I went through, which surprised me in a good way, is that in the end, I was not really forced to “shutdown ECC / modify ECC parameters / restart ECC” in order to work with the failed-over node although, in my set up , I had not switched IP adresses from one node to another.

I’ll try to understand why. This looked like some kind of “scale-out”

The update of all the components was performed also :

/wp-content/uploads/2015/09/failback27_787264.png

NZDT update : Update of the old primary node

The situation is as follows now :

/wp-content/uploads/2015/09/failback28_787518.png

Hdbtest1 is back as primary node running the HDB in version 1.0.97.

Hdbtest2 is offline and still on version 1.0.93.

Replication is off.

We update the hdbnode2 :

From the hdb software SPS directory  as root on hdbnode2 :



hdbupd –nostart=on ( as stated in the SAP_HANA_Administration guide ) -> fails in my set up ( would have worked without any plugins installed ):


SAP HANA Lifecycle Management – Database Upgrade 1.00.097.00.1434028111

***********************************************************************

Select a SAP HANA Database installation:

No | System | Properties

————————————

0  | HTL    | 1.00.093.00.1424770727

   |        | hdbtest2 (worker)

   |        |

1  | None   | (Abort upgrade)

Specify the sequence number of the system to be upgraded [1]: 0

Upgrade failed

  SAP HANA Database 1.00.097.00.1434028111 is not compatible with installed plugin(s):

    SAP Application Function Libraries

      Currently active version: 1.00.093.1.1425042048

      No installed, inactive newer version found.

       => Update the ‘SAP Application Function Libraries’ plugin!

      Skip this plugin dependency check with the command line option

      –ignore=check_plugin_dependencies if you want to deactivate the

      ‘SAP Application Function Libraries’ plugin and update it later, or

      if you no longer use the functions provided by this plugin.

      Follow the instructions in SAP Note 1920457.

    SAP liveCache Applications

      Currently active version: 1.00.093.00.451387

      No installed, inactive newer version found.

       => Update the ‘SAP liveCache Applications’ plugin!

      Skip this plugin dependency check with the command line option

      –ignore=check_plugin_dependencies if you want to deactivate the

      ‘SAP liveCache Applications’ plugin and update it later, or

      if you no longer use the functions provided by this plugin.

      Follow the instructions in SAP Note 1920457.

    SAP TRD AFL FOR SAP HANA

      Currently active version: 1.00.093.1.1425042048

      No installed, inactive newer version found.

       => Update the ‘SAP TRD AFL FOR SAP HANA’ plugin!

      Skip this plugin dependency check with the command line option

      –ignore=check_plugin_dependencies if you want to deactivate the

      ‘SAP TRD AFL FOR SAP HANA’ plugin and update it later, or

      if you no longer use the functions provided by this plugin.

      Follow the instructions in SAP Note 1920457.


I could follow the guidelines in the SAP note, but to me as I am updating a standby instance, I think I’d probably use the hdblcm tool instead with the following extra options :

hdbtest2:/hana/EXTRACT/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64 # ./hdblcm –action=update –hdbupd_server_nostart

SAP HANA Lifecycle Management – SAP HANA 1.00.097.00.1434028111

***************************************************************

Scanning Software Locations…

Detected components:

    SAP HANA Database (1.00.097.00.1434028111) in /hana/EXTRACT/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server

    SAP HANA AFL (Misc) (1.00.097.00.1434039685) in /hana/EXTRACT/51049967/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages

    SAP HANA LCAPPS (1.00.097.000.454405) in /hana/EXTRACT/51049967/DATA_UNITS/HANA_LCAPPS_10_LINUX_X86_64/packages

    SAP TRD AFL FOR HANA (1.00.097.00.1434039685) in /hana/EXTRACT/51049967/DATA_UNITS/HDB_TRD_AFL_LINUX_X86_64/packages

    SAP HANA Database Client (1.00.097.00.1434028111) in /hana/EXTRACT/51049967/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client

    SAP HANA Studio (2.00.0.19.000000) in /hana/EXTRACT/51049967/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio

    SAP HANA Smart Data Access (1.00.4.004.0) in /hana/EXTRACT/51049967/DATA_UNITS/SAP_HANA_SDA_10/packages

Choose system to update

  Index | System            | Database Properties

  ————————————————–

  1     | HTL (update)      | 1.00.093.00.1424770727

        |                   | hdbtest2 (worker)

        |                   |

  2     | Exit (do nothing) |


Enter selected system index [2]: 1

Choose components to be installed or updated:

  Index | Components | Description

  ————————————————————————————————————————–

  1     | all        | All components

  2     | server     | Update SAP HANA Database from version 1.00.093.00.1424770727 to version 1.00.097.00.1434028111

  3     | client     | Update SAP HANA Database Client from version 1.00.093.00.1424770727 to version 1.00.097.00.1434028111

  4     | afl        | Update SAP HANA AFL (Misc) from version 1.00.093.1.1425042048 to version 1.00.097.00.1434039685

  5     | lcapps     | Update SAP HANA LCAPPS from version 1.00.093.00.451387 to version 1.00.097.000.454405

  6     | smartda    | Update SAP HANA Smart Data Access from version 1.00.3.005.0 to version 1.00.4.004.0

  7     | studio     | Update SAP HANA Studio from version 2.00.0.11.000000 to version 2.00.0.19.000000

  8     | trd        | Update SAP TRD AFL FOR HANA from version 1.00.093.1.1425042048 to version 1.00.097.00.1434039685

Enter comma-separated list of the selected indices [2,3,4,5,6,8]: 1

Enter System Administrator (htladm) Password:

Enter Database User Name [SYSTEM]:

Enter Database User (SYSTEM) Password:

Summary before execution:

=========================

SAP HANA Components

   Update Parameters

      Remote Execution: ssh

      SAP HANA System ID: HTL

      Database User Name: SYSTEM

      SAP HANA Database Client Installation Path: /hana/shared/HTL/hdbclient

      SAP HANA Studio Installation Path: /hana/shared/HTL/hdbstudio

   Software Components

      SAP HANA AFL (Misc)

         Update from version 1.00.093.1.1425042048 to 1.00.097.00.1434039685

         Location: /hana/EXTRACT/51049967/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages

      SAP HANA LCAPPS

         Update from version 1.00.093.00.451387 to 1.00.097.000.454405

         Location: /hana/EXTRACT/51049967/DATA_UNITS/HANA_LCAPPS_10_LINUX_X86_64/packages

      SAP TRD AFL FOR HANA

         Update from version 1.00.093.1.1425042048 to 1.00.097.00.1434039685

         Location: /hana/EXTRACT/51049967/DATA_UNITS/HDB_TRD_AFL_LINUX_X86_64/packages

      SAP HANA Database

         Update from version 1.00.093.00.1424770727 to 1.00.097.00.1434028111

         Location: /hana/EXTRACT/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server

      SAP HANA Database Client

         Update from version 1.00.093.00.1424770727 to 1.00.097.00.1434028111

         Location: /hana/EXTRACT/51049967/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client

      SAP HANA Studio

         Update from version 2.00.0.11.000000 to 2.00.0.19.000000

         Location: /hana/EXTRACT/51049967/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio

      SAP HANA Smart Data Access

         Update from version 1.00.3.005.0 to 1.00.4.004.0

         Location: /hana/EXTRACT/51049967/DATA_UNITS/SAP_HANA_SDA_10/packages

Note: Cannot verify database user (SYSTEM) password in advance: no connection available.

Note: Cannot perform license check: no connection available

Do you want to continue? (y/n): y

Updating components…

Updating SAP HANA AFL (Misc)…

  Preparing package ‘AFL’…

  Installing SAP Application Function Libraries to /hana/shared/HTL/exe/linuxx86_64/plugins/afl_1.00.097.00.1434039685_2158696…

  Installing package ‘AFL’…

Updating SAP HANA LCAPPS…

  Preparing package ‘LCAPPS’…

  Installing SAP liveCache Applications to /hana/shared/HTL/exe/linuxx86_64/plugins/lcapps_1.00.097.00.454405_4578353…

  Installing package ‘LCAPPS’…

Updating SAP TRD AFL FOR HANA…

  Preparing package ‘TRD’…

  Installing SAP TRD AFL FOR SAP HANA to /hana/shared/HTL/exe/linuxx86_64/plugins/trd_1.00.097.00.1434039685_2158696…

  Installing package ‘TRD’…

Updating SAP HANA Database…

  Extracting software…

  Updating package ‘Saphostagent Setup’…

  Updating package ‘Python Support’…

  Updating package ‘Python Runtime’…

  Updating package ‘Product Manifest’…

  Updating package ‘Binaries’…

  Updating package ‘Installer’…

  Updating package ‘Ini Files’…

  Updating package ‘Emergency Support Package’…

  Updating package ‘Documentation’…

  Updating package ‘Delivery Units’…

  Updating package ‘DAT Languages’…

  Updating package ‘DAT Configfiles’…

  Stopping system…

Updating Resident hdblcm…

  Cleaning up old installation of Resident hdblcm…

  Installing Resident hdblcm…

Updating SAP HANA Database Client…

  Preparing package ‘Python Runtime’…

  Preparing package ‘Product Manifest’…

  Preparing package ‘SQLDBC’…

  Preparing package ‘REPOTOOLS’…

  Preparing package ‘Python DB API’…

  Preparing package ‘ODBC’…

  Preparing package ‘JDBC’…

  Preparing package ‘HALM Client’…

  Preparing package ‘Client Installer’…

  Installing SAP HANA Database Client to /hana/shared/HTL/hdbclient…

  Updating package ‘Python Runtime’…

  Updating package ‘Product Manifest’…

  Updating package ‘SQLDBC’…

  Updating package ‘REPOTOOLS’…

  Updating package ‘Python DB API’…

  Updating package ‘ODBC’…

  Updating package ‘JDBC’…

  Updating package ‘HALM Client’…

  Updating package ‘Client Installer’…

Updating SAP HANA Studio…

  Preparing package ‘Studio Director’…

  Preparing package ‘Client Installer’…

  Installing SAP HANA Studio to /hana/shared/HTL/hdbstudio…

  Updating package ‘Studio Director’…

  Updating package ‘Client Installer’…

Updating SAP HANA Studio Update repository…

Installing SAP HANA Smart Data Access…

Updating Component List…

Updating SAP HANA instance integration on local host…

  Deploying SAP Host Agent configurations…

SAP HANA components updated with warnings.

Note:

Log file written to ‘/var/tmp/hdb_hdblcm_update_2015-09-09_15.07.32/hdblcm.log’ on host ‘hdbtest2’.

The update is done and O.K.

A quick check to make sure :

hdbtest2:/usr/sap/HTL/HDB00/hdbtest2/trace> HDB version

HDB version info:

  version:             1.00.097.00.1434028111

  branch:              fa/newdb100_maint_rel

  git hash:            e6e474976d1dd01703d242877bb1ee5e7b3b2f2a

  git merge time:      2015-06-11 15:08:31

  weekstone:           0000.00.0

  compile date:        2015-06-11 15:22:05

  compile host:        ld7272.wdf.sap.corp

  compile type:        rel

Now I can set the hdbnode2 back in the replication configuration :

hdbtest2:/usr/sap/HTL/HDB00/hdbtest2/trace> hdbnsutil -sr_state

checking for active or inactive nameserver …

nameserver hdbtest2:30001 not responding.

nameserver hdbtest2:30001 not responding.

System Replication State

~~~~~~~~~~~~~~~~~~~~~~~~

mode: primary

site id: 2

site name: HTLSTBY

done.

hdbtest2:/usr/sap/HTL/HDB00/hdbtest2/trace> hdbnsutil -sr_register –remoteHost=hdbtest1 –remoteInstance=HTL –mode=syncmem –name=HTLSTBY –force_full_replica

adding site …

checking for inactive nameserver …

nameserver hdbtest2:30001 not responding.

collecting information …

updating local ini files …

done.

hdbnode2 is back in the game.

Last verification before rstarting the STBY system :

hdbtest2:/usr/sap/HTL/HDB00/hdbtest2/trace> hdbnsutil -sr_state

checking for active or inactive nameserver …

nameserver hdbtest2:30001 not responding.

nameserver hdbtest2:30001 not responding.

System Replication State

~~~~~~~~~~~~~~~~~~~~~~~~

mode: syncmem

site id: 2

site name: HTLSTBY

done.

Now let’s restart the hdbnode2 HDB to have the replication back online :

/wp-content/uploads/2015/09/failback30_787265.png

/wp-content/uploads/2015/09/failback31_787266.png

/wp-content/uploads/2015/09/failback32_787267.png

Everybody is back and up to date !!

Target :


hdbtest1 is the primary host running the HDB

the standby host is hdbtest2

HDB version : 1.0.97

Replication is set back ( hdbtest1 -> hdbtest2 )

What else ?


From an HANA server perspective, the update is completed.

That said, we still need to perform the usual post update steps :

redeploy the views

updating the SAP HDB studio on the workstations ( the one on the server was updated ) .

updating the HDB client

These were described here : SAP HANA Hands on tests ( part 3.1 ) : Applying patches to HANA DB

In the end I’d rather perform the hdb db client and hdb studio updates first and then the HDB server update.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply