View Issue Details

IDProjectCategoryView StatusLast Update
0005778SymmetricDSImprovementpublic2023-05-17 15:29
Reportercquamme Assigned Tocquamme  
Status resolvedResolutionfixed 
Target Version3.15.0Fixed in Version3.15.0 
Summary0005778: Change timestamp size on sym tables with a timestamp as a primary key
DescriptionTo avoid errors during table syncs between databases with different precisions, we will change the timestamp size on sym tables with a timestamp as a primary key to be a size of 2. Some databases (Oracle, SQL Server) will have an error during upgrade with this change, so we will make sure the appropriate actions are taken during the upgrade process to avoid this causing an error.

Affected sym tables:
TagsNo tags attached.


related to 0002826 resolvedcquamme Monitor event duplicate key when syncing 
related to 0003505 resolvedelong SYM_TABLE_RELOAD_REQUEST is updated via DateTime which sometimes fails due to precision mismatch 


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2023-04-06 16:59 cquamme New Issue
2023-04-06 16:59 cquamme Status new => assigned
2023-04-06 16:59 cquamme Assigned To => cquamme
2023-04-13 16:47 cquamme Status assigned => resolved
2023-05-10 18:18 cquamme Status resolved => assigned
2023-05-10 18:18 cquamme Resolution fixed => open
2023-05-10 18:18 cquamme Fixed in Version 3.15.0 =>
2023-05-15 12:01 cquamme Target Version => 3.15.0
2023-05-15 18:49 cquamme Summary Change create_time size on sym_table_reload_request table => Change timestamp size on sym tables with a timestamp as a primary key
2023-05-15 18:49 cquamme Description Updated View Revisions
2023-05-16 12:58 elong Relationship added related to 0002826
2023-05-16 17:40 cquamme Status assigned => resolved
2023-05-16 17:40 cquamme Resolution open => fixed
2023-05-17 15:29 elong Relationship added related to 0003505