3696618 - SAP ASE: During 'online database', extents accounting for OAM page may reference allocation page not in sysusages

In rare occasions, user reports cases of OAM extents-accounting sysusages row not found errors after large db extend, reorg rebuild of large tables, & db shrink

This can happen when the extended/shrunk database is loaded to another server, giving an error like:

00:0002:00000:00200:2023/01/24 12:32:07.69 server  *** WARNING ******************
00:0002:00000:00200:2023/01/24 12:32:07.69 server  Unable to find the sysusages row that controls the allocation page 105334272 while doing the extents accounting for OAM page 3085680, object ID 652526327, index ID 0, database ID 21 (OAM entry 511).

Or, if checkalloc is run just after the shrink, you may see errors like:

00:0009:00000:00544:2023/02/12 23:00:38.63 server  Error: 1161, Severity: 21, State: 1
00:0009:00000:00544:2023/02/12 23:00:38.63 server  Invalid OAM entry found at slot 1399 in OAM page 89309697 for table ID 624002223 with index ID 3 in database 'MyDB' (ID 7). This entry is either out of order or its allocation page number is wrong. 

ASE 16.0, RedHat Linux

dbcc checkalloc, error 1161, reorg rebuild, dump database, sysusages, alter database , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem