Preparing Oracle Database for Installation
This page describes how to use codeBeamer 8.0 or higher with an Oracle 12c database. To use this document you must be familiar with the Oracle database and with the database administration.
For the installation/migration you will need Oracle DBA permissions. IMPORTANT: Backup your data! Before doing anything, backup your existing database. Also ensure that nobody uses the database during migration, as this may result loss of data.
Prepare new Oracle Schema
It must be ensured that codeBeamer is not running.
Edit the configuration file: <cb-installation-dir>/tomcat/webapps/cb/WEB-INF/classes/general.xml
<!-- Comment out to use Oracle
<database
JDBC_Driver="oracle.jdbc.driver.OracleDriver"
JDBC_ConnectionURL="jdbc:oracle:thin:@//127.0.0.1:1521/ORCL"
JDBC_Username="cbroot"
JDBC_Password="cbpassword"
>
<props>
<prop key="SetBigStringTryClob" >true</prop>
</props>
</database>
-->
Remove the markers '<!-- Comment out to use Oracle' and '-->' above and below to uncomment this section.
Change the ORACLE host address (in the example: 127.0.0.1), port (in the example above: 1521) and SID (in the example above: ORCL) in the JDBC_ConnectionURL="jdbc:oracle:thin:@//URL:port/SID" parameter to address your ORACLE database instance.
Also set the parameters JDBC_Username and JDBC_Password to the schema/user name and password you assigned to the codeBeamer database schema.
Enclose all other <database ...>...</database> sections with comment markers, if not already present, or delete them.
Start codeBeamer.
The database tables will be automatically created upon the first start of codeBeamer, so this first startup will take significantly longer than subsequent startups.
Upgrading an existing codeBeamer ORACLE database to a newer codeBeamer version
You must only configure the new codeBeamer installation to access the existing ORACLE database (see above). All necessary database upgrades are automatically executed when you start the new codeBeamer instance for the first time.
To migrate a codeBeamer schema from one ORACLE instance to another, export the schema from the old instance and import at the new instance. Then (re-)configure codeBeamer to access the new instance.
IMPORTANT: Backup your data! Before doing anything, backup your existing database. Also ensure that nobody uses the database during migration, as this may result in loss of data.
If you're upgrading an existing database, make sure the old codeBeamer installation is shut down.
After the upgrade, you cannot easily go back to the old codeBeamer version, because that will most probably not run with the upgraded database. The only safe way to revert the upgrade is to restore the old database from a backup.