Entering content frame

Process documentation Database Copy Locate the document in its SAP Library structure

Purpose

You can use a database copy to test new applications, to check the database structures without affecting operation or to set up a new standby database, for example. You also need a database copy to create a system copy of an SAP system.

To copy a database, use a complete data backup.

Original Instance and Copy

This graphic is explained in the accompanying text

Prerequisites

·        Original and target computers are compatible, see Compatible Processor Architectures for Database Copies

Note

To execute a database copy on a non-compatible processor architecture, use the Structure linkLoader database tool.

·        The target instance uses the same version of the database software as the original instance.

Process Flow

You use the Database Manager database tool.

...

       1.      You create a complete data backup of the original instance on a backup medium; see

¡        Database Manager GUI, Structure linkBackup Wizard

¡        Database Manager CLI, Structure linkBacking Up the Database Instance

       2.      You initialize an existing target instance or create a new target instance using the for recovery option:

                            a.      For the database parameters of the target instance, you use the database parameter values of the original instance.

                            b.      In the target instance, you create volumes that are large enough for importing the data backup from the original instance.

                            c.      In the target instance, you define a backup medium that is compatible with the backup medium on which you created the data backup of the original instance.

See:

¡        Database Manager GUI, Structure linkInitializing an Existing Database Instance and Structure linkCreating a Database Instance

¡        Database Manager CLI, Structure linkInitializing an Existing Database Instance and Structure linkCreating a Database Instance

       3.      Import the complete data backup of the original instance to the target instance.

Caution

You must not transfer the target instance into the ONLINE operational state before you import the data backup from the original instance. If the target instance has already been in the ONLINE operational state, reinitialize the target instance.

Note

You can use pipes to transport the data backup.

See:

¡        Database Manager GUI: Structure linkRestoring Without a Backup History

¡        Database Manager CLI, Structure linkRestoring a Database Instance with Initialization

       4.      You transfer the target instance to the ONLINE operational state.

       5.      You update the system tables in the target instance. You enter the database system administrator. See:

¡        Database Manager GUI, Structure linkUpdating the System Tables

¡        Database Manager CLI, Structure linkLoading the System Tables

       6.      If necessary, restore indexes in the target instance that are no longer current (BAD INDEXES). See:

¡        Database Manager GUI, Structure linkRestoring Indexes After a Database Restore

¡        Database Manager CLI, Structure linkRestoring a Damaged Index

See also:

Replication and High Availability

 

Leaving content frame