Allocation Migration Fails with 'ORA-00001: unique constraint (ATOMIC.PK_FSI_M_ALLOC_DETAILS) violated'
(Doc ID 2484528.1)
Last updated on JULY 02, 2019
Applies to:Oracle Financial Services Profitability Management - Version 8.0.4 to 22.214.171.124.0 [Release 8]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
On Oracle Financial Services Profitability Management (PFT) 8.0.4+, for Offline Migration, when attempting to export and import Allocation Models or Allocations using Offline Migration, the import fails with the following in the offline_migration.log file from the web server's OFSAA log directory:
[21-06-18 11:53:37 AM] ~ INFO ~ MIGRATION ~ Record::,,600,493618,D,,,,-99100,,,,,,,,,,,426788
[21-06-18 11:53:37 AM] ~ ERROR ~ MIGRATION ~ Import--> Error::ORA-00001: unique constraint (ATOMIC.PK_FSI_M_ALLOC_DETAILS) violated
java.sql.BatchUpdateException: ORA-00001: unique constraint (ATOMIC.PK_FSI_M_ALLOC_DETAILS) violated
[21-06-18 11:53:38 AM] ~ INFO ~ MIGRATION ~ Updating allocation source sys IDS with new sys id
[21-06-18 11:53:38 AM] ~ INFO ~ MIGRATION ~ Executing Enabling queries ::
[21-06-18 11:53:38 AM] ~ ERROR ~ MIGRATION ~ Error while Enabling batches
java.sql.BatchUpdateException: error occurred during batching: ORA-02298: cannot validate (ATOMIC.FK_M_ALLOCATION_RULE) - parent keys not found
Due to this issue, some Allocations cannot be migrated to the target environment.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|If using PFT 8.0.6:|
|If using PFT 8.0.5:|