Search docs.molo17.com

    Oracle XStream logo Oracle XStream agent changelog

    Release notes

    2.3.2.0

    Released: November 10, 2026

    • Source: a change of an entity’s table that arrives between two polls is kept and handed over by the next poll, in order, instead of being dropped, which moved the low watermark past it with nothing in the log;

    • Source: positions are compared as unsigned bytes and each entity is handed only the changes past the position it has read, instead of every entity receiving everything from the oldest position and a later low watermark being sent to the outbound server;

    • GSSD-1483: Target: CHAR, VARCHAR and VARCHAR2 columns are created in characters (n CHAR) in target tables, CDC tables and the bulk staging table, instead of following NLS_LENGTH_SEMANTICS (bytes by default), which failed a snapshot in a loop with ORA-12899 once 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 failing ORA-12899 on a CHAR(10 BYTE) column;

    • GSSD-1346: Target: the bulk flush matches staged keys one NULL pattern at a time (IS NULL or =), 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.0.1

    Released: October 15, 2026

    • 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;

    • 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;