Bug report: Oracle TIMESTAMP WITH TIME ZONE / TIMESTAMP WITH LOCAL TIME ZONE columns with NULL values cause IndexOutOfBoundsException during replication

Esa U. — Thu, 23 Apr 2026 14:46:07 -0000

I cannot test the bug in 3.17.1 community edition because Oracle DB is not supported anymore and install fails. So I made a new test environment for 3.16.12 and reproduced the bug. Support snapshots are attached.

Bug report: Oracle TIMESTAMP WITH TIME ZONE / TIMESTAMP WITH LOCAL TIME ZONE columns with NULL values cause IndexOutOfBoundsException during replication

Michael Drouard — Wed, 22 Apr 2026 17:13:36 -0000

Would you be able to upload a Symmetric Support Snapshot from the 3.17.1 install?
Details to take a support snapshot can be found here: https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline

Bug report: Oracle TIMESTAMP WITH TIME ZONE / TIMESTAMP WITH LOCAL TIME ZONE columns with NULL values cause IndexOutOfBoundsException during replication

Esa Unas — Tue, 21 Apr 2026 22:05:02 -0000

Summary

Replication fails with IndexOutOfBoundsException when an Oracle TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE column contains a NULL value. Regular TIMESTAMP columns with NULL values replicate correctly.

SymmetricDS Version

3.14.19 (community edition)
3.15.22 (community edition)
3.16.12 (community edition)
3.17.1 (community edition)

Database

Oracle 19c (source and target)

Steps to Reproduce

Create a test table on the source database:

CREATE TABLE ORA_TIMESTAMP_TEST
(
    ID                   NUMBER(12) NOT NULL,
    TIMESTAMP3           TIMESTAMP(3),
    TIMESTAMP6           TIMESTAMP(6),
    TIMESTAMP3_WITH_TZ   TIMESTAMP(3) WITH TIME ZONE,
    TIMESTAMP6_WITH_TZ   TIMESTAMP(6) WITH TIME ZONE,
    TIMESTAMP3_WITH_LTZ  TIMESTAMP(3) WITH LOCAL TIME ZONE,
    TIMESTAMP6_WITH_LTZ  TIMESTAMP(6) WITH LOCAL TIME ZONE
);

ALTER TABLE ORA_TIMESTAMP_TEST
    ADD CONSTRAINT ORA_TIMESTAMP_TEST_PK PRIMARY KEY (ID);

Configure the table for replication.
Insert rows with various NULL combinations:

-- Row 1: No NULLs → replicates OK
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (1, current_timestamp, current_timestamp, current_timestamp,
     current_timestamp, current_timestamp, current_timestamp);

-- Row 2: TIMESTAMP(3) NULL → replicates OK
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (2, NULL, current_timestamp, current_timestamp,
     current_timestamp, current_timestamp, current_timestamp);

-- Row 3: TIMESTAMP(6) NULL → replicates OK
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (3, current_timestamp, NULL, current_timestamp,
     current_timestamp, current_timestamp, current_timestamp);

-- Row 4: TIMESTAMP WITH TIME ZONE NULL → FAILS
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (4, current_timestamp, current_timestamp, NULL,
     current_timestamp, current_timestamp, current_timestamp);

-- Row 5: TIMESTAMP WITH TIME ZONE NULL → FAILS
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (5, current_timestamp, current_timestamp, current_timestamp,
     NULL, current_timestamp, current_timestamp);

-- Row 6: TIMESTAMP WITH LOCAL TIME ZONE NULL → FAILS
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (6, current_timestamp, current_timestamp, current_timestamp,
     current_timestamp, NULL, current_timestamp);

-- Row 7: TIMESTAMP WITH LOCAL TIME ZONE NULL → FAILS
INSERT INTO ORA_TIMESTAMP_TEST VALUES
    (7, current_timestamp, current_timestamp, current_timestamp,
     current_timestamp, current_timestamp, NULL);

Expected Behavior

All rows replicate successfully, including those with NULL values in TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE columns.

Actual Behavior

Rows with NULL values in TIMESTAMP WITH TIME ZONE or TIMESTAMP WITH LOCAL TIME ZONE columns fail with:

IndexOutOfBoundsException: Index 6 out of bounds for length 5

Full error log for the 1st failed case (others are similar):

2026-04-17 13:54:31,842 WARN [trg-001] [DefaultDatabaseWriter] [ORA_TIMESTAMP_TEST-dataloader-8] Failed to process insert event in batch 000-13 at line 1 on channel 'schema1'.
Failed raw sql was: insert into "SCHEMA1"."ORA_TIMESTAMP_TEST" ("ID", "TIMESTAMP3", "TIMESTAMP6", "TIMESTAMP3_WITH_TZ", "TIMESTAMP6_WITH_TZ", "TIMESTAMP3_WITH_LTZ", "TIMESTAMP6_WITH_LTZ") values (?,?,?,TO_TIMESTAMP_TZ(?, 'YYYY-MM-DD HH24:MI:SS.FF TZH:TZM'),TO_TIMESTAMP_TZ(?, 'YYYY-MM-DD HH24:MI:SS.FF TZH:TZM'),TO_TIMESTAMP_TZ(?, 'YYYY-MM-DD HH24:MI:SS.FF TZH:TZM'),TO_TIMESTAMP_TZ(?, 'YYYY-MM-DD HH24:MI:SS.FF TZH:TZM'))
Failed sql parameters types: [NUMERIC, TIMESTAMP, TIMESTAMP, TIMESTAMPTZ, TIMESTAMPTZ, TIMESTAMPLTZ, TIMESTAMPLTZ]
 StackTraceKey.init [IndexOutOfBoundsException:2676289281] java.lang.IndexOutOfBoundsException: Index 6 out of bounds for length 5
        at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:100)
        at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:106)
        at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:302)
        at java.base/java.util.Objects.checkIndex(Objects.java:365)
        at java.base/java.util.ArrayList.remove(ArrayList.java:552)
        at oracle.jdbc.driver.OracleParameterMetaDataParser.getParameterMetaDataSqlForInsert(OracleParameterMetaDataParser.java:848)
        at oracle.jdbc.driver.OracleParameterMetaDataParser.getParameterMetaDataSql_internal(OracleParameterMetaDataParser.java:604)
        at oracle.jdbc.driver.OracleParameterMetaDataParser.getParameterMetaDataSql(OracleParameterMetaDataParser.java:1500)
        at oracle.jdbc.driver.OracleParameterMetaData.parseAndQuery(OracleParameterMetaData.java:266)
        at oracle.jdbc.driver.OracleParameterMetaData.checkValidIndex(OracleParameterMetaData.java:767)
        at oracle.jdbc.driver.OracleParameterMetaData.getParameterType(OracleParameterMetaData.java:921)
        at org.springframework.jdbc.core.StatementCreatorUtils.setNull(StatementCreatorUtils.java:275)
        at org.springframework.jdbc.core.StatementCreatorUtils.setParameterValueInternal(StatementCreatorUtils.java:239)
        at org.springframework.jdbc.core.StatementCreatorUtils.setParameterValue(StatementCreatorUtils.java:174)
        at org.jumpmind.db.sql.JdbcSqlTemplate.setValues(JdbcSqlTemplate.java:1242)
        at org.jumpmind.db.sql.JdbcSqlTransaction.addRow(JdbcSqlTransaction.java:427)
        at org.jumpmind.symmetric.io.data.writer.DefaultDatabaseWriter.execute(DefaultDatabaseWriter.java:1232)
        at org.jumpmind.symmetric.io.data.writer.DefaultDatabaseWriter.insert(DefaultDatabaseWriter.java:289)
        at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriter.write(AbstractDatabaseWriter.java:192)
        at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:62)
        at org.jumpmind.symmetric.model.ProcessInfoDataWriter.write(ProcessInfoDataWriter.java:98)
        at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:62)
        at org.jumpmind.symmetric.io.data.writer.TransformWriter.write(TransformWriter.java:187)
        at org.jumpmind.symmetric.io.data.DataProcessor.forEachDataInTable(DataProcessor.java:194)
        at org.jumpmind.symmetric.io.data.DataProcessor.forEachTableInBatch(DataProcessor.java:160)
        at org.jumpmind.symmetric.io.data.DataProcessor.process(DataProcessor.java:108)
        at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$2.call(DataLoaderService.java:1106)
        at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$2.call(DataLoaderService.java:1082)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:328)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1090)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
        at java.base/java.lang.Thread.run(Thread.java:1474)

2026-04-17 13:54:31,847 WARN [trg-001] [DefaultDatabaseWriter] [trg-001-dataloader-8] Failed to process insert event in batch 000-13 at line 1 on channel 'schema1'.
 StackTraceKey [IndexOutOfBoundsException:2676289281]
2026-04-17 13:54:31,876 ERROR [trg-001] [ManageIncomingBatchListener] [trg-001-dataloader-8] Failed to load batch 000-13 StackTraceKey [IndexOutOfBoundsException:2676289281]
2026-04-17 13:54:31,948 ERROR [trg-001] [DataLoaderService] [qtp1910326820-35] Failed to process incoming batch from node '000' StackTraceKey [IndexOutOfBoundsException:2676289281]
2026-04-17 13:54:31,966 ERROR [src-000] [AcknowledgeService] [src-000-push-default-8] The outgoing batch 001-13 failed at line 1 on data 16: Index 6 out of bounds for length 5

Note: After this is only speculation!

Root Cause Analysis

The issue might be in JdbcSqlTemplate.verifyArgType() (symmetric-jdbc/src/main/java/org/jumpmind/db/sql/JdbcSqlTemplate.java):

protected int verifyArgType(Object arg, int argType) {
    if (argType == ORACLE_TIMESTAMPTZ || argType == ORACLE_TIMESTAMPLTZ
            || argType == Types.OTHER || argType == ColumnTypes.MSSQL_SQL_VARIANT) {
        return SqlTypeValue.TYPE_UNKNOWN;
    }
    ...
}

When ORACLE_TIMESTAMPTZ or ORACLE_TIMESTAMPLTZ is passed with a NULL value, this method returns SqlTypeValue.TYPE_UNKNOWN. Spring's StatementCreatorUtils.setParameterValue() then attempts to determine the actual SQL type by calling ps.getParameterMetaData().getParameterType(index). The Oracle JDBC driver fails to correctly parse the SQL containing TO_TIMESTAMP_TZ(?, '...') function wrappers, resulting in a mismatched internal parameter list and the IndexOutOfBoundsException.

Non-null values work because Spring uses ps.setObject() directly without needing getParameterMetaData(). Regular TIMESTAMP columns work because they return Types.TIMESTAMP (not TYPE_UNKNOWN), so ps.setNull(i, Types.TIMESTAMP) is called directly.

Suggested Fix

Separate ORACLE_TIMESTAMPTZ and ORACLE_TIMESTAMPLTZ handling from Types.OTHER and return Types.VARCHAR instead of TYPE_UNKNOWN, since the TO_TIMESTAMP_TZ(?, '...') wrapper expects a string parameter:

protected int verifyArgType(Object arg, int argType) {
    if (argType == ORACLE_TIMESTAMPTZ || argType == ORACLE_TIMESTAMPLTZ) {
        return Types.VARCHAR;
    } else if (argType == Types.OTHER || argType == ColumnTypes.MSSQL_SQL_VARIANT) {
        return SqlTypeValue.TYPE_UNKNOWN;
    } else if ((argType == Types.INTEGER && arg instanceof BigInteger) ||
            (argType == Types.BIGINT && arg instanceof BigDecimal)) {
        return Types.DECIMAL;
    } else {
        return argType;
    }
}

This ensures ps.setNull(i, Types.VARCHAR) is called for NULL TIMESTAMPTZ values, avoiding the problematic getParameterMetaData() call entirely.

SymmetricsDS issue after upgrade from 3.11.11 to 3.15.11

Pavel — Thu, 16 Apr 2026 17:37:56 -0000

Hi Susant,

This an unusual issue! Could you share a support snapshot or logs from the node that has this problem, please?

You can find instructions for capturing a Support Snapshot here:

Command line: https://support.jumpmind.com/kb/article/34-Take-a-Support-Snapshot-from-Commandline
PRO edition's web UI: https://support.jumpmind.com/kb/article/30-How-To-Take-A-Support-Snapshot

Warm regards,
Pavel

SymmetricsDS issue after upgrade from 3.11.11 to 3.15.11

Susant Mohapatra — Thu, 16 Apr 2026 04:45:06 -0000

Hi,

I recently upgraded SymmetricDS from version 3.11.11 to 3.15.11.

My setup includes one central node, multiple store nodes, and their respective register nodes. So far, I have upgraded the central node, one store node, and two register nodes to 3.15.11. The remaining store and register nodes are still on version 3.11.11.

After the upgrade, I’m facing an issue with data synchronization from the central node to the store node.

Batches for master data (employee table) are being created repeatedly in a loop:

From central (3.15.11) to all store nodes
From the upgraded store node (3.15.11) to its register nodes

However, there is no issue with store nodes that are still on version 3.11.11 syncing to their registers.

I would like to understand why batch creation is looping from the central node to all store nodes after the upgrade. can you please let me know as early as possible. I am facing this in production

need to map existing nav with sym data with new mysql

Pavel — Mon, 09 Mar 2026 17:07:44 -0000

Also, SymmetricDS version 3.17+ supports MySQL log-mining (in the PRO edition), which does not require any SYM-tables in the source database.
Check it out: https://www.jumpmind.com/symmetricds/trial/

Data encryption open source Symmetricds-3.12.11 from source to dest

Pavel — Mon, 09 Mar 2026 16:40:30 -0000

SymmetricDS uses encryption which is part of the HTTPS protocol.

Is there any alternate option available for Symds DB user can have without PROCESS privilege access for MariaDB

Andrew Webb — Wed, 04 Mar 2026 18:22:55 -0000

Hi Shan,

Please refer to Symmetric DS User Guide MySQL section:
https://symmetricds.sourceforge.net/doc/3.16/html/user-guide.html#_mysql.

You will want to use the instructions and grants outlined there and in the MariaDB section as well.

SymmetricDS Parallel

Andrew Webb — Wed, 04 Mar 2026 18:16:29 -0000

Hi Dwi,
If you don't have any foreign keys across tables you could move them into separate channels and queues to achieve parallel processing. You could move all the tables with foreign keys into a channel and queue as well.
Here's a related article: https://medium.com/data-weekly/channel-ing-your-symmetricds-configuration-706b6c19cb.

Is there any alternate option available for Symds DB user can have without PROCESS privilege access for MariaDB

shan — Mon, 23 Feb 2026 11:18:26 -0000

Hi Team,
currently configured SymmetricDS version 3.16.6 with MariaDB 10.x.
After upgrading to MariaDb 11.8, during Symds startup, getting the below error message in the Symds log:
1) Failed to get metadata - Access denied: you need (atleast one of) the process privilege( s) for this operation.
2) Failed to retrive node group links.

i.e Accessing any tables from information schema, getting Access denied error. This issue is observed after upgrading Mariadb.

Team is having concern to give grant PROCESS access for Symds DB user. Minimal access i.e select(read only) access on information schema will help to resolve this error. Kindly suggest or any alternative approach for this concern plz.

Thanks.

Recent posts to Discussion

Bug report: Oracle TIMESTAMP WITH TIME ZONE / TIMESTAMP WITH LOCAL TIME ZONE columns with NULL values cause IndexOutOfBoundsException during replication

Bug report: Oracle TIMESTAMP WITH TIME ZONE / TIMESTAMP WITH LOCAL TIME ZONE columns with NULL values cause IndexOutOfBoundsException during replication

Bug report: Oracle TIMESTAMP WITH TIME ZONE / TIMESTAMP WITH LOCAL TIME ZONE columns with NULL values cause IndexOutOfBoundsException during replication

Summary

SymmetricDS Version

Database

Steps to Reproduce

Expected Behavior

Actual Behavior

Note: After this is only speculation!

Root Cause Analysis

Suggested Fix

SymmetricsDS issue after upgrade from 3.11.11 to 3.15.11

SymmetricsDS issue after upgrade from 3.11.11 to 3.15.11

need to map existing nav with sym data with new mysql

Data encryption open source Symmetricds-3.12.11 from source to dest

Is there any alternate option available for Symds DB user can have without PROCESS privilege access for MariaDB

SymmetricDS Parallel

Is there any alternate option available for Symds DB user can have without PROCESS privilege access for MariaDB