SAP firefighter installation steps_VIRSANH_VIRSAHR


  •  Users must be locked
  • suspend background jobs by using BTCTRNS1 report.
  • Maintain enough free space on G drive[Installation directory]
  • Download the VIRSANH and VIRSAHR component and put into EPS folder


Here am going to install the firefighter for the first time by using SAINT Tcode.[You can upgrade the patch level by using SPAM Tcode]





Now the above two component successfully added into the target system.

Step2:Next step is proceed with installation. click on start.




First we are going to install the VIRSANH component as per the SAP note recommendation.





Kindly go though the below SAP note for password request:




Step4: Start with background option



Installation phase started. PFB for your reference.

10Step5: Add on was successfully imported. click with finish.

11Step6: Repeat the same steps for the VIRSAHR component. PFB for your reference.



For further reference like password request please read the below SAP note.

Note2Step7: We have successfully completed the firefighter installation. PFB for your reference.

14Next thing is we need to increase the patch level to latest Level[N-1 Level]. Please check with market place for your reference.

Step8: To increase the patch level by using SPAM Tcode.





Finally we have completed the component upgrade for the above VIRASANH and VIRSAHR component.

17Kindly revert in-case of any queries.

Thanks and Regards,

Sabarish Vasudevan.







Step by step to install sql service package upgrade


  • Download the required support package and put into D drive or installation directory.
  • SAP should be stopped on all the instance
  • SQL services should be stopped before starting the upgrade activity. [MSSQLSEVICE, Etc]

Step 1:Double click on the SP dumps and run the file


Step 2:

startingStep 3: SQL Server update completed,then proceed with next for License Terms.List of Phase

Step 4:


Step 5: We can select the features. Normally proceed with default.


Step 6:

Checking files

Step 7:PFB the list of features ready to update, click next to update progress

Ready to update

Step 8: After completed the SQL SP, you need to reboot the server.

RebootStep 9: We have successfully completed the SQL SP upgrade.


Step 10: Finally we can verify using the below SQL command.[In this case we upgraded to SP2 level]


Kindly Let me know in case of any queries.

Thanks & Regards,

Sabarish Vasudevan.

SAP liveCache Technology

The SAP liveCache technology is an object-based enhancement of the SAP MaxDB database system. It was developed for managing complex objects in applications in which large quantities of data must be constantly available and changeable. You can only use SAP liveCache technology with SAP applications.

Properties of an SAP application with SAP liveCache technology:

  • With optimal configuration, all application data and objects are located in the working memory
  • Multiple application servers are sharing the read/write cache
  • Relational and object-oriented data modelling
  • Data-intensive business logic is executed close to the application data (minimizing round trips)
  • All database functions are available


SAP liveCache Technology: Technical System Landscape:

In addition to the SAP MaxDB database kernel which provides basic database functions such as saving, restoring, and transaction management, an SAP liveCache database instance also comprises the following software layers:

  • SAP liveCache Applications (LCApps)

    The business logic is included in the SAP liveCache kernel by using DB procedures (stored procedures). This removes much of the work that would otherwise be needed for communication and the transfer of data.

  • Object Management System (OMS)

    A large part of the application data in an SAP liveCache database instance is managed in objects (OMS data). OMS data is managed in containers that are assigned to a persistent C++ class of the object type as object memory.

SAP liveCache Technology: Architecture
Sabarish Vasudevan.

How to start sap from command line in Windows without MMC console

Step 1:start -> run -> cmd

Step 2: Go to the SAP installation directory Ex:[\usr\sap\SID\SYS\exe\uc\NTAMD64]

Step 3: now execute: [STARTSAP name=<SID> nr=<SYSNR> SAPDIAHOST=<host>]

Step 4:

where SID = your sap system id

nr = instance number

SAPDIAHOST = host name of your sap server

Step 5: Now you can able to that STARTSAP Continues status.

Step 6: Finally put R3trans -d command to verify whether the system returen code is 00. PFB for your reference.

R3transPlease revert if you have any queries.


Sabarish Vasudevan.


Java node not coming up,dispatcher and SDM is running

Problem statement:

We have enabled the debug port as per the client requirement. This enabling the debug port, system need to be restarted for this get into effect. After the restart 2 java node not coming up out of three nodes,dispatcher and SDM is up and running fine.


Example screen shorts of before restart:

Before restart_Debug mode disabled

You can able to see that the debug mode is disabled.

Step 1: SAP standard information for your reference.

Portal std port number-5-system number-portocol port[EX: 53000] if it’s https connection use [53001].

Debug std port number-5-system number-start with 21.[EX: 53021].

Step 2: We have given the same debug  port number for all the three java nodes. So here FCFS concepts working,only one java node is capable for working,rest of two java node don’t have any other port number. so the result is java node went down.

Step 3: Go to config tool [EX:G:\usr\sap\SID\JC30\j2ee\configtool.bat].

Step 4:Two possible method to declare the debug port :

   1. Global Server Configuration[ We can declare the port number as a global value]

2.Instance Configuration [ Need to declare each and every instance]. PFB for your quick reference.

Config Tool

Step 5: In this case we have 3 java nodes, obviously we can choose the option two.

We have given the three port number as Node 1=53021

Node 2=53026

Node 3 =53031

PFB for your reference:

Node 1:

Node 1

Node 2:

Node 2

Node 3:

Node 3

Step 6: After the restart, java system up and running fine without any issues. Please revert if you have any queries.

PFB the debug mode is switched on.

Debug on


Sabarish Vasudevan.

Java Support Package Manager_Step by Step screen shorts for Patches upgrade:

Step 1: Removing the Bug from production environment we going to upgrade the necessary component to latest release level.

Step 2: In this case we going to upgrade 4 component[below mentioned] level from to level.

Step 3:we have downloaded the below mentioned component in service market place and load it in EPS folder.[EX:G:\usr\sap\trans\EPS\in]

Step 4: Open G:\usr\sap\SID\J20\j2ee\JSPM\ under the folder you can able to find the go batch file then right-click  run as an administrator the go.bat file.

Step 5:Main Screen of JSPM:



Step 6: Log in with administrator:


Step 7: You can see the various option of JSPM, In this case we are going to upgrade the patches level, so we should choose third option[Single support packages and patches[Advanced user only]


Step 8: JSPM automatically fetch the component from EPS folder. PFB the component need to be upgrade to latest level.


Step 9:Validation check for the four component:


Step 10:deploying the selected support packages.


Step 11: deployment of support packages has completed.


Step 12: After the Patches upgrade to latest level, the  issues resolved. Kindly revert if you have any queries.