OneDB v2.8.1

Release Date: June 2026
Release Type: Patch Release
Branch: 2.8.1

New Features

Listener Database Scope

OneDB now supports listener-level database scope management.

A single listener can be configured to allow access only to selected databases or schemas. Queries targeting databases outside the configured scope are blocked before reaching the backend database.

This enhancement provides stronger database segmentation and improves security when multiple databases share the same backend server.

Enhancements

Oracle Listener Result-Set Masking

Oracle listener masking has been enhanced to improve protection accuracy across a wider range of query patterns and client tools.

Improvements include:

  • Better support for Oracle SQL Developer Data-tab queries.
  • Improved handling of SELECT *, explicit column selection, aliases, qualified table names, and unqualified table names.
  • Improved protection for multiple protected columns within the same result set.
  • Improved handling of large Oracle result sets and multi-packet responses.
  • More accurate policy-to-column mapping to prevent unintended masking of adjacent fields.
  • Improved response metadata handling for reused Oracle sessions.
  • Enhanced Oracle masking diagnostics without exposing sensitive values in logs.

Cluster Runtime Reconciliation

Cluster runtime synchronization has been improved to keep listener state, cache data, and license usage aligned across all nodes.

Enhancements include:

  • Automatic listener runtime reconciliation after replicated configuration changes.
  • Automatic cache refresh after cluster membership changes.
  • Improved listener diagnostics and runtime mismatch detection.
  • Improved cluster configuration synchronization between nodes.

Cluster Membership Recovery

Cluster nodes now recover more gracefully after temporary outages or interrupted synchronization events.

Enhancements include:

  • Automatic recovery of eligible nodes that become temporarily unavailable.
  • Improved startup reconciliation and heartbeat validation.
  • Improved cluster diagnostics and recovery visibility through ODB-DIAG.

License Capacity Reporting

Cluster and High Availability license reporting has been improved.

Enhancements include:

  • More accurate cluster node capacity calculations.
  • Improved dashboard visibility for licensed and active node counts.
  • Enhanced ODB-DIAG reporting for cluster license utilization.

Session Context Handling

Session tracking has been improved for database listeners.

Enhancements include:

  • Improved database session awareness for Microsoft SQL Server listeners.
  • Better handling of database context changes using USE <database>.
  • More accurate policy resolution for unqualified SQL statements.
  • Improved isolation between concurrent client sessions sharing the same listener.

Bug Fixes

Listener Scope Replication

Resolved an issue where listener database scope information was not fully synchronized across cluster nodes.

Fixes include:

  • Improved replication of listener database scope configuration.
  • Improved listener deletion handling across clustered environments.
  • Improved synchronization of listener runtime state after replicated changes.

Backup and Restore

Resolved an issue where listener database scope configuration could be lost during backup and restore operations.

Fixes include:

  • Listener database scope data is now included in backup exports.
  • Listener database scope data is now restored automatically.
  • Improved restore dependency handling for listener-related configuration.

Oracle Masking Stability

Resolved several Oracle listener masking issues that could cause inconsistent masking behavior under specific query patterns and response packet layouts.

MSSQL Session Database Resolution

Resolved an issue where unqualified SQL statements could be evaluated against the listener’s default database instead of the active session database after a USE <database> command.

Security Updates

Listener Database Boundary Enforcement

OneDB now enforces configured listener database scope boundaries more consistently.

Queries attempting to access databases outside the listener’s configured scope are blocked before reaching the backend database.

This helps prevent unintended cross-database access when multiple databases are hosted on the same database server.

Known Notes

  • Existing installations upgrading to v2.8.1 automatically preserve listener database scope configuration through schema upgrade procedures.
  • No manual migration steps are required for standard upgrades from v2.8.0.
  • Customers using clustered deployments should ensure all nodes are upgraded to the same version before resuming production replication traffic.