Showing posts from May, 2013

Converting an Administrator-Managed Database to a Policy-Managed Database and vise versa.


Cluster database configuration can be Policy-Managed or Administrator-Managed. A Policy-Managed database is dynamic with instances managed automatically based on server pools for effective resource utilization. Admin-Managed database results in instances tied to specific servers. 

When we create 11g Release 2 RAC database, on database configuration assistant’s 3 of 13 step we must choose Configuration type : Admin-Managed or Polisy-Managed.

As you know, we can convert configuration type of Oracle RAC Database after installation.In this post I want share steps of conversion of Admin-Managed database to Policy managed (Case #1) and Policy-Managed to Admin-Managed (Case #2). In my case my test RAC Database (racdb) is created Adminstrator-Managed.
Case #1 : Convert Administrator-Managed Database to Policy-Managed Database
Checking configuration of racdb database.
[oracle@oel62-rac1 /]$ srvctl config database -d racdb Database unique name: racdb Database name: Oracle home: /…

Which device is mapped Oracle ASM disk?


Yesterday Yuva Kishore is commented on my Oracleasm - Instantiating disk : failed post and asked a question: We can list the asm disks (listdisks) but where can we find the mapping that ASMDISK1 is mapped to /dev/sda1 and so on? 

I want answer this question with this post.

If you  are using ASMLib for configure ASM Disks, then you can use following steps for define which device mapped which ASM Disk.

As you  know, oracleasm listdisks is return only ASM disk names

[grid@oel62-rac1 ~]$ oracleasm listdisks ASMDISK01 ASMDISK02 ASMDISK03 ASMDISK04 ASMDISK05 [grid@oel62-rac1 ~]$
If you want find which ASM disk is mapped which device, then you must use oracleasm querydisk with ASM disk name.

[grid@oel62-rac1 ~]$ oracleasm querydisk -d ASMDISK01 Disk "ASMDISK01"  Is a valid ASM disk On device[8,17]
As see you, ASMDISK01 is valid ASM disk on device [8,17].

What is means?

It means ASMDISK01 is mapped to device [8,17].

How to find [8,17] device?

We must use Linux ls –l  c…

Oracle Data Guard 11g - Redo Transport User


As you know when we create Data Guard Configuration, we must copy password file. Because SYS user is default redo transport user on Data Guard configurations.

SYS password is changed on primary

When we change SYS password on primary database, redo transport service is stopping and we are getting error: ORA-01031: insufficient privileges. When redo transport failed for this reason we can recreate standby password file with copy from primary side. Same time we can change redo transport user, by setting REDO_TRANSPORT_USER with SYSOPER privileged user. I demonstrated in two case, when SYS password changing on primary database.

Password files.

Traditionally we are coping password file from primary with operating system command (cp, copy). After Oracle Database 11g version RMAN can duplicate password file with DUPLICATE command, so when we using RMAN DUPLICATE command with FOR STANDBY FROM ACTIVE DATABASE option, we can use PASSWORD FILE option for copy primary database password file…