Loading...
Loading...
On Raptor DB instances, if there are 10,000+ script includes, there is a possibility for script include cache to be corrupted when a nested query is executed while loading the cache. This issue is an edge case that you may not encounter. ServiceNow is working to proactively deploy a workaround on instances that are currently on Raptor DB. As a part of implementing this workaround, we will be performing a rolling restart on your application nodes. Note: This issue does not affect data integrity inside the RaptorDB engine or its ability to store or process queries.
There are no steps to reproduce this issue.
ServiceNow will perform maintenance on your RaptorDB instance(s) to implement a workaround and prevent impact. This maintenance entails adding the "glide.db.postgresql.jdbc.largeResultSetProtectionMethod=disk" property to the instance's application nodes, followed by a rolling restart of the patched nodes. - Sub-production instances will receive this maintenance on Wednesday, December 11, beginning at 18:00 PST. - Production instances will receive this maintenance on Friday, December 13, beginning at 20:00 PST. FAQ Q: Does this affect production instances, sub-production instances, or both? A: Both production and sub-production instances are affected by this issue. Q: Can I implement the workaround manually? A: There are no manual workarounds. The application nodes must be updated by ServiceNow. Q: Will the workaround cause downtime or performance impact? A: There is no anticipated performance impact or downtime as we will be bouncing nodes in a rolling fashion. Q: Can I reschedule or opt-out of this maintenance activity? A: No. This maintenance is crucial to preventing impact to your instance, and we have ensured that it will not conflict with any previously scheduled changes. Q: How do I know if my instance is receiving this maintenance? A: If your instance is being targeted in this maintenance, you will receive a communication from ServiceNow detailing the maintenance time. Q: Which versions of the platform contain a fix? A: A permanent fix for this issue will be deployed in Xanadu Patch 5 and above. Q: Do I need to revert the workaround once I've upgraded to a fixed version? A: Reverting the workaround will be handled by ServiceNow in fixed versions.
PRB1788274
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.