Node views / roles not created for a Company in Master/Subordinate UVMS

book

Article ID: 140409

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

New node from a company CNA050 was installed and declared on a Subordinate UVMS, nevertheless the Security is not pushed to the node as the Node Views and Roles that are automatically created have not been created in UVMS and cannot be created manually either ( it says that the company does not exist).
 
If we declare a new node for a new company on the same UVMS Subordinate, it does automatically create the nodeviews, so we think that the database must have some records that prevent security from being automatically created on UVMS Master.
 
As a result, the Nodes from company CNA050 cannot be used as any action will result into a permission error in UVC or command line.
 
Synchronization between master and subordinate may take a lot of time when the subordinate has several groups.
 
 

Cause

Some records in tables UNI_UV_PERMISSIONS and UNI_UV_ROLES2 kept automatic creation of Node View / Roles from being created for a specific Company name.

Environment

Release : 6.10

Component : DOLLAR UNIVERSE

Subcomponent: UVMS

Resolution

In order to fix the issue, some records needs to be purged from the  UVMS Master tables.

Please contact Technical Support to help you diagnose exactly what records need to be deleted.


Example for this case:

uniderby -q "delete from UNI_UV_PERMISSIONS where ROLE_ID in (select ID from UNI_UV_ROLES2 where COMPANY = 'CNA050' and IS_DELETED=0)"

uniderby -q "delete from UNI_UV_ROLES2 where COMPANY = 'CNA050' AND IS_DELETED=0"



Additionally, you will need to upgrade the UVMS Master to version 6.10.21 or superior as some improvements on Roles / Groups queries has been performed in case a Master / Subordinate Architecture is being used.

This version will be available by January 15th 2020

Additional Information

The synchronization request from the master to the subordinate may take a lot of time caused by multiple requests to the database, which also may result to a high CPU consumption.
The synchronization request has been reduced on the master side.