| DBMS_ALERT [message #50818] |
Tue, 09 April 2002 06:41  |
Doug
Messages: 7
Registered: May 2001
|
Junior Member |
|
|
|
DBMS_ALERT looks like a great choice for asynchronous data movement. We want to use it. Problem is DBMS_ALERT.SIGNAL is too slow. It takes about 4X the time for an SQL insert. We are AIX 4.3.3 Oracle 8.1.7.0. Does anybody else have this problem? Is that much overhead normal? I did open a tar with Oracle, no response yet.
|
|
|
|
|
|
| Re: DBMS_ALERT [message #50836 is a reply to message #50818] |
Wed, 10 April 2002 06:19  |
Doug
Messages: 7
Registered: May 2001
|
Junior Member |
|
|
|
I don't think so. The DBMS_ALERT.SIGNAL does not get sent until the commit, but the statement itself doesn't block. So I don't think I'm waiting.
|
|
|
|
| Re: DBMS_ALERT [message #57156 is a reply to message #50818] |
Fri, 23 May 2003 03:21 |
RCHU
Messages: 3
Registered: May 2003
|
Junior Member |
|
|
|
My experience with DBMS_ALERT is even worse. After we've upgraded to Oracle 8.1.7 from Oracle 8.1.6 we are getting intermittent "End of file on communication channel" during DBMS_ALERT.WAITONE(ID). Up to now, we are still trying to determine what could have caused this error intermittently, especially after a long wait such as more than 2 hours. This problem does not exist in Oracle 8.1.6.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
