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
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…
When you need safely remove broker-managed Data Guard Configuration then, oracle recommend following steps…
You know dg_broker_start parameter is TRUE and data guard configuration information contains in broker configuration files dg_broker_config_file1, dg_broker_config_file2 with broker-managed Data Guard Configuration.
Following steps I use on my test machines witch is running on Oracle Virtual Box. I captures video on this machines, too. Primary and Standby Database running on Oracle Linux Server 6.2 and installed Oracle Database 11g Release 2 (18.104.22.168).
DG – is my breoker-managed Data Guard configuration. admdb is primary database, stldb – is standby database.
DGMGRL> show configuration
Configuration - dg
Protection Mode: MaxPerformance
admdb - Primary database
stldb - Physical standby database
Fast-Start Failover: DISABLED
Archive log destinations like as
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.
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…