I've noticed a few posts out there, but it doesn't seem like anyone has come across a fix. Posting here to see if maybe I'm missing something.
Our problem is, on our Ora9.2 database, the first query that is run is stuck on Initializing... for 10-60 seconds before the query runs. In SQL*Plus, this does not happen. Also, this does not happen when logged into an Ora 8.1.7.4 Database via PL/SQL Delveloper. Other posts I have read suggested tweaking the PL/SQL Developer Preferences, but all of the following attempts have resulted in the same error:
PL/SQL Developer Preferences: Single Session, Multi-Session, Dual Session, OCI Library autodetect, OCI Library fixed (C:\oracle\ora904DS\bin\oci.dll), connect via sqlnet.ora/ONames, connect via tnsnames.ora entry, etc. This is only happened the first time a query is run in the SQL Window. After it hangs up, it runs normally. I also did a SQL level trace, and it looks like this is the statement that is hanging things up:
It looks like this could be part of the problem:
select value
from v$sesstat
where sid = :sid
order by statistic#
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.01 0.01 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 1 12.17 13.02 0 0 0 0
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 3 12.18 13.03 0 0 0 0
thanks,
Ryan.
Our problem is, on our Ora9.2 database, the first query that is run is stuck on Initializing... for 10-60 seconds before the query runs. In SQL*Plus, this does not happen. Also, this does not happen when logged into an Ora 8.1.7.4 Database via PL/SQL Delveloper. Other posts I have read suggested tweaking the PL/SQL Developer Preferences, but all of the following attempts have resulted in the same error:
PL/SQL Developer Preferences: Single Session, Multi-Session, Dual Session, OCI Library autodetect, OCI Library fixed (C:\oracle\ora904DS\bin\oci.dll), connect via sqlnet.ora/ONames, connect via tnsnames.ora entry, etc. This is only happened the first time a query is run in the SQL Window. After it hangs up, it runs normally. I also did a SQL level trace, and it looks like this is the statement that is hanging things up:
It looks like this could be part of the problem:
select value
from v$sesstat
where sid = :sid
order by statistic#
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.01 0.01 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 1 12.17 13.02 0 0 0 0
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 3 12.18 13.03 0 0 0 0
thanks,
Ryan.
