Home

Getting Started

Utilities

Indexing

Omnidex

Development

Tutorials

Quick Links

 

OmniAccess API

Functions

Syntax

Options

Example

 

OmniAccess API

Programming Basics

Managing Data

Functions

 

OACOMMIT

oacommit marks the end of an indexing transaction. It commits all updates to the indexes that occurred since the last call to oabegin.

When you call oacommit, it commits all indexing transactions involving oainsertindex, oaupdateindex or oadeleteindex since the most recent call to oabegin. This includes index transactions that were posted using the IMMEDIATE option, or the ROLLFORWARD option in oasavepoint.

Once committed, index updates cannot be rolled back. Therefore, the update application should verify that the native update was successfully committed before calling oacommit to post the corresponding updates to Omnidex index files.

Transaction management applies to the Omnidex indexes only. If transaction management is required for the database, use the DBMS transaction management system.

See Also: ODXAIM

 

Syntax

oacommit (instance, options, status)

instance -- Instance identifies a unique connection to a catalog previously established by oaconnect. This is a 32-bit signed integer passed by value

options -- Options is currently reserved and must contain a semicolon or a null character passed by reference.

status -- Indicates the success or failure of the oacommit routine. A zero status.error means a successful call to oacommit. The status structure is passed by reference and contains fourteen 32-bit signed integers, followed by a 36-character buffer.

 

Options

 

 

Example

 

Top