This content has been marked as final. Show 3 replies
I would indeed start by looking in the alert_log of the ASM instance.
It looks like it is not completely started.
A local test with seperate users for DB and ASM instance shows:
$ sqlplus system/passwordSo, als system user, it is possible to create a tablespace.
SQL*Plus: Release 10.2.0.4.0 - Production on Thu Dec 17 13:40:35 2009
SQL> create temporary tablespace a_temp tempfile '+DB01' size 1g;
We however don't use sysoper and sysdba seperation, but even that should not bring a problem here.
Its not System user which is not able to create tablespace, Even if you try sys it will still fail with same error. Check permission on the raw disk used for ORADATA diskgroup.
Permission should be
for all "asm disk string"
Confirm whether ASM and Database are installed under same user ? Also confirm the value of SQLNET.AUTHENTICATION_SERVICES from sqlnet.ora of $ORACLE_HOME