Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

To recreate the Oracle tempfiles
1
If the tempfiles were not residing on the same file systems as the datafiles,
the dbed_vmclonedb command displays 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 /tmp/add_tf.$ORACLE_SID.sql.
where $ORACLE_SID is the name of the clone database.
2
A script named 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.
3
Make a copy of the /tmp/add_tf.$ORACLE_SID.sql script and open it to view
the list of missing tempfiles.
An example of the add_tf.$ORACLE_SID.sql script is shown below:
$ cat add_tf.mnt2.sql
-- Commands to add tempfiles to temporary tablespaces.
-- Online tempfiles have complete space information.
-- Other tempfiles may require adjustment.
ALTER TABLESPACE TEMP ADD TEMPFILE 'DBED:ADJUST_BEFORE_RUN/snap_data11r2/mnt2/temp01.dbf'
SIZE 20971520 REUSE AUTOEXTEND ON NEXT 655360 MAXSIZE 32767M;
4
Evaluate whether you need to recreate any temp files. If you want to recreate
tempfiles, proceed to the next step.
5
In the add_tf.$ORACLE_SID.sql file, edit the sizes and default path names of
the tempfiles as needed to reside on cloned volumes configured for database
storage.
Warning: Do not run the script without first editing it because path names
may not exist and the specified mount points may not contain sufficient
space.
6
After you have modified the add_tf.$ORACLE_SID.sql script, execute it
against your clone database.
7
After you have successfully run the script, you may delete it.
Using Database FlashSnap for backup and off-host processing
FlashSnap commands
190