SAP HA Cluster Start and stop Process:

SAP HA Cluster Start and Stop:

In this blog we have explained the Production system Application and Database stop and start Process for SAP HA Cluster start and stop process.
We have explained the Complete application (AAS, PAS , ASCS and ERS) System stopping and starting sequence and Database cluster master and slave stopping and starting steps details(SAP HA Cluster start and stop process)

Example:
If Production system 2 AAS , PAS , ASCS & ERS Servers.
• Vmfep01 (ASCS)
• Vmfep02(ERS)
• Vmfep03(PAS)
• Vmfep04(AAS)
• Vmfep05(AAS)
• Vmfep06(ASCS LB)
• Vmfep07(ERS LB)
• Vmfep08DB Primary)
• Vmfep09(DB Secondary)

* OS : Suse linux
* Product : ECC
* DB : DB2

1st we will stop the Additional application server. Before stopping the Application servers we will do below pre steps.

• DB Full Backup
• Lock the all users
• Suspend the Backup Ground jobs –BTCTRNS1
• If any jobs is running then cancel the jobs manually
• Clear the failed update locks.

Once above steps has been completed then stop the SAP Application.
Stopping sequence for SAP Application:

• AAS
• PAS
• ERS
• ASCS

Need to set maintenance mode on/off on DB , ASCS & ERS Servers.
Cluster Maintenance mode on:
Crm configure property maintenance-mode=true
Cluster Maintenance mode off:
Crm configure property maintenance-mode=false
AAS(Additional application server) Stopping steps:
Using the below command stop the AAS Applications.

Command:
• Login to the sidadm
• Su – sidadm
• Execute the below command for stop the application
• Sapcontrol –nr xx –function StopSystem
• Check status
• Sapcontrol –nr xx –function GetProcessList
• Cleanipc xx remove. XX mean instance.

PAS (Primary application server) Stopping steps:
Using the below command stop the PAS Applications.

Command:
• Login to the sidadm
• Su – sidadm
• Execute the below command for stop the application
• Sapcontrol –nr xx –function StopSystem
• Check status
• Sapcontrol –nr xx –function GetProcessList
• Cleanipc xx remove. XX mean instance.

ASCS & ERS Stopping steps:
Using the below command stop the PAS Applications.

Command:
• Sapcontrol –nr xx –function StopSystem

Once Application has been stopped successfully then we will check if any active connection from application to database. Before stopping the database cluster we need to check the active connection.
How to check the DB Active Connections:

• Login to the database server
• Su – db2sid
• Execute below command for check active connection details.
• Db2 list active databases
• If zero connection then it is fine.
• If getting any active connection , then we will login to the application servers kill the active connection using the below command
• Ps –ef|grep sid

All application servers has been stopped successfully. We will stop the DB2 Database HA Cluster Systems.
DB2 High availability cluster stopping Process:
We need understand the stopping sequence for Master and slave server:

• Deactivate the Primary server
• Deactivate the secondary server
• Stop the DB on primary server
• Stop the DB on secondary server.

We need understand the starting sequence for Master and slave server:

• Start the DB on secondary server
• Execute the command for HADR as standby
• Start the DB on Primary server
• Execute the command for HADR as Primary
• Activate the DB on standby.
• Check status on Primary and secondary HADR Status.

Before stopping the database systems, we will check the Master and slave system details.

• Primary(Master server)
• Secondary (Slave server)

SAP HA Cluster start and stop process.
SAP HA Cluster Stopping Process:
We can login to the Master server (Primary server) for deactivate the db

• Login to the database using db sid:
• Su – db2sid
• Check active databases
#Db2 list active databases
If no active databases, check for further process.
• Check for HADR status and log_gap status.
• Deactivate the primary database using below command.
#db2 deactivate db SID
• Primary database has deactivated successfully.

We can login to the Slave server(Secondary server) for deactivate the db:

• Login to the database using db sid:
• Su – db2sid
• Check for HADR status and log_gap status.
• Deactivate the secondary database using below command.
#db2 deactivate db SID
• Slave database has deactivated successfully.

We can login to the Master server(Primary server) for stop the db:

• Login to the database using db sid:
• Su – db2sid
• Stop the master server
• #db2stop
• Execute the below command for ipclean
• Ipclean

We can login to the Slave server(Secondary server) for stop the db:

• Login to the database using db sid:
• Su – db2sid
• Stop the slave server
• #db2stop
• Execute the below command for ip clean
• Ipclean

SAP HA Cluster start and stop process.
HA Cluster Starting Process:
We can login to the Slave server(Secondary server) for start the db:

• Login to the database using db sid:
• Su – db2sid
• Start the slave server
• #db2start
• Execute the below command for set secondary server has standby(Secondary server)
• #db2 start HADR on db SID as STANDBY
• Check HADR_STATE and Log_GAP status.
• #db2pd – d SID –hadr

We can login to the Master server(Primary server) for start the db:

• Login to the database using db sid:
• Su – db2sid
• Start the master server
• #db2start
• Execute the below command for set Primary server has master(Secondary server)
• #db2 start HADR on db SID as PRIMARY
• Check HADR_STATE and Log_GAP status.
• #db2pd – d SID –hadr

We can login to the Slave server(Secondary server) for Activate the db:

• Login to the database using db sid:
• Su – db2sid
• activate the secondary database using below command.
#db2 activate db SID
• check HADR status on Primary and secondary node.
• #db2pd – d SID –hadr

Once database HA Cluster a server has started successfully then remove the maintenance-mode.
Command:
Crm configure property maintenance-mode=false
We have performed the SAP HA Cluster start and stop process on sap distribution and HA System..
Start Application server sequence:

• Start the ASCS server
• Start the ERS Server
• Start the PAS Server
• Start the AAS server.

Using the below command start the Applications.

Command:
• Login to the sidadm
• Su – sidadm
• Execute the below command for start the application
• Sapcontrol –nr xx –function StartSystem
• Check status
• Sapcontrol –nr xx –function GetProcessList
• XX mean instance.

We have successfully started the Application and Database HA Cluster Systems.
Check the application health status.
If everything is fine then you can perform the below steps

• Release the Background jobs
• Check Critical RFCS
• Inform to concern team for check the RFC/Other health checks.
• Unlock the users
• Release the system for Business.

Conclusion:
• We have successfully stopped and started the SAP Application and Database Cluster servers.
• SAP HA Cluster start and stop process.

Other Posts:

• Hana db installation steps Hana2.0

• ECC to S4 HANA CONVERSION SAP

FAQ For SAP HA System: