This page last changed on Feb 20, 2011 by sruiz.
To switch to an Oracle database, install Oracle and follow the steps below. Please note that during the migration of database servers, the FishEye instance will not be available to users or to external API clients.
 | Oracle support for FishEye and Crucible was introduced in version 2.5.0. In order to migrate to Oracle, your instance must be currently running at least version 2.5. If you are running an older version, then you will be required to first upgrade FishEye and then migrate. |
 |
Install and Create a Oracle Database |
- The JDBC drivers for Oracle are bundled with FishEye. Skip to step 2 if this meets your needs. If you want to install a specific, different version of the bundled JDBC driver, download the download the Oracle JDBC driver .jar file from the Oracle website and copy the .jar file to your FISHEYE_INST/lib directory (create the lib/ directory if it doesn't already exist). Move the existing JDBC .jar file to another location (and back it up). Restart FishEye or Crucible to have it pick up the new driver.
- Because creating a database with Oracle is a complex process, we recommend speaking to your resident DBA for creation of a new database for usage with Crucible. We highly recommend installing Oracle with the AL32UTF8 encoding otherwise you may see encoding issues in the product.
 |
Configure FishEye to use Oracle, and Migrate Data |
In order to migrate to a different database backend, you must create a backup of sql data, configure the database and finally import the data via a backup restoration process. This can be done from either the FishEye administration console, which streamlines the process, or via the command line tool which FishEye provides.
From FishEye's Administration
- Navigate to the Database page in FishEye's Administration console
- Then click 'Test Connection' to verify that Crucible or FishEye can log in to the database:
- Select Oracle from the database type
- Fill in the appropriate fields, replacing the host, port, database name, username and password as required
- Click on Test Connection to validate the values
Screenshot: Testing the Connection

If this fails, verify that you have the Oracle JDBC driver .jar file in the classpath (by placing the .jar file in FISHEYE_INST/lib). Also, ensure that the database user can log in to the database from the machine that Crucible or FishEye is running on and that all the required privileges are present.
- Click 'Save & Migrate Data' to start the migration process.
During the migration process (which will take several minutes, depending on the size of your database and network throughput), the product will be inaccessible to users and external API clients. Users will see a maintenance screen that informs them of the process. Should the migration fail for any reason, FishEye will not switch to the new database and report on the encountered problems. Because the destination database may now contain some, but not yet all data, drop all tables, indexes and constraints before attempting a new migration.
Screenshot: Migrating the Database

From the command line
- Create a backup of the sql data from the FishEye instance. Information on how to create a backup can be found at Backing Up and Restoring FishEye Data
- Run the following command from the bin directory in FISHEYE_INST
- When the import is complete, FishEye can be started and will use Oracle.
 |
Further Resources |
Troubleshooting Databases
|