Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Jakarta Patch 2 Hot Fix 4

Log in to subscribe to topics and get notified when content changes.

Jakarta Patch 2 Hot Fix 4

The Jakarta Patch 2 Hot Fix 4 release contains fixes to these problems.

For Jakarta Patch 2 Hot Fix 4:
Build date: 09-21-2017_1310
Build tag: glide-jakarta-05-03-2017__patch2-hotfix4-09-20-2017
Important: For more information about how to upgrade an instance, see Upgrade to Jakarta.

For more information about the release cycle, see the ServiceNow Release Cycle. For a downloadable, sortable version of Jakarta fixed problems, see KB0623655.

Note: This version is approved for FedRAMP.

Fixed problem in Jakarta Patch 2 Hot Fix 4

Problem Short description Description Steps to Reproduce




Chunk copying a large table on an Oracle database can degrade over time (e.g. during the TPP migration on a Jakarta upgrade) Chunk copying is a mechanism for moving data from one table to another. It is done in operations such as online alters and the TPP migration in Jakarta. On an Oracle database, the speed at which the chunk copying is done can degrade over time, causing these operations to take a long time to complete.

Refer to the listed Known Error KB article for details.




CMDB TPP migration during a Jakarta upgrade can fail if the migration takes over 24 hours

On an upgrade to Jakarta, the CMDB table will go through a migration called TPP. This can fail if the migration runs for longer than 24 hours as the database connections are destroyed after being marked as obsolete by the connection pool sweeper.

The upgrade will get stuck on the fix script that is running the TPP migration, z_z_migrate_cmdb_tpp.xml. This can be observed in the upgrade monitor and will require manual interventions or a rollback of the upgrade.

Refer to the listed Known Error KB article for details.



An ALTER that has already taken 24 hours is not finished as expected

Fixes included with Jakarta Patch 2 Hot Fix 4

* Unless any exceptions are noted, you can safely upgrade to this release version from any of the versions listed below. These prior versions contain PRB fixes that are also included with this release. Be sure to upgrade to the latest listed patch that includes all of the PRB fixes you are interested in.