Don't forget that your sequence and PLB code could be out of date as well!

Generally, it is not lost and can be simply added to the backup machine by
copying the files named /opt/fox/ciocfg/<cmpdName> from the "real" system to
the "test" system.


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 


        -----Original Message-----
        From:   [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
        Sent:   Friday, April 06, 2001 1:46 PM
        To:     [EMAIL PROTECTED]
        Subject:        RE: Failed SaveAll -- the rest of the story

        Thanks to all for all of your helpful suggestions.

        Thanks to Alex for offering to examine my control database.
Unfortunately,
        his prognosis ("It's fried!") was not what I wanted to hear.

        Thanks to Bo for his suggestion of using check_db_sync. I didn't get
around
        to using it, but I'll have to make a note of checking into it before
the
        next disaster drill. (And despite Bo's misgiving about automating
the
        SaveAll job, I'll continue running this weekly job. I just have to
do a
        better job of raising awareness among our group as to all the things
I'm
        doing behind the scene. And to just say no!)

        Here's how we fix our problem:

        I'm fortunate to have the old hard drive for the host AW still
sitting
        around since the last upgrade. Even though it was at v6.1, it's good
enough
        for our purpose. I booted it up in an off-line node along with the
CP in
        question (20CP02). I then did a LoadAll using a good SaveAll from
two weeks
        back. Then it's just grunt work of comparing the list of blocks in
the
        compounds between the off-line CP versus the real-life CP. We had to
delete
        a compound and add a block to another compound to make the off-line
CP match
        the on-line one.

        At that point, I copied all of the files in /opt/fox/ciocfg/20CP02
(workfile
        and all the .O files) from the off-line AW to the real-life system,
did an
        upload and shrink. Then I  verified that we now could do a SaveAll.
I
        further verified that that SaveAll is good by loading it back to the
        off-line CP. Everything is hunky-dory without having to initialize
and
        reboot the CP.

        Hope this may be of help to somebody who may end up in the same dire
strait
        some day.

        Regards,

        Duc

        -- 
        Duc M. Do
        Process Control Systems
        Dow Corning, Carrollton Plant
        Carrollton, KY, US

        
_____________________________________________________________________
        This message has been checked for all known viruses by the 
        MessageLabs Virus Control Centre. For further information visit
        http://www.messagelabs.com/stats.asp


        
-----------------------------------------------------------------------
        This list is neither sponsored nor endorsed by the Foxboro Company.
All 
        postings from this list are the work of list subscribers and no
warranty 
        is made or implied as to the accuracy of any information
disseminated 
        through this medium. By subscribing to this list you agree to hold
the 
        list sponsor(s) blameless for any and all mishaps which might occur
due to 
        your application of information received from this mailing list.

        To be removed from this list, send mail to 
        [EMAIL PROTECTED] 
        with "unsubscribe foxboro" in the Subject. Or, send any mail to
        [EMAIL PROTECTED]

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to