My Oracle Support Banner

Discoverer Upgrade Fails With "MigrateDiscoConnectionException: Copying Data From 10g to 11g Schema" When RCU Rolled Back (Doc ID 1536398.1)

Last updated on JUNE 29, 2023

Applies to:

Oracle Fusion Middleware - Version and later
Oracle Discoverer - Version and later
Information in this document applies to any platform.
Tested on Solaris Sparc 10
Upgrade of Discoverer to fails to upgrade Schema
RCU Does not fully rollback database, retry may leave schema's and tables with invalid values.



While running the Upgrade Assistant, the Discoverer upgrade fails with the following errors:


The installactions.log shows:

2013-02-22T14:23:09.922-08:00] [DISCOVERER] [ERROR] [] [upgrade.DISCOVERER] [tid: <tid>] [ecid: <ecid>] Cause: An error occurred either during Discoverer precheck run or upgrade run. Action: Contact Oracle Support Services.
[2013-02-22T14:23:09.925-08:00] [DISCOVERER] [NOTIFICATION] [] [upgrade.DISCOVERER] [tid: <tid>] [ecid: <ecid>] oracle.ias.mrua.plugin.discoverer.MigrateDiscoConnectionException: Error while copying data from 10g to 11g schema.[[
    at oracle.ias.mrua.plugin.discoverer.MigrateDiscoConnection.bulkCopyPstoreDataTo_11g(
    at oracle.ias.mrua.plugin.discoverer.MigrateDiscoConnection.copyDataFrom10gTo11g(
    at oracle.ias.mrua.plugin.discoverer.MigrateDiscoConnection.doMigrate(
    at oracle.ias.mrua.plugin.discoverer.DiscovererPlugin.massageData(
    at oracle.ias.mrua.plugin.discoverer.DiscovererPlugin.discoUpgrade(
    at oracle.ias.mrua.plugin.discoverer.DiscovererPlugin.doUpgrade(
    at oracle.ias.mrua.MRUA.executePlugins(
    at oracle.ias.mrua.MRUA.internal_driver(
    at oracle.ias.mrua.MRUA.driver(
Caused by: java.sql.SQLException: ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "BI_DISCOVERER_PS.WWSSO_UTL", line 506
ORA-06502: PL/SQL: numeric or value error: hex to raw conversion error

    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4C8Oall.processError(
    at oracle.jdbc.driver.T4CTTIfun.receive(
    at oracle.jdbc.driver.T4CTTIfun.doRPC(
    at oracle.jdbc.driver.T4C8Oall.doOALL(
    at oracle.jdbc.driver.T4CPreparedStatement.doOall8(
    at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
    at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(
    at oracle.jdbc.driver.OraclePreparedStatement.execute(
    at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(
    at oracle.ias.mrua.plugin.discoverer.Utils.copyUserinfo(
    at oracle.ias.mrua.plugin.discoverer.Utils.migratePstoreData(
    at oracle.ias.mrua.plugin.discoverer.MigrateDiscoConnection.bulkCopyPstoreDataTo_11g(
    ... 9 more


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)


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.