Loading...
Loading...
Australia Patch 5 (AP5) and Australia Patch 5 W33 introduced a change to how certain database auto-increment sequences are managed. Under specific conditions, this change can cause the sequence used to generate new record identifiers to become invalid or out of sync with the database. When this occurs, attempts to create new records may fail. As a result, transient state records may not be created as expected in tables with auto-increment field. This impacts many functional areas that rely on sequence records to track the order of states, logs, or messages, including: ATF rollback operations, Patch/Plugin install rollback, Record delete rollback Outbound HTTP logs and synchronization queues CDC, inter instance replication functionality, ServiceBridge and PA report that leverage CDC data Chat and Virtual Agent capabilities Now Assist and summarization features Real-time workspace updates and record watch functionality Text search indexing Platform predictive clustering API AMB functionality can impact exports of data visualizations, where the export screen is stuck and doesn't let you know that its done exporting and present you with a download export prompt This can be identified by viewing instance logs: Review your instance logs for messages such as:Unique Key violation detected by database (ERROR: duplicate key value violates unique constraint "sys_rollback_sequence_pkey" Detail: Key (number)=(0) already exists.) OR "relation http_log0002_sequence_seq does not exist". Affected Versions: Australia Patch 5 or Australia Patch 5 W33 Steps to Reproduce 1) In AP5 or AP5 W33, run any script in scripts-background. 2) Observe that few inserts to sys_rollback_sequence fails with duplicate key error on number field Unique Key violation detected by database (ERROR: duplicate key value violates unique constraint "sys_rollback_sequence_pkey" Detail: Key (number)=(0) already exists.)
Please upgrade to a version with the permanent fix by reviewing the "Fixed In" section at the bottom of the KB. -- Warning: Upgrades from an instance presently on Australia Patch 5 or Australia Patch 5 Week 33 that upgrades to Australia Patch 5 Week 34 (or above) will will require maintenance cleanup to take care of the artifacts (see the steps below). Upgrades from ANY VERSION BEFORE Australia Patch 5 OR BEFORE Australia Patch 5 Week 33 directly into Australia Patch 5 Week 34 (or above) will NOT require maintenance follow up and will avoid this defect entirely. -- The following steps below are necessary for full remediation regarding the AP5/AP5W33 > AP5W34 (or above) path: Step 1: Upgrade to the Fixed Version (Customer Action Required) Please upgrade your impacted instance to a fixed version at your earliest convenience by reviewing the Fixed In section at the bottom of the KB. Step 2: (If the instance upgraded from AP5 or AP5W33 version and is now on AP5W34 (or above)) : Clean up activity for sequence metadata correction (ServiceNow Maintenance) ServiceNow will check for instances with faulty sequence metadata/attribute artifacts caused by this defect that are on AP5W34 (or above). If found, a separate communication will be sent regarding the maintenance activity to perform cleanup. -- FAQs Q: When will this maintenance happen? A: A COMM record will be sent to notify you with the dates and times if an instance is determined for maintenance. Q: How can I tell if I am affected by this issue? A: Functions that rely on auto-increment sequences will be affected upon insert. You will also receive a notification for the maintenance. A instance can be affected by this if they are on AP5, AP5W33, or if they upgraded to AP5W34 (or above) coming from the impacted versions mentioned. Q: Why is this issue happening? A: A change introduced in AP5/AP5W33 affected database auto-increment sequences are managed. Q: What does the maintenance do? A: The maintenance cleans up artifacts on sys_dictionary records introduced in AP5/AP5W33 that is still resulting in impact once an instance is on AP5W34 (or above). The maintenance carefully distinguishes true leftover residue from legitimate attribute configuration for successful cleanup. Q: Will this maintenance have any service impact? A: No service impact. Cache flush or node restart is NOT required during the maintenance. Q: Can I opt out of this maintenance or reschedule? A: Opting out of the maintenance or rescheduling is not an option as the maintenance is necessary for instance stability. Q: Can I run this maintenance on my own? A: No. The maintenance can only be run by ServiceNow. Q: What am I to expect once the maintenance is completed? What is the validation? A: Functionality impacted by auto-increment sequences will be able to function properly post maintenance. Q: Is this maintenance updating the code defect itself or updating the job? A: The hardcode will not be updated. Q: I have an instance that wasn't added for maintenance even though I believe it can be affected by this issue. What do I do? A: Reach out to technical support. Q: I have an activity occurring at the same time as the maintenance, such as deploying an update set. Will this impact my deployment? A: The maintenance will not interrupt ongoing activities being performed at the same time. However, if the instance is temporarily down due to an activity such as a clone, the maintenance will not proceed. Please reach out to technical support to assist applying the maintenance. Q: What versions will address this issue? A: This is addressed in the versions listed in the intended fixed versions at the bottom of the KB. Q: Will upgrading to the fixed version will fully resolve the issue? A: Upgrading from a version BEFORE AP5 or BEFORE AP5W33 directly upgrading into AP5W34 (or above) fully resolves the issue and will not require a maintenance . Upgrading from a version that is on AP5 OR AP5W33 into AP5W34 (or above) requires maintenance to clean up artifacts for full remediation. Q: Why should I upgrade to a fixed version if the issue is not fully resolved? A: Upgrading to a fixed version is the prerequisite for the remediation process for the maintenance. Upgrading is still mandatory because it contains the fix that prevents the issue from continuing to occur and stops the artifacts from being generated. Q: When will the faulty sequence metadata/attributes/artifacts be corrected if my instance is impacted? A: The first step is to upgrade to a fixed version (AP5W34 or upward). After the instance is upgraded to a fixed version, a separate communication will be sent regarding the maintenance activity to repair the corrupted metadata if your upgrade path is from AP5 or AP5W33 upgraded into AP5W34 or above. Q: My instance is upgrading from AP5 or AP5W33 into AP5W35 (or above). Do I need this maintenance? A: If you are experiencing the issue presently on AP5 or AP5W33, and upgrade into AP5W35 or above, you will still need the maintenance as the artifacts mentioned will not be cleaned after upgrading to AP5W35. The same scenario will apply as if you upgraded to AP5W34. Q: Why can't the maintenance be applied to instances presently on AP5 or AP5W33 before upgrading to the fixed versions? A: Due to the nature of the defect, the code will reinsert the faulty artifacts. The goal of the maintenance is to perform cleanup, but it does not take care of the code root cause. If the maintenance is performed on a AP5 or AP5W33 instance, the artifacts will be removed, but will be reinserted. This is why it's a requirement to upgrade from AP5 or AP5W33 into AP5W34 (or above) for you to have the root cause addressed, and to clean up the artifacts. Q: I upgraded from AP5 (or AP5W33) and upgraded into AP5W34 (or above). One (or more) of my instances received notification for the maintenance but not X instance. Why is this happening? A: The issue to create the artifacts was not encountered while the instance was on AP5 or AP5W33 for the instance mentioned. Since you are safely now on AP5W34 or above, the artifact issue will not happen and maintenance is not necessary.
PRB2075293
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.