Upgrade Script to Edition Existing Schemas is Failing for Schemas Including Custom Objects
(Doc ID 2816785.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Data Management Workbench - Version 3.1.0 to 3.1.0 [Release 3.1.0]Oracle Life Sciences Data Hub - Version 3.1.0 to 3.1.0 [Release 3.1.0]
Information in this document applies to any platform.
Symptoms
On Oracle Life Sciences Data Hub (LSH) 3.1.0 version,
ACTUAL BEHAVIOR
---------------
While upgrading LSH from version 3.0 to 3.1, few schema failed to upgrade during the script dmeupg31runprgs.sql execution.
EXPECTED BEHAVIOR
-----------------------
It would be expected that the schema upgrade to be completed successfully.
STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Perform the upgrade steps from LSH 3.0 to 3.1.
2. As part of the steps in "Run the Upgrade Script to Edition Existing Schemas" section from LSH 3.1 Installation Guide document, execute the script dmeupg31runprgs.sql
3. Monitor the upgrade process using the following query:
The query is returning a value higher than zero for the 'failed_schema_Count'.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |