Oracle triggers agent changelog
Release notes
2.2.11.9
Released: September 29, 2026
-
GSSD-1374: Added support for "Enable TLS" and the trust store and key store of the connection, so reaching Oracle over TLS no longer requires a wallet;
2.2.11.8
Released: September 28, 2026
-
Arena batches are handed over in the order they were written instead of being re-sorted by transaction id, which on Oracle LogMiner inverted two changes sharing an SCN and wrote the older value to the target;
2.2.11.6
Released: September 24, 2026
-
Booleans and maps keep their type through the arena cache, instead of reaching the target as "true"/"false" and as a non-JSON string;
-
The change readers are stopped when their agent is unassigned or closed, and the MySql and MariaDB binlog reconnect loop is cancelled on stop;
2.2.11.4
Released: September 21, 2026
-
Added the source lag probe, reporting the unread change backlog and how far behind the last read transaction is;
-
GSSD-1357: CDC table reconciliation no longer drops and re-adds columns whose declared type never changed, which wiped them to NULL and raised a resync notification on every setup run;
-
GSSD-1357: A failing CDC table update no longer leaves a column dropped and unreplaced, breaking every read until a later setup run succeeds;
-
GSSD-1357: A column type that could not be rendered is now logged with its cause and with which side failed;
-
A failing CDC iteration now backs off like a successful one, instead of busy-looping against the source;
-
GSSD-1357: The two unchecked arena length fields are now bounded, so a damaged arena is reported as a corrupted record instead of surfacing as a NumberFormatException or advancing the recovery scan into garbage;
-
GSSD-1357: An arena is no longer mapped at a size the filesystem refused to give it, which on a full disk wrote into a sparse region with no blocks behind it;
2.2.11.2
Released: September 14, 2026
-
Replaced the Chronicle Queue source cache with ArenaCache, the local cache first proven on Oracle LogMiner. See Source agent caching layer;
2.2.10.13
Released: August 21, 2026
-
Target character columns: a value longer than its target column is now refused instead of being stored truncated with the transaction reported as written. Affects the IBM i series, Informix, MS SQL Server and Oracle targets, on the direct and the bulk write path alike (GSSD-1292, GSSD-1267);
-
Oracle target: a source value wider than its target column now fails the write even when the excess is only the padding of a fixed-length source; apply a TrimString field function on the target column to shorten a value on purpose;
-
MS SQL Server and Oracle targets: a failed insert batch is retried as an upsert only when the target already holds the row, so a rejection from the server is no longer turned into a truncation;
2.2.9.10
Released: July 17, 2026
-
GSSD-1160: Fixed escape single quotes in Oracle staging table column names;
2.2.9.2
Released: July 2, 2026
-
Fixed wrong description for source change retention causing ambiguity and loss of data when an entity is paused;
2.2.8.10
Released: June 22, 2026
-
Added support to primary keys value update in Trigger, generating delete + insert operations;
-
Fixed cdc table alignment to entity configuration;
-
Added support to floating point numbers;
2.2.8.9
Released: June 18, 2026
-
GSSD-944: Removed manual PK constraint names on Oracle CDC tables to avoid ORA-02264 and add query gen unit tests;
2.2.8.8
Released: June 16, 2026
-
GSSD-944: Fixed cdc table structure with not null columns and not aligned to entity selected columns;
2.2.7.6
Released: June 3, 2026
-
Added logic to recreate staging table for bulk operations to keep it aligned with entity schema;
2.2.7.5
Released: June 1, 2026
-
GSSD-990: Added support for trimming trailing spaces for text columns;
2.2.6.0
Released: April 30, 2026
-
Improved support for enhaced columns discovery (precision, lenght, scale);
-
The agent now supports local caching of transactions to improve performance and lower the footprint on the source database;
2.2.5.6
Released: April 30, 2026
-
Fixed an issue with the enablement/disabling of recursion protection;
2.2.5.4
Released: April 24, 2026
-
GSSD-871: Fixed an issue with last transaction retrieval on high concurrency scenarios;
2.2.5.3
Released: April 23, 2026
-
Fixed possible duplicate key error using bulk operations for target agent.
-
Added support for cdc tables daily partitioning (Gluesync will migrate the existing table only on Oracle database with version >= 12.2).
2.2.5.0
Released: April 15, 2026
-
Snapshot performance enhancements;
-
New watermark index now allows for faster lookups on large CDC datasets;
-
Enhanced audit data retrieval queries;
2.2.4.0
Released: April 1, 2026
-
GSSD-686: Fixed historical timezone offsets (e.g., Uruguay UTC-3:30) causing unwanted date/time shifts behaviors;
2.2.1.1
Released: March 18, 2026
-
An update to the way Java.Long values are handled in newer JVM versions caused a recreation of triggers when upgrading to 2.2.0.8. This can be identified by looking at the triggers' name which has 00000000 (8 zero digits) at the very beginning of its name;
Additional created triggers can be removed by issuing the following SQL command:
BEGIN
FOR r IN (
SELECT owner, trigger_name
FROM all_triggers
WHERE owner = 'USR_GLUESSYNC' -- Replace with your schema name (name of the user used in Gluesync)
AND trigger_name LIKE '%00000000%'
) LOOP
EXECUTE IMMEDIATE 'DROP TRIGGER ' || r.owner || '.' || r.trigger_name;
END LOOP;
END;
/