When adding an element to a particular table in the CMDB hierarchy and another element to a grandchild (or lower) of that table within the same update set, the storage aliases can be corrupted so that the elements are stored in the same column. This can cause functional problems and data loss.

Steps to Reproduce


  1. Retrieve, preview, and commit the attached update set (t364460-1.xml).

    This will create two new elements: cmdb_ci_hardware.u_t364460_grandparent, and cmdb_ci_server.u_t364460_posterity.

  2. Go to sys_storage_alias.list for these elements and check the alias assignment.

    They should be assigned to different storage columns (e.g., "cmdb$par1.a_str_18"). The error is that they are assigned to the same storage column.


Create the elements one at a time, or manually delete one of the elements and re-create it to assign it to a new storage column.

Related Problem: PRB1296576

Seen In

There is no data to report.

Intended Fix Version


Fixed In

Jakarta Patch 10
Kingston Patch 8
London Patch 1

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:2019-01-15 01:39:36