Overview

This article explains the following configuration parameters for Oracle:

• The fetchSizeSupported which needs to be set to false in the jive_startup.xml.
• The special JVM property - Doracle.jdbc.maxCachedBufferSize=12 - to ensure "good performance".

Information 

This applies to Jive Interactive Intranet - Jive Core environment.

The fetchSizeSupported Tag

• This is the default Oracle row fetch size value.
• By default, when Oracle JDBC runs a query, it retrieves a result set of 10 rows at a time from the database cursor.
• Running any API calls may fetch only up to 10 contents (places, spaces, etc).
• When set to false, it does not restrict the number of rows in the result set.

This can be implemented by adding the tag in jive_startup.xml file.

Use <fetchSizeSupported>false</fetchSizeSupported> as a child element of the parent <database>...</database> tags.

The JVM property -Doracle.jdbc.maxCachedBufferSize=12 Property

• Oracle introduced this property in database drivers to address the large buffer problem.
• This property bounds the maximum size of the buffer that will be saved in the buffer cache.
• The driver uses this buffer size to retrieve query results.
• These buffers can be quite large and are cached. If some queries create particularly large buffers, this will force the driver to use this large buffer size for all queries.
• It is better to reduce the buffer size of those queries to a smaller value. Therefore, It is recommended to set this property to prevent these large buffers from being cached.
• The appropriate value depends on the heap size, number of connections open, number of statements open at once, and the fraction of the heap that can be allocated to JDBC.

Refer to the article Database Configuration and Best Practices to learn more.

Back to top