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.
SELECT on USER_INDEXES
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.2.1 Content Platform Engine databases.
For object stores upgraded from version 4.5.1, as part of the auto-upgrade of Oracle-based Content Engine data, table columns defined by the DATE property are automatically converted to the TIMESTAMP property, even if there is an index on the DATE property. However, auto-upgrade will not be able to perform this conversion on function-based indexes, such as the descending (DESC) keyword, that involve the DATE property. Because it is not feasible to resolve this conversion failure within the auto-upgrade framework, plan to manually convert DATE columns with function-based indexes to TIMESTAMP columns by dropping these indexes, altering the property and recreating the index. Upgrade procedures direct you to complete this procedure after the auto-upgrade finishes.