Duplicate Logo Records During Upgrade to IDSP 4.0

Products

• Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Issue/Introduction

During an upgrade from Symantec Identity Security Platform (IDSP) version 3.4.x to 4.0, the application fails to start at bootstrap initialization. The service terminates immediately with a fatal error indicating that a database query for logo records returned 2 results when exactly 1 was expected.

This failure blocks all further initialization — including tenant setup and authentication service startup — rendering the environment completely unavailable after the upgrade.

The same error was observed in both UAT and Production environments following an upgrade from version 3.3.5 → 3.4.6 → 4.02.

Error Observed: Bootstrap: Failed initialization. Reason: Query did not return a unique result: 2 results were returned. Unable to continue.

Exception: org.springframework.dao.IncorrectResultSizeDataAccessException

Caused by: org.hibernate.NonUniqueResultException: Query did not return a unique result: 2 results were returned

Environment

Symantec Identity Security Platform - IDSP (formerly VIP Authentication Hub)

Resolution

1. Roll back to 3.4.6 to restore availability
2. Identify duplicate logo rows with a GROUP BY tenant_id, type HAVING COUNT(*) > 1 query
3. Delete duplicate records keeping only the most recent per key (PostgreSQL/MySQL and Oracle variants provided)
4. Re-run the Helm upgrade to 4.0 with dataseed.enabled=true
5. Verify clean bootstrap in the logs

Note-> Broadcom Engineering team also created a fix to address this and it will be available in the 4.0.3 release.