History Log Missing 800xA AC800M etc
3 Part Question
1. I am missing history logs up too 1 year ago after editing a log definition which logged 1day_1month_1year ..in a log template it seems to have just started again and deleted all the old data , i have managed to recover the 30gb or so of data off the history server from an iso however i cannot re implement the data onto the trend pages.
2. IM_Event_Collector Not running , IM_Industrial IT_Archive Not running would re enabling these effect my system in anyway? and could this have something too do with losing my old data?
3. Also have a problem with parameters reverting back to old values after a period of time. Mainly Scaling Min and Max Values any ideas?
Voted best answer
Resolving this problem will probably become quite complex, I therefore recommend that you ask your regional ABB support center to assist you.
Editing of Log Template(s) must be made with care - it's possible to erase all stored data with a few wrong clicks.
I don't have exact information about what has happened - but I fear that most of the logged data is gone. Run this command on the IM to create a textual report of what is in its logs:
C:\> hsdbmaint -report > report.txt
This will iterate all logs and output a report stating log name, time stamp of oldest data, time stamp of most recent data, etc. Such report usually take hour(s) if the log config is large. When command has run to completion, open the report.txt and study the information (I usually import it to Excel to sort, filter, etc)
The "oldest data" stamps will tell you how old data you have in the logs. There are columns telling you the number of good values - the combination of "oldest data" + "# of good rows" will tell where you are.
Do you have any IM Backup (made with hsBAR.exe)? Such backups are good to have in hand if things like this happen. Correctly applied, such backup can be used to recreate corrupt or missing Log Template & Log Configuration aspects as well.
Most (all) of the log configuration is stored based on a set of IDs (GUID) which are generated randomly each time a log is created - if the logs have been erased, an ISO image of the data drive will not do you so much good since all identities are just random numbers and you will need the (lost) configuration in the modified Log Template(s) and Log Configuration(s) to match the things together.
I'm not ruling out that the ISO might save your day; but probably an IM expert of highest rank (=R&D) will need remote into the IM station and spend some hours, or guide you through what is required to restore the database and log files in usable state. However, such recovery is not covered by the regular support scope.
A complete set of drive image files (C:\ + all other drive containing Oracle database + flat log files) might allow you to restore the IM to a state before it lost its data; however, as soon as the IM connects to the 800xA system, the new "incompatible" Log Template / Log Configuration settings will take effect (=data is lost again).
It might, and I really mean might, be possible to recover by:
a) restore IM to previous known good state from ISO; but keep it down/not started
b) perform IM History Backup (hsBAR.exe)
c) clean current log configuration (possibly erase all) in 800xA system
d) restore IM History Backup from step b), including recreation of log templates & configuration.
Ask the regional ABB support team to assist you with judging your options.
The IM Event Collector and Archive services will only enter service state if the IM History services are up and running and the configuration is correct. As they seem to have gone offline, it indicates there is some problem with the configuration.
Most 800xA trend interfaces offers dynamic trend scaling (the presentation attributes are read straight from the controller on each callup and will update immediately if there is a change made there). Hence, there is often no need to configure any static things as MIN, MAX, UNIT, NOOFDEC, etc. in the IM (but the IM Desktop tools will probably need them though).