This blog covers all SAP Unix commands to Bounce SAP systems and clean memory:
- Sap System Download
- Uninstall Sap System Manually Access
- Uninstall Sap System Manually Connect
- Sap Gui Uninstall
- Uninstall Sap System Manually Access
- Sap System Definition
<iframe src=”//www.googletagmanager.com/ns.html?id=GTM-NKZ9FM” height=”0″ width=”0″ style=”display:none;visibility:hidden”></iframe>
A way to remove SAP Business Client 6.5 from your PC using Advanced Uninstaller PRO SAP Business Client 6.5 is an application offered by SAP SE. Sometimes, users decide to erase this application. This is hard because uninstalling this manually takes some knowledge related to PCs. 2027955-How to manually remove/uninstall SAP BusinessObjects Business Intelligence 4.x from the system in Unix/Linux environment? It states to uninstall the SAP system through Add/remove programs. ', if you mean to uninstall using Windows Add/remove program, then it is not the correct way. For your solman 3.1, when you go into the directory /usr/sap/ or usr/sap/ you will find a file name uninstall.exe. The uninstall process is designed to remove as much as possible of the SAP system to be deleted. If an item cannot be removed, a message informs you that you have to remove this item manually. You can do this either at once or after the uninstall process has finished. As soon as you confirm the message, the uninstall process continues. On Macintosh, SAPgui uninstall and reinstall. Move Applications SAP to Trash. Move the following directory to the Trash: Userhome Library Preferences SAP. Move the following directory to the Trash: Macintosh HD Library Preferences SAP. (If that folder exists.) This will take care of the preferences at the System level.
SAP System Bounce Sequence with all commands on Unix:
| Batch Job Hold |
| To hold critical batch jobs and check active jobs before bringing down application |
| Shutdown System |
| stopsap all(stop sap system) |
| Kill remaing processes |
| ps –ef|grep sidadm ( check if any process is running) |
| kill -9 PID (kill the process) |
| Clean Memory |
| cleanipc <systen no>remove (clean shared memory) |
| for ex:- |
| cleanipc 00 remove |
| cleanipc 01 remove |
| ipcs|grep sidadm ( to check if shared memory still exists if entries found) clean as below |
| ipcrm –s pid –m pid –m pid –m pid –s pid (clean the remaining shared memory) |
| ipcs|grep adm (should return Blank) |
| Start SAP |
| startsap all |
SAP Validation including Database connectivity once system is up R3trans –d (to check database connectivity) |
| Release Batch Jobs: |
| Once SAP is up,Ask batch team to release batch jobs |
To bring down system Manually:
stopsap r3 D00 (D00 Instance no, it can also be D01, D10 etc, we need to check this from cdpro –>ll )
To bring up system Manually:
startsap r3 D00
Stopping & Starting Up the Oracle Database System :
sqlplus “/ as sysdba”
sql>shutdown
or
sql>shutdown immediate
——————————————————————————
sql>startup
—————————————————————————-
The shadow instance start/stop is controlled by the upgrade.
Attention! Start/stop the shadow instance manually only, if it is really requested, unwanted start/stop can impact the whole update.
Possible situations, when the shadow instance needs to be started/stopped manually:
- An error occured in one of the START_SHDI* STOP_SHDI_* phases and you want to check if a manual start stop is working
- During the ACT_UPG phase instance parameter(s) needs to be changed and activated with an instance restart for optimizing runtime or avoid an error
REMARK: Some instance parameter can be activated dinamically without instance restart, check the parameter documentation in the transaction RZ11.
- Restart the shadow instance in the nZDM scenario
To stop the shadow instance manually, proceed as follows:
Step 1
UNIX: cd <update directory>/abap/bin example: cd /usr/sap/PRD/SUM/abap/bin
WINDOWS: <drive> example: D:
cd <update directory>abapbin example: cd usrsapSUMabapbin
Step 2
UNIX: ./SAPup stopshd
WINDOWS: .SAPup stopshd
Step 3
The following output can be displayed:
Sap System Download
Enter the path of your root directory [D:usrsapSUMabap]: Root directory =
Confirm if the correct SUM directory is displayed and press Enter
The following output will be displayed:
Stopping shadow system ...
Stopping service ...
To start the shadow instance manually, proceed as follows:
Step 1
UNIX: cd <update directory>/abap/bin example: cd /usr/sap/PRD/SUM/abap/bin
WINDOWS: <drive> example: D:
cd <update directory>abapbin example: cd usrsapSUMabapbin
Step 2
UNIX: ./SAPup startshd
WINDOWS: .SAPup startshd
Step 3
The following output will be displayed:
Starting shadow system ...
Starting service ...
waiting 4 seconds for system to come up ...
testing if system is available ...
REMARK: If the shadow instance is not working in the current upgrade phase, one of the following message will be displayed:
At this time of the procedure, the shadow instance does not yet exist since you are before phase START_SHDI_*!
or
At this time of the procedure, the shadow instance does not exist anymore since you are passed phase STOP_SHDI_*!'
Conclusion: Depending on the update phase another instance needs to be started or stopped.
To identify the currently used instance or to analyse other start/stop errors please follow the troubleshooting guide
Before the actual command for starting and stopping the shadow instance for the platform IBM i, you must start a QP2TERM session and supplement the execution environment, for example, in the following way:
1. Perform the following steps as <SID>OFR or as <SID>ADM (depending on the user concept that is active).
2. Call QP2TERM. Then in the QP2TERM session:
3. cd <upgrade_directory>/bin
4. export LIBPATH=.
5. Execute the command R3up/SAPup/SAPehpi specified below.
6. You can exit the QP2TERM session using F12/F3.
- Starting the shadow instance
Uninstall Sap System Manually Access
Start SAPup as the user <sid>adm as follows:
SAPup startshd
Uninstall Sap System Manually Connect
- Stopping the shadow instance
Sap Gui Uninstall
Stop SAPup as the user <sid>adm as follows:
SAPup stopshd
Troubleshooting shadow instance start problems
If the instance terminates with error during startup, troubleshooting steps can be found on the wiki page
Uninstall Sap System Manually Access
Troubleshooting instance start-stop situations during update
Chapter Typical upgrade phases, where the shadow instance is used:
SAP note 398100 - Shadow instance during upgrade
Sap System Definition
SAP note 525677 - Problems when starting shadow instance