You can create a duplicate of a SESAM/SQL database; these duplicates are fully functional databases which have an identical structure and identical contents to the original database. To use a full foreign copy as a database duplicate you must perform the following steps:
To make it possible to access the duplicate database, the system administrator adds an appropriate entry to the SQL database catalog with the administration statement ADD-SQL-DB-CATALOG-ENTRY. Here, the system administrator can assign the physical database name any appropriate logical database name that has not yet been assigned. The duplicate database can then be addressed using this logical database name.
If different storage media apply for the database duplicate than for the original database, the database administrator modifies the definitions of the storage groups and user spaces with the SQL statements ALTER STOGROUP and ALTER SPACE (see “SQL Reference Manual Part 1: SQL Statements”).
If the duplicate's database-specific files are to be created on storage media other than those used for the corresponding files in the original database, the database administrator modifies the duplicate's media table accordingly with the utility statements ALTER MEDIA DESCRIPTION, CREATE MEDIA DESCRIPTION, DROP MEDIA DESCRIPTION (see section “Add the first media record for DA-LOG and PBI files to the media table”and section “Maintain the media table”).
Using the utility statement COPY CATALOG, the database administrator creates a SESAM backup copy of the duplicate database (see section “Creating a SESAM backup copy with COPY”).
The database administrator uses the utility monitor to delete records from the CAT-REC file that are earlier than the new backup and still refer to the original.
Using the utility statement MODIFY, the database administrator deletes all information on SESAM backup copies of user spaces that still refer to the original from the duplicate's RECOVERY_UNITS catalog table (see section “Maintenance of the metadata of SESAM backup copies”).