Oracle RAC with SSL database planning

Determine whether Oracle RAC database components will be dedicated to individual Content Cortex components or shared and review other Oracle RAC database requirements.

In a shared configuration, multiple Content Cortex components can store their data in a single database. Most components allow for data to be collocated. However, the best practice is to keep some in dedicated table spaces:
  • The global configuration database: it is recommended not to share this table space.
  • Object stores and their workflow system data although those part of a single application family can be collocated given the factors listed below. If you configure object stores in separate databases, you have more flexibility and control with security access, backup scheduling and execution, updates, and scheduled outages.
  • IBM® Content Navigator configuration data: Using the same table space for the IBM Content Navigator configuration data and the global configuration database (GCD) is not recommended.
Consider the following factors when deciding whether to share a database for multiple components:
  • Ensure that backup and recovery requirements align for all data in the shared database.
  • Verify that database security policies permit data collocation.
  • Sharing a database can improve resource efficiency, particularly for database connections.
  • Create distinct data sources within a shared database to optimize resource usage.

Verify that the database host machine meets all preinstallation requirements specified in the Oracle RAC installation documentation.

Refer to IBM FileNet® P8 system requirements for required operating system and database patch sets, and service packs. The Oracle RAC patches are available at the Oracle website. The Oracle RAC patch installation procedure might be less complicated if you do it before you create any databases.

Content Platform Engine supports the Oracle Advanced Security functionality of secure data transfer across network protocol boundaries.

Use locally managed tablespaces for optimal performance. IBM recommends locally managed tablespaces over dictionary managed tablespaces. Oracle Database Assistant (dbca) creates locally managed tablespaces by default.

There are no requirements to install Oracle RAC client software on the Content Platform Engine if the database is remote.