After a clone database is created and opened, the tempfiles are added if they were residing on the snapshot volumes. If the tempfiles were not residing on the same file systems as the datafiles, dbed_vmsnap
does not include the underlying volumes in the snapshot. In this situation, dbed_vmclonedb
issues a warning message and you can then recreate any needed tempfiles on the clone database as described in the following procedure.
To recreate the Oracle tempfiles
dbed_vmclonedb
will display the WARNING and INFO messages similar to the following:
WARNING: Not all tempfiles were included in snapshot for $ORACLE_SID, there is no snapshot volume for /clone_path/temp02.dbf.
WARNING: Could not recreate tempfiles for $ORACLE_SID due to lack of free space.
INFO: The sql script for adding tempfiles to $ORACLE_SID is at
add_tf.
$ORACLE_SID
.sql
is provided in the /tmp directory for the purpose of recreating Oracle tempfiles. This script contains the SQL*Plus commands to recreate the missing tempfiles.
An example of the add_tf.$ORACLE_SID.sql script is shown below:
$ cat /tmp/add_tf.$ORACLE_SID.sql
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE
SIZE 4194304 REUSE AUTOEXTEND ON NEXT 1048576 MAXSIZE 33554432 ;
ALTER TABLESPACE TEMP ADD TEMPFILE
'/clone_path/temp02.dbf' REUSE;
add_tf.
$ORACLE_SID
.sql
script, execute it against your clone database.