Creating plan baseline from AWR in PDB
Target database is 19.22 single-tenant on Exadata and OEM is 13.5 RU21.
Today we had a query change its plan. I found the query in OEM (ASH Analytics) and ran SQL Tuning Advisor on it from OEM. The tuning results showed the bad plan was in the cursor cache and the 2 much better plans were in AWR which is in the CDB.
Still in OEM, changed the context to the CDB, and added the SQL_ID to a SQL Tuning Set. From there, was able to chose the better plan and add to a plan baseline.
This is where things went sideways…