Is there a possibility that the consumer is opening and processing through a file that is being reopened in the creator? There might be some weird OS timing issues in that situation.
We ran into this a while back with our credit card server; for drop file interfaces we had to follow a specific protocol for moving data between the creator and consumer: 1) Create the file under a temporary name; 2) After the file has been closed, rename it to a name suitable for the consumer. And then for the consumer, it was coded to skip over files with the temporary name. This completely eliminated any conflicts like this. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anmol Chandrakant Khopade Sent: Tuesday, July 19, 2005 5:01 PM To: [email protected] Subject: [U2] DATABASE write problem Hi, I am facing a problem wherein a "WRITE" operation to a type 19 file is failing in some cases. The call to STATUS() function within the ON ERROR clause returns error 40019. Strangely this problem does not occur for all the writes operations, but approximately 100 times (out of 60K write operations). The record id contains the current time, so it doesn't seem to be an issue of 2 concurrent writes using the same record id. A point to note that this file has read and writes happening simulatneously i.e. A process keeps writing records, while the other process keeps on polling this file to read the records. Any pointers to the below points will be highly appreciated 1. Documentation where the error number can be looked up (40019 in this case) 2. If anyone has encountered a similar problem with write operation on a type 19 files, and has a solution, it would really help. Thanks in advance Warm regards Anmol **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.9.1/51 - Release Date: 7/18/2005 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
