System Environment
Active HANA Node à ***hana***a (10.**.**.$$)
Passive HANA Node à ***hana***p (10.**.**.**)
Parameter Change Process
To change parameter in HANA System
Login to HANA System
Go to à
Configurations
Search for the parameter (e.g. statement_memory_limit)
Right Click à
Change
Enter the value in the column “New
Value”.
Note:-
There are 2 sections in the Change
Configuration Value box. One is the “System” sections wherein if the parameter
value is inserted in this section the change would be replicated across the
system. Second is the Host section (In case of Multi-Node Cluster) wherein if
the parameter value changed is specific to the particular host.
Once changed Click on Save.
Note that once the parameter is changed,
the same would be available at the OS level at the following path under the
respective “.ini” file :-
/hana/shared/SID/global/hdb/custom/config
As part of the Standard process, since our
System is setup in a System Replication Environment, the same parameter change
has to be manually changed in the respective “.ini” file in Passive Node (e.g. ***hana***p)
Restart HANA System
In some cases, you might require to take a
restart of the HANA System, in order to perform the restart of HANA System:-
Stopping HANA System
Stopping Sequence à
1.
Stop Passive Node (***hana***p)
2.
Stop Active Node (***hana***a)
Login to Passive Node à ***hana***p (10.**.**.**)
Execute the command à HDB stop
To check if HANA System is down à HDB info
Login to Active HANA Node à ***hana***a (10.**.**.$$)
Execute the command à HDB stop
To check if the HANA System à HDB info
Starting HANA System
Starting Sequence
1.
Start Active Node (***hana***a)
2.
Start Passive Node
(***hana***
To start the HANA System login to Active
Node and execute the following command
HDB start
To check the status of the HANA System
Note that all the HANA Services (hdbnameserver,
hdbindexserver, hdbpreprocessor, hdbcompileserver, hdbxsengine, hdbwebdispatcher,
sapstartsrv) should be visible.
In HANA Studio
Start the HANA System on the Passive Node
Troubleshooting
In case of errors kindly check the
Statup/Stop logs in the following path :-