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

Shanmukha AV

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.

Shanmukha AV

@SteveF-Oracle @Gianni Ceresa