Oracle triggers agent changelog
Release notes
2.3.2.1
Released: November 11, 2026
-
A region of the cache whose flush to the disk fails stays dirty and is flushed again, instead of being forgotten after that one failed attempt;
2.3.2.0
Released: November 10, 2026
-
GSSD-1330: the CDC tables of stopped entities are purged every hour down to the source change retention (hours,
0disables it), instead of growing while the triggers keep writing and no entity reads them; the purge logs the dropped changes atWARNand stops as soon as an entity of the table starts; -
GSSD-1483: Target:
CHAR,VARCHARandVARCHAR2columns are created in characters (n CHAR) in target tables, CDC tables and the bulk staging table, instead of followingNLS_LENGTH_SEMANTICS(bytes by default), which failed a snapshot in a loop withORA-12899once a line held accented letters; existing CDC tables are left alone; -
GSSD-1483: Target: the blank padding of a key no longer reaches the values written, instead of three accented letters padded to
CHAR(10 CHAR)making 13 bytes and failingORA-12899on aCHAR(10 BYTE)column; -
GSSD-1346: Target: the bulk flush matches staged keys one NULL pattern at a time (
IS NULLor=), so a flush of 5,000 staged keys on a 970K-row table deletes in 0.04 to 0.11 s instead of 136 s;
2.3.1.4
Released: November 2, 2026
-
PARALLEL is written as a real optimizer hint where it belongs and dropped where it does not, instead of a plain comment that always ran serially while the text suggested otherwise;
-
The ordered resumable snapshot carries INDEX_ASC on the key columns, so a table whose statistics were gathered while it was empty is walked through the key index instead of being sorted whole on TEMP, which took 29 minutes on a 10M-row table;
2.3.1.2
Released: October 28, 2026
-
Snapshot: the ordered resumable snapshot is read without the
PARALLELhint, so Oracle walks the key index instead of sorting the whole table on TEMP and delaying the first row by tens of minutes;
2.3.1.1
Released: October 27, 2026
-
Entities on the same source table share its reader, trigger, CDC table and sequence safely: stopping one no longer stops the reading for the others, and deleting one or switching it to snapshot-only no longer drops the objects the others capture through;
-
The CDC table and the trigger carry the columns of every CDC entity reading the table. Adding a narrower entity no longer stalls every entity of the table on
ORA-00904, and a wider one gets its extra columns. The reader polls at the shortest polling interval and the largest fetch size of those entities; -
CDC: the local cache is drained up to its head in one poll instead of one message per poll, so a backlog reaches the target faster;
-
Metrics: a page’s read time no longer includes the wait for the target to consume the previous page;
-
Oracle triggers (legacy): GSSD-1330: the CDC tables of stopped entities are purged too, instead of growing while the entity is stopped and being emptied in one unbatched delete afterwards. A CDC table that cannot be purged no longer leaves the tables after it unpurged until the next pass;
-
Target: an object field from a NoSQL source is written as its JSON text instead of
{name=Ada, age=36}, and an array that holds a map or a nested array is written as a JSON array instead of[Ljava.lang.Object;@…;
2.3.0.1
Released: October 15, 2026
-
Oracle triggers (legacy): the agent reports its own tag;
-
Bulk operations: an insert and a delete, or two updates, of a row keyed by binary or array values in one batch are merged instead of leaving the row on the target or failing with a duplicate key;
-
The agent hands its pooled database back when its pipeline is deleted or detached and when its initialization fails. Before, the next pipeline writing to the same database could fail in a loop with
NoClassDefFoundError;
2.3.0
Released: October 13, 2026
-
Agent compatibility upgrade to Gluesync 2.3;
-
CDC retention purge also covers stopped entities (GSSD-1330);
-
The source cache saves the corrected read position after a recovery scan, so a restart no longer starts reading mid-record or discards records written after a torn record;
-
The type matrix no longer lists INT, LONG and SHORT, which Oracle does not have, as target types;
-
Columns are discovered in their table order instead of the order the query plan happened to produce;
-
Discovery returns schemas and tables in alphabetical order, so Query Studio pages no longer skip or repeat objects;