Codemuch 01010101011101101010110001...

One of the most exciting features available from Oracle's Real Application Clusters (RAC) is 24/7 availability. When a node fails, Transparent Application Failover (TAF), allows transactions to restart or be resumed on another node in the cluster, in theory providing no interruption of service to the client.

As a developer, there is nothing transparent about TAF. I recently had a client move to an Oracle RAC environment for their existing application. They assumed that RAC would take care of everything and there would be minimal or no code changes.

The Oracle RAC installation book has been updated to include a guide on how to install, upgrade and configure a database instance.

It can be found here.

The Oracle RAC installation book has been updated to include a guide on how to install, upgrade and configure Automatic Storage Management.

It can be found here.

The Oracle RAC installation book has been updated to include a guide on how to upgrade Clusterware to patchset 2.

It can be found here.

Recently I needed to manage an Oracle RAC installation and needed to setup a test environment to mirror the production environment of the client. So I wrote up what I hope is straight forward guide to installing Clusterware on Windows Server 2003.

The guide can be found here.

It only covers installation of Clusterware software for now. Guides for ASM and cluster database install to follow soon.