Due to the size and extent of OCS packages (Support Packages, Add-On Installation Packages, and Add-On Upgrades), importing packages entails lengthy system downtime. The system is not restarted when Support Packages are imported. However, the system should not be used productively during the import process. This restriction is often a disadvantage in production systems.
To reduce downtime when importing Support Packages, import mode downtime-minimized has been developed. This allows you to import most objects while the system is in production operation. These objects are the program code and program texts. This new procedure can reduce downtime considerably if the package contains a large proportion of program code and program texts. (This proportion is around 70-80% in SAP_BASIS and SAP_APPL Support Packages.)
In import mode downtime-minimized, the objects are imported into the database in an inactive state, where they are largely ‘invisible’ to the system. The system can still be used productively.
The new procedure contains some actions (activation of the inactive objects) and organizational steps that were not in the old procedure. This lengthens the duration of the import process. The efficiency or time saved in the non-production phase over the conventional procedure partly depends on the proportion of inactively imported objects in the total imported data. The duration of other actions performed in downtime (such as after-import methods or XPRAs) also contributes to the time saved.
Import the packages in queues that are as large as possible (ideally in a single queue).
In some cases, it is not possible to import Support Packages in a queue using Support Package Manager. Read the relevant SAP Note for known problems in your release. To find out the number of the SAP Note in question, see composite 97620.
Use import mode downtime-minimized:
- In production systems
- In test systems, if you want to test the expected downtime of the production system
During the import, you must treat the systems like production systems (make no manual changes to program objects, no parallel imports from other transport requests).
Do not use import mode downtime-minimized:
- In development systems, or in systems where frequent imports are made (QA or test systems)
The consistency of the system cannot be guaranteed during the import if manual changes are made to program objects at the same time, or if other transport requests are imported.
- To import Support Packages into BBP/CRM systems
The additional pre- and post-import steps in the special BBP/CRM Support Package Manager ensure that the whole import can be performed effectively during downtime.
- To import Preconfigured Systems (SAP Best Practices) with Add-On Installation Tool
Temporary free space is required in the database, since the inactive objects exist in the database alongside the active versions.
A defined process that is triggered by Support Package Manager or Add-On Installation Tool activates the objects later. However, since the inactive objects are not completely isolated from the system, parallel changes might cause unwanted activation and inconsistencies in the system.
Make sure of the following during the import:
- You have enough free space in the database.
We recommend around 1.5 times the size of the packages that you are importing.
Database Tablespaces/Dbspaces/Volumes Affected Oracle
Informix psapes <REL> MaxDB If necessary, create a new volume to extend the database (see also 34690).End of the recommendation.
- No other transport requests are imported at the same time.
- The development environment is not being used productively.