1. Cache Guide
  2. Compatibility Between TimesTen and Oracle Databases
  3. Transaction Semantics

Transaction Semantics

TimesTen and Oracle Database transaction semantics differ in a few ways.

  • Oracle Database serializable transactions can fail at commit time because the transaction cannot be serialized. TimesTen uses locking to enforce serializability.

  • Oracle Database can provide both statement-level and transaction-level consistency by using a multi-version consistency model. TimesTen does not provide statement-level consistency. TimesTen provides transaction-level consistency by using serializable isolation.

  • Oracle Database users can lock tables manually through SQL. This locking feature is not supported in TimesTen.

  • Oracle Database supports savepoints while TimesTen does not.

  • In Oracle Database, a transaction can be set to be read-only or read/write. This is not supported in TimesTen.

See Transaction Management in Oracle TimesTen In-Memory Database Operations Guide.