Problems connecting to ODB with OmnisSQL

[Jef Leys | Desim]

Hi,

I use ODB 1.77 on a Mac mini OS X 11.6.4.  I (still) use Omnis DML. Omnis RT 10.2 versions 31315 & 30204.

When transferring to 1.77 I had the problem that the database could not be found at startup.  At startup the IP address and database name are being fetched from an INI-file in the omnis package.

A connection could be made by using the command ‘change database’ in my code.  The standard popup window would appear and a connection could be made.
It felt as if my network was too slow to find the ODB.  The problem occurred always when connecting through wifi

Setting the timeout to 100 solved it.  

Haven’t had any issues since.

Jef

> Op 8 mrt. 2022, om 11:43 heeft Reg Paling <reg.paling at lokanet.com> het volgende geschreven:
> 
> Hi Jef,
> 
> I can see from your previous posts that your issue was very similar to mine, but my socket timeout is already 120 so for me that must be not the cause.
> 
> Kind regards,
> Reg
> 
> 
> 
> On 1/3/2022 7:26 pm, Jef Leys | Desim wrote:
>> Hi
>> 
>> I solved this issue by increasing the socket timeout in the ODB connections config to 100.
>> 
>> Jef Leys
>> 
>>> Op 1 mrt. 2022, om 02:59 heeft Reg Paling <reg.paling at lokanet.com> het volgende geschreven:
>>> 
>>> Hi all,
>>> 
>>> Michael Houlberg mentioned in another thread:
>>> > Also, we’re having problems getting the other computers, other than the ODB host, to connect with the OmnisSQL DAM. Has anyone else seen problems here?
>>> 
>>> I am starting another thread because I am hoping that this issue might see a bit of discussion in its own right...
>>> 
>>> Yes Michael, I am having difficult-to-diagnose problems.  In my case, these problems occur when the workstation is configured to skip the logon window and just automatically open the datafile with saved credentials.  If I turn the Logon window back on, then the small delay or interruption thus created seems to avoid the problem.
>>> 
>>> I have put some sleep() commands into the logic and they seem to (maybe) reduce the frequency of the issue but they don't totally remove it.
>>> 
>>> Sometimes I will get a "table not found" error from OmnisSQL, sometimes it hangs in other ways.
>>> 
>>> On affected computers it happens 10% or 20% of the time and the rest of the time it starts up without a problem.
>>> 
>>> I am not sure it is due to ODB v1.77 - I think it is more a Studio 10.2 thing.
>>> 
>>> I have wrapped the logon in a repeat loop to try the connection again if it fails, but I can't always diagnose the failure.
>>> 
>>> Does anyone know exactly what this is?
>>> 
>>> Thanks,
>>> Reg
>>> 
>>> _____________________________________________________________
>>> Manage your list subscriptions at https://lists.omnis-dev.com
>>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com <mailto:omnisdev-en at lists.omnis-dev.com> <mailto:omnisdev-en at lists.omnis-dev.com <mailto:omnisdev-en at lists.omnis-dev.com>>
>> 
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com <https://lists.omnis-dev.com/>
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com <mailto:omnisdev-en at lists.omnis-dev.com>