A .cshrc file containing several aliases was setup to easy moving around and executing repetitive commands.

On this document there is a general explanation of how the environment can be used.

Details on this file: Server Enviroment Setup And Aliases

Some of the asmcmd commands display information, these information is based on v$asm views, other commands actually make changes to the structure like mkdir or rm.

Details on file: ASMCMD Use And Options

To do that we copied the vm to another location, without including the ASM disks, that are located on a separate folder, this way the second vm is pointing to the same ASM disks as the first one.

Details on file: Storage Consolidation With ASM

Checksum Mismatch After Storage Crash, AMDU an 11g tool that can be used with 10g as well, Blockdumps, Asmiostats and asmdebug

Details on this file: ASM Metadata and Other Checkups

We will produce the load using swingbench and we will gather AWR snapshots every 10 minutes. After some time we will be able to check througput statistics based on the AWR snapshots information.

Details on this Document: Measuring Throughput

Another useful script for checking IO:

set pages 50000 lines 250
alter session set nls_date_format='dd-mm-yy hh24:mi';
spool chkio1-Physical-rw.log
select min(begin_time), max(end_time),
sum(case metric_name when 'Physical Read Total Bytes Per Sec' then average end) Physical_Read_Total_Bps,
sum(case metric_name when 'Physical Write Total Bytes Per Sec' then average end) Physical_Write_Total_Bps,
snap_id
from dba_hist_sysmetric_summary
group by snap_id
order by snap_id;
spool off

select min(begin_time), max(end_time),
sum(case metric_name when 'Physical Read Total Bytes Per Sec' then maxval end) Physical_Read_Total_Bps,
sum(case metric_name when 'Physical Write Total Bytes Per Sec' then maxval end) Physical_Write_Total_Bps,
sum(case metric_name when 'Physical Read Total Bytes Per Sec' then maxval end) +
sum(case metric_name when 'Physical Write Total Bytes Per Sec' then maxval end) Total_IO,
snap_id
from dba_hist_sysmetric_summary
group by snap_id
order by snap_id
/

Swingbench provide an easy configurable tool to run oltp or dss like stress tests; that is very useful when the customer does not have any possibility to benchmark the new configuration.

Oswatcher will collect statistics from the OS in a cyclic 2-day period by default, which can be extended to whatever period is convenient for you.

Details on this file:
Lab16-Configure-SwingBench-and-OsWatcher.pdf

But there are very large databases, which are usually cloned using storage tools like bcv, srdf or snapshots that cannot consider Rman as a viable possibility.

For these databases there is the possibility to implement the procedure we will test on this lab.

Note that the rename disk group script has not been made public.
The rename disk group functionality is available on 11g R2 that was made available to the general public on August 2009.

These are the steps required to complete the process:

1. Prepare a set of storage devices with enough space to hold a copy of the diskgroup to be copied
2. Shutdown the source database
3. Make a bit by bit copy of the source database on the target devices
4. Add kfed path to the path of user root
5. Execute the rename diskgroup script
6. Rename ASM disks of the cloned devices
7. Rescan ASM disks
8. Start the ASM instance and mount the new diskgroup
9. Recreate the controlfile and rename the database based on the cloned diskgroup
10.Open the clone with the resetlogs option

Details on this file:
Cloning Disk Group

The compatibility parameters compatible.asm and compatible.rdbms define the minimum ASM and database versions that will be able to connect to a disk group. These parameters can be advanced only

On the resilience probe we will do the following tests

• · Add ASM disks and bring down the ASM instance on the middle of the operation
• · Remove ASM disks and bring down the ASM instance on the middle of the operation
• · Destroy the ASM metadata and restore the disk

Details on this file:
11g Compatibility Parameters and Resilience Test

• · System tablespace loss
• · Recover system tablespace
• · User datafile loss
• · Recover users tablespace
• · Online redo loss
• · Recover from redo loss
• · Controlfile loss
• · Recover from controlfile loss
• · Database loss
• · Recover from total loss

Details on this file
ASM and Rman Crash Restore and Recovery Scenarios

The restore is done in 6 steps
· Re-create the ASM metada
· Restore the spfile
· Restore the controlfile
· Restore the datafiles
· Recover the database
· Open resetlogs

This is covered on this file:
Restoring a Lost Database From Backup

On the previous Labs we created ASM disks based on OS Files, before continuing with the next labs we need to clear them.

This is explained on this file:
Cleanup File based ASM Diskgroups

The first steps of the migration, Installing 11.1.0.6 on it's own Oracle Home and applying patch 11.1.0.7 are ready on this environment, so we can go ahead with the migration process.

In this lab we will migrate only ASM, the database migration is a little longer for the time frame we have so we will continue by moving to ASM an 11g database that already exist on this server.

Details on this document:
Migrating 10g ASM to 11g

ASMLib provides global open close call that will improve performance and transparently implement device labeling, an important aspect when managing storage on Linux.

This lab explain the procedure to migrate these devices to ASMLib.

Details on this document:
Migrating Raw and Block Devices to ASMLib

XDB enable use of FTP and HTML protocols to access and manage files located on ASM disksgroups.

Files can be easily browsed or moved in/out from ASM this way. This option is available only when the database is fully available.

Details on this document:

Configure XDB for ASM Access Through FTP and HTML

This Hands ON series move on a later lab the database to 11g to test this options. In this lab we still work with 10g.

Normal Redundancy on 10g provides protection against disk failures, but it does require for the failed disk to be reconfigured after failure.

On this lab we will simulate a disk failure and then we will restore the failed disk

Details on this document:
Normal Redundancy Resilience Test 10g

The lab can be found on this document:
Looking into PST Metadata

Note that when reading the Metadata to seee the PST you must add to the kfed command the parameter "aunum = 1", that is written in the guide but is not clear enough.