rs_non_blocking_commit

Requests data servers to immediately send a positive response to a COMMIT statement without waiting for transactions to be written to disk.

Usage

  • rs_non_blocking_commit has function-string-class scope.

  • rs_non_blocking_commit executes every time DSI connects to the replicate data server when the dsi_non_blocking_commit value is from 1 to 60. If the value of dsi_non_blocking_commit is zero, rs_non_blocking_commit does not execute.

  • rs_non_blocking_commit function maps to the “set delayed_commit on” function string in Adaptive Server 15.0 and later, and to the corresponding “alter session set commit_write = nowait;” function string in Oracle 10g v2 and later. For all other non-Sybase databases, rs_non_blocking_commit 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.

Related reference
rs_non_blocking_commit_flush