View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004464 | SymmetricDS | Bug | public | 2020-07-02 20:02 | 2022-08-05 20:00 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.12.0 | ||||
| Target Version | 3.12.2 | Fixed in Version | 3.12.2 | ||
| Summary | 0004464: Failed to load batch ORA-00932: inconsistent datatypes: expected - got CLOB | ||||
| Description | The default detection type of USE_CHANGED_DATA will put columns in the where clause of the update statement and bind the old values as a way to detect a conflict. On Oracle, if a LOB column is changed, it tries to put it in the where clause, but Oracle doesn't allow querying LOB columns. 2020-07-02 15:51:21,543 ERROR [server] [ManageIncomingBatchListener] [server-dataloader-44] Failed to load batch 1-18 org.jumpmind.db.sql.SqlException: ORA-00932: inconsistent datatypes: expected - got CLOB at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:306) at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:295) at org.jumpmind.db.sql.JdbcSqlTransaction.addRow(JdbcSqlTransaction.java:466) at org.jumpmind.symmetric.io.data.writer.DefaultDatabaseWriter.execute(DefaultDatabaseWriter.java:964) at org.jumpmind.symmetric.io.data.writer.DefaultDatabaseWriter.update(DefaultDatabaseWriter.java:529) at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriter.write(AbstractDatabaseWriter.java:189) at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:64) at org.jumpmind.symmetric.model.ProcessInfoDataWriter.write(ProcessInfoDataWriter.java:84) at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:64) at org.jumpmind.symmetric.io.data.writer.TransformWriter.write(TransformWriter.java:201) at org.jumpmind.symmetric.io.data.DataProcessor.forEachDataInTable(DataProcessor.java:212) at org.jumpmind.symmetric.io.data.DataProcessor.forEachTableInBatch(DataProcessor.java:178) at org.jumpmind.symmetric.io.data.DataProcessor.process(DataProcessor.java:124) | ||||
| Additional Information | Workaround is to configure a conflict for all tables with detection using USE_PK_DATA. | ||||
| Tags | conflict manager, dialect: oracle | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-07-02 20:02 | elong | New Issue | |
| 2020-07-02 20:02 | elong | Status | new => assigned |
| 2020-07-02 20:02 | elong | Assigned To | => elong |
| 2020-07-02 20:02 | elong | Tag Attached: conflict manager | |
| 2020-07-02 20:02 | elong | Tag Attached: dialect: oracle | |
| 2020-07-02 20:04 | elong | Status | assigned => resolved |
| 2020-07-02 20:04 | elong | Resolution | open => fixed |
| 2020-07-02 20:04 | elong | Fixed in Version | => 3.12.2 |
| 2020-07-02 20:05 | admin | Changeset attached | => SymmetricDS 3.12 3aab7444 |
| 2020-07-20 14:50 | elong | Status | resolved => closed |
| 2022-08-05 20:00 | elong | Relationship added | related to 0002362 |
| 2022-08-05 20:00 | elong | Relationship added | related to 0002358 |