View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003123 | SymmetricDS Pro | Bug | public | 2017-05-23 18:37 | 2021-01-15 20:57 |
| Reporter | gwilmer | Assigned To | josh-a-hicks | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.7.32 | ||||
| Target Version | 3.12.6 | Fixed in Version | 3.12.6 | ||
| Summary | 0003123: License Key fails to synchronize (data truncated) to target node of DB2 on zSeries | ||||
| Description | Log file will show the following error: DB2 SQL Error: SQLCODE=-723, SQLSTATE=09000, SQLERRMC=AMD0007.SYM_ON_I_FOR_SYM_PRMTR_PRDDB2;-433;22001;"ALL","ALL","console., DRIVER=3.57.82 It looks to me like the license key row is loaded into sym_parameter on the db2 side, the symmetric trigger fires to capture that row into sym_data, and the corresponding write to sym_data fails because of the -433,22001 failure, which is that data being inserted is too large and will be truncated. | ||||
| Tags | No tags attached. | ||||
| related to | 0004709 | closed | josh-a-hicks | SymmetricDS | DB2 zOS uses long varchar instead of clobs |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-05-23 18:37 | gwilmer | New Issue | |
| 2019-04-29 13:21 | elong | Summary | License Key fails to synchronize to target node of DB2 on zSeries => License Key fails to synchronize (data truncated) to target node of DB2 on zSeries |
| 2021-01-15 20:28 | elong | Relationship added | related to 0004709 |
| 2021-01-15 20:29 | elong | Assigned To | => josh-a-hicks |
| 2021-01-15 20:29 | elong | Status | new => resolved |
| 2021-01-15 20:29 | elong | Resolution | open => fixed |
| 2021-01-15 20:29 | elong | Fixed in Version | => 3.12.7 |
| 2021-01-15 20:29 | elong | Target Version | => 3.12.7 |
| 2021-01-15 20:57 | elong | Status | resolved => closed |
| 2021-01-15 20:57 | elong | Fixed in Version | 3.12.7 => 3.12.6 |
| 2021-01-15 20:57 | elong | Target Version | 3.12.7 => 3.12.6 |