Single Database High Available with Oracle Clusterware

It is interested thought to make a single (Multitenant) database High Available inside  the  Oracle Cluster environment. In most cases we make Application High available by making a resource  without predefined Cluster Resource Types. Instead every time create a full stack of settings we have now created a predefined type in which we have set the predefined attributes for the cluster resource to handle on. We have created a type which can be used multiple times by different resources with the same fingerprint.

Link: Right Availability in RAC environment Playing with Oracleclusterware infrastructure components

Oracle Edition Based Redefinition the end of a BIG BANG for application upgrades

When upgrading an application or implementing improvements on stored PL/SQL procedures rule is compiling of those objects needed. During this phase, the end users can not using the application, they must wait until the whole change in the application implemented is finished or otherwise unexpected behavior may occur. In Oracle 11g Release 2 this problem is solved by usubg editions. With editions it is now possible to do live deployments of the new code to compile, whitehout users have to wait for implementing the changes. This is the end of a 'BIG BANG' at application upgrades. It is even possible to have multiple application versions operational.

In this blog i will descibe the mechanism of the Edition Based Redefinition.

Installing and Using Standby Statspack in 11g (by active Data Guard)

Statspack cannot be executed on a standby Database due to its read-only nature therefore tuning the performance of the apply process involves manually collecting statistics.

In the new Active Data Guard option, users can now use statspack from the primary database to collect data from a standby database that is opened read-only and performing recovery. The standby statspack is installed in a separate schema on the Primary database, STDBYPERF which is then propagated to the standby. This user "STDBYPERF" user does not have DBA privileges and has no access to local V$ tables.