My Oracle Support Banner

Upgrade Utility Encounter Issues With Table Modifications, Unique Constraints When Upgrading An Existing Database From v10.2.x To v11.3.x (Doc ID 2872702.1)

Last updated on MAY 27, 2022

Applies to:

Oracle Insurance Policy Administration J2EE - Version and later
Information in this document applies to any platform.


On : version, Upgrade Utility

Upgrade Utility keeps failing to upgrade from v10.2.4.0 -->v11.3.1.x.
Many issues regarding the following table modifications, which had to be fixed manually before rerunning the Utility.

Table Modifications:
Most modifications targeting the following tables with the upgrade did not work. 
In some cases, there are stored procedures that attempt to populate columns in these tables with values that contain more decimals than what the column was set to take in another earlier script (e.g. column set to decimal(19,4) and then later script is meant to populate it with a value coming from a decimal(19,10) column).
- AsDepositValue
- AsFundValue
- AsPolicyValue
- AsGroupCustomerIntakeRecord

Unique Constraints:
There are files where the logic doesn't seem correct, between AsActivity and AsActivitySequence tables. One part enforces the ActivityGUID to be unique and in the next part it is not the case, and the column is allowing nulls. 

The issue can be reproduced at will with the following steps:
1. Provided a SQL Server 2017 database with existing OIPA data.
2. The OIPA version needs to be a 10.2.x version.
3. Run the Upgrade Utility to upgrade this v11.3.1.x.
4. The issues will show up on the logs of the Upgrade Utility as it fails to complete.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.