Terminating Information is Lost When Connection Spec Was Changed for Connections Created by EWO Order
Last updated on FEBRUARY 22, 2017
Applies to:Oracle Communications MetaSolv Solution - Version 6.2.1 and later
Information in this document applies to any platform.
An EWO was issued for a mixture of circuits – some of which are Ethernet (template-based).
When the following circuit was first built, the spec used was CUST_SITE TO ETH (because ETH TO ETH was not available):
101 /TLM /JUNEAKBRQ41/JUNEAKBR00W
The engineers then went and added elements to a network and they wanted the TLM (Bandwidth) reassigned between the elements.
As such, we created an ETH_TO_ETH connection spec.
The process we were advised to follow to ‘change the spec’ for the existing bandwidth was to go into the network and assign it to the connection we wanted.
We did this and it updated the network system information but it lost its terminating location. There are probably several in this category.
So, my question is – does this look familiar? Is it a hole in the code? Is there a hung Z location somewhere in the tables that thinks this is still associated to an end user location?
Please provide an answer as well as a SQL script to clean/update these items.
Looking in the database, there is Customer Site that is still in the database, with Status 1 - Pending status.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms