Manage Oracle 11gR2 ASM and RDBMS audit logs on Linux.

If you don't change anything after a new 11gR2 ASM and RDBMS installation, your system's local file systems will slowly fill up with several thousands of audit log files. To fix this problem, you can either:

1. Modify the system's crontab to clean the audit logs directory periodically
2. Configure both the ASM and the RDBMS audit parameters to use syslog.

The crontab solution is easy, but I prefer the syslog solution because:

Installing patch 11.2.0.2 to Oracle 11.2.0.1 when the Clusterware and RDBMS owners are different.

Today we will patch our Grid Infrastructure (GI) and database (RDBMS) homes from 11.2.0.1 to 11.2.0.2. Be ready, this is a relatively long process.

Oracle Grid Infrastructure and Database Patch from 11.2.0.1 to 11.2.0.2

Important changes to Oracle patches.

• Doc ID 1189783.1 - Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2
• Doc ID 854428.1 - Patch Set Updates for Oracle Products
• Doc ID 880782.1 - ALERT: Oracle 11g Release 2 (11.2) Support Status and Alerts
• Doc ID 1179474.1 - 11.2.0.2 Patch Set - Availability and Known Issues 
• Doc ID 1179583.1 - 11.2.0.2 Patch Set - List of Bug Fixes by Problem Type 
• Doc ID 1266978.1 - Potential security issue requires a new download of Oracle Database 11.2.0.2 and Grid Control 11.1.0.1
• Doc ID 10036834.8 - Bug 10036834 - Linux Platforms: Patches not found upgrading Grid Infrastructure from 11.2.0.1 to 11.2.0.2

Oracle 11gR2 RAC - howto fix the "ORACLE_BASE not set in environment" error.

One of our Oracle 11gR2 RAC instances running version 11.2.0.2 was reporting the following error in it's alert log:

« ORACLE_BASE not set in environment. It is recommended that ORACLE_BASE be set in the environment »

To fix the problem, one simply has to issue a simple command.