Kronodoc Database Setup for Oracle 10g or 11g

Database Creation

The Kronodoc database must be created from the database template provided by Kronodoc (in the kronodbsetup tar package). To start the setup of a Kronodoc database, please perform the following actions:

• Uncompress and place the krono_10g_kd40_v*.dbt or krono_11g_kd40_v*.dbt database template into $ORACLE_HOME/assistants/dbca/templates depending on your Oracle version.
• Start the Oracle Database Configuration Assistant (dbca) and start creation of a new database based on the Kronodoc template appropriate for your Oracle version (“krono 1*g kd 40 v*”)

The following settings are mandatory for the newly created database. Possible changes and modifications to these settings must be confirmed by Kronodoc:

• Configure the Database with Enterprise Manager ENABLED (to ease database management)
• File System Storage
• Disable ARCHIVELOG unless you are familiar with Oracle database backups and have procedures for cleaning up archive files in place
• Database Components:

• Oracle Text
• (Enterprise Manager Repository)

• Allocate as much memory to Oracle as possible during database creation based on the amount of physical memory available and services running on the database server. The SGA size (SGA_MAX_SIZE) should be at least 10% of the size of the database, including indexes.
• The database character set to use for Kronodoc 5.0 databases is AL32UTF8
• Multiplex redo log and control files according to file system fault-tolerance. Redo log files are not multiplexed by default.

For security reasons the Oracle listener should be configured to bind to localhost (127.0.0.1) interface when Kronodoc and Oracle are running on the same server. When Kronodoc and Oracle are on different servers it is recommended to block traffic to the Oracle server from sources other than the Kronodoc server.

Refer to Appendix 3 for detailed information about Oracle database setup.

Refer to Oracle documentation for further information on installing Oracle.

It is recommended that a plustrace role is created to grant access to Oracle Dynamic Performance Tables. This helps in tuning the database and recognizing possible bottlenecks in query performance. The role is created by issuing the following command while the database is running:

sqlplus / as sysdba < $ORACLE_HOME/sqlplus/admin/plustrce.sql
Setting up database schema for Kronodoc
Once the database has been created Kronodoc user account needs to be created with specific access rights. The provided kronouser.sql creates the user ‘kronodoc’ with the password ‘kronodoc’, these may be changed by editing the kronouser.sql script.
sqlplus / as sysdba < path_to_kronodbsetup/kronorole.sql sqlplus / as sysdba < path_to_kronodbsetup/kronouser.sql 

Refer to Appendix 3 for detailed information about database user setup.

Post-installation tuning
Certain database parameters such as memory allocation parameters should be tuned after the system has been running in production for 1 to 2 weeks. You can use the Oracle10g Automatic Database Diagnostic Monitor (ADDM) to get advice on tuning these parameters. Use of these tools may require additional licenses or Enterprise Edition.