Loading...
Loading...
There is a difference in how the auto-increment sequence is managed for tables under rotation between Oracle DB. This has caused the AMBPublishedCacheManager to fail to initialize. AMB message table (sys_amb_message) table is configured for table rotation with 7 shards and each shard for a 2-hour duration. AMB Message table has an AUTOINCREMENT number field. The sequence is maintained per shard and is getting reset every time a shard is created. On Oracle, the sequence is maintained at a base table and is used by all shards. It is never reset to zero/1 on shard truncation. This caused the number to grow beyond the Integer.MAX_VALUE. AMB is expecting the number to be an integer, but when the max number for the current shard is beyond the Integer.MAX_VALUE the AMBTableRotationManager could not handle it and threw a NumberFormatException. Steps to Reproduce 1. Alter the sequence object to artificially increment the value to near the MAX_VALUE: Flood the current sys_amb_message shard until the number column is > Integer.MAX_VALUE Or Insert a record in the current sys_amb_message shard table with the number value > Integer.MAX_VALUE Or Update the sequence number of the current sya_amb_message shard > Integer.MAX_VALUE 2. Restart the node.
Reset the sequence number, rotate the table to the next shard and delete all the data within that shard
PRB1685886
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.