Duc,

It might be worthwhile to compare an iccprt listing of your station
with a dbvu listing (dbvu -t -CDB20CP02.UC -MOS1C40.map -IOS1C40 should
do it).  This will compare your checkpoint file (which is good, as the
CP reboot worked) with your workfile.  This is better than doing an
upload and checking in the icc configurator, because an upload only
updates the settable parameters.  

At the last plant I worked at, our field service engineer used a tool
called ck_sync (I believe) to check for mismatches between CSA,
workfile, and checkpoint file.  You may want to check with TAC or your
field service engineer on this.

If you can locate the faulty data, doing a delete and undelete should
correct the station workfile and the CSA to match the CP.  This will
break remote connections until checkpoint is done.

While this may not free you of the need to do an initialize, reboot and
loadall, it may give you a better idea of where the mismatches or
corruption are.

Regards,

Kevin FitzGerrell



--- [EMAIL PROTECTED] wrote:
> warning: long message
> ---------------------
> 
> Hi folks,
> 
> I have a CP (CP-40) that has its control database corrupted when a
> person
> answered Yes when presented with the "Database locked. Override?"
> dialogue
> box.
> 
> A little background: I schedule a weekly cron job to perform SaveAll
> on all
> of our CPs using the ICCAPI save_all command. As luck would have it,
> this
> person was called in on a Sunday to fix a sequence problem, and he
> tried to
> open a CIOCFG session on this CP while the ICCAPI save_all was
> running. When
> presented with the "Database locked. Override?" question, he didn't
> hesitate
> long, reasoning that it was Sunday and nobody would be working on
> that CP,
> must be a mistake. Once in the control session, he still couldn't
> connect to
> the CP so he rebooted it.
> 
> Since then, I have not been able to perform a good SaveAll for this
> CP.
> Using the CIOCFG interface the SaveAll appears to run successfully,
> but I
> can't perform a LoadAll with the resulting disk (to an off-line CP),
> I keep
> getting "Invalid block type" error for each of the compounds in this
> CP.
> Using the ICCAPI save_all command always resulted in a failure
> message with
> the following text in the /tmp/output* files (at different times
> after
> trying different things to mitigate the problem):
> 
> 04AW01# more /tmp/output*
> FAIL     3 save 20CP02!: Wed Mar 28 16:27:01 2001 -8 Save cmd: no
> path name
> arg
> 
> 04AW01# more /tmp/output*
> FAIL     2 getorder 20CP02!: Thu Mar 29 15:52:50 2001 -15 Get
> compound order
> cmd
> : ICCget error: class= 20 error= 4 text= load_wrk: fread error
> 
> 04AW01# more /tmp/output*
> FAIL     4 save 20CP02!20CP02_STA: Fri Mar 30 09:08:34 2001 -8 Save
> cmd: no
> path
>  name arg
> 
> BTW, I can do an upload for this CP and the workfile appears to be in
> good
> condition (at least good enough so that I can see all the compounds,
> blocks,
> and parameters while in a CIOCFG session). And the CP is still
> running okay
> as we speak.
> 
> Questions:
> 
> 1. What are my options in getting a good SaveAll for this CP?
> 
> 2. If I have no option, would initializing/rebooting/reloading it
> with a
> good SaveAll (from 2 weeks back) get me out of this jam?
> 
> 3. Has anybody encountered problem similar to this, and what's your
> remedy?
> 
> Thanks for any thought and help.
> 
> Duc
> 
> -- 
> Duc M. Do
> Process Control Systems
> Dow Corning, Carrollton Plant
> Carrollton, KY, US


__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/

-----------------------------------------------------------------------
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