December « 2009 « Oracle DBA – Tips and Techniques

11g ASM rolling upgrade from 11.1.0.6 to 11.1.0.7

In Oracle 11g, we can now do rolling upgrades of the ASM instanaces in a RAC cluster configuration. In this example shown below, one of the ASM instances is being upgraded to 11.1.0.7 while the other instance is still running on version 11.1.0.6. While the ASM software is being upgraded, client connections to the RAC database will continue as the service will get relocated to the other node in the cluster which is not being currently upgraded. So in other words this is an online patch application.

The database name here is racdba and the two instances are racdba1 and racdba2 running on nodes middba1 and middba2. The platform used in this example is AIX 5.3 64 bit on a P series LPAR.

On one of the nodes in the cluster, connect to the ASM instance (+ASM1) and issue the command to start the rolling migration.

SQL> alter system start rolling migration to

Continue reading 11g ASM rolling upgrade from 11.1.0.6 to 11.1.0.7

11.1.0.6 Clusterware upgrade to 11.1.0.7

The following screenshots are taken from a RAC Clusterware upgrade from 11.1.0.6 to 11.1.0.7 on AIX 64 bit platform.

We encountered an issue related to Bug 8925669: ROOT111.SH 0509-150 DEPENDENT MODULE LIBTTSH11.SO COULD NOT BE LOADED. I have provided the workaround we used in this case and which did work for us.

The last screen will indicate that we need to run the root111.sh script which will stop and start the clusterware processes in the upgraded CRS Home

The installer has detected that your Cluster Ready Services (CRS) installation is distributed across the following nodes:

middba1
middba2

Because the software consists of local identical copies distributed across each of the nodes in the cluster, it is possible to patchyour CRS installation in a rolling manner, one node at a time.

To complete the installation of this patchset, you must perform the following tasks on each node:

1. Log in as the root user.
2. As the root user, perform the following

Continue reading 11.1.0.6 Clusterware upgrade to 11.1.0.7

Duplicate from active database – ASM Primary to ASM Standby

In my earlier post 11g Standby Database Creation Without Any RMAN Backups I had illustrated how to create a standby database using the 11g Active Duplication feature which enabled us to create a standby database without any backup taken of the primary database. In this case it was a ASM Primary and a non ASM Standby database.

This example now illustrates how the same procedure can be extended to create an ASM Standby database from an ASM Primary database using the same active duplication method.

After following all the steps explained in the previous example, run the following command after launching RMAN and connecting to the auxiliary instance.

DUPLICATE TARGET DATABASE
FOR STANDBY
FROM ACTIVE DATABASE
NOFILENAMECHECK
DORECOVER
SPFILE
PARAMETER_VALUE_CONVERT
‘/u01/oracle/admin/test_fc’,’/u01/oracle/admin/test_js’
SET DB_UNIQUE_NAME=”test_js”
SET LOG_ARCHIVE_DEST_2=”service=test_fc LGWR SYNC REGISTER VALID_FOR=(online_logfile,primary_role)”
SET FAL_SERVER=”test_fc”
SET FAL_CLIENT=”test_js”

Continue reading Duplicate from active database – ASM Primary to ASM Standby

11g Standby database creation without any RMAN backups

Quick steps to set up a 11g Standby database with Active Data Guard using the Active Duplication feature available in 11g where we can create a standby database without having to take a backup on the primary database. Datafiles are copied over the network.

Primary machine – OATU036
Standby machine – DROU036

Database Name – SID1O

TNS alias for Primary – sid1o_fc
TNS alias for standby – sid1o_js

Enable force logging on the Primary database

SQL> alter database force logging;

Database altered.

Create the Standby log files on the Primary database

Copy the password file from the $ORACLE_HOME/dbs directory on primary server to $ORACLE_HOME/dbs on the standby server

Update listener.ora on Standby machine

(SID_DESC=
(GLOBAL_DBNAME=sid1o_js)
(ORACLE_HOME=/u01/oracle/product/11.1.0/db_1)
(SID_NAME=sid1o)
)

Stop and Restart the listener on the standby site

Update tnsnames.ora on Standby as well as Primary site with the alias ‘sid1o_js’ and

Continue reading 11g Standby database creation without any RMAN backups

How to manually clear EM Grid Control alerts

We can use the procedure outlined below to clear outstanding warning and critical alerts which are displayed on the EM Grid console home page. Normally these alerts get cleared automatically when the event ot threshold which caused these events in the first place is longer in the ‘critical’ or ‘warning’ state.

But there are some times when we wish to manually clear the alerts – there are some notes on Metalink which document cases where alerts are not cleared even after the event which caused them no longer exists – and also we may want to clear all the warning alerts which concern alerts related to logins by SYS user – out of the box auditing of the SYS user logins is enabled and every time SYS connects, it will generate a warning alert.

In a forthcoming post I will detail now to create a customised monitoring template and deploy it enterprise

Continue reading How to manually clear EM Grid Control alerts

11g Release 2 RMAN Backup Compression

Oracle 11g Release 2 introduced compression algorithm levels which can be used for compressing table data, Data Pump exports and RMAN backups as well.

The compression levels are BASIC, LOW, MEDIUM and HIGH and each affords a trade off related to backup througput and the degree of compression afforded.

To use this option, we can run the following RMAN commands

RMAN> CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;

followed by ..

RMAN> CONFIGURE COMPRESSION ALGORITHM ‘HIGH’;
or
RMAN> CONFIGURE COMPRESSION ALGORITHM ‘MEDIUM’;
or
RMAN> CONFIGURE COMPRESSION ALGORITHM ‘LOW’;
or
RMAN> CONFIGURE COMPRESSION ALGORITHM ‘BASIC’;

Tests carried out on a small 1.5 GB database returned compression ratios of about 4.7 at best case. However, it should be noted that use of LOW, MEDIUM and HIGH requires the Advanced Compression license. The backupset size and backup durations are shown below.

Compression Level ‘HIGH’

backupset size: 226.18M
time: 00:02:21

Compression Level ‘Medium’

backupset size: 293.80M
time: 00:00:30

Compression Level ‘Low’

backupset size: 352.59M
time: 00:00:20

Compression Level ‘Basic’

backupset size:

Continue reading 11g Release 2 RMAN Backup Compression

11g RMAN Virtual Private Catalog

In Oracle 11g, we can grant restricted access to the RMAN catalog to some users so that they can only access a limited set of databases that are registered in the RMAN catalog.

This is done by creating a Virtual Private Catalog which in turn will grant a particular user read/write access to only that user’s RMAN metadata. We can in this way create a number of multiple recovery catalog users each seeing only having access to a limited set of databases while the base recovery catalog owner has access to the entire metadata.

For example, in the RMAN catalog owned by user RMAN11D, there a a number of databases registered, but we would like to restrict access to the APEX database to a single user – RMAN_APEX.

So we need to first create a user in the database which houses the base RMAN catalog, grant that user the RECOVERY_CATALOG_OWNER role and then

Continue reading 11g RMAN Virtual Private Catalog

Oracle DBA – Tips and Techniques

That’s Me

Feedback

Categories

Archives

Recent Posts

Administration