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

Conference orarep::nomahs::dbms

Title:VAX DBMS
Notice:THIS NOTESFILE IS NOT A FORMAL SUPPORT CHANNEL
Moderator:SCARY::CHARLAND
Created:Thu Feb 20 1986
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2642
Total number of notes:11044

2029.0. "system-f-illpagcnt @ kod$get_vm + 3FB" by FINDER::JACKSON (Peter Jackson - UK CSC TP/IM) Tue Sep 14 1993 11:40

T.RTitleUserPersonal
Name
DateLines
2029.1yupCOOKIE::MEADPaul Mead, DBS Sustaining EngineeringTue Sep 14 1993 20:086
2029.2I wish I had a better memoryKERNEL::JACKSONPeter Jackson - UK CSC TP/IMThu Apr 07 1994 12:2111
2029.3corrupt rootDBSUK2::GRICEPhil Grice DBS Sustaining EngineeringThu Apr 07 1994 13:4211
2029.4KERNEL::JACKSONPeter Jackson - UK CSC TP/IMFri Apr 08 1994 06:269
2029.5Diff scenario...same error?M5::BLITTINThu Apr 10 1997 13:0624
    
    Have another incidence of this error.  However, the circumstances
    are a bit different.  Customer is migrating from, he believes, a
    3100 to a 7110 or 7010.  Both are running VMS 6.1 and DBMS 5.1-11.
    
    He just trying to restore his db to the 7000 and gets this error
    after the restore is about 2/3 complete.  Got the bugcheck.  Had him
    check the logical assignment and they appear to be ok.
    
    Now some info about the backup that he is using.  The remote site
    that has the 3100 does a DBO/BACKUP to disk. I suggested using
    DBO/BACKUP/MULTI to tape and told him it would be faster. The remote
    site has 8mm, and his site has 4mm.  To get a copy of the backup,
    he FTP'd the file to his site.  I'm thinking that his backup may
    be corrupt in some way...so he is going to try to restore just the
    area that the original restore failed on and if this fails, he will
    do the same thing at the remote site.  They have never restored 
    the db at the remote site...good practice, NOT, but are not having
    any problems running their applications (manman).
    
    A re-run of restore generates the same error in the same place.
    
    
    Any thoughts/suggestions appreciated....