Last updated on APRIL 13, 2016
Applies to:Oracle Insurance Policy Administration J2EE - Version 126.96.36.199 and later
Information in this document applies to any platform.
The SQL statements in Patch upgrade scripts, ex. OIPA_DB2.sql, are in reverse order and cannot be executed twice in succession.
The script is ordered newest to oldest. But users are expected to run it oldest to newest.
This means users cannot run this script as is in an automated way without manual intervention.
Users are advised:
“Due to the nature of the SQL script updates, duplicate records or tables may exist. Errors associated with those can be ignored.”
Can the scripts be revised to automatically check for duplicate records and tables?
That way users can terminate the deployments on any errors generated without manual intervention.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms