What is the purpose of this configuration?

You have applications that have frequently executed queries, and produce small and static result
sets.
You configure the sqlnet.ora file in the client machine to set a nonzero value for the
OCI_RESULT_CACHE_MAX_SIZE parameter.
What is the purpose of this configuration?

You have applications that have frequently executed queries, and produce small and static result
sets.
You configure the sqlnet.ora file in the client machine to set a nonzero value for the
OCI_RESULT_CACHE_MAX_SIZE parameter.
What is the purpose of this configuration?

A.
to avoid round trips to the server by enabling caching of query results in client memory

B.
to improve performance by storing a copy of the data from the private SQL area of the PGA

C.
to enhance the query performance by creating a cache in the client memory for sorting
operations

D.
to avoid the storing of query plans and results in the server by creating a cache in the client
memory



Leave a Reply 1

Your email address will not be published. Required fields are marked *


Helcio

Helcio

Benefits of Client Result Cache

The benefits of OCI client query result cache are:

Since the result cache is on the client-side, a cache hit causes OCIStmtExecute() and OCIStmtFetch() calls to be processed locally, instead of server round trips. This can result in huge performance savings for server resources, for example, server CPU and server I/O.

The OCI client-side query result set cache is a transparent and consistent cache.

The result cache on OCI client is per-process, so multiple client sessions can simultaneously use matching cached result sets.

It minimizes the need for each OCI application to have its own custom result set cache.

It transparently manages the caching aspects of the cached result sets, that is: concurrent access by multiple threads, multiple statements, multiple sessions; invalidation, refreshing of result sets in the cache; and cache memory management.

It transparently invalidates the cached result sets on any database changes that may affect the result sets, when OCI process makes round trips to the server.

This consistent cache is automatically available to all OCI applications and drivers (such as JDBC-OCI, ODP.Net, OCCI, Pro*C/C++, Pro*COBOL, ODBC, and so on) built using OCI.

The cache uses OCI client memory that may be cheaper than server memory.

A local cache on the client will have better locality of reference for queries executed by that client.