Dataencryption in global.ini in SAP HANA 2.0 and SAP HANA 1.0 Mar 29, 2017 at 12:38 PM 435 Views In SAP HANA 2.0 it seems the parameter persistencedataencryption in global.ini is not being used/set for enabling encryption.
- Lógon to appliance ás basic or sudo user
Create fresh website directory where information and log files will be saved Eg. mkdir /hánadata Bracket the brand-new drive, NFS position or LUN át /hanadata. This will be typically accomplished in /etc/fstáb, but I earned't proceed into details here Create information and sign subdirectories under new mount point - cd /hanadata
- mkdir information
mkdir log - Shift ownership of brand-new information dir to go with ownership of /usr/sáp/lt;SIDgt;
- cd /hanadata
chown It;sidgt;adm:sápgrp /lt;newmountgt; -R - eg. chown anaadm:sapsys /hanadata/ -Ur
Modification location of determination in Hana facility - HANA must become running - Search to worldwide.inigt;persistencegt;
Up time basepathdatavolumes to stage to /lt;newmountgt;/information- Revise basepathlogvolumes to stage to /lt;newmountgt;/sign
Halt HANA - su - lt;sidgt;adm
- HDB cease
Copy documents to brand-new location I suggest to copy, rather of move, in situation there are usually any complications. The primary data files can be removed/deleted after confirming HANA can be upward and operating using the fresh file location.
cp /usr/sáp/lt;SIDgt;/global/hdb/data/. /hanadata/data -rp
Vérify HANA solutions are stopped - Search to worldwide.inigt;persistencegt;
cp /usr/sáp/lt;SIDgt;/global/hdb/log/. /hanadata/record -rp - Thé l can be recursive to consist of all sub-diréctories
The g will be preserve setting, to keep all permissions I simply set this concern by again working the below control chown It;sidgt;adm:sápgrp /lt;newmountgt; -Ur
because l didn't usé the -g change in my duplicate command word, so the data files got the basic permissions. I have always been including to display what will happen if It;sidgt;adm doésn't have create permissions to the information or sign documents.