rs_non_blocking_commit

Sends an insert, delete, or update command to the data servers so that transactions that were sent through a connection configured with rs_ non_blocking_commit are saved to disk.

Examples

Example 1 – Creates an instance of an rs_non_blocking_commit_flush function string for Adaptive Server:

create function string rs_non_blocking_commit_flush
         for sqlserver_derived_class
         output language
         ‘set delayed_commit off; begin tran; update rs_lastcommit set
         origin_time = getdate() where origin = 0; commit tran; 
         set delayed_commit on’

Example 2 – Creates an instance of an rs_non_blocking_commit_flush function string for Oracle:

create function string rs_non_blocking_commit_flush
         for oracle_derived_class
         output language
         ‘alter session set commit_write = immediate; begin tran; 
         update rs_lastcommit set origin_time = getdate() where
         origin = 0; commit tran; alter session set commit_write = nowait’

Usage

rs_non_blocking_commit_flush has function-string-class scope.
rs_non_blocking_commit_flush executes at intervals equal to any number of minutes from 1 to 60 that you specify with dsi_non_blocking_commit. rs_non_blocking_commit_flush does not execute if the value of dsi_non_blocking_commit is zero.
rs_non_blocking_commit_flush maps to the corresponding function string in Adaptive Server 15.0 and later, and Oracle 10g v2 and later. For all other non-Sybase databases, rs_non_blocking_commit_flush maps to null.
Replication Server with non-blocking commit enabled, supports replication into Oracle 10g v2 or later because Oracle 10g v2 supports functionality similar to delayed commit.

Replication Server 15.2 heterogeneous datatype support (HDS) scripts have new function strings that support the non-blocking commit feature. Sybase Enterprise Connect Data Access for Oracle supports these function strings. See the Replication Server Options 15.1 Overview Guide.