Hi Ganesh,

The value for {hvr_cap_tstamp} represents the commit timestamp from the database. HVR generically implements this for all databases. Some databases provide the value no more accurate than 1 second (in fact, Oracle used to document that the commit timestamp may actually decrease for a subsequent commit and that it is no more accurate than +/- 3 seconds).

Fundamentally, for every database, only the commit number (LSN, or SCN) is guaranteed to increase for subsequent commits.

Reporting {hvr_cap_tstamp} in milliseconds would create an illusion of accuracy that even database vendors do not stand behind. We have no plans nor desire to do this. This is different on the destination side where we have full control over the integration process.

Hope this clarifies.
Mark.