Client caching

Hello,

Hopefully this is the right place to ask this question.
This week, we started on upgrading to Open Enterprise Server on Netware.
The new NSS "broke" some poorly written application that uses a
TopSpeed database (never heard of that one before). It appears that when
we move the DB files to a traditional volume, the app starts working
again. After some digging in the KB, I found that when you enable client
file caching on the server and the client, the app starts working when
run off the NSS volume.
So my question is actually, is turning on "client file caching" safe or
are there things to watch out for, for instance with .xls or .mdb files?
Thanks for any insights,

Roland

  • We have experience similar issues.

    I don't know what version of NetWare you've upgraded from, but earlier
    versions of NetWare used to ship with this disabled, along with
    Opportunistic Locking.

    We had problems when we upgraded because the default change to 'ON' and
    we didn't realise.

    Despite all the TID's and fixes, neither of these has ever worked in
    our environment and we set our servers thus:

    SET CLIENT FILE CACHING ENABLED=OFF
    SET LEVEL 2 OPLOCKS ENABLED=OFF

    The client setting doesn't matter too much, as it can only work if
    enabled at the server.

    I had to disable OpLock again last week on a new OES box we installed.

    Maybe worth a try?


    --
    guerandel
  • Guerandel,

    It looks like by default on our servers the settings are:
    caching: off
    op lock: on

    Not sure if that's like that before the upgrade, but some servers that
    haven't been migrated yet, seem to have the same settings. This
    indicates that something changed in NSS that "breaks" this database app.
    Turning on caching is in this case a solution, but I was wondering if it
    can have any negative impact on other programs, like word/excel/access?
    Thanks,

    Roland

    guerandel wrote:
    > We have experience similar issues.
    >
    > I don't know what version of NetWare you've upgraded from, but earlier
    > versions of NetWare used to ship with this disabled, along with
    > Opportunistic Locking.
    >
    > We had problems when we upgraded because the default change to 'ON' and
    > we didn't realise.
    >
    > Despite all the TID's and fixes, neither of these has ever worked in
    > our environment and we set our servers thus:
    >
    > SET CLIENT FILE CACHING ENABLED=OFF
    > SET LEVEL 2 OPLOCKS ENABLED=OFF
    >
    > The client setting doesn't matter too much, as it can only work if
    > enabled at the server.
    >
    > I had to disable OpLock again last week on a new OES box we installed.
    >
    > Maybe worth a try?
    >
    >