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

Conference iosg::all-in-1

Title:ALL-IN-1 (tm) Support Conference
Notice:Please spell ALL-IN-1 correctly - all CAPITALS!
Moderator:IOSG::PYECE
Created:Fri Jul 01 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2716
Total number of notes:12169

2647.0. "Error reading from Partition file" by KERNEL::BURDENI () Thu Apr 24 1997 14:12

    I have a customer with the following problem within ALL-IN-1 3.1 on an
    Openvms 6.2 system.
    
    When running the Housekeeping procedure TRM, the following happens.
    
    
    %START_BATCH-I processing completed ok for %START_BATCH
    %SMJACKET-I Invoking Utility command file "OA$LIB:OA$SM_FCVR_SCHEDULE.COM"
    Previous value of OA$FCVR_FILES has been superseded
    
    %OA-I-LASTLINE, 12:09am
    %OA-I-LASTLINE, 12:09am
    ALL-IN-1 File Cabinet Verification and Repair Program
    =====================================================
    
    Version 3.1-10
    Error reading from Partition file
       ?Illegal file name 
    Terminating program
    %SMJACKET-I Invoking common END_BATCH procedure
    %END_BATCH-I Performing End batch job procedures for "TRM"
    
    
    Can anyone give me any pointers as to what I should be looking at for
    this one.  They have no other problems reported on this system other
    than the failure of this Housekeeping job.
    
    Many Thanks
    Ivan.
T.RTitleUserPersonal
Name
DateLines
2647.1First thing to tryIOSG::STANDAGEMy hovercraft is full of eelsThu Apr 24 1997 14:2717
    
    Ivan,
    
    The FCVR procedure is looking in the PARTITION.DAT to get the drawer
    uid and device name for each drawer on your system in order to perform
    the checks/repair. I can't remember if the log file outputs each drawer
    as it works on it, if this is the case then you might have sone rubbish
    or corruption at the very beginning of this datafile. If the log file
    doesn't log each drawer as it works on it then the 'corruption' might 
    be a little more tricky to find.
    
    I'd start with a DUMP/REC of PARTITION.DAT and see what the first
    record looks like...
    
    -Kevin.
    
    
2647.2MAIL1::KMAHERHay amores que son rosa y son espinasThu Apr 24 1997 21:041
    you might also try reseeding the partition.
2647.3IOSG::PYEGraham - ALL-IN-1 Sorcerer's ApprenticeFri Apr 25 1997 17:136
    But note that .2's suggestion will either only rewrite the records for
    MAIN drawers, or if you recreate the partition file, it will lose the
    partition records for all the other drawers.
    
    I presume that ANAL/RMS of the file didn't show any basic errors in the
    structure?
2647.4DowntimeKERNEL::BURDENIMon Apr 28 1997 19:106
    Unfortunately, it is a problem getting All_IN-1 downtime on this sytem
    to check the PARTITION.DAT, (open files), I am getting the customer to
    schedule some downtime in the not so distant future.  Many Thanks so
    far.
    
    Ivan
2647.5Reseed seemed to workKERNEL::BURDENITue Jun 03 1997 19:496
    This problem seems to fixed, as the latest logs for TRM are showing no
    errors.  I can only assume that the removal of the top record in
    partition.dat and the subsequent reseed cleared the error.
    
    Many Thanks
    Ivan.