Header Ads Widget

Responsive Advertisement

How to handle HANA Alert 51: 'Size of diagnosis files

 Symptom

This KBA is part of a series of Knowledge Base Articles (KBAs). Its focus is on checking the size of diagnosis files. To free disk space for new logs and traces and delete obsolete diagnosis files.

Environment

SAP HANA Database 1.0, 2.0

Cause

Large diagnosis files are triggering this alert 51.

Resolution

PROCEDURE

I. Check the current rating of the alert

II. Analyze Problem

III. Apply Solution

PATH

SAP HANA Studio - Administration Console - Alerts

• Solution Manager - DBACOCKPIT - Choose HANA System - Current Status - Alerts

HOW-TO

I. Check current rating of alerts

Start transaction DBACOCKPIT.

1.

In the drop-down list, select the HANA system.

2.

Choose Current Statue -> Alerts.

3.In the Alert Check Information table, check the record for alert 51. Verify that the rating is still red or yellow.

4. Do one of the following:

5. If the rating is yellow or red, perform the next step of this guided procedure.

If the rating is green, no action is required.

In edit mode, select a status in the Execution status column:

6. If the activity was successful, select Performed.

• If an error occurred, select Performed with Errors.

II. Analyze Problem

1. Check for large diagnosis files

Start transaction DBACOCKPIT.

In the drop-down list, select the HANA system.

•   Choose Diagnostics -> Diagnosis Files.

•  Sort the diagnosis files by size.

•  To check whether the obsolete diagnosis files are current, check the value in the column Modified time.

2. Identify obsolete Diagnosis Files

Start transaction DBACOCKPIT.

• In the drop-down list, select the HANA system.

•  Choose Diagnostics -> Diagnosis Files.

•  Check whether the files can be deleted in compliance with your retention policy for diagnosis files. (It is usually sufficient, to keep files for 1-2 weeks.)

•  To ensure that you do not delete files still required for ongoing problem analysis, check the system status and open issues or incidents.

•  If in doubt, move large tables to a disk that does not consume disk space of the productive database.

III. Apply Solution

1. Manual Delete of obsolete files

Choose Start -> Programs -> SAP HANA Studio

• In the Navigator View, select the HANA system.

• Choose Diagnosis Files.

• Choose Delete Trace Files. The Delete Trace Files dialog box appears.

• To delete diagnosis files, do one of the following:

•  To delete a specific diagnosis file, choose to Delete in the context menu. Note: If a service is currently writing to the file, it cannot be deleted and it disappears from the list in HANA Studio and is hidden in the file system at the operating system level. As long as a service is still writing to the file, it still exists and consumes disk space. Once the file reaches its maximum size, the system stops writing to it and creates a new trace file. When the file is physically deleted depends on how to trace file rotation is configured.

•  To batch delete diagnosis files, for example, all the trace files of service, choose the Delete Trace Files push-button and make the selection. If you cannot delete trace files because they are open, the content of the file is cleared. The file still exists but its size is reduced.

•  Note: You can also delete individual trace files in transaction DBACOCKPIT under Diagnostics -> Diagnosis Files.



Post a Comment

0 Comments

SPAM/SAINT Support Package and Stack Upgrade in SAP