Discoverer Upgrade Fails With "MigrateDiscoConnectionException: Copying Data From 10g to 11g Schema" When RCU Rolled Back
(Doc ID 1536398.1)
Last updated on JULY 01, 2024
Applies to:
Oracle Fusion Middleware - Version 11.1.1.2.0 and laterOracle Discoverer - Version 11.1.1.2.0 and later
Information in this document applies to any platform.
Symptoms
While running the Upgrade Assistant, the Discoverer upgrade fails with the following errors:
The installactions.log shows:
Changes
In this particular case, it was found that the first run of RCU failed, (e.g. in this case due to NLS setting), by default it rolls back. However this left tables in the Database. Even though subsequent RCU succeeds, corrupted tables are left in the Database which will cause Install or Upgrade issues.
This may not be the only errors we see as a result of this: Depending on why RCU failed the first time, and allowing the rollback and retry to continue will vary on errors and component being installed. (In general, allowing RCU rollback is not a good idea)
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 |
Changes |
Cause |
Solution |
References |