HANA File System & logs, traces files locations

 File system:



Logs & traces are written to location :[ /usr/sap/< SID >/HDB< Instance number >/< hostname >/trace ]

Tenant db logs under /trace/DB_SID directories
Examples :

faxadm@linux07:/home/faxadm> cdtrace
#--- show tenant database trace and log directories

faxadm@linux07:/usr/sap/FAX/HDB07/linux07/trace> ls -lrt -d */
drwxr-x--x 2 faxadm sapsys 4096 Jul 16 23:35 DB_DHW/
drwxr-x--x 2 faxadm sapsys 4096 Oct 17 12:08 DB_CRD/
drwxr-x--x 2 faxadm sapsys 4096 Oct 20 13:00 DB_LTS/
drwxr-x--x 2 faxadm sapsys 4096 Oct 27 11:48 DB_LBW/
#--- show systemdb log file names

faxadm@linux07:/usr/sap/FAX/HDB07/linux07/trace> ls -lrt *.log
-rw-r----- 1 faxadm sapsys 1293 Jul 18 13:33 sapstartsrv.log
-rw-r--r-- 1 faxadm sapsys 2841 Jul 18 13:33 sapstart.log
-rw-r----- 1 faxadm sapsys 1108 Oct 27 08:36 backintcheck.log
-rw-r----- 1 faxadm sapsys 2506 Oct 31 14:58 backupcheck.log
-rw-r--r-- 1 faxadm sapsys 1780 Dec 5 00:27 sldreg.log
-rw-r----- 1 faxadm sapsys 89426300 Dec 5 10:53 backup.log
-rw-r----- 1 faxadm sapsys 61914996 Dec 5 10:53 backint.log
#--- show systemdb tracefile names
faxadm@linux07:/usr/sap/FAX/HDB07/linux07/trace> ls -lrt *.trc
-rw-r----- 1 faxadm sapsys 1686 Dec 1 11:45 compileserver_alert_linux07.trc
-rw-r----- 1 faxadm sapsys 2162736 Dec 1 11:45 preprocessor_alert_linux07.trc
-rw-r----- 1 faxadm sapsys 129606 Dec 1 15:12 webdispatcher_linux07.30206.000.trc
-rw-r----- 1 faxadm sapsys 14414 Dec 1 11:45 webdispatcher_alert_linux07.trc
-rw-r----- 1 faxadm sapsys 10001949 Dec 3 22:28 daemon_linux07.30200.045.trc
-rw-r----- 1 faxadm sapsys 47356805 Dec 5 11:07 nameserver_alert_linux07.trc
-rw-r----- 1 faxadm sapsys 1882466 Dec 5 09:13 nameserver_linux07.30201.loads.001.trc
-rw-r----- 1 faxadm sapsys 2616819 Dec 5 11:08 nameserver_linux07.30201.017.trc
faxadm@linux07:/usr/sap/FAX/HDB07/linux07/trace> cd DB_DHW
-rw-r----- 1 faxadm sapsys 2096522 Dec 5 11:08 daemon_linux07.30200.046.trc
-rw-r--r-- 1 faxadm sapsys 87203331 Dec 5 11:09 nameserver_history.trc
#--- show tenant database trace and logfile names
#--- Go to tenant database trace and log directory

faxadm@linux07:/usr/sap/HAX/HDB02/linux07/trace/DB_BHD> ll
total 318128
-rw-r----- 1 faxadm sapsys 18367837 Dec 4 23:15 backint.log
-rw-r----- 1 faxadm sapsys 17548682 Dec 4 23:15 backup.log
-rw-r----- 1 faxadm sapsys 2283605 Dec 1 11:43 dpserver_alert_linux07.trc
-rw-r----- 1 faxadm sapsys 2797559 Dec 5 04:42 dpserver_linux07.30270.000.trc

Additional:

1. usr/sap/SID/HDB<instance>/exe --> contains processes like hdbnameserver,
hdbindexserver etc.. and python scripts under python_support directory.

2.usr/sap/SID/SYS/global/sapcontrol/snapshots --> contains the fullsysteminfodump
created for troubleshooting using python script fullsysteminfodump.py from python_support.

3.The SAP HANA lifecycle management tools hdblcm and hdblcmgui write log files during installation.
The most recent log file is always available under /var/tmp/hdblcm.log or /var/tmp/hdblcmgui.log.
Additionally, a copy of the log files is archived in the directory hdb_<SID>_hdblcm_<action>_<date>.

/var/tmp/hdb_<SID>_<action>_<time_stamp>

where <action> :: = install | update | addhost | uninstall | and so on

The following log files are written during performing the action:

  • <hdbcommand>.log: can be read using a text editor
  • <hdbcommand>.msg: XML format for the display in the installation tool with the GUI
  • <hostname>_tracediff.tgz: provides a delta analysis of the original trace files, makes a detailed analysis easier

You can also view the last three log files in the SAP HANA studio using the administration function Diagnosis Files. For more information, see the SAP HANA Administration Guide.

4. location of customer-specific configuration files:

Configuration Settings

Location

Global configuration settings

$DIR_INSTANCE/../SYS/global/hdb/custom/config

Database-specific configuration settings

$DIR_INSTANCE/../SYS/global/hdb/custom/config/<database_name>

Comments

Post a Comment

Popular Posts

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, th...
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 f...
Read more

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 impo...
Read more

SNOTE Implementation and FAQ

Image
 SAP Note : SAP Maintains a knowledge base of problems and resolutions which are accessed from market place. www.service.sap.com/notes.SAP provides resolutions in the form of a note which is a number. Note can be searched on number (if we know)or we can search with the problem code, error number etc. Note provides info. Reg the problem, as follows 1.Problem 2.Pre-Requisites 3.Cause of the problem 4.Solution, Corrections, attachments, and note may redirect one or more notes. Notes of 3 types : 1.Informative note Which consists of details to solve the problem 2.Corrective note This provides changes to the data dictionary elements or repository objects. 3.Manual note: Some of the steps will be present in notes to solve the issue.   Procedure : Read the note carefully and check for validity, Pre-Implementation steps , Post-Implementation steps and Pre-requisite Notes. Do the manual pre-implementation steps in case the Note sugges...
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...
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...
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 o...
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 / Landsc...
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. Th...
Read more

SAP Control Commands

Image
  SAPSTARTSRV (through SAPCONTROL interface) offers a variety of web methods that can be used to monitor/manage the instances of the system. They are specially useful for handling startup error scenarios. The "must-know" ones are listed below and also the general pattern for executing them: GetSystemInstanceList OK hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus testserver001, 0, 50013, 50014, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN testserver001 , 1, 50113, 50114, 1, MESSAGESERVER|ENQUE, GREEN testserver001 , 2, 50213, 50214, 3, ABAP|GATEWAY|ICMAN|IGS, GREEN sapcontrol -nr <instance number> -function <web method name> 1: "GetSystemInstanceList": This one returns the list of active instances for the system, along with component list and the current status. GetSystemInstanceList   OK   hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus   testserver001, 0, 50013, 50014, 3, ABAP|GATEWAY|...
Read more