Hello,
When using the Dual session Session Mode, we've noticed that the code in the AfterConnect.sql script does not always fire.
To replicate the issue,
1) Open a new instance of PL/SQL developer, and choose a connection from the saved list of connections on the drop down
2) Create a new SQL window, and query the value set by the AfterConnect.sql script (in our case, we set up a value on a package)
Value is still null
3) Click on Session, Disconnect all sessions, then at the bottom of the SQL window, select a connection again.
4) Query the value set by the AfterConnect.sql script, it is now set as expected.
When using the multi session connection mode, this works as expected.
I have a screen recording of the issue, which can be shared on request,
We are using Version 14.0.0.1961 currently however this issue also happened on 13.
Thank you
When using the Dual session Session Mode, we've noticed that the code in the AfterConnect.sql script does not always fire.
To replicate the issue,
1) Open a new instance of PL/SQL developer, and choose a connection from the saved list of connections on the drop down
2) Create a new SQL window, and query the value set by the AfterConnect.sql script (in our case, we set up a value on a package)
Value is still null
3) Click on Session, Disconnect all sessions, then at the bottom of the SQL window, select a connection again.
4) Query the value set by the AfterConnect.sql script, it is now set as expected.
When using the multi session connection mode, this works as expected.
I have a screen recording of the issue, which can be shared on request,
We are using Version 14.0.0.1961 currently however this issue also happened on 13.
Thank you
Last edited:
