Devart Forums

Hello,

Our firewall tells us our application compiled with ODAC 6 is opening a second listening port.

Compiled with the previous version ODAC 5.80 our application is only opening one port.

We use no oraalerter component, only Toraquery and Torastoredproc.

What is the second listening port usefull for ? Is this by design ? can ODAC 6 still work with one port ?

Thanks

Set the OCIEvents variable from the OraCall unit to False in the initialization section of one of your program units.

Thank you.

Your solution is working well, the second port is closed now.

Just one question. Can you tell me wich feature or components require OCIEvents set to True ? Just in case we might want to use it someday.

Best regards

The OCIEvents variable must be set to True if you are using the TOraChangeNotification component or the AsyncNotification property of the TOraQueue component.

Wouldn't it be a better way, to deactivate this by default, and activate it only when TOraChangeNotification or TOraQueue are used?

Greetings
Jens

The OCIEvents variable should be set before the first connect to the database. We cannot detect at this point whether the TOraChangeNotification or TOraQueue component will be used.

What about adding this to the initialization part of the units of OraChangeNotification and TOraQueue.

So it's only be done, if the unit's are added to the app.

In the next ODAC build the OCIEvents will be enabled by default only starting with Oracle client 10.2 (it does not have the bug with opening a second port), or if the OraAQ unit is used in the project.

We have a similar problem, but in .net.

Currently we use version 6.00.0.4 of the ODAC for VCL, and are setting OCIEvents := False; in code which prevents the windows firewall from popping up.

Now we are starting to use ODAC.NET version 4.30.20.0, and have the same problem. What is the equivalent solution in .NET ?

Do you mean OraDirect.NET ?

Sorry, I do mean OraDirect.NET .