Planning for Oracle database upgrades

Review upgrade requirements for Oracle databases.

Update to the appropriate database versions and patches before you upgrade FileNet® P8 components. For minimum patch requirements, see IBM® FileNet P8 system requirements.

Content Platform Engine databases must be configured with AL32UTF8 character sets. It is not required to set the national character set (NLS_NCHAR_CHARACTERSET) to a specific value; you can take the default. If you change the character set for an existing database, the workflow system or legacy workflow system locale must not change when the database character set is converted to AL32UTF8.

Any Oracle database users must have the following permission for the upgrade:
SELECT on USER_INDEXES
For users on WebSphere Application Server V8.5.5 and Oracle 12C or Oracle 18c, the version for the following authentication protocol values must be set to 11:
  • SQLNET.ALLOWED_LOGON_VERSION_SERVER=11
  • SQLNET.ALLOWED_LOGON_VERSION_CLIENT=11

Planning for Content Platform Engine (or Content Engine) Oracle database upgrades

If you have set the oracle.jdbc.V8Compatible flag to true for your Content Platform Engine (or Content Engine) database, as documented in the Enabling Oracle Data Index Use in the FileNet Content Engine technical notice (see http://www.ibm.com/support/docview.wss?uid=swg21397282), you need to set the flag to false. The flag is not supported in Oracle 11g and is not needed in version 5.5.0 Content Platform Engine databases.