>We are running batch processes every night. From time to time we are getting an error updating one of our largest tables. Here is the error:
>“Cannot update the cursor CURSORNAME, since it is read-only”
>What is so bad about that problem is that cursor (table) is not read-only at all.
>That error usually occurs on the middle of update process. So a few hundreds of records have got updated.
>Can someone help, please?
>
>Thanks, Mark

Also try to run your update process from a different client PC to see if the problem follows. If it doesn't then there is some sort of configuration issue on the first pc. If it does you've eliminated that possibility. You might try running the batch process directly on the server rather than from a client to determine if the network has a glich.

If you are already running the batch process directly on the server - no network processes imbetween to worry about - then you might want to take a closer look at the server operating system settings. Or the server hard drive setup. Are you using RAID - or some sort of buffering system (hardware or software) for disk access to speed things up like special 'high speed' disk cards. Windows NT and 2000 server like to have the buffering turned on by default and it can cause problems for database systems that often close and reopen the same table(s)/file(s) unlike most other types of applications (i.e., MS did it to make those other applications appear to work faster rather than write them with cleaner code). I'm not a Novell guy but doesn't Novell have FILES issues (at least it used to) that needed to be tweaked for the maximum number of files you might have open at one time.

It's maddening when the operating system or network messes with your properly written code!