Running with F5, the "ScriptRunner Task" in the top of the SQL Worksheet and in the Script Output tab and the "ScriptRunner Task (Running)" in the Task Progress window all stop after 660 seconds.
begin dbms_lock.sleep(660); end; /
Are you sure that it isn't something outside of SQL Developer that is closing your connection (ie SQL Net or resource limit or something)?I am sure. I run on this machine only the SQL Develeoper.
Before you cancel the ScriptRunner, but after you think it has stopped working, does Oracle Manager (OEM?) show that your SQL Developer is still connected?OEM shows me that the SQL Developer is not conncted to the Database. And in the process curve I see that my anonymous block is done.
Just came across this, it might solve the issue.
The firewall might drop inactive jdbc connections to the database server. However, the OC4J instance cannot detect that the firewall has timed out the connection to the database.
Oracle Net can be configured with Dead Connection Detection (SQLNET.EXPIRE_TIME) to workaround this problem. Set EXPIRE_TIME on the database server to a value less than the firewall connection timeout so that DCD keeps the connection to the database alive. See Note 151972.1 "Dead Connection Detection (DCD) Explained". Since this is a setting configured on the database server, not on the midtier, it will apply for all database connections (OCI and thin JDBC).
- Disable or increase the idle timeout parameter of the firewall.
- Configure the TCP Keepalive time setting on the database and on midtier servers to a value less than the firewall connection timeout. After setting the TCP Keepalive time, the machines will send repeatedly a null packet after the minutes specified to keep the connections alive. As the packet is sent every time inside the firewall idle timeout, the connection will not get closed.