Finally on this...

Removing duplicate keys in the tables, backing up and restoring,
corrects the fault and all tables now work properly with unique
primary keys.

--- In ib-support@y..., "csswa" <csswa@y...> wrote:
> Further to this issue:
>
> The existing 6 or so tables existing in this db, where the key has
> been defined using the DOM_KEY domain, all exhibit the not-unique
> fault. However, new tables, and new tables created with the
existing
> tables' metadata, exhibit correct primary key unique behaviour.
>
> Regards,
> Andrew Ferguson