TOracleEvent
- Thread starter jeff
- Start date
If you are using Oracle8 8.0.4 or 8.0.5, see FAQ: The TOracleEvent does not work properly .
If you are using alerts, it can also be that an uncommitted signal exists that locks it.
If you are using alerts, it can also be that an uncommitted signal exists that locks it.
Is there a way to override this wait? I mean - if a user shuts my application down, I don't want to wait for uncommitted signals, I want to shut down the whole application.
Maybe it helps to logoff the session? Or that maybe causes a call to TOracleEvent.Stop as well? Anyway, I think TOracleEvent.Stop should stop the waiting immediately, not caring about uncommitted signals.
Thanks for the reply. We are using 8.05 and are uping it to 8.06. Funny thing is that we are using these versions because we noticed that under the latest 8i connecting to the database was taking as much as 30 seconds. This is not just with DOA but also with SQL Plus.
Has anyone else had this experience? We think it has to do with the latest Java support added to 8i.
Has anyone else had this experience? We think it has to do with the latest Java support added to 8i.
We did experience this problem and lots of others relating to DBMS_ALERT with Oracle 8.0.4 (in fact alerts just don't seem to work with this version of Oracle). In 8.1.5 we had no problems at all.
One way we found to fix the problem was to set a timeout on the OracleEvent component and call the Start method in the OnTimeOut event (I thin this periodically synchronises the waiting thread with the main thread).
One way we found to fix the problem was to set a timeout on the OracleEvent component and call the Start method in the OnTimeOut event (I thin this periodically synchronises the waiting thread with the main thread).
Regarding long connect times we found a very interesting problem recently:
New versions of the Oracle client include the following in sqlnet.ora:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
with this present, the clients when running again some of our Oracle servers (not all) experienced major delays in logging on (also we got lots of security errors logged on the server).
Commenting this out this line resolved the problem (put a # in front of the line).
Hope this helps.
New versions of the Oracle client include the following in sqlnet.ora:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
with this present, the clients when running again some of our Oracle servers (not all) experienced major delays in logging on (also we got lots of security errors logged on the server).
Commenting this out this line resolved the problem (put a # in front of the line).
Hope this helps.
Similar threads
