Oracle Database Setup

If the Oracle Database is not used, then do the SQL*Server Database Setup or go back to the Installation Table of Contents.

If Oracle is not installed, that has to be done first. See the installation documentation included with Oracle.

**It's always a good idea to save the output logs when running any script -- they may come in handy should a problem occur.

Once Oracle is up and running, the following has to be done:

Create Tablespace and Schema

Create a tablespace that will be the tablespace for the Unanet tables and a temporary tablespace for the temp space. Consult with the DBA or System Administrator to determine the physical location where the datafiles will be located. Refer to the Oracle documentation for optimal locations for the datafiles, for the best performance.

After the tablespaces are created, a Unanet schema has to be created. This schema should be created as Unanet.

Also, it is necessary to grant connect and resource to the Unanet schema.

This is an example of creating a tablespace and a Unanet schema using Oracle on NT (logged in as a dba):

create tablespace temporary datafile 'c:\orant\database\temporary.dbf' size 25M default storage (pctincrease 0);
create tablespace unanet datafile 'c:\orant\database\unanet.dbf' size 100M default storage (pctincrease 0);

create user unanet identified by unanet default tablespace unanet temporary tablespace temporary;
grant connect to unanet;

You will need to work with the DBA to determine the appropriate size for your installation. As a rough guideline, we estimate you will need 12 MB of disk space per user in determining the unanet datafile size parameter. This estimate assumes a standard usage pattern and allows for the storage of 2 years worth of history per person. Your actual usage may vary, and the DBA will need to monitor space usage on a periodic basis.

Create Unanet Tables and Relationships (running the script)

To run the c_unanet.sql script, make sure you are logged into the Unanet Schema (Do not run this script in the SYSTEM Schema). The script is located in the Unanet Home Directory, under the /database/oracle directory. For best results, use SQL Plus to run the script. Login as the unanet user and run the c_unanet.sql script. As you see from the table below, the script calls a sequence of scripts which create the Unanet database objects.

Please do not run any of the individual scripts (other than the c_unanet.sql script) without first consulting the Unanet support staff. This is important since many of the scripts delete objects from the database.

c_unanet.sql	(calls the scripts below)	Creates the Unanet Tables, Foreign Keys, Check Constraints, Indexes and Views. This script actually calls the following scripts, also in the same directory:
	c01_tables.sql	Creates all the tables.
	c02_pk.sql	Creates all the primary keys.
	c03_data.sql	Loads all the static data into the tables.
	c04_fk.sql	Creates all the foreign keys.
	c05_cc.sql	Creates all the check constraints.
	c06_indexes.sql	Creates all the indexes.
	c07_views.sql	Creates all the views.

After the script has run, you will see two log files created in the same directory where you started SQL Plus. These files store the results of any script run against the database. Please do not delete these scripts -- they are very useful to the Unanet support staff in the event of a problem. You should also make sure that there were NO errors in the c_unanet.log file before you continue with the installation. The two log files are described in more detail below:

d_unanet.log	This log file contains all the output from the deletion process that runs before anything is created. If this is the first time you have created the Unanet schema, you can ignore any error or warning messages that you see in this log file.
c_unanet.log	This log file contains all the output from the creation process. It is very important that you check this log file for any warnings or errors. If it does contain any errors, contact the Unanet support staff and email them both log files.

Important Note: Whenever the c_unanet.sql script is run, it first tries to delete any Unanet objects that may already be in the database. For this reason, it is important that you never re-run this script if there is data in the database that you want to keep. If you think you might need to re-run any of the sql scripts, contact the Unanet support staff first and we'll help you decide the best course of action. Remember, always back up your database before performing any maintenance activities!!

Configure database.properties File

Open the Unanet database.properties file located in the properties directory in [C:\Unanet\properties] (where C:\ is the default) on the web server. Comment out any lines that do not refer to the Oracle JDBC driver. Follow the documentation notes in the database.properties file on setting up those parameters.

Once the database is setup and the web server connected to the Unanet Database ,it is time to test the Unanet Application.

Back to Installation Table of Contents