74 views

Description

After upgrading to any release pre-Kingston Patch 7, the tables asmt_template and asmt_template_definition contain invalid sys_metadata records, due to incorrect reparenting during the upgrade process.

 

Steps to Reproduce

1. Login a non-upgraded instance from an earlier release (Helsinki, Istanbul, Jakarta)
2. Make a note of the number of records in asmt_template_definition.list
3. Upgrade that Instance to an early Kingston patch
4. Check the asmt_template_definition.list and observe missing records
5. In new upgraded Kingston patch 2 instance, navigate to sys_metadata and set class > is > ( either of the 2 tables classes that are affected) and take note of the number of records
6. Navigate to the listview of either of the tables and take note of the number of records. Notice an obvious difference in sys_metadata records as opposed to list view, per table.

Workaround

This problem is fixed in upcoming patches. Customers encountering this issue after an upgrade should contact SN support to apply the data alignment procedure on the instance database.

 

 


Related Problem: PRB1257594

Seen In

There is no data to report.

Intended Fix Version

Kingston Patch 7
London

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2018-06-06 23:29:14
Published:2018-06-07