197 views

Description

Beginning from Kingston Patch 4+ and Jakarta Patch 9+, coalesce jobs get stuck in Running because the Field Normalization configuration fails to coalesce to a single reference.

Steps to Reproduce

 

  1. Create five records in location table as follows (with name as Location1, Location2, Location3, Location4, Location5).

  2. Create one more record with name as LocationCentral in location table.

    Note that there are six records on location table. 

  3. Go to Normalization and create a normalization called "Location Name Normalization". 

    For more information, see the product documentation topic Normalization Data Services.

  4. Set the following properties:

    • Table: cmn_location 
    • Field: Name 
    • Coalesce each normal: Checked
  5. Save the records and do not click on Collect Pending Values in related links.

  6. Under the Normalized Value tab, click New to create a new entry, provide the following values for it, and save it.

    • Value: Test
    • Coalesce to: LocationCentral
  7. In the Alias tab on the form that appears, click on Aliases under related links and add all the values created earlier (Location1 through Location5).

  8. Go back to Normalization and activate and run the jobs.

  9. After a while, check the locations.

    Note that location1 through location5 are normalized to LocationCentral but you see all six records.

    The expectation is to have one single record because Coalesce was selected.

    If you go to the data jobs, note that all of these records are stuck in Running.

 

 

Workaround

  1. Navigate to the Run Job business rule on the fn_extant_data_normalization table.

  2. Change the When field from async to "after".

  3. Replace the script with the contents of the attached text file (workaround_br_replacement_script (1).txt).

    For more information, see the documentation topic Coalesce records on a normal value.

 


Related Problem: PRB1286063

Seen In

Jakarta Patch 9
Kingston Patch 3

Intended Fix Version

Madrid

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-10-16 21:32:45
Published:2018-07-01