Plan and prepare your Oracle servers for Case Analyzer installation.
Review the general Oracle database planning information and verify that the database is installed and configured. For more information about database planning, see Oracle database planning.
Also, determine whether to use a shared database instance or a separate database instance for Case Analyzer store data. The system can place the Case Analyzer store data in the database instance that is used for the object store or in a separate database instance. Determine whether to use a shared database instance and table spaces or a separate database instance or table spaces for Case Analyzer store data. Consider the capacity of your database server, the case size, and the case load when determining where to store Case Analyzer data.
When Case Analyzer store data is stored in the database instance that is used for the object store, you do not need to define an additional JDBC data source. You can also back up the Case Analyzer store and the object store simultaneously. However, including the Case Analyzer store increases the load on the database server, and this increased load can have a negative impact on performance. Defining a separate database on the same remote database server as the object store can also degrade performance.
Alternatively, the system can store Case Analyzer data in a separate database instance. For example, you might want to use a separate, remote database server if I/O throughput is problematic. If the system stores extended Case Analyzer data on a different remote database server, you can get additional disk arms, disk space, CPU, and memory to support it.