3238005 - After reset source database's timestamp, dumped and loaded database, target database was corrupted due to a few pages having invalid high timestamps -- SAP ASE

1. Source ASE:

• DBA ran dbcc dbrepair (<database-name>, 'fixtimestamp') on source ASE (production system) to reset database timestamp.
• No page timestamp error was detected by dbcc checkdb and dbcc checkalloc on source database after reset database timestamp.
• Dumped database.

2. Target ASE:

• Loaded database dump to target ASE (disaster recovery system) and online database, corruption errors in ASE errorlog.
• Dbcc checkdb reported page allocation corruption error 605.
• Dbcc checkalloc reported table corruption error 2525.
• Dbcc page(dbname|dbid, pageno_in_error, 0) shows some page timestamp is higher than database timestamp dbt_dbts (which is in dbcc dbtable(dbname) output), e.g.
• Page 27955300 in error 605 output.
• Page header from dbcc page(dbname, 27955300,0) output shows
• Page header for leaf page 0x24cdd800
• pageno=27955300 nextpg=27955301 prevpg=27955299 ptnid=1685578012 timestamp=fffc 6910944d     <---- invalid high page timestamp 
• Database timestamp dbt_dbts=0x0000 0x0ab47b90  in ‘dbcc dbtable(dbname)’ output
• Invalid page timestamp fffc 6910944d in page header which is higher than database timestamp dbt_dbts 0x0000 0ab47b90.

SAP ASE 16.0 SP03 PL09 or later

CR 827044, 827044, error 605, 605, dbcc dbrepair, fixtimestamp, timestamp, dbt_dbts, error 2525, 2525, target database, corruption, table corruption, page allocation corruption.
, KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed