Veritas Storage Foundation™ for Oracle 5.0.1 Administrator's Guide

So a 1TB file system can potentially store up to 2TB worth of files if there are
sufficient blocks containing zeroes. Quick I/O files cannot be sparse and will
always have all blocks specified allocated to them.
Handling Oracle temporary tablespaces and Quick
I/O
You can create a new temporary tablespace using Quick I/O files. However, you
cannot convert existing temporary tablespaces which use regular files to Quick
I/O with the qio_getdbfiles command on Oracle9.
By default, qio_getdbfiles skips any tablespaces marked TEMPORARY because
they can be sparse, which means that not all blocks in the file are allocated. Quick
I/O files cannot be sparse, as Quick I/O provides a raw-type interface to storage.
If a sparse file is converted to a Quick I/O file, the Oracle instance can fail if Oracle
attempts to write into one of these unallocated blocks. When you initially create
a temporary tablespace on Quick I/O files, however, Oracle sees them as raw
devices and does not create sparse files.
To convert a temporary tablespace using regular files to Quick I/O files, you can
drop your existing temporary tablespaces which use regular files and recreate
them using Quick I/O files. You can also leave the temporary tablespaces as regular
files.
To obtain a list of file names that are not temporary
◆
Use the following SQL statements:
$ sqlplus /nolog
SQL> connect / as sysdba;
SQL> select file_name from dba_data_files a,
dba_tablespaces b where a.tablespace_name =
b.tablespace_name and b.contents <> 'TEMPORARY';
91Using Veritas Quick I/O
Handling Oracle temporary tablespaces and Quick I/O