Thanks for that information Jim. Good to hear from you again. Btw, how is
retirement? I tried it once but found I couldn't afford to live in the manner
to which my wife has become accustomed;<)
Tom VandeWater
Control Conversions, Inc.
On Feb 4, 2016, at 5:59 AM, Jim Kahlden <jim.kahlden@xxxxxxxxx> wrote:
Tom,
I had a similar problem in the past and found this on the TAC website years
ago that helped me.
Another thing to consider with AIM Historian:
DELETED points count towards the AIM historian license count.
FORCE-DELETED points do not count towards the AIM historian license count.
Even when a point is FORCE-DELETED its index is not released for re-use and
thus the next available index is used. When the index hits the MAXPTS limit
imposed by the historian instance configuration you will not be able to add
new points, even if your license count is not reached (the license count
appears in the MXSRVPTS instance parameter).
To avoid this, set-up your instance upfront with MAXPTS higher than MXSRVPTS
(double the value should usually do).
For a running instance you can increase the MAXPTS as described under
"Modifying Maximum Value Attributes" in B0193YL.
Jim Kahlden
Retired LCRA
On Wed, Feb 3, 2016 at 8:35 PM, Tom Vandewater <tjvandew@xxxxxxxxx> wrote:<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Thanks for this info Anthony. I think it will come in handy in the near
future for me.
Tom VandeWater
Control Conversions, Inc.
On Feb 3, 2016, at 4:46 AM, "Stankiewicz, Anthony P." <X2STANKI@xxxxxxxxxxxxxx> wrote:
input file that only contains the valid points. The other file contains all
Tom,
You can delete points 2 ways.
1 is to do the export, then clear out the instance and re-import the
points, deleted and not-deleted and has "_del" in the file name. This, of
course, requires you to have an "outage" because the historian will be
offline. If you do this, your historical files (rtp) need to be removed
(this gets done when you remove the instance). I tend to do this when we
have an outage and just start over with the historian. We have an OIS for
long term history anyways.
The other option is to do the export, re-import (valid point file only),then do an xrebuild. The program xrebuild is an AIM*Historian emergency
utility that rebuilds cross-reference files when there is a suspicion of
database corruption [B0193YL]. This, I believe, re-aligns the point data
with the historical data files (rtp).
I have simplified the steps just to give an outline of possibilities. Ihave done this a number of years ago with success, I just don't recall all
the steps unless I were to go through it again in detail. It can be
nerve-racking, hoping everything will work ok. There are a couple of
Foxboro guys that are good at this in TAC. Sometimes just worth walking
through with them just to be sure everything goes well - like buying
insurance.
My 2 cents worth.
Tony Stankiewicz
Southern Company
_
This
email has been sent from a virus-free computer protected by Avast.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
