Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
ALL-IN-1 V3.0 I have a customer that is asking about the OA$LOG:OA$DAF_ERR.LOG file that has recently appeared. In this file he has similar error messages to ours: DAF Record Error Log NBS Date Drawer DAF Record 1994020409523032 [LIDDLE.LC]STEERING COMMITTEE [.DOC9]ZVBOE0AAO.WPL Error: target record currently locked by another stream 1994020409574522 [LIDDLE.LC]STEERING COMMITTEE [.DOC9]ZVBOE0AAO.WPL Error: target record currently locked by another stream 1994020410061975 [LIDDLE.LC]STEERING COMMITTEE [.DOC9]ZVBOE0AAO.WPL Error: target record currently locked by another stream 1994020410090575 [LIDDLE.LC]STEERING COMMITTEE [.DOC9]ZVBOE0AAO.WPL Error: target record currently locked by another stream When is the file created, what does it log and is any action required on these messages, Thanks, Richard Simpson.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3853.1 | IOSG::MAURICE | I left my heart in Alcatraz | Mon Feb 07 1994 11:48 | 20 | |
Hi, These errors are logged when the DAF code fails when accessing a DAF record. The error logging was primarily put in for the SDAF (system DAF) records since they can be large, and there is the possible of sufficient contention that accesses would fail. But this is not what's happening to you. It's the first time I've seen this error reported against a PDAF (private DAF). It looks like your customer has an application that is accessing a document in such a way that the normal document locking controls have been bypassed. I recommend that the customer determines the document, and then finds out which application(s) are accessing it. To find the document you could do: <for first cab$ with .filename <=> "ZVBOE0AAO" do get .%key Cheers Stuart | |||||
3853.2 | WAYOUT::TALBOT | Trevor Talbot | Mon Feb 07 1994 15:51 | 13 | |
Hi Stuart, I am not convinved about the 'other' application locking these records, the reason for my doubt is that we have a file in oa$log also holding information relating to Pdaf, and we don;t have 3rd party apps. running! Could it be that the stream being locked, could be caused by 2 slave FCVR processes that just happen to bump into each other on an account that is common to each run? I.E the slaves think they run on different disks but the logicals etc are finally translated out to the same disk? -Trev | |||||
3853.3 | IOSG::MAURICE | I left my heart in Alcatraz | Mon Feb 07 1994 16:31 | 9 | |
Hi, You can easily determine if it's the FCVR by looking at the time stamps. What was running at 1994020409523032 (9:52 am on 4th Feb) for example? Cheers Stuart |