Omnis Data File issues
Marc De Roover
omnis1 at arcict.com
Sat Apr 3 08:12:44 UTC 2021
Thad,
If you want I can ask Nick to send you the test library we use to
stress-test a new ODB installation especially in respect to record
locking.
Regards,
Marc
On 2 Apr 2021, at 15:14, Thad Bogert wrote:
> Hi Stefan,
>
> I am not entirely sure about the locking. But messages.txt (logging
> is set to 2) does show the following when the application sets the
> main file at startup:
>
> Client IP = 192.168.59.5: Omnis Bridge Error: Specified byte/byte
> range lock was not found
>
> The odd thing is that none of the files are read/write at that point.
> I also found and old list post that stated that this error isn’t
> necessarily an indicator of an issue. Perhaps it does?
>
> I tried logging level three previously, but it produced a significant
> amount of information about every DML operation, but nothing that
> would give indication of an issue. I may try it again.
>
> If locking was was an issue, do you have any thoughts about how to
> address it?
>
>
> Hi Kelly,
>
> I am using the latest version of Studio. 10.2 29818
>
>
> Thanks everyone,
>
> Thad
>
>
>
>> On Apr 2, 2021, at 4:34 AM, Stefan Csomor
>> <csomor at advancedconcepts.ch> wrote:
>>
>> Hi
>>
>> Am 01.04.21, 23:42 schrieb "omnisdev-en im Auftrag von Thad
>> Bogert" <omnisdev-en-bounces at lists.omnis-dev.com
>> <mailto:omnisdev-en-bounces at lists.omnis-dev.com> im Auftrag von
>> thad at technosolver.com <mailto:thad at technosolver.com>> :
>>
>> 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.
>>
>> Just a shot in the dark : did you test whether record locking still
>> works at all in this configuration, if not - then these errors would
>> be the consequence ...
>>
>> Best,
>>
>> Stefan
>>
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com
>> <http://lists.omnis-dev.com/>
>> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>> <mailto:omnisdev-en at lists.omnis-dev.com>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
More information about the omnisdev-en
mailing list