Oracle/HP Best Practices Guide for HP IO Accelerators

Single-instance performance architectures 18
The TEMP tablespace cannot be moved during the mount stage by using the ALTER DATABASE RENAME
FILE command. A workaround to this issue is to create a new temp tablespace.
1. Create a new temporary tablespace called TEMP2:
CREATE TEMPORARY TABLESPACE TEMP2 SIZE 10240M AUTOEXTEND ON;
2. Assign the default TEMP tablespace for the database to the TEMP2 tablespace:
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;
3. Drop the old TEMP tablespace:
DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;
4. Recreate the TEMP tablespace in the IO Accelerator diskgroup:
CREATE TEMPORARY TABLESPACE TEMP TEMPFILE '+TEMPDG' SIZE 10240M
AUTOEXTEND ON;
5. Assign the default TEMP tablespace for the database back to the TEMP tablespace:
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;
6. Drop the TEMP2 tablespace:
DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;
The TEMP tablespace now resides on the IO Accelerator in the +TEMPDG disk group.
Hosting redo logs on the IO Accelerator
Because of the IO Accelerator low-latency capabilities, moving the logs off of traditional storage to the IO
Accelerator yields a significant performance benefit for write-latency-bound applications. Common
workloads, system configurations, and applications that might be improved include:
• High-volume OLTP applications
• Demanding internet applications that are write-intensive
Best practices for this architecture include using multiple IO Accelerators in a mirrored configuration for
storing the data or replicating logs off-system.
Example C: Migrating redo logs to an IO Accelerator on a local
filesystem
For this example:
• The database is a single-instance standalone database.
• All of the current database datafiles reside in the /u01/oradata/TESTDB directory.
• The database does not use OMFs.
• The current REDO log sets are not multiplexed.
• /u02/oradata is an appropriately configured and redundant IO Accelerator-backed filesystem.
1. Change the ownership and permissions for the /u02/oradata directory:
chown -R oracle.oinstall /u02/oradata
chmod 775 /u02/oradata
2. Log on as the oracle user:
su - oracle