| Issue with timestamp precision [message #269717] |
Mon, 24 September 2007 05:07 |
adiga
Messages: 6
Registered: August 2007
|
Junior Member |
|
|
Background:
We have a central oracle DB and a number of local sybase SQL Anywhere DBs spread out over different geographical locations. The schema is identical in all the DBs. We have a synchronization module written in java (JDBC) that picks up any insert/update/delete happening in sybase and fires the same in the central oracle DB.
Problem:
When an insert happens in sybase, the sync module captures the insert statement and fires it in oracle. We are facing an issue with timestamp columns. In Oracle, as in sybase, the timestamp precision is the default -- 6. But the fractional seconds value is getting changed during the insert into oracle. For eg: if the fractional seconds value is .266666 in sybase, its changing to .2666667 in Oracle. Is there some round-off associated with timestamp data types in Oracle?
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
