In DX Netops Portal the Spectrum data source synch is failing after upgrade to 24.3.6

Products

• Network Observability
• CA Performance Management

Issue/Introduction

Spectrum data source was synching fine, then it started failing.

We upgraded to 24.3.6 but after the upgrade all DS were green.

 

We see this in the DMService.log:

INFO   | jvm 1    | 2025/03/04 14:30:34 | ON DUPLICATE KEY UPDATE UpdatedOn=1741116615, `ItemSubTypeName`=VALUES(`ItemSubTypeName`), `LocalID`=VALUES(`LocalID`), `ItemName`=VALUES(`ItemName`), `ItemDesc`=VALUES(`ItemDesc`), `Address`=VALUES(`Address`), `DomainID`=VALUES(`DomainID`), `SdnId`=VALUES(`SdnId`), `GatewayUUID`=VALUES(`GatewayUUID`), `ContextTypes`=VALUES(`ContextTypes`), `SerialNumber`=VALUES(`SerialNumber`), `SnmpReadID`=VALUES(`SnmpReadID`), `SnmpWriteID`=VALUES(`SnmpWriteID`)]; Data truncation: Data too long for column 'SerialNumber' at row 51

…..

Caused by: com.mysql.cj.jdbc.exceptions.MysqlDataTruncation: Data truncation: Data too long for column 'SerialNumber' at row 51

 

Environment

 DX NetOps 24.3.6

Cause

In 24.3.6, broadcom added a new value for serial number to devices.

Some devices coming in from VNA are concatenating multiple serial numbers, separated by a comma and this causes the length of the data to exceed the width of the serial number column in portal mysql netqosportal db.

Resolution

 A workaround to fix this is to run this mysql query on portal

mysql -Uroot -p

use netqosportal;

update item_property_types set PropDbType='VARCHAR(64)' where itemtype=4 and propname='SerialNumber';

 

Then wait for the next synch push to update the table width and the synch should finish.

If a synch has already started, then it may take 2 synchs before it fixes it.