RDBPROD: BAD TSNs From RMU/UNLOAD/AFTER (LogMiner)
Last updated on JANUARY 26, 2018
Applies to:Oracle Rdb Server on OpenVMS - Version 7.0 to 184.108.40.206 [Release 7.0 to 7.3]
HP OpenVMS Itanium
HP OpenVMS Alpha
Logminer has format issues with large TSNs (greater then 2,147,483,647).
RMU/UNLOAD/AFTER with FORMAT=DUMP or FORMAT=DELIMITED_TEXT appears to be treating the TSN as a signed INTEGER instead of a quadword. For example with TSN=2147483686
RMU/UNLOAD/AFTER to a binary file shows the TSN as FFFFFFFF 80000026 where it should be 00000000 80000026
TSN (transaction sequence number) crosses the 'large TSN' threshold of 2147483647.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms