Oracle/HP Best Practices Guide for HP IO Accelerators

Single-instance performance architectures 20
execute immediate stmt;
else
stmt := 'alter database add logfile thread ' ||
rlcRec.thr || ' ''/u02/oradata/TESTDB/redo0' || rlcRec.grp || '.log''
size ' || rlcRec.bytes_k || 'K';
execute immediate stmt;
begin
stmt := 'alter database drop logfile group ' || rlcRec.grp;
dbms_output.put_line(stmt);
execute immediate stmt;
exception
when others then
execute immediate swtstmt;
execute immediate ckpstmt;
execute immediate stmt;
end;
end if;
end loop;
end;
/
When the script completes, the database REDO logs reside in the IO Accelerator location. Because
OMFs are not used, you must remove the old REDO log datafiles from the /u01/oradata/TESTDB
directory using operating system commands.
2. Enter the following SQL query to display the new location of the REDO logs:
select a.group# "Group Nbr",
b.thread# "Thread Nbr",
substr(a.member,1,65) "Member",
b.bytes/1048576 size_kb "Size (MB)",
b.sequence# "Seq Nbr",
b.archived "Archived",
b.status "Status"
from v$logfile a, v$log b
order by b.thread#, a.group#, substr(a.member,1,65);
Example D: Migrating redo logs to an IO Accelerator
configured with ASM
For this example:
• The database is a single-instance standalone database using ASM for datafile storage.
• All of the current database datafiles reside in the ASM disk group +DATADG.
• The DB_CREATE_FILE_DEST parameter for the TESTDB database is +DATADG.
• The ASM disk group +REDODG is built from IO Accelerators and configured with the appropriate
level of redundancy.