My Oracle Support Banner

MSS Crashing when Deleting a Diversity Set with Design Violations (Doc ID 2424568.1)

Last updated on JULY 18, 2018

Applies to:

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

Symptoms

PROBLEM STATEMENT

Users are unable to delete a Diversity Set when there is has a design violation.

There isn’t a way to break up a diversity set of two circuits.
The popup window can’t be closed without two valid circuit IDs, so we can’t remove one or both.
An attempt to delete the diversity set results in the crash shown below

STEPS

1. Create Diversity Rules: Test0 for DS0 and Test1 for DS1
2. Using EWO, create 4 circuits: Special DS0: CKT-1 & CKT-2 -- Facility DS1: FAC-1 & FAC-2
3. Create a Diversity Set MT-DS0 with Type Diversity with CKT-1 and CKT-2
4. Assign CKT-1 to facility FAC-1 &  CKT-2 to facility FAC-2

5. Delete Diversity Set MT-DS0
    ---> MSS deletes the set without problems

6. Recreate Diversity Set MT-DS0 as in step (3)

7. Assign CKT-1 to facility FAC-1
          CKT-2 to facility FAC-1 ----> MSS Flags a diversity violation

     ===> MSS throws a Violation Override window asking if the user wants to override
               Accepted: entered Reason Description & Reconcile Approach and hit [ OK ]

8. Deleting the Diversity Set MT-DS0: right-click Delete

    ===> The MSS crashes with the following errors

ERROR MESSAGES

(1) Oracle Communications MetaSolv Solution

Error Number 36.
Error text = Name not found accessing external object property
tfc_network_id_child
Window/Menu/Object = n_cst_log_violations.
Error Object/Control = n_cst_log_violations.
Script = of_removediversitysetviolations.
Line in Script = 199.

(2) Oracle Communications MetaSolv Solution

Error 21.
Error text = Bad runtime function reference.
Window/Menu/Object = n_cst_log_violations.
Error Object/Control = n_cst_log_violations.
Script = of_removediversitysetviolations.
Line in Script = 199.

(3) Oracle Communications MetaSolv Solution

Error 65.
Error text = Dynamic function not found. Possible causes include:
pass by value/reference mismatch.
Window/Menu/Object = u_tabpg_results_diversity.
Error Object/Control = dw_results.
Script = pfc_deleterow.
Line in Script = 21.

(4) Oracle Communications MetaSolv Solution

Error 2.
Error text = Null object reference.
Window/Menu/Object = pfc_w_master.
Error Object/Control = pfc_w_master.
Script = pfc_messagerouter.
Line in Script = 49.

(5) tbs.exe

tbs.exe has stopped working
Windows can check online for a solution to the problem.
• Check online for a solution and close the program
--> • Close the program

OTHER TEST CASES

1. Disconnect one circuit. Works, but still leaves us with the issue above.
    The disconnected circuit doesn’t have a hierarchy, so will not cause design violations.

2. Add or remove one design violation for diversity set that already has violations.
    Verify in Design Violations window. Pass.

3. Perform groom with Groom Tool. Cancel groom when violations are reported at Process Groom stage.
    Works for ISR. I don’t see a way to supp/cancel an EWO for this process.

4. Perform groom with Groom Tool. Do not cancel groom when violations are reported at Process Groom stage.
    Check Design Violations. Pass.

5. Place the same circuit in multiple diversity sets. Allowed. Not sure if this is a pass or fail.

6. Create design violation at grandparent level by assigning diverse DS1s to T3s that ride the same OC12.
    Create the violation while working a DS1. Pass. The code uses a hierarchical query and should see conflicts at any level.

7. Create design violation at grandparent level with diverse DS1s riding T3s that ride same the OC12.
    Create the design violation while working a T3, and assigning it to the OC12. Pass.

8. Add two circuits with existing design violations to a new diversity set.
    Verify in Design Violations window. Pass, requires Options/Log Violations and Refresh actions.

BUSINESS IMPACT

Users unable to delete the Diversity Set, but MSS should not crash.

WORKAROUND

A workaround is to replace one or both circuit IDs with disconnected circuits or dummy circuits.

Changes

 

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!


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