Skip to main content


Showing posts from June, 2022

HANA 101 Series - Decoding - HANA DB Version

Hana corrections usually are shipped in the form of support packages( SP ) , Support Pack Stack ( SPS ) & Revisions( Rev ).  This blog will be help us to identify on which SPS & revision is the HANA running by looking at the version. This decoding can come in handy while planning for a HANA SPS Update or a revision update. Please see below for what each digit in HANA DB version actually means : Another Example: Version :   HANA Ø        HANA 2.00 – HANA platform edition 2, Support pack(SP) 00. Ø        HANA 2.00.054 – HANA platform edition 2, Support pack(SP) 00, Support Pack Stack(SPS) 5, Revision 54. Ø        HANA - HANA platform edition 2, support pack stack(SPS) 5, Revision 54, Patch number 0, build reference number  1611906357 .   PS : Typically, Revision will always be called with the SPS like on SPS5 it is revised for 4 th time, it is called revision 54(fifty four). Likewise, if it is revised for 7 th ti

Applying JAVA License when System is down and starting in SAFE Mode

 We faced a strange situation :- 1. Java License was expired. 2. Now in normal situation you get a window of 30 mins after restart to apply License. 3. But for some reason the system started getting into SAFE MODE  .  4. In SAFE MODE , J2EE Engine does not start without license. 5. All this was happening during System Installation/Upgrade. The issue was weird because we tried to remove the system from SAFE mode by going to \usr\sap\<SID>\<instID>\j2ee\configtool\ and using configtool.bat/s h but for this tool to work your java system should be up. We encountered a deadlock we need to get our java system up , we need to remove our system from SAFE mode to do that the way we know was using configtool which would not work until we have our JAVA System up. We were able to get off this situation using consoleconfig.bat/sh it is present in the same location but we were initially not aware of this . Mentioned in 2861966 .   Once you have started consoleconfig.bat/sh go through t

Understanding Splunk Monitoring : BLOG 1

This blog is nothing but my notes from Splunk admin training available on Linkedin Learning by Josh Samuelson , System Admin and DevOps Engineer. This will be a series of 5 blogs :- 1. Understanding Splunk  2. Search  3. Reporting and Dashboard 4. Alerting 5. Practical Splunk  So we use Splunk to monitor machine data and system logs. What we can do with System Logs of Splunk :  Collect , Search , Reporting , Visualizations and Alerting. Collect : One of the major benefit of splunk is that , you can collect all of your data . No need to hunt for logs on multiple server and also gives you benefit of cross reference. Tracing issue from App server to Database server. Search : A powerful way of searching which comes up with simple filtering and basic constraints along with advance Search context Reporting Visualization and Alerting : Provides you with the functionality of generating simple reports and dashboards . Dashboards are nothing but data abstracted into simple graphs which helps you