Omnis Data File issues

[Das Goravani]

Sounds like Big Sur doesn’t like the databridge. All other parts have alibis, used to work. 

As an aside I have converting to SQL worked out to it’s lowest easiest way.. has been used by me and 1 other by now.. but you’re an expert on that.. using SQL and staying in the CRB for least amount of conversion work. If you want to use my stuff just let me know. 

M1’s give all kinds of little errors on Omnis presently.. would suspect that if you hadn’t taken it out and used an Intel Mac and got the errors there too.. would definitely suspect the M1 then.. 

Runtime and Big Sur and Databridge, something is up. Runtimes used to work.. Big Sur seems to be the culprit. 



> On Apr 1, 2021, at 2:41 PM, Thad Bogert <thad at technosolver.com> wrote:
> 
> Hi All,
> 
> I am experiencing a perplexing issue that I hope someone might be able to shed some light on.
> 
> We recently deployed an orphaned application that we converted from Studio 6 to Studio 10.2 so that the client could use the application on 64bit MacOS machines.
> 
> The converted application uses a two segment datafile that is being shared via ODB 1.75. 
> 
> The issue that we are experiencing is that when users with runtimes connect to the database, they are occasionally presented with the following errors:
> 
> •Bad file number passed to data manager.
> 
> •An error occurred locating a header record for a slot.
> 
> •Communication error on connection 
> 
> The interesting thing is that if I connect using the Studio SDK, the errors don’t occur. However, if I serialize that SDK as a runtime, the errors return.
> 
> The ODB is on an M1 Mac; which made me wonder if there might be compatibility issues.  But the same errors occur when it is shared from an Intel Mac. Almost all of the Macs are running Big Sur.
> 
> I have tried rebuilding the datafile, however it did not resolve the issue.
> 
> At this point, I am at a loss as to what could be causing the issue.  A similar configuration with Studio 6 and an ODB worked there for years without any issues.
> 
> My final thought is that there might be something network related. The client is going to try replacing the switch to see if it makes any difference.
> 
> 
> Other than going on site and reviewing their configuration, does any have any thoughts as to what might be going on?  Omnis support has not been able to provide any insights into the issue.
> 
> 
> Thanks,
> 
> Thad
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com