Documentation Center

Database layer changes

Changes and additions impact Microsoft SQL Server and Oracle database systems performance, setup or process.

Empty database

This applies to both Microsoft SQL Server and Oracle.

A ready-to-use database is available in order to facilitate fast setup. This database already contains the basic structure helping an immediate application, as well as all minimal settings.

Specifically:
  • The database is upgraded toContent Manager 14.0.1.
  • The latest out-of-the-box configuration files (e.g. Admin.XMLStatusConfiguration.xml) are submitted.
  • All DITA 1.3 editor templates are submitted and released in English, German, Dutch, Japanese and Chinese.
Even if the database is up-to-date with the Content Manager version, you still need to run DBUpgradeTool (DBUT) to ensure that a database job is created, the latest database upgrade scripts are executed and all statistics for the indexes are generated.

Oracle

We are now supporting Oracle Database 19c (19.3.0.0) .

The consequences are as follows:
  • Oracle Data Access Client (ODAC) is raised from 12.2.0.1.0 to 19.3.0.0.0.
  • We also moved the .NET components to Oracle Managed Data Access which is now part of the delivered product and does not require extra installation. This means that only the OLEDB components of Oracle Data Access Client (ODAC) must be installed. However this also means that we need an extra system environment variable, TNS_ADMIN, to allow the .NET components to find tnsnames.ora. More details can be found in the Oracle Data Access Components chapter of our Content Manager installation documentation.
The setup needs to be adapted when upgrading our database from a previous Oracle setup to Oracle Database 19c (19.3.0.0) . We expect all Oracle Database 19c (19.3.0.0) environment to run with the following characteristics:
  • Apply new database template files, that we deliver.
  • Dynamic sampling is turned off. Dynamic sampling is a functionality introduced in Oracle Database 12c that gathers statistics on the fly during query execution. When switched on, it had a neutral to adverse effect on the performance during our testing. Therefore we decided to turn it off by default, and we apply it to Oracle Database 19c (19.3.0.0) as well: Oracle's optimizer_dynamic_sampling is set to 0 by default.