Oracle database planning

Determine whether Oracle database components will be dedicated to individual Content Cortex components or shared and review other Oracle 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.
When you make the decision about whether to share a database for multiple components, consider the following factors:
  • Database backup/recovery requirements should allow for the data that resides in a single database to be backed up and recovered together.
  • Database security should allow for collocation of data.
  • Sharing of a database might allow for more efficient usage of database resources like database connections.
  • If you decide to share a database, you might want to create distinct data sources to allow for more efficient usage.

Make sure the machine hosting the database satisfies all preinstallation requirements specified in the Oracle installation documentation.

Refer to IBM FileNet® P8 system requirements for required operating system and database patch sets, and service packs. The Oracle patches are available at the Oracle website. The Oracle 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.

Plan to use locally managed table spaces. For performance reasons, IBM recommends that you create locally managed, rather than dictionary managed, table spaces. (The table spaces you create via Oracle Database assistant (dbca) are locally managed by default.)

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