Forum OpenACS Q&A: Can't create tablespace in Oracle

Request notifications

Posted by Michael Olan on
I've been installing OACS on a new slackware box, but after a couple aborted attempts due to my own failures, can't seem to create a new tablespace in Oracle due to a permission problem. I've checked & I am a member of the dba group, the ownership of the ora8 directory is me.web, and its permission is 775. However, I still get the following:
SVRMGR> connect internal;
SVRMGR> create tablespace oacs 
             datafile '/ora8/m02/oradata/ora8/oacs01.dbf' 
             size 50M 
             autoextend on 
             next 10M
             maxsize 300M
             extent management local
             uniform size 32K;     

create tablespace oacs4 
ORA-01119: error in creating database file '/ora8/m02/oradata/ora8/oacs01.dbf'
ORA-27040: skgfrcre: create error, unable to create file
Linux Error: 13: Permission denied
Posted by Bruno Mattarollo on
Wild guess but the directory should be owned by "oracle.dba"... Try that and run the script as the user "oracle" just in case.

Hope this helps.

Posted by Michael Olan on
Not according to the OACS installation instructions, and not how I have it running on another box:
SVRMGR> exit
joeuser:~$ su -
Password: ************
root:~# mkdir -p /ora8/m02/oradata/ora8/
root:~# chown joeuser.web /ora8/m02/oradata/ora8
root:~# chmod 775 /ora8/m02/oradata/ora8
root:~# exit
I did get around the problem by changing permissions on the directory to 777 just to complete this step, but now have problems that suggest errors with jvminst. So looks like starting over is the next step. Thanks.
Posted by Bruno Mattarollo on


The OACS installation instructions are:

root:~# mkdir /ora8
root:/ora8# cd /ora8
root:/ora8# mkdir -p m01 m02 m03/oradata/ora8
root:/ora8# chown -R oracle.dba /ora8
root:/ora8# exit

As you can see, this is taken from this page and there is no mention that this directory should be joeuser.web since it's the oracle directory!

Note: The above mention refers to /ora8/m03 but it's the same as using m02.

Permissions 777 poses a security risk that I wouldn't be willing to take ;-).