DUAS Node appears with status "Unknown" after upgrading from v5 to v6

Document ID : KB000086928
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
In uvserver.log file from UVMS:
======================================================================
| 2014-04-09 13:54:08 |ERROR| request-worker-12270 | org.hibernate.util.JDBCExceptionReporter | The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_NODES_INFO_NODE". The conflict occurred in database "ews_uvmsdb", table "dbo.UNI_UV_NODES", column 'ID'.
| 2014-04-09 13:54:08 |ERROR| request-worker-12270 | org.hibernate.event.def.AbstractFlushingEventListener | Could not synchronize database state with session
org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update
=============================================================================

Patch level detected:Univiewer Management Server 6.2.00
After the upgrade from DUAS v5 to v6 on the UVC console the node appears with theĀ  Unknown connection status but it was reachable and objects / node settings could be displayed.

On UVC - UVMS Database Monitoring section is not possible to display the databaseĀ  tables
The UVMS was on version 6.2 with an external Database (MS SQL Server).
Environment:
OS: All
Cause:
Cause type:
Other
Root Cause: A problem in the UVMS Database would not allow the modiification of the table UNI_UV_NODES
Resolution:
Restarting the UVMS allows to update again the impacted line of the table UNI_UV_NODES, as a result the node appeared as Connected again.

Fix Status: No Fix