Oracle/HP Best Practices Guide for HP IO Accelerators

Single-instance performance architectures 17
chmod 775 /u02/oradata
2. Log on as the oracle user:
su - oracle
3. Create the subdirectory for the TESTDB database under /u02/oradata:
mkdir -p /u02/oradata/TESTDB
The IO Accelerator is configured as an EXT3 filesystem and is ready for use by the Oracle TESTDB
database.
4. As the oracle user, move the TEMP tablespace to the IO Accelerator.
Migrating the TEMP Tablespace
1. Log on to sqlplus as sysdba:
export ORACLE_SID=TESTDB
sqlplus / as sysdba
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.
2. Create a new temporary tablespace named TEMP2:
CREATE TEMPORARY TABLESPACE TEMP2
TEMPFILE '/u01/app/oradata/temp201.dbf' SIZE 10240M AUTOEXTEND ON EXTENT
MANAGEMENT LOCAL UNIFORM SIZE 1M;
3. Assign the default TEMP tablespace for the database to the TEMP2 tablespace:
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp2;
4. Drop the old TEMP tablespace:
DROP TABLESPACE temp INCLUDING CONTENTS AND DATAFILES;
5. Recreate the TEMP tablespace on the IO Accelerator filesystem:
CREATE TEMPORARY TABLESPACE TEMP
TEMPFILE '/u02/app/oradata/temp01.dbf' SIZE 10240M AUTOEXTEND ON EXTENT
MANAGEMENT LOCAL UNIFORM SIZE 1M;
6. Assign the default TEMP tablespace for the database back to the TEMP tablespace:
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE temp;
7. Drop the TEMP2 tablespace:
DROP TABLESPACE temp2 INCLUDING CONTENTS AND DATAFILES;
The TEMP tablespace now resides on the IO Accelerator.
Example B: Migrating temp tablespace to an ASM disk group
backed by IO Accelerators
For this example:
• All of the current database data files reside in the +DATADG ASM disk group.
• The DB_CREATE_FILE_DEST parameter for the TESTDB database is +DATADG.
• An appropriately configured ASM disk group named +TEMPDG has been created and includes only
the target IO Accelerators (likely using normal redundancy or some form of replication).