TDP 3.2 connection timeout issues with Oracle 11gR1 database

Toad Data Point & Toad Intelligence Central
1

I start getting the following error after leaving Toad idle with a live connection for some period of time, say 30 minutes, on a WinXP SP1 machine:

  • ORA-12151: TNS:received bad packet type from network layer

I’m using Toad Data Point 3.2 and connecting to a remote (off-site) Oracle 11gR1 (11.1.0.7.0) database, using the full 11gR2 (11.2.0.1) client. The same issue occurs when using Toad Data Point 3.3 and I believe I used to see this problem when using Toad for Data Analysts 3.1.

I never see this error when running Toad for Oracle 11.5 against the same database from the same workstation.

Sometimes browsing other tables can clear up the problem. Sometimes it requires a database re-connection. And other times a full application re-start is required.

Can someone from Quest attempt to verify this issue and see about getting it working better in TDP 3.3?

Thanks,

MJ

2

Do you have any resource restictions on your connections? Such as closing after a specific amount of time?

Our code is suppose to check everytime we use a connection to see if it is open. If it is not open then we are to reconnect. So if we have missed a spot where we should be checking that is one issue.

But since you are getting “received bad packet type from network layer” you have an open connection but a packet got corrupted or something. I am not sure what we can do about this, as network traffic of packets is managed by the Oracle client.

One idea might be to turn on Oracle trace and have your administator look into the trace file when the error occurs. That may give us more details on what is occuring. But again, this issue is in the Oracle Client.

Debbie

3

I don’t believe I have any resource restrictions on the connection.

I will see about getting an Oracle trace log going.

As mentioned previously, I don’t see any problems of this nature with Toad for Oracle 11.5, using the same Oracle full client.

Several people in my office have been running into this issue.

Another Oracle error message we’re seeing is:

  • ORA-03106: fatal two-task communication protocol error

  • MJ

4

I have not found much about ORA-03106: fatal two-task communication protocol error – it is Oracle’s internal message and users should not see it. Oracle suggests contacting customer support.