SAP system copy Possibility of manual intervention in case of delta import - SAP Basis

Direkt zum Seiteninhalt
Possibility of manual intervention in case of delta import
Critical factor: Availability
Table splitting reduces the risk of losing a lot of time during export in case of an error. When restarting, the complete table does not have to be exported again, but only a subset. Simultaneous processing of a table by several R3load processes can reduce the total runtime for this table.

Packages that have not been explicitly assigned a special DDLORA file receive the DDL file specified via the "ddlFile=" parameter. The default is DDLORA.TPL.
Hybrid: for example, the source systems on-premises and the target systems on cloud
SAP system copies are necessary, regardless of the basic infrastructure. Particularly in the context of automation, preference should be given to solutions that support all relevant types of SAP system operation.

Another method of creating an SAP system copy is to use external tools such as Oracle RMAN or Microsoft SQL Server Backup. These tools allow you to create a complete copy of the database as well as a copy of the file system. However, it is important to note that special knowledge is required when using these tools to ensure that the backup is created correctly.

If you have used "Shortcut for SAP Systems" to save system-specific tables before the system refresh, several manual steps can be omitted - the data can be restored by restoring the data saved before the system copy.

The delay is actually only caused by the meticulous matching of trivial things, such as directory names.

Adminsitration passwords (DDIC, DB-Admin, Winadmin), create system snapshots (recovery), perform database import.
SAP BASIS
Zurück zum Seiteninhalt