We've experienced an issue using UNIQUEKEYS on a Solaris server where duplicates keys can be generated, and I'd be interested is anyone else has encountered such as issue.
We were initially interested in using UNIQUEKEYS to update log files of daily transactions, but it became clear that some records were being overwritten. I wrote a simple program to generate UNIQUEKEY keys, and after writing a file of over 60 million keys, none were duplicated. So, I changed the program to just write 100 keys each time it ran, and placed it in the login proc for a user account. This way lots of users were each contributing 100 keys to the file. After a week, we had about 4 million records, with about 14,000 duplicates. Under each duplicated UNIQUEKEY record I recorded the date, time, @PID and TIMESTAMP(). For example, for one duplicate, the values returned were.. Key= AAAvJoAAAAAAAADE... Date Time PID TIMESTAMP 15978 38483 12070 1317246083.4399 15983 54802 12070 1317694402.2317 Its interesting that the PID was the same.. I haven't yet tried testing this on a RH/Centos server to see whether a similar behaviour can be shown. For us, we're a bit more cautious about assuming that UNIQUEKEY keys are always unique, at least on Solaris. -- Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
