https://wiki.scn.sap.com/wiki/display/Basis/Basis+HowTo+Guides?src=breadcrumbs-parent
https://wiki.scn.sap.com/wiki/display/Basis/ABAP+System+Maintenance
It is always asked whether it is necessary to stop/restart SAP ABAP system to do system maintenance operations. The following is the summary
of some scenarios for your reference:
1. kernel update
It is necessary to shut down SAP system before kernel update.
2. change request transport
It is necessary to log on ABAP system and use T-code : STMS to
transport change request between systems, so there is no need to shut
down SAP system. but it is better for you to prevent any other operation
running during request transport. Changes are activated automatically
during import, so you do not need to restart target system after
transport.
3. SAP note implementation
SAP notes are implemented via T-code : SNOTE on sap system, so
there is no need to shut down SAP system. but it is better for you to
prevent any other dialog/background operation running during note
implementation. Changes are activated automatically during note
implementation, so you do not need to restart SAP system after note
implementation.
4. support package implementation/add-on installation
You should log on client 000 and use T-code : SPAM/SAINT to
implement support packages or install add-ons, so there is no need to
shut down SAP system. But you should make sure that no any other
operation is running during support package implementation/add-on
installation. You do not need to restart SAP system after support
package implementation/add-on installation, but it is suggested to run
T-code:SGEN to generate ABAP program loads.
5. system upgrade
You do not need to stop SAP system manually during system upgrade.
The upgrade tool permits users to do normal operations before reaching
downtime phase. SAP system will shut down automatically when reaching
downtime phase, and SAP system will be restarted by upgrade tool after
downtime phase.
6. OS kernel parameters maintenance
Dynamic OS kernel parameters become active automatically after
changing, while static OS kernel parameters will not become active until
OS restart. But no matter whether it is dynamic or static, It is
recommended to stop SAP system before changing OS kernel parameters.
7. SAP profile parameters maintenance
SAP profile parameters can be either changed via T-code :
RZ10/RZ11 on SAP system, or edited directly in the sap profile on OS
level. It is not necessary to stop SAP system. But to get changed
parameters activated, you have to restart SAP system.
8. database online backup + archive redo log
It is recommended to do database online backup + archive redo log
every day. You can schedule daily background jobs to do it via T-code :
DB13 on SAP system, so there is no need to stop SAP system.
9. database offline backup
It is recommended to do at least one full offline backup every
month. It is necessary to shut down database to do database offline
backup, which means that you should stop SAP system also.
网友评论