Continuing the warm data management exploration, we implemented and tested another feature – the HANA Extension Node, which exists in scale-out landscape as a slave node, for use in either Native HANA or in BW scenarios

1. Configuring and Monitoring HANA Extension Node
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 1

2. Exploring SAP HANA Extension Node
IT-Conductor continues to stay on top of new release features of SAP HANA.
In the previous presentations, we explored HANA’s warm data management
offering – dynamic tiering.
• SAP HANA2 Dynamic Tiering Overview including HANA Monitoring
• SAP HANA Dynamic Tiering Test-drive
Continuing the warm data management exploration, we implemented and tested
another feature – the Extension Node, which exists in scale-out landscape as a slave
node, for use in either Native HANA or in BW scenarios. The worker/master node
stores the ’hot’ data, while the extension node stores the warm data. The
implementation of the extension node is transparent to the queries – queries
automatically retrieves data from where data is stored – either in master for hot
data, and extension node for warm data.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 2

3. References/Guides
Blog: Employing Extend Nodes for Warm Data Management
SAP HANA Administration Guide
OSS note 241279 – How-To: Configuring SAP HANA for SAP
HANA Extension node.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 3

4. Brief
In this scenario/testing,
1. Existing master node is imdbhdb
2. Will add extension node ozbwhana
3. ‘Restrict/Limit’ table distribution of hot data only into the master
node imdbhdb
4. Assign a schema for hot data/node and create tables
5. Assign a schema for warm data/node and create tables
6. Move back and forth a table from hot to warm and vice-versa
The steps followed were based on extension node for SAP HANA native
application.
• Note that configuring extension node for BW is covered by another OSS note.
During the testing, IT-Conductor automatically discovers any change in the
landscape and will monitor any new addition/change.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 4

5. Adding an Extension Node - 1
Extension node is added like any other node in scale-out
system, by simple adding a host to existing Hana system
Master node IMDBHDB
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 5

6. Adding an Extension Node -2
The new host ozbwhana is added as a ‘worker’ node
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 6

7. Adding an Extension Node -3
New host ozbwhana, added to master node imdbhdb.
From HANA Studio -
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 7

8. IT-Conductor monitoring - 1
IT-Conductor, which was previously monitoring master imdhbdb, will
automatically ‘discover’ and will start monitoring the newly added host
ozbwhana and all of its services
From SYSTEMDB
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 8
Master node
Extension node

9. IT-Conductor monitoring - 2
From tenant DB
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 9

10. Configuring the extension node - 1
1. Change the worker group of the extension node to
‘workder_dt’
call SYS.UPDATE_LANDSCAPE_CONFIGURATION('SET WORKERGROUPS', 'ozbwhana',
'worker_dt');
2. Get the volume_id of the hot-data node(s). This is to limit the
table distribution default to hot node(s)
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 10

11. Configuring the extension node - 2
3. Overwrite the default setting of table distribution to use
the hot-data node volumes only
From SYSTEMDB
From tenant DB
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 11
From previous
step

12. Table placements – Hot data (1)
Assign an schema to hot node(s) – distribution to all nodes
except the extension node
ALTER SYSTEM ALTER TABLE PLACEMENT
(SCHEMA_NAME => 'A11111')
SET (LOCATION => 'all', MIN_ROWS_FOR_PARTITIONING => 0,
INITIAL_PARTITIONS => 1, REPARTITIONING_THRESHOLD => 0);
Display table location for the schema
select schema_name, location
from table_placement
where schema_name = 'A11111';
Create a table for schema A11111
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 12

13. Table placements – Hot data (2)
Display location the newly created ‘hot’ table
Using HANA Studio run information
Or
SQL - select * from table_placement
where schema_name = 'A11111';
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 13
Hot Node

14. Table Placement – Warm data (1)
Assign tables for an schema H99999 as ‘warm data’ - created
in extension node
ALTER SYSTEM ALTER TABLE PLACEMENT
(SCHEMA_NAME => 'H99999',
GROUP_TYPE => 'WARM_DATA')
SET (LOCATION => 'worker_dt', MIN_ROWS_FOR_PARTITIONING => 0,
INITIAL_PARTITIONS => 1, REPARTITIONING_THRESHOLD => 0);
All new tables created in schema H99999 will be distributed
to the extension node.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 14
Select schema_name, location
from table_placement
Where schema_name = ‘H99999’

15. Table Placement – Warm data (2)
Create table for schema H99999
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 15

16. Moving table from HOT to Warm
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 16

17. Moving table form Warm to HOT
Move a table from WARM to HOT
Alter to WARM and REORG
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 17

18. Table Distribution
More information on table distribution can be found on the
following
• OSS note 2081591 – FAQ: SAP Table Distribution
• Administration Guide – ‘Table Redistribution Commands’
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 18

19. Summary
• The use/implementation of the Extension Node for warm
data management is straight forward and should be
considered due to its benefits.
• IT-Conductor will automatically discover and monitor any
new additional host.
• If system replication is enabled, the secondary host for the extension
node is also automatically discovered and monitored.
Author: Terry Kempis
Editor: Linh Nguyen
ITConductor.com 19

20. • Any Questions?
• Contact Info:
Linh Nguyen linh.nguyen@itconductor.com
Terry Kempis terry.kempis@itconductor.com
Let
itconductor.com
@itconductor