Verify membership by typing groups when you login:

service0:~$ groups
dba web

If you do not see these groups, take the following action:

service0:~$ su -      
Password: ************
root:~# adduser service0 dba

If you get an error about an undefined group, then add that group manually:

root:~# groupadd dba
root:~# groupadd web

Make sure to logout as root when you are finished with this step and log back in as your regular user.

Connect to Oracle using svrmgrl and login:

service0:~$ svrmgrl

SVRMGR> connect internal
Connected.

Determine where the system tablespaces are stored:

SVRMGR>  select file_name from dba_data_files;

Example results:

/ora8/m01/app/oracle/oradata/ora8/system01.dbf
/ora8/m01/app/oracle/oradata/ora8/tools01.dbf
/ora8/m01/app/oracle/oradata/ora8/rbs01.dbf
/ora8/m01/app/oracle/oradata/ora8/temp01.dbf
/ora8/m01/app/oracle/oradata/ora8/users01.dbf
/ora8/m01/app/oracle/oradata/ora8/indx01.dbf
/ora8/m01/app/oracle/oradata/ora8/drsys01.dbf

Using the above output, you should determine where to store your tablespace. As a general rule, you'll want to store your tablespace on a mount point under the /ora8 directory that is separate from the Oracle system data files. By default, the Oracle system is on m01, so we will use m02. This enables your Oracle system and database files to be on separate disks for optimized performance. For more information on such a configuration, see Chapter 12 of Philip's book. For this example, we'll use /ora8/m02/oradata/ora8/.

Create the directory for the datafile; to do this, exit from svrmgrl and login as root for this step:

SVRMGR> exit
service0:~$ su -
Password: ************
root:~# mkdir -p /ora8/m02/oradata/ora8/
root:~# chown service0.web /ora8/m02/oradata/ora8
root:~# chmod 775 /ora8/m02/oradata/ora8
root:~# exit
service0:~$

Create a tablespace for the service. It is important that the tablespace can autoextend. This allows the tablespace's storage capacity to grow as the size of the data grows. We set the pctincrease to be a very low value so that our extents won't grow geometrically. We do not set it to 0 at the tablespace level because this would affect Oracle's ability to automatically coalesce free space in the tablespace.

service0:~$ svrmgrl

SVRMGR> connect internal;
SVRMGR> create tablespace service0 
             datafile '/ora8/m02/oradata/ora8/service001.dbf' 
             size 50M 
             autoextend on 
             next 10M
             maxsize 300M
             extent management local
             uniform size 32K;

Create a database user for this service. Give the user access to the tablespace and rights to connect. We'll use service0password as our password.

Write down what you specify as service_name (i.e. service0) and database_password (i.e. service0password). You will need this information for configuring exports and AOLserver.

SVRMGR> create user service0 identified by service0password default tablespace service0
temporary tablespace temp quota unlimited on service0;
SVRMGR> grant connect, resource, ctxapp, javasyspriv, query rewrite to service0;
SVRMGR> revoke unlimited tablespace from service0;
SVRMGR> alter user service0 quota unlimited on service0;
SVRMGR> exit;

Your table space is now ready. In case you are trying to delete a previous OpenACS installation, consult these commands in Section , “Deleting a tablespace” below.

Make sure that you can login to Oracle using your service_name account:

service0:~$ sqlplus service0/service0password
SQL> select sysdate from dual;

SYSDATE
----------
2001-12-20

SQL> exit

You should see today's date in a format 'YYYY-MM-DD.' If you can't login, try redoing step 1 again. If the date is in the wrong format, make sure you followed the steps outlined in Section , “Troubleshooting Oracle Dates”