10.17.1 Set Up Oracle for OpenClinica Versions Pre-3.1.2
Follow these instructions to configure an Oracle 10g database to run with OpenClinica versions 3.1 and 3.1.1.
- Open a shell/command prompt window and change the current directory to the location of the OpenClinica database files.
- Ensure there is at least 512MB of disk space available at that location.
- Start sqlplus:
- Run
sqlplus sys as sysdba - When prompted for the password, enter the sys password.
- Run
- At the SQL prompt, run the script to set up the database tablespace and database user “clinica”:
- Run
@oracle_setup_db.sql - When the following prompts are display (shown below in bold), provide these values (shown below in code font):
- Specify Tablespace name for Clinica Data:
openclinica - Specify Tablespace type for Clinica Data (S/M/L):
L
(This specifies a tablespace size of Large, 512MB.) - DataFile Name (with exact path):
/usr/lib/oracle/xe/oradata/XE/OPENCLINICA01.DBF
(This is the default oradata directory for Linux; specify the full path to the oradata directory on your system.) - Specify the wanted username for the OpenClinica oracle account:
clinica
- Specify Tablespace name for Clinica Data:
- Check spool_oracle_setup_db.txt for any errors.
- Run
- Change the default password “clinica” to a secure password:
- As the sysdba user, connect to your instance via sqlplus by running
sqlplus sys as sysdba - Run the following command, where PASSWORD is the new, secure password you are sepcifying for the clinica database user:
alter user clinica identified by PASSWORD;
- As the sysdba user, connect to your instance via sqlplus by running
- Start Tomcat, which will build the OpenClinica database within the tablespace.
- After the tablespace is built, create indexes to help performance by running the following:
- Connect to sqlplus as the clinica user by running:
sqlplus clinica/clinica - Run this script:
@performance.sql
- Connect to sqlplus as the clinica user by running:
10.17.2 Set Up Oracle for OpenClinica 3.1.2 or Above
Follow these instructions to configure an Oracle 10g database to run with OpenClinica versions 3.1.2 or above.
- Open a shell/command prompt window and change the current directory to the location of the OpenClinica database files.
- Ensure there is at least 512MB of disk space available at that location.
- Start sqlplus:
- Run
sqlplus sys as sysdba - When prompted for the password, enter the sys password.
- Run
- At the SQL prompt, run the script to create the tablespace:
- Run
@create_ts.sql - When the following prompts display (shown below in bold), provide these values (shown below in code font):
- Specify Tablespace name for Clinica Data:
openclinica - Specify Tablespace type for Clinica Data (S/M/L):
L
(This specifies a tablespace size of Large, 512MB.) - DataFile Name (with exact path):
/usr/lib/oracle/xe/oradata/XE/OPENCLINICA01.DBF
(This is the default oradata directory for Linux; specify the full path to the oradata directory on your system.)
- Specify Tablespace name for Clinica Data:
- Run
- At the SQL prompt, run the script to create the database user “clinica”:
- Run
@oracle_setup_db.sql - When the following prompts display (shown below in bold), provide these values (shown below in code font):
- Specify the Tablespace name you provided when you executed the create_ts.sql script:
openclinica - Specify the wanted username for the OpenClinica oracle account:
clinica
- Specify the Tablespace name you provided when you executed the create_ts.sql script:
- Check spool_oracle_setup_db.txt for any errors.
- Run
- Change the default password “clinica” to a secure password:
- As the sysdba user, connect to your instance via sqlplus by running
sqlplus sys as sysdba - Run the following command, where PASSWORD is the new, secure password you are sepcifying for the clinica database user:
alter user clinica identified by PASSWORD;
- As the sysdba user, connect to your instance via sqlplus by running
- Start Tomcat, which will build the OpenClinica database within the tablespace.
- After the tablespace is built, create indexes to help performance by running the following:
- Connect to sqlplus as the clinica user by running
sqlplus clinica/clinica - Run this script:
@performance.sql
- Connect to sqlplus as the clinica user by running