Hello All,
Apologize if this is in the wild already. I wasnt able to find the answer.
When I log into the root container and do an alter session set container=diff_pdb;
Is there a way/setting to see where I am on the editor or on the screens? Not an oracle command but similar to how my toad tabs say my connection name.
I ask because I can run
alter session set container=diff_pdb; ran with ctrl+enter and that editor is in diff_pdb.
Then in the same editor I can run sho con_name as script and it will show cdb$root. I understand why but just trying to figure a way to visually know.
Thanks
Dave
Depending on your settings, Toad may launch separate sessions to the database, all within a "connection". So if you go into the Editor and run an "alter session", it may only apply to that Editor tab.
The best way to change containers is to right-click on the connection button and do it from there. When you do it that way, 1) Toad will display the container that you've changed to on the connection button, and 2), if Toad launches any other sessions within that connection, it'll make sure those are also on the right container.
In the screenshot below, I've changed containers in this way, and you can see the container name on the connection bar button as well as Toad's title bar.
cool thanks.
Looks like the schema browser acts odd. Do privs carry through?
I opened a new schema browser and I can see all the objects in that container from the sys views but when i click on a specific table I get table or view does not exist.
I log directly in or do alter session I can see the data in the tables.
Thanks
Dave
Hi Dave,
I just tested it here and didn't have any problem viewing data in a table that exists only in the pluggable that I switched to.
Then I looked here.
That first option - "Execute queries in threads" was unchecked, so I checked it, then closed and re-opened the schema browser, and I was able to reproduce the problem. This is a bug. 
That separate session (used for the data grid) is not getting the "alter session set container" command after all. I will fix this today so the fix will be in the next beta.
If you uncheck that option, it will work as expected. Sorry about that.
no worries, thanks for looking into it.
Here's a workaround, if you want to leave "Execute queries in threads" checked:
- Make your initial connection to the container
- Go to Schema Browser. Select any table and go to the data tab.
- Right-click on the connection bar button and change to a pluggable.
- Refresh the Schema Browser with the button circled below.
- Browse to whatever schema/table you want in the schema browser and now the data tab will work.
ok, I think I ended up doing that setting to keep from locking up my session but I forget.
I do a set and forget lol
WOW! I have only ever used an "alter session..." within an editor window, and I had no idea that under some conditions it might not affect the entire Toad "session". I do not use threaded queries, but it is good to know that it might be a problem. I will let my peeps know.
Cheers,
Russ
If you make your settings as shown, there is only one Oracle session for each connection from Toad, and it's not a problem.
1 Like
my question would be.
If I have a query that runs for 10 mins will that lock up my toad program? I had issues with that in older toad versions and wasnt sure if that was fixed in an update or it was a fix because of a setting change.
I feel I received a recommendation on that setting from a toad forum 
yeah, there would be a modal dialog with a cancel button in that case. We can only run one SQL at a time per session. That's why the "threaded" option launches a separate background session, and that's why the modal dialog otherwise.
1 Like
