Import Mode: Downtime-Minimized

Use

Due to the size and extent of OCS packages (Support Packages, Add-On Installation Packages, and Add-On Upgrades), the import of the packages has a large impact on the length of system downtime. The system is not restarted when Support Packages are imported; however, it should not be used productively. This restriction is often a disadvantage in production systems.

To reduce the downtime when importing Support Packages, the import mode downtime-minimized has been developed, which lets you import the majority of the objects during production operation of the system. These objects consist of the program code and program texts. This new procedure can reduce downtime considerably if a package contains a large proportion of program code and program texts. (This proportion is around 70-80% in Basis and APPL Support Packages.)

In the 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 continue to be used productively.

In contrast to the previous import procedure, the new procedure contains some new actions (activation of the inactive objects) and additional organizational steps. 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).

Note that in some cases, Support Packages cannot be imported in a queue with the Support Package Manager. Read the corresponding SAP Note for known problems in your release. To find out the number of the corresponding SAP Note, see composite SAP Note 97620.

Prerequisites

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 the import tool Support Package Manager or the SAP Add-On Installation Tool activates the objects later. However, since the inactive objects are not completely isolated from the system, parallel modifications 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

DB2 Universal Database

PSAPES <REL>D

PSAPES <REL>I

Informix

psapes <REL>

MaxDB

If necessary, create a new volume to extend the database (see also SAP Note 34690).

·        No other transport requests are imported at the same time.

·        The development environment is not being used productively.

Use the 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 the 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 of the special BBP/CRM Support Package Manager make sure that the whole import can be performed effectively during downtime.

·        To import Preconfigured Systems (SAP Best Practices) with the Add-On Installation Tool