Re: [foxboro] Legacy Historians and Version 6.5

I have faced a similar problem that was related to informix but didn't 
crashed historian database. It gave problem with application object 
creations related to connoisseur based APC. The following was the scenario.
To add one WP51D on the node we committed AW51E which was already on Ver 
6.5. The commit was o.k. and the system added the WP51D successfully. After 
few days we shutdown the AW and restarted with 'boot -s' to make a tape 
backup. We successfully made the tape backup but when restarted the AW51 
everything was o.k except application object creation. Application object 
creation failed. As a result we followed the manual procedures to create 
application objects.
We had made several successful tape backups before but there was a little 
difference this time. The difference was that we totally shutdown the AW and 
started with boot -s. To confirm the problem with the procedure we followed 
the old procedure once again to make a tape backup. The old procedure didn't 
come up with application object creation problem. In normal tape backups we 
just shutdown the AW and enter into the single user mode during shutdown (do 
not go to complete shutdown). In this single user mode we make the tape 
backup and restart the system using reboot command.

Rgds,
Ali Ahmed Zahidi
Karachi, Pakistan.



>From: Teresa L Heckathorn <teresa.heckathorn@xxxxxxxx>
>Reply-To: foxboro@xxxxxxxxxxxxx
>To: <foxboro@xxxxxxxxxxxxx>
>Subject: [foxboro] Legacy Historians and Version 6.5
>Date: Tue, 20 Feb 2007 15:13:22 -0600
>
>Several Legacy Historians on our plant site have had corrupted database
>issues that have caused the systems to loose all data including
>configuration.  This has happened to five systems on site.  This phenomenon
>has only started happening since the systems were updated to version 6.5
>and up. The latest incident occurred when two historians running on 51B
>boxes totally erased their database.  Now we will be required to completely
>re-configure both historians.  Before the last incident, the historians
>were only partially corrupted.  This occurrence has happened on both 51B
>and 51E boxes.
>
>       We are theorizing that upon shutting down for a tape backup that
>something happens within the Informix system that is causing the database
>to get corrupted.  Corey Clingo has now written a script that will stop
>Informix as the system is shutting down.  We will need to wait and see if
>this will solve the problem.
>
>       We are theorizing something that was changed with Version 6.5 has
>started this phenomenon.  Is there anyone else out there in the Foxboro
>world that has had a similar occurrence?  And if you have, what did you do
>to fix it?
>
>
>Tracy Heckathorn
>BASF Corporation
>
>
>
>_______________________________________________________________________
>This mailing list is neither sponsored nor endorsed by Invensys Process
>Systems (formerly The Foxboro Company). Use the info you obtain here at
>your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
>foxboro mailing list:             http://www.freelists.org/list/foxboro
>to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: