[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

3755.0. "Error trying to share record" by MASALA::KCHICK (Ken Chick) Wed Jan 12 1994 12:00

Recently on our ALL-IN-1 V3.0 system we have been experiencing an *intermitent* 
error message when sending mail. 

ERROR trying to SHARE record

It will always work correctly on a second attempt.

Has anyone seen this before or have any ideas where to start looking?

Thanks


Ken
T.RTitleUserPersonal
Name		DateLines
3755.1Logical problem?IOSG::MAURICEI left my heart in AlcatrazWed Jan 12 1994 12:0610
Hi,

After the error press GOLD W to see the error message. Quite likely you will 
find that one of the shared area directories does not have a logical 
defined. For example it might be trying to write into directories 
OA$SHARE200 to OA$SHARE300, but OA$SHARE250 is not defined.

HTH

Stuart
3755.2More infoMASALA::KCHICKKen ChickMon Jan 17 1994 11:0414
I've checked out each of the cluster nodes for OA$SHAR logicals 
and they all check out OK 

I've managed to find the error message which is

 %OA-W-RECORD_IO_ERROR, Error occurred while attempting to SHARE the record   
 -RMS-F-CHK, bucket format check failed for VBN = 1850401 

any ideas?


Thanks

Ken
3755.3Corrupt SDAF?IOSG::MAURICEI left my heart in AlcatrazMon Jan 17 1994 13:5936
    Hi,
    
    I've never seen it before, but here's what the System messages manual
    has to say:
    
    CHK, bucket format check failed for VBN = 'nnn'
    
    Facility: RMS
    
    Explanation: VMS RMS detected a corrupted bucket in an indexed file.
    The bucket address check or bucket checksum is incorrect.
    
    User Action: Reorganize the file, if possible; otherwise, re-create the
    file.
    
    				-oOo-
    
    As the error points to an indexed file, I guess the file concerned is
    the system DAF. Which DAF it is you will know from the logical name:
    
    If it it's OA$SHARAnnn then OA$SHARA:OA$DAF_A.DAT
    If it it's OA$SHARBnnn then OA$SHARA:OA$DAF_B.DAT etc.
    
    I suspect $anal/rms will show some errors.
    
    Then you will need to run the file recovery utility, which CSCs have. 
    
    When you have got the file back into order then examine your backup
    procedures very carefully. The common cause of corruption is sites that
    backup their DAFs with /ignore=interlock, and then find that when they
    restore the file that it has corruptions.
    
    HTH
    
    Stuart