"not connected to ORACLE" when re-executing a report

[Worker]

I usually have one instance of PL/SQL Developer open all day. In it, I have a report open that I randomly re-execute with different values. This report is set up with its own connection parameters and it does not use the 'normal' PL/SQL Developer session.

If I don't execute the report for a long time, the connection apparently times out because I get a "ORA-03114: not connected to ORACLE" error when I try to execute it. Once that happens, the only way to fix it is to close the report and re-open it.

Would it be possible (and a good idea) to have reports automatically reconnect?

 

[Marco Kalter]

We'll fix it by checking the connection before executing the report, and re-establishing it if necessary.

 

[Worker]

With (I assume) work currently going on for version 6.1, and our service contract for 6.0 running out earlier this month, what are the odds that this fix still makes it into a 6.0.x version?

(As if I won't try to bug the people in charge to pay up for 6.1 )

 

[Marco Kalter]

I'll see what I can do to incorporate it into the upcoming 6.0.6 patch release.

 

[Worker]

Wonderful! Thank you very much.

(Even if you can't fit it in, thank you for trying.)