ORACLE CALL INTERFACE
Virtual Machine
|
ORACLE CALL INTERFACE |
Virtual Machine |
|
The Oracle Call Interface (OCI) defines the APIs that PROIV can use to add, retrieve and manipulate information stored in the Oracle database. PROIV v8 accesses Oracle database using Oracle Call Interface routines. The overall performance is improved with the use of the OCI8 routines in PROIV v8 by replacing the obsolescent OCI routines.
PROIV provides "OraProcLogon" routine for logging onto an Oracle database which you can replace with your routine to customize the logon procedure based on your business requirement.
In PROIV, the "ORA_CACHE" global logic call must be executed prior to any file access on the file that needs to be cached. You must add the proiv file name associated with tables to the cached-files list by calling the global logic ORA_CACHE<filename>.
To use the Oracle result set caching feature, you must configure the "OCI8_CACHE_OPT" environment variable
|
|
Note: PROIV v8 operates with Oracle 9.2 and above. |
To enable cache for OCI caching model:
Open the PROIV Control Panel and click Environment.
Set OCI8_CACHE_OPT environment variable to Y or R.
|
|
Note: The default value is N where caching does not takes place. Y indicates the caching is enabled and R indicates caching is enabled where select statement uses ROWNUM. |
If an Update or Report cycle is defined as One Time Cycle, then the OCI interface will cache the primary file’s row returned. Concurrently, this is true for all secondary file reads, whether the cycle is called as One Time or Many Time cycle, since all secondary file reads are in effect as ‘One Time’. It records when a full key read is executed. Caching is performed for the files in Look mode (L), transparent SQL, and not for any type of full-function SQL .
To use the Oracle caching feature, the database and tables which require their result set to be cached, must be configured to enable result set caching by the oracle database administrator.
Topic ID: 700055
