Today while creating database on ASM using DBCA I got following error exactly after reaching 4%.

After searching on net I found, a workaround of using “custom database” tempalate instead of “general purpos or transaction processing” in dbca.

I was not sure about this workaround, and as expected it failed at same point with same error.

DBCA was failing to create datafile in +DATA diskgroup. ASM database was up & running with +DATA in MOUNTED state.

Was it due to file permission issue on raw disks under ASM??

We have separate OS users for grid & rdbms home which belong to same primary group “oinstall”.

root@rmb-zdr-odb01# pwd
/dev/rdsk
root@rmb-zdr-odb01# ls -lrt
crw-r----- 1 grid oinstall 206, 69 Aug 16 10:39 c0t5000CCA01D2EC43Cd0s5
crw-r----- 1 grid oinstall 206, 68 Aug 16 10:39 c0t5000CCA01D2EC43Cd0s4
crw-r----- 1 grid oinstall 206, 66 Aug 17 17:24 c0t5000CCA01D2EC43Cd0s2
crw-r----- 1 grid oinstall 206, 64 Aug 17 17:24 c0t5000CCA01D2EC43Cd0s0
crw-r----- 1 grid oinstall 206, 67 Aug 17 17:26 c0t5000CCA01D2EC43Cd0s3
crw-r----- 1 grid oinstall 206, 65 Aug 17 17:36 c0t5000CCA01D2EC43Cd0s1

So here’s the culprit 🙂 . Changed permissions to 660 instead of 640

root@rmb-zdr-odb01# ls -lrt
crw-rw---- 1 grid oinstall 206, 69 Aug 16 10:39 c0t5000CCA01D2EC43Cd0s5
crw-rw---- 1 grid oinstall 206, 68 Aug 16 10:39 c0t5000CCA01D2EC43Cd0s4
crw-rw---- 1 grid oinstall 206, 66 Aug 17 17:24 c0t5000CCA01D2EC43Cd0s2
crw-rw---- 1 grid oinstall 206, 64 Aug 17 17:24 c0t5000CCA01D2EC43Cd0s0
crw-rw---- 1 grid oinstall 206, 67 Aug 17 17:26 c0t5000CCA01D2EC43Cd0s3
crw-rw---- 1 grid oinstall 206, 65 Aug 17 17:36 c0t5000CCA01D2EC43Cd0s1

This time DBCA worked successfully without any issue!!

Hope so u will find this post very useful 🙂

Cheers

Regards,

Adityanath