This HTML5 document contains 4 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Namespace Prefixes

PrefixIRI
wdrshttp://www.w3.org/2007/05/powder-s#
schemahttp://schema.org/
n5https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/
n4https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
n2http://data.openlinksw.com/oplweb/faq/UDA/WhatDoesOCIPrefetchMemoryDoAnswer#
xsdhhttp://www.w3.org/2001/XMLSchema#

Statements

Subject Item
n2:this
wdrs:describedby
n4:uda-faq.ttl n5:uda-faq.ttl
rdf:type
schema:Answer
schema:answerExplanation
OCIPrefetchMemory and OCIPrefetchRows control parameters relating to the Oracle OCI's prefetching facility. However, use of this facility has been disabled in the OpenLink agent and Lite driver because of problems experienced with Oracle 8.x and indicator variables. To minimize server round trips and maximize performance, the OCI can prefetch result set rows when executing a query. This prefetching operates independently of OpenLink's prefetching facility. The OCI prefetching can be customized by setting two attributes, OCI_ATTR_PREFETCH_ROWS and OCI_ATTR_PREFETCH_MEMORY. The OCIPrefetchMemory and OCIPrefetchRows settings in the OpenLink setup dialogs map directly to these OCI attributes. OCIPrefetchMemory sets the memory allocated for rows to be prefetched. The application then fetches as many rows as will fit into that much memory. OCIPrefetchRows sets the number of rows to be prefetched. When both of these attributes are set, the OCI prefetches rows up to the OCIPrefetchRows limit, or until the OCIPrefetchMemory limit is reached, if this is lower.