Re: [foxboro] Unable to access Alarm History
- From: "DUNHAM, KENNETH J" <kdunham@xxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Sat, 31 Jan 2009 11:02:26 -0600
Check your cpu usage as well. I have had this problem when the process that
acquires the real time points (process name escapes) starts misbehaving and
consuming excessive cpu utlization.
I solved the problem by rebooting the historian box.
As stated below, you may also need to archive some of the older aim history
files but I would try the reboot first.
Ken Dunham
DCS System Engineer
Fort Calhoun Station
Omaha Public Power District
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
Larsen, Ed [ed.larsen@xxxxxxxxxxxxxxxx]
Sent: Friday, January 30, 2009 10:36 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Unable to access Alarm History
How many messages files do you have?
I have seen where too many message files in Aim* Historian cause this.
From GCS knowledgebase:
Solution
Unable to access alarm history on Alarm History Display (AHD)
September 24, 2008
Problem Description
Unable to call up Alarm History Display (AHD) from Current Alarm Display (CAD).
Get the following message "unable to access alarm history for hist01 on
A1AW01'' or " Too many historian alarms in database <histname> on <wsname>.
Please archive your database
The AIM*API calls may timeout if there are too many alarms and return an error
with no data to the AM. The AM displays the above message instructing you to
archive.
Fix/Resolution
Ref to v8.2 release note B0700RN rev C sec 8.9.6 talk about issue with alarm
history. The solution describe in this release note and can also apply on your
current v8.0 is to archive the message file in the historian database. Can
have up to 180 message (m###.fdb file) in your /opt/aim/inst/histname
directory. Ref to historian user guide to use manual archiver and then setup
auto archiver. Q0302BR
Steps to resolve your alarm history issue.
In /opt/aim/inst/histname
m*.fdb is for all message file, meaning these are the alarm history
r*.fdb for sample file, meaning these are the measurement value
Ref to AIM historian user guide in AIM 3.2.3 suite CD Q0302BR
Use manual achiver and copy and delete m*.fdb file to ANY OTHER DIRECTORY
beside /opt/aim/inst/histname, /opt/aim/pbk or any directory define in DBPATH
(use histcfg >select instance cfg to check). Only leave up to 180 m*.fdb in
the /opt/aim/inst/histname directory.
When above steps are done, go to /opt/aim/bin and run " xrebuild histname 4 "
......select ' Y ' to commit the system.
Re-launch alarm history, and alarm should appear.
When the issue is resolve, setup auto-achiver on the message file. This will
copy and delete you message file base on the schedule date and time.
Hope this helps.
Ed
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Ali Ahmed Zahidi
Sent: Friday, January 30, 2009 10:07 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Unable to access Alarm History
Hi All,I am unable to access alarm history in Alarm History Display (AHD) of
alarm manager on Windows XP based P92 stations. I am getting the following
message when AHD is invoked "Unable to access alarm history for hist01 on
01AW02"
We are using AIM*Historian for historical data collection. I have checked the
historian instance hist01 for proper function. It is running properly. If
anyone have some idea to solve this problem, please share.
Rgds,
Ali
_________________________________________________________________
Love Hotmail? Check out the new services from Windows Live!
http://clk.atdmt.com/UKM/go/132630768/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
* Confidentiality Notice:
This e-mail and any associated files are intended solely for the individual or
entity to whom they are addressed. Please do not copy it or use it for any
purposes, or disclose its contents to any other person. Further, this e-mail
and any associated files may be confidential and further may be legally
privileged. This email is from the Invensys Process Systems business unit of
Invensys plc which is a company registered in England and Wales with its
registered office at Portland House, Bressenden Place, London, SW1E 5BF
(Registered number 166023). For a list of European legal entities within the
Invensys Process Systems business group, please click here
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77.
If you have received this e-mail in error, you are on notice of its status.
Please notify us immediately by reply e-mail and then delete this message from
your system. Thank you for your co-operation. You may contact our Helpdesk on
+44 (0)20 7821 3859 / 2105 or email inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail
and any attachments thereto may be subject to the terms of any agreements
between Invensys (and/or its subsidiaries and affiliates) and the recipient
(and/or its subsidiaries and affiliates).
_______________________________________________________________________
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
This e-mail contains Omaha Public Power District's confidential and proprietary
information and is for use only by the intended recipient. Unless explicitly
stated otherwise, this e-mail is not a contract offer, amendment, nor
acceptance. If you are not the intended recipient you are notified that
disclosing, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited.
_______________________________________________________________________
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: