Oracle Analytics Forum

Home› Oracle Analytics and AI› Oracle Analytics and AI Forums› Oracle Analytics Forums› Oracle Analytics Forum

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OAS 2025 to 2026 inplace Upgrade Failing for OPSS, MDS, and IAU Schemas with ‘Invalid DB Role’ Error

73
Views
12
Comments
Shanmukha AV
Shanmukha AV Rank 3 - Community Apprentice
in Oracle Analytics Forum

We are currently performing an in-place upgrade of Oracle Analytics Server (OAS) from version 2025 (FMW 12.2.1.4.0) to OAS 2026 (14.1.2.0.0) on Oracle Linux 8.

During the upgrade process, we executed Upgrade Assistant and select the option “All Schemas Used by a Domain.”

Observed Behavior

The Examine phase completes successfully for all schemas without any reported issues.

However, during the Upgrade phase, the process fails immediately for the following schemas:

OPSS

MDS

IAU

The failure is associated with an "Invalid DB Role" error.

Troubleshooting Steps Performed

We collaborated closely with our DBA team to investigate the issue and performed the following actions:

After each failed upgrade attempt, the DBA team manually updated the schema_version_registry table to reset the status of the OPSS, MDS, and IAU schemas back to VALID.

We verified that the reset was successful by confirming that the status for all three schemas was set to VALID in the registry.

After confirming the update, we re-ran the Upgrade Assistant.

Current Issue

Despite resetting the schema statuses to VALID, the upgrade process fails again with the same "Invalid DB Role" error. Additionally, after the failure occurs, the Upgrade Assistant automatically updates the status of the affected schemas back to INVALID in the schema_version_registry table.

Request for Guidance

We would appreciate any insights on the following:

Has anyone encountered this "Invalid DB Role" error during an OAS 2026 upgrade?

Are there any specific database roles, privileges, or configuration requirements that must be validated for OPSS, MDS, and IAU schemas prior to running the Upgrade Assistant?

Is there a recommended procedure for safely resetting schema states after a failed upgrade attempt?

Any suggestions, documentation references, or similar experiences would be greatly appreciated.

invalid.png valid.png failed upgrade .jpg
«1

Comments

  • Shanmukha AV
    Shanmukha AV Rank 3 - Community Apprentice

    @SteveF-Oracle @Gianni Ceresa

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Mar 16, 2026 9:37PM

    Observed Behavior

    The Examine phase completes successfully for all schemas without any reported issues.

    However, during the Upgrade phase, the process fails immediately for the following schemas:

    OPSS

    MDS

    IAU

    The failure is associated with an "Invalid DB Role" error.

    Troubleshooting Steps Performed

    I have not encountered that.
    It is hard for me to say, not knowing the details of the user you connected with in the -readiness and the upgrade phase and their database roles.

    I did encounter an issue as documented here, but was able to use the workaround.

    UA readiness will fail for wls schema with error INVALID_WLS_COMPONENT_SCHEMA_OWNER during 14c upgrade KB605325

    I don't recommend any manual updates, you should rollback and retry and file a service request if necessary.

    A workaround, if needed, can be an out-of-place migration.

  • Shanmukha AV
    Shanmukha AV Rank 3 - Community Apprentice

    @SteveF-Oracle We have already raised a Service Request with Oracle Support and are currently waiting for their response. As mentioned, your team is testing the issue in your environment.

    Regarding KB605325, it refers to updating the WLS schema parameter. However, the issue we are encountering is that while running the Upgrade Assistant, the status of the affected schemas is automatically being updated back to INVALID in the schema_version_registry table on the database side.

    This behavior seems to be occurring during the upgrade from OAS 2025 to OAS 2026(12.2.1.4 to 14.1.2) and it appears that this may need further investigation from the Oracle side to understand why the schema status is reverting to INVALID during the upgrade process.

    Could you please confirm whether an in-place upgrade from OAS 2025 to OAS 2026 is supported or not.

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Mar 17, 2026 12:46PM

    It is supported.
    I believe this is a side effect due to EBR support in 14c.
    Allow Support to continue their analysis, reproduce, etc.

  • Shanmukha AV
    Shanmukha AV Rank 3 - Community Apprentice

    Thanks for the update @SteveF-Oracle .We will work with the Support Team and keep you posted on the progress

  • SteveF-Oracle
    SteveF-Oracle Mod
    edited Mar 17, 2026 2:20PM



    Execute the script from this document and upload to the SR

    SRDC: Script to collect more EBR data for further analysis of dependencies/invalidation problems KB142172

    It may be a helpful data collection point in addition to the UA logs

    Thanks

  • Shanmukha AV
    Shanmukha AV Rank 3 - Community Apprentice

    Hi @SteveF-Oracle The script has already been executed, and the results have been uploaded to the SR.

  • Gianni Ceresa
    Gianni Ceresa Mod
    edited Mar 17, 2026 2:48PM

    As OAS 2026 is barely a week old, there is probably little to no one who did an in-place upgrade. That's why I don't expect many other people replying here.

    I'm still going through the things I find a bit strange (wrong, poorly documented, etc.) in OAS 2026 itself, without even thinking at trying an in-place upgrade and see what happen.

    Your SR will probably result in a MOS note being published when fixed.

  • Shanmukha AV
    Shanmukha AV Rank 3 - Community Apprentice

    @Gianni Ceresa @SteveF-Oracle Thank you for the update. We have raised the SR, and the engineering team is currently coordinating with the internal team. We are still awaiting further feedback from Oracle Support. Based on the observations so far, it appears that some of the issues may require fixes or additional clarification from Oracle’s side.

    Could you please confirm whether Oracle Analytics Server 2026 was formally tested for in-place upgrades prior to its release? For context, Oracle Analytics Server 2025 is based on Oracle Fusion Middleware 12.2.1.4, while Oracle Analytics Server 2026 is based on Oracle Fusion Middleware 14.1.2.0.0. Since this represents a significant underlying platform version change, it is important to confirm that the upgrade path has been fully validated.

    In particular, could you please clarify whether the development or QA teams performed validation of the in-place upgrade from Oracle Analytics Server 2025 (8.2) to Oracle Analytics Server 2026, including schema migrations, compatibility checks, and functional testing? Additionally, could you confirm whether the schema failures we are experiencing were observed during standard pre-release upgrade testing, or if they appear to be specific to our environment?

    Clarification on these points will help us determine whether the issue is isolated to our environment or represents a broader upgrade concern that may require further action or fixes from Oracle. A detailed confirmation will also help us plan appropriate mitigation steps while we continue to coordinate with Oracle Support.

  • SteveF-Oracle
    SteveF-Oracle Mod

    Generally speaking upgrade scenarios are validated; however, not every combination, or scenario may be possible.
    All of that information can be handled via the Service Request.
    The appropriate parties have been informed, but it may take some time for the responses while your specific scenario is documented and reproduced.