I was tuning a query that was running on Instance 1. I was connected to Instance 2 and I ran the same query (and got a slightly different execution plan).
Went back to session browser to look at execution plan on Instance 1 using DBMS_XPLAN display mode, what I actually saw was the plan I just generated on Instance 2 (same . I usually forget that DBMS_XPLAN cannot show plans from the other Instance, but I usually get an error that it couldn’t find the SQL_ID. In this case it did find it and displayed it just fine, though it wasn’t the plan I was expecting. Took me a bit to figure out why the Tree display and the DBMS_XPLAN display were different.
Can Session Browser be smart enough to tell me DBMS_XPLAN should not be used because I’m connected to the wrong Instance? Would be nice to be able to use DBMS_XPLAN regardless of what Instance I’m currently connected to, but that’s really an Oracle issue, unless you all have some inventive method to overcome their shortsightedness :).