Categories
- All Categories
- Oracle Analytics and AI Learning Hub
- 54 Oracle Analytics and AI Sharing Center
- 26 Oracle Analytics and AI Lounge
- 312 Oracle Analytics and AI News
- 57 Oracle Analytics and AI Videos
- 16.4K Oracle Analytics and AI Forums
- 6.7K Oracle Analytics and AI Labs
- Oracle Analytics and AI User Groups
- 117 Oracle Analytics and AI Trainings
- 24 Oracle Analytics and AI Challenge
- Find Partners
- For Partners
OAS 2025 to 2026 inplace Upgrade Failing for OPSS, MDS, and IAU Schemas with ‘Invalid DB Role’ Error
Comments
-
I'm quite sure Steve has as much info as you, if not less…
The SR will let you know before almost anybody else what's the status there. Until they can give you a workaround, a patch, or something allowing you to perform your in-place upgrade, they will keep working (I imagine the SR will stay open till it get a resolution).
At that time, there will probably be a MOS document explaining the issue and the solution, linking to the required patch if any, or what other workaround should be performed. But you should also get that same info given in your SR.
Right now, keep following your SR, that's where you will get updates (before anyone else) directly.
0 -
If I had a public update, I would have shared it already 😀.
Understand and aware of the implications.The correct engineering folks are looking into it, including the proper path to resolution.
The assigned person to your Service Request should be providing you updates and there are defined escalation paths, if necessary.0 -
Thank you for your update.
While it is understood that the issue is under investigation, the current level of detail makes it difficult to assess progress or plan next steps.
Given that this seems to be a product-level issue related to the in-place upgrade from OAS 2025(8.2) to OAS 2026, any additional context—such as known issues, expected timelines, or interim recommendations—would be very helpful.
We will continue to track the SR and appreciate any further insights that can be shared.
0 -
Thank you <address removed> and team, for your prompt support in providing a workaround for the in-place upgrade issue from OAS 2025 to OAS 2026.Your timely assistance and efforts in identifying and addressing the issue are greatly appreciated.
Moderation note: do NOT share email addresses publicly, Oracle support employees included
0 -
We request further investigation from the Dev team. Could you please clarify why the schemas are automatically entering an invalid state during the Upgrade Assistant phase?
0 -
I am going to close this thread, because this is not the appropriate place to be placing Support team contact information in a public setting , requesting escalations, asking for clarifications about the progress. This should be done via the Service Request.
Your situation can potentially be slightly unique.
Once everything is sorted out I will reopen the thread once we have clarity (patch, additional steps, MOS note, etc.) .
The only thing that will be helpful in the thread is the problem and the answer, not all the in between discussion, request for updates , and commentary.
The standing workaround is a new installation with an out-of-place migration.0
