Hana -Cleanup of Logs/Traces

  

  • Cleanup of backup catalog entries
  • Cleanup of trace files
  • Cleanup of SAP HANA alerts
  • Cleanup of Dumps

How to check the size of backup catalog?

1. Use below sql 

SELECT T3.DESTINATION_PATH CATALOG_FILE_NAME,
    T3.DESTINATION_TYPE_NAME FILE_TYPE,
    TO_CHAR(TO_DECIMAL(T3.CATALOG_SIZE_MB,10,2))||' MB' CATALOG_SIZE,
    TO_CHAR(T4.OLDEST_BACKUP_DATE,'YYYY/MM/DD HH24:MI:SS') OLDEST_BACKUP_DATE,
    LPAD(T4.OLDEST_BACKUP_DAYS,18) BACKUP_RETENTION_DAYS,
    TO_CHAR(CURRENT_TIMESTAMP,'YYYY/MM/DD HH24:MI:SS') ANALYSIS_TIME       
 FROM  (SELECT TOP 1 T2.DESTINATION_PATH, 
  T2.DESTINATION_TYPE_NAME,
  T2.BACKUP_SIZE / 1024 / 1024  CATALOG_SIZE_MB
     FROM  M_BACKUP_CATALOG T1,
   M_BACKUP_CATALOG_FILES T2
     WHERE T1.BACKUP_ID = T2.BACKUP_ID
     AND T2.SOURCE_TYPE_NAME = 'catalog' AND T1.STATE_NAME = 'successful'
     ORDER BY T1.SYS_START_TIME DESC ) T3,
    (SELECT MIN(SYS_START_TIME) OLDEST_BACKUP_DATE,
    DAYS_BETWEEN(MIN(SYS_START_TIME), CURRENT_TIMESTAMP) OLDEST_BACKUP_DAYS
     FROM   M_BACKUP_CATALOG
     ) T4

  Output:

2. Use " catalogsize " from imported sql statements.

      


Trace and logs location -> /usr/sap/SID/HDB00/hostname/trace/DB_SID

-> This location contains :

  • trace files of executed, expensive, load and unload statement traces etc..
  • Alerts (zip) compressed files
  • Dumps (rte..ooo dumps, crash dumps....)
From OS location we can see trace, alert and dump files...
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID

$sidadm@hostname:/usr/sap/SID/ HDB00/hostname/trace/DB_SID> ls indexserver_alert*.gz | wc -1
121   -->Alerts (compressed) zip files
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID> ls expensive statements*.trc | wc -1
10
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID 1s 30003.loads*.trc | wc -1 
10
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB SID> 19 unloads.trc | wc -1
51 
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID> 19 *oom.tre | wc -1
11  --> Dumps
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID> 19 executed statements.trc | wc -1
10
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID> ls indexserver_alert_hostname.trc | wc -1
1
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID> 19* | wc -1
201   -->Total files in trace folder (DB_SID)
$sidadm@hostname:/usr/sap/SID/HDB00/hostname/trace/DB_SID> pwd
/usr/sap/SID/HDB00/hostname/trace/DB_SID


Types of files mostly required cleanup?

  1. Trcae files
  2. Alerts
  3. Dumps (runtimedumps, crashdumps, oom dumps )

1.How to configure HANA log/trace file rotation/cleanup?

A: Trace file (.trc) rotation using parameters maxfiles (number of files, typically 10) and maxfilesize (size of each file, typically 10 MB). When all files are written, the first one will be removed and a new, empty one is created.



2.The parameter global.ini -> [trace] -> maxalertfilesize defines the maximum size of alert files (default: 50 MB). When the configured size is reached, the file is compressed (including a timestamp in its name) and a new file is written from scratch.


Note : Alert files and dumps are not part of the trace file rotation/cleanup configured via parameter maxfiles.

  • Alert files are zipped after reaching the size configured in maxalertfilesize.
  • Dumps (runtimedumps, crashdumps, oom dumps) are not part of any trace rotation.

 

3.Below parameters will help in cleaning up the alerts and rtedumps,crash dumps.


                                                             
                                                             (OR)


How to delete old SAP HANA trace/log files manually also if required?
If you wish to delete the log/trace files then you can execute following command at OS level: 

cdtrace --> /usr/sap/SID/HDB00/hostname/trace

cmd:
find -type f -mtime +60 -exec rm -rf {} \;   //this will delete files older then 60 days.

                                                      
                                                         (OR)

How to automate cleanup using Hana cleaner ?

https://elrincondeosalla.blogspot.com/2018/06/how-to-configuring-automatic-sap-hana.html

Comments

Post a Comment

Popular Posts

Interview Questions

Image
1. Startup profile from 7.3? Answer: Now the Start profile contents are merged with the Instance profile. With help of the new Instance, profile SAP processes are started and at the same time, instance-specific parameters are read. 2. SAP Application server connects with Database using database client. 3. Difference b/w profiles? Default.PFL - default profile Instance Profile - SID_DVEBMGS"nr"_Hostname location = usr/sap/SID/SYS/Profile 4. Below are the common errors in SAP transport management Return code 4:  Imported with warnings Generation of program, colomns or row missing . Return code 8 :  Imported with errors Syntax error Program generation error Dictionary activation error or method execution error Return code 12 :  Indicates Import Cancelled Program cancelled due to job Import cancelled due to object missing Import cancelled due to object not active Return code 18 :  Indicates Import Cancelled Due to system down while import Due to user expired during import Due to
Read more

EHP Upgrade (SUM)

Image
  Introduction: SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team, and functional consultants' role is limited and mostly confined to regression testing. Reasons for SAP Technical Upgrade : Since technology and businesses evolve, companies need to maintain a technological infrastructure that can support that change. This is the major reason why companies should undertake a technical upgrade of their SAP system. Of course, there are many secondary reasons, the significant one being the fact that like all software vendors SAP supports a released version of its software only for a limited period. Now we can go through the detailed phases included in the SUM upgrade process. latest SPAM version and Kernal also considered prerequisites  Prerequisites : 1. Check SYSTEM user is De-active, if yes, it should be activated. Passwords for th
Read more

SAP Logon Configuration(Load Balancing)

Image
Logon groups (or work groups) are configured to dynamically distribute the load being processed by the dialog work processes. Setting up logon groups helps in uniform distribution of the work load across the available instances. While logging on using a logon group, the ABAP message server is contacted to identify the instance with best performance statistics within the selected logon group . A report runs in SAP every 5 minutes which determines the load across each server and updates in the memory area of the message server. This information will be used by SAP GUI to determine the best instance to distribute the next user.   SAP Logon Process Let’s start with discussing an overview of SAP Logon process. High-level understanding of the process will help to explain details of SAP Logon configuration. SAP Logon Process Overview When user(s) accessing SAP system via  SAP GUI , the request is forwarded into ABAP dispatcher for the direct logon. If SAP GUI is using logon group, the logon w
Read more

SAP Startup Troubleshooting

Image
  1. IS DATABASE UP AND RUNNING? This is an  absolute  prerequisite for SAP SYSTEM to start. In order to test this, operating system command  R3trans -d   can be executed (as SIDadm user). Any return code different than 0 means that DB cannot be reached by DIALOG work processes, and so SAP system will not initiate. The following return indicates that the database is up, running, and reachable by SAP work processes: <hostname>:SIDadm > R3trans -d This is R3trans version X.xx (release 742 - 18.11.14 - 20:14:09). unicode enabled version R3trans finished (0000). -->There is  NO POINT  in moving the analysis further while the return code is different than zero. --> In case the return code is different than zero, please involve your DBA/Network/OS teams. 2 . IS SAP STARTUP AGENT (SAPSTARTSRV) RUNNING? There must be  ONLY ONE  sapstartsrv process running for each instance. Examples for each platform below: Examples As an example, we will use a centralized system with the follow
Read more

HANA Installation & upgrade

Image
  Software Download: SAP HANA System Types : Ø   Single-host system - One  SAP HANA  instance on one host Ø   Multiple-host (distributed) system - Multiple  SAP HANA  instances distributed over multiple hosts, with one instance per host. SAP HANA Deployment Types : Tenant Databases : The tenant database deployment type makes it possible to run several SAP HANA instances on the same hardware in a production environment. Multiple Components on One Database (MCOD) : MCOD deployments are characterized by multiple applications on one SAP HANA system. SAP supports deploying and running multiple applications on a single SAP HANA production database  only  for packaged applications and scenarios listed on the "White List" included in SAP Note 1661202. Virtualized : SAP HANA systems can be run on virtual machines with restrictions to the hypervisor (including logical partitions). Multiple Components on One System (MCOS): MCOS deployments are characterized by
Read more

SAP HANA Backup

Image
  SAP HANA Persistence To ensure optimal performance, the SAP HANA database holds most of its data in-memory. However, it still uses persistent storage to provide a fallback in case of failure.   During normal database operation, data is automatically saved from memory to disk at regular savepoints . Additionally, all data changes are recorded in the redo log . The redo log is saved from memory to disk with each committed database transaction. After a power failure , you can restart the database as you would with any disk-based database. It then returns to its last consistent state by replaying the redo log since the last savepoints . Although savepoints and log writing protect your data against power failures, savepoints do not help if the persistent storage itself is damaged . To protect against data loss because of disk failures, backups are required . Backups save the payload (the actual data) of the data area and log area to different locations.   Types of Back-ups: 1.
Read more

SAP Transport Management System (STMS)

Image
TMS is used to move, manage and control copy development objects and customizing settings in an orderly fashion across SAP Landscape. STMS [SAP Transport Management System] Domain Controller–:  It is used to control the landscape. There will be only one domain controller in the landscape. Initially, it is set to development and later can be moved to on higher available system such as PRD/QAS/Pre7/ production but to keep things simple most of the cases we keep DEV as Domain Controller Member Systems–: The other systems are included in the domain referred to as member systems.  How to Configure   STMS Log on to the SAP system, which is decided to be the Domain Controller, in client  000  and enter the transaction code  STMS. If there is no Domain Controller already, a system will prompt you to create one. When the Transport Domain is created for the first time, the following activities happen in the background: Initiation of the Transport Domain / Landscape / Group Creating the user  TMS
Read more

SAP Kernel Upgrade in Distributed System

Image
What is the kernel of an SAP system? The kernel is a central program that acts as an interface between the SAP application and operating system. These files help startup the R/3 system, initialize the memory, create buffers and start managing the requests from users and effectively utilizing of hardware resources. The kernel is also responsible for starting and stopping all the application services like dispatcher, message server, collector, etc. Why Kernel Upgrade? SAP Kernel is the core of the application. Like all other applications, the Kernel contains the executable files (.EXE files for stating various processes in SAP). The Kernel is the heart of the operating system. It contains those files which are used to run every event in SAP. E.g.|: starting database, shutdowns of the database, starting sap, shutdown of sap, saposcol, to uncar the sap files etc. That's the reason why when a Kernel upgrade is done it means new versions of the various EXE files replace the older version
Read more

Set Up SAP HANA System Replication with hdbnsutil

Image
  Procedure:                                               SITE -A Enable system replication on the primary system(SITE A) as follows: In the Administration editor of SAP HANA studio, choose the  Configuration  tab and ensure that  log_mode  is set to "normal" in the  persistence  section of the  global.ini  file. Log mode  normal  means that log segments must be backed up. Log mode  overwrite  means log segments are freed by the savepoint (therefore only useful for test installations without backup and recovery). Do an initial data backup or create a storage snapshot. In multiple-container systems, the system database and all tenant databases must be backed up. As  <sid>adm  on the command line enable the primary for system replication and give it a logical name with the following command. The primary system must be online at this time: cd /usr/sap/<sid>/HDB<instancenr>/exe hdbnsutil -sr_enable --name=SITEA To check if the site has been successfully enable
Read more

SAP Client Copy

Image
Client copy means " transferring client-specific data"  within the same instance(SID) or between different instances(SID). Client copy can be performed with three different methods - Local client copy. Local client copy. Remote client copy. Client Import/Export. Prerequisites : Disconnect and lock dialog users. Suspend background jobs : This can be done using the report BTCTRNS1. The jobs will be released afterward using the report BTCTRNS2. Client Space check by using the report "RSSPACECHECK" in SE38. 1. Local Client Copy A local client copy copies between clients within the same SAP system. The local client copy must be initiated from the target client. The steps to perform a local client copy: Create an entry for the target client in the client maintenance table, choose transaction  SCC4 . In this example, client 101 will be created: Log on to the target client (client 101) as  SAP*  with the initial password pass (The user SAP* with the password pass is only ac
Read more