Oracle recommendations and optional configuration

This section provides additional configuration options for your consideration.

Oracle recommends:

• Partitioning the tables under HRLCORE schema for scaling with a large volume of data.
• Hash partition tables on the PATIENT_ID column where this column exists.
• You consider hash partition on the ID column of the ASSOCIATION_HM and ASSOCIATION_OTH tables.
• You use Oracle database secure file and compression to store CLOB data and reduce the storage size without impacting the performance significantly.
• If you want to return sorted document IDs in the Find query, you must create composite index(es) on DOC_ENTRY with keys PATIENT_ID, ID, and sort attribute. The provided script does not create indexes to optimize this query type to save disk space.
• You increase the default LOB prefetch size. Since this release enables DocumentEntry XML fragments stored in CLOB columns, improving CLOB data read performance between the database and application server improves overall Registry query performance, especially where the response type is LeafClass. Oracle 11.2 JDBC driver lets you increase default LOB prefetch size from 4k. You can configure this parameter through a JVM option. For example:

  -Doracle.jdbc.defaultLobPrefetchSize=32000