View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005818 | SymmetricDS | Task | public | 2023-05-02 13:51 | 2023-09-13 17:25 |
| Reporter | achintya.de@uk.daiwacm.com | Assigned To | |||
| Priority | high | ||||
| Status | closed | Resolution | open | ||
| Product Version | 3.12.0 | ||||
| Summary | 0005818: Sybase timestamp datatype col's replication to SQL Server is throwing error | ||||
| Description | hi all, I'm having a trouble in replicating timestamp datatype column's values from Sybase to SQL Server. Ive used SSMA to convert a sybase db to sql server db although sql server used it's timestamp datatype as a default datatype but i can remap that to varbinary(8) or so at a later attempt i think the problem will still persist as SymDS is passing values of timestamp col's like below while a new row is being inserted in Sybase and throwing this error sql_message: Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column. example source/sybase table sample_table (col 1, varchar(256), col2 varchar(256), col3 timestamp) target/ms sql table sample_table (col 1, varchar(256), col2 varchar(256), col3 timestamp) row_data: "value 1", "value 2","00000100a41fb5f0" Event_Type : Insert Basically SymDS is sending "00000100a41fb5f0" as a value of the col3 from Sybase/Source to SQL Server/Target and it is failing at MSSQL Side and even with a varbinary(8) datatype on SQL Server it wont work Please let me know your thought on this case Thanks Achintya | ||||
| Tags | No tags attached. | ||||
|
|
You should add that column to the excluded column list on the trigger, this column doesn't contain user data so it is safe to exclude. |
|
|
thanks for your comment, it makes sense, so how would i do that ? by editing the actual Ins,Del,Upd etc SYM_ON_* triggers defined on that table ? most explorers like DBArtisan etc doesnt show the SYM_ON_* triggers , these could be hidden ? any further comment will be very helpful to me |
|
|
i think ive got it what you meant, it looks like i need to update the sym_trigger table to include the excluded column name(s) in the "excluded_column_names" ? one question here though, for multiple column exclusion , should i just add those using comma as a separator so, like begin tran update sym_trigger set excluded_column_names ="col1, col2, col3" where trigger_id = 'triger_name' ? pls comment thanks again achintya |
|
|
@achintya.de@uk.daiwacm.com Yes, you add those using comma as a separator. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-05-02 13:51 | achintya.de@uk.daiwacm.com | New Issue | |
| 2023-05-03 17:20 | cquamme | Note Added: 0002312 | |
| 2023-05-03 17:21 | cquamme | Status | new => feedback |
| 2023-05-04 09:14 | achintya.de@uk.daiwacm.com | Note Added: 0002314 | |
| 2023-05-04 09:14 | achintya.de@uk.daiwacm.com | Status | feedback => new |
| 2023-05-04 09:20 | achintya.de@uk.daiwacm.com | Note Added: 0002315 | |
| 2023-05-10 17:39 | cquamme | Note Added: 0002321 | |
| 2023-05-10 17:39 | cquamme | Status | new => feedback |
| 2023-09-13 17:25 | emiller | Status | feedback => closed |