Use the following procedure to create a clone database in an environment outside of a DB2® pureScale® environment. Although you can write to clone databases, they are generally used for read-only activities such as running reports.
If the primary database was configured for log archiving, the cloned database will share the same log archiving configuration. If the archive log location is accessible to the cloned database, this could cause the cloned database to archive log files to the same location as the primary database and can affect the recoverability of both databases. While the cloned database will initially use a different log chain from the primary database, the primary database could eventually use the same log chain value as the cloned database. You should change the log archiving destination for the cloned database to be different from that of the primary database before running the db2inidb command to avoid recoverability issues.
You cannot back up a cloned database, restore the backup image on the original system, or roll forward through log files produced on the original system. The cloned database provides an instantaneous copy of the database only at that time when the I/O is suspended; any other outstanding uncommitted work will be rolled back after the db2inidb command is executed on the clone.