New My Oracle Support – updates and issues
Oracle is taking seriously the confusion created with the abrupt migration to the new My Oracle Support (MOS) portal. Today there was a meeting between several VPs and other responsible and the Oracle ACE community. Thanks a lot!
We see many things are being improved and solved and the team is working hard to get the trust back from the community. We are here to help!
My top issues today (15.Dec.2025) with the new MOS are here:
Content related issues
- A list with “Last viewed Docs” + “Last searches” sections would very useful to find again documents. The list should include the last updated date in a column
- InĀ “My Favorites” section, it is important to see the “last updated date” as a column. Old DocId may be removed. Folders/Categories were useful
- The “Favorites” were the base for the “Oracle Support HOT Topics” daily email, and this was where users can get information if any of our favorites was updated. This email seems not to exist anymore.
- Bugs are not part of the search – it is useful to know the bug exists, even if it is marked “not public”. This was the case in old MOS;
- Missing wget script to download patch – this was important, as usually we do not have browsers where we need the patch;
- SRs in “Pending Final Closure” do not appear any where (neither open, nor close). Should be in “need your attention” part. (Example SR 4-0001431240)
- There are still too many “Request Header Or Cookie Too Large” errors!
- Login timeout even when actively using the portal!
- Search results do not prioritize recent and most viewer content (example, search for “CPU October 2025” – it does not give KB795208 which is a top50 document)
- Internal links are not working (low priority)
UX related issues
- Choose sections to have in front page
- My Favorites + My last viewed searches are important for me in first page
- Archived Service Requests are not important to me in first page
- The Search box should be visible on every page, without need to return to the Home!
- Some text overflows the defined column and cannot be read (see KI35841)
- Instead of having two columns (left column with Title, DocID, Last Updated, Service | right with Doc text)
- better would be two cells, top cell with content of the left column, followed by bottom cell with text
- both cells would have 1296px width, which would give more place for tables (and the document title in top)
E-Mail related issues
- SR update emails do not have the “Title” of SR neither information the “Tenancy” the SR relates. As consultant I’ve about 50 CSI/Tenancies and this is important to prioritize my work
- SR Creation and Update emails do not have the information about the “Tenancy”.
I’m sending this information also by email to my contacts at MOS, hoping it helps prioritizing the issues.
