My Oracle Support Banner

Groom Exception for "Indirect Rehome Notification - The terminating component was not updated as it could not be derived due to the resultant non-contiguous path." (Doc ID 2908674.1)

Last updated on NOVEMBER 17, 2022

Applies to:

Oracle Communications MetaSolv Solution - Version 6.3.0 and later
Information in this document applies to any platform.

Symptoms

MetaSolv Solution version 6.3.0.733

A groom project/order was created to groom an EVC onto a different customer circuit at the terminating end of the circuit which has a different CLLI Code. This resulted in an indirect rehome. The groom did not process the virtual circuit due to an informational type Groom Exception indicating it would have created a non-contiguous path (exception below).

 

Indirect Rehome Notification - The terminating component was not updated as it could not be derived due to the resultant non-contiguous path.

 

After the exception, it was discovered that the process had removed the EVC's Originating Component. Because of this, the Schematic Design of the circuit cannot be viewed as the Originating Component must be populated before attempting to open other pages of the design.

The Originating Component is a customer site related to an End User Location and the Network System/Element Search window does not have sufficient criteria available to find the proper Originating Component associated with the originating End User Location. The element name cannot be used as all customer sites receive a default name of CUST_SITE based on the component name from the template. Retrieving all CUST_SITE components can easily exceed the defined retrieval limit and requires significant scrolling through the results set with no guarantee that the location was retrieved within it.

At this stage, the order cannot be cancelled to revert back to the original design and, without the originating component, there is no access to the "Redesign Circuit" option to reset the components based on the PRILOC/SECLOC from the order. This circuit is effectively stuck unless updates are applied directly to the database outside of the application (SQL Developer, etc).

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.