Conference iosg::all-in-1_v30

3919.0. "PAT failed to backup document savesets" by KERNEL::VANRIXTELE (Emma van Rixtel) Wed Feb 23 1994 19:39

    
    
    I have a customer who is trying to transfer an account using ALL-IN-1
    V2.4 to a remote node, but it keeps failing with the following error..
    
    "USER unable to backup the documents saveset"
    
    In the error log, the only error that appears is just as it starts to
    prepare users filecab..
    
    %BACKUP-W-NOFILES, no files selected from
    		OA$TRANSFER:[OMULLANE_J.OMULLANE_J]DOCUMENTS_*.DCK:*
    %BACKUP-W-NOFILES, no files selected from
    		OA$TRANSFER:[OMULLANE_J.OMULLANE_J]DOCUMENT_REF.DAT;*
    %BACKUP-I-STARTDELETE, starting file deletion pass
    %BACKUP-W-NONEDEL, no files processed on deletion pass
    
    I have got him to check the OA$TRANSFER:[OMULLANE_J.OMULLANE_J] and
    there is one directory, DOCUMENTS.DIR which is empty and then 2 other
    files; OMULLANE_J.REPLY and ZDOCUMENTS.BCK which are also both empty.
    
    He has tried the transfer twice, the first time it failed only some of
    the documents were in an archived state, so he restored the account
    from backup and tried again, this time none of the documents were
    archived and the account can still be used.
    
    I can not find any other articles which are similar to this and I don't
    know what else to suggest, so if someone has come across this before
    could someone please give me some pointers!
    
    Thank you,
    
    Emma
    

    Check the easy ones first - I suppose ...DOCUMENTS_*.DCK:* 
    is a typo?                                                     ^
    Transfers using V2 were notoriously unreliable...and usually not
    recoverable. The message you are seeing is coming from either 
    MUA_PAT.COM or SM_PAT_SWITCH_SAVESET.COM and is OA$_SA_PAT_F_BCK_DOCS. 
    The errors you are seeing probably come from the command:
    $backup/delete 'arch_savesets' 'doc_saveset' /saveset/owner=parent in
    MUA_PAT.COM.
    I'm sorry that we don't have a V2.4 system running here to try this. We
    are also all very busy working on future releases. Perhaps you could
    get your customer to set verify on the relevant portion of MUA_PAT.COM?
    One other thing to try is to check whether something strange is
    happening because of the particular username (O'Mullane? - affecting
    parse user?)
    DaveT
    
    
    

    
    	The BACKUP command is failing to select any files from the
    	directory it uses during the PAT. That either means there
    	were no documents in the directory (there was a known bug
    	that you couldn't PAT a user with no documents, only messages,
    	in V2.4), or that the /SELECT clause is wrong and is passing
    	over all the documents in the directory. I have seen both
    	problems occur, but that was 3 years ago during V3.0 development
    	so I'm afraid I don't remember exactly what caused it.
    
    Regards,
    Paul