How to Handle HANA Alert 28: 'Most recent savepoint operation'

 

Handle HANA Alert 28: 'Most recent savepoint operation'

Symptom:

• In SAP HANA alert 'Most recent savepoint operation' (Alert ID = 28) is raised.
• In HANA Studio this corresponds to the alert description:
• "The last savepoint operation on host **** (host):***** (port) was executed * minutes ago. This may indicate a problem with savepoint processing and impact the recoverability of your database."

Resolution:

Procedure

1. Check the configuration of parameter savepoint_interval_s in file global.ini - persistence.
2. Check the configuration of alert thresholds.  
3. Check the safepoint statistics.
4. Analyze for performance issues in savepoint writing according to KBA 1977220.

Path:

1. SAP HANA Studio - SAP HANA Administration Console - Configuration.
2. SAP HANA Studio - SAP HANA Administration Console - Alerts - Configure Check Settings - Configure Check Thresholds.
3. SAP Solution Manager - Configuration.
4. SAP HANA Studio - SAP HANA Administration Console - SQL Console.

How to HANDLE ALERT ‘CHECK LAST SAVEPOINT TIME'

RESOLUTION: 

1. If savepoint interval has been configured to a custom value, then confirm the setting with your architect.

Check what action is required for this alert and if alert thresholds shall be adhusted. 

2. For the alert triggered due to improper threshold value setting, it could be resolved by reset it to default 

or a higher threshold value.

x

3. If the savepoint writing and alerting are configured correctly, then check statistics of savepoint writing. 

The information about the last save point time is stored in the system view _SAVEPOINT_STATISTICS. 

You can check for the last save point time by execution the following SQL command in HANA Studio:

Select * from SYS.M_SAVEPOINT_STATISTICS

The result is like:

1. Check if the delay of savepoint writing occurs regularly or if its occurrance is just temporary, 

sporadic or continual.

2. Check if the delay is due to a difference between REQUESTED_FREQUENCY and 

LAST_FREQUENCY or if its due to long LAST_DURATION

Try to trigger a savepoint manually by executing the SQL statement from the SQL Console:

ALTER SYSTEM SAVEPOINT

Repeat the check on savepoint statistics and check if the savepoint has been completed as expected:

select * from SYS.M_SAVEPOINT_STATISTICS

Further actions: 

1. If the actual frequency of savepoint writing repeatedly deviates a lot from configured frequency, 

then create a ticket to SAP Support with component HAN-DB.

2. If delay is due to long duration of savepoint writing, then proceed the analysis steps 

recommended in KBA 1977220 – How to handle HANA Alert 54: Savepoint Duration

Reference : 1977291 (Educational Purpose only)