Wikis - Page

Knowledge Doc: SM 9.80 – “no duplicates” key on postgresql no longer allows multiple null entries

0 Likes

Defect OCTCR19X2176595 Duplicate key on fields with “no duplicates” key when loading data during migration from older SM version

Environment

Service Manager (SM) 9.80 with PostgreSQL 15 or 16
 

Situation

While using a “no duplicates” key on a table ORACLE allows to have multiple records with a null entry in this column/field.
Changing with SM 9.80 to postgres this key does not allow to have multiple records with null entries.
Loading unload files from those tables to SM9.80 fail with “duplicate key”.
 

Cause

With SM 9.80 there was a change introduced to solve this defect :
OCTCR19X1982243 Duplicated favorite item can be added when user uses Postgres as database
https://kmviewer.saas.microfocus.com/#/OCTCR19X1982243

Solution for OCTCR19X1982243 :
From PostgreSQL 15, Specifying NULLS NOT DISTINCT on unique indexes / constraints will cause NULL to be treated as not distinct.
So, in SM Server, when creating unique index in PostgreSQL 15 DB, the SQL statement will apply 'NULLS NOT DISTINCT'.

Read the complete knowledge article for resolution

Labels:

Support Tips/Knowledge Docs
Comment List
Related
Recommended