• Not Answered

process historian in ovation

A few days ago the historian started to show errors in the error log and the historian diagnostic tool shows that the partner, drop201, has "no response" and the main drop has the historian connection down message displayed.  The error log is showing that is is a RAIMA problem.  Killed orphan user is the description.  There are 4 error messages.  They repeat every 30 minutes.

I am not sure why this has happened.  1 point was added to the historian.  The point works.  All the other points are trendable and do not seem to have any problems.

Any suggestions or ideas about what has happened and how to fix it?

Thanks,

Dean.

Dean Schneider

• 10 Feb 2025 2:21 PM
• Cancel

4 Replies

• Andre Dicaire

  

  • 10 Feb 2025 6:30 PM

  What Historian are you using? DVCH, Advanced Historian, PI Enterprise? The default DVCH historian does not support redundancy, so the referenced to the "partner, Drop201" doesn't make sense to me. DeltaV also does not support redundancy on the Advanced Historian either, which is based on PI. Redundant Historians are supported with an Enterprise Historian, but I believe this is an AVEVA PI feature.
  
  Which Error Log are you referring to? Is this a Windows/Application log or other? Maybe provide a more detailed example of the log content. "RAIMA problem" is not something I've come across on the DeltaV Historians.
  
  If this is relating to DVCH or Advanced Historian, which are both installed from DeltaV media on an App Station, you should log a call with GSC.

  Andre Dicaire

  • Cancel
• Dean Schneider

  

  • 10 Feb 2025 7:51 PM

  In reply to Andre Dicaire:

  This is not a delta-v system. It is ovation. It is called the Ovation Process Historian. The error log I am referring to is the Ovation error log on the historian drop, drop160. To follow are some lines taken from the error log.
  
  <Err dts="02/10/25 11:42:22" dtl="1739212942" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r00001F9800794B, PID [8088], TID [476], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 124 9 0</Err>
  <Err dts="02/10/25 11:42:32" dtl="1739212952" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r0000261C005309, PID [9756], TID [7428], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 126 9 0</Err>
  <Err dts="02/10/25 11:42:42" dtl="1739212962" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r00002A8C006D22, PID [10892], TID [7376], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 125 9 0</Err>
  <Err dts="02/10/25 11:42:42" dtl="1739212962" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r00000DA000763A, PID [3488], TID [11164], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 130 9 0</Err>
  <Err dts="02/10/25 12:12:22" dtl="1739214742" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r000000CC007E12, PID [204], TID [872], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 124 9 0</Err>
  <Err dts="02/10/25 12:12:32" dtl="1739214752" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r000023C0008A3E, PID [9152], TID [9024], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 126 9 0</Err>
  <Err dts="02/10/25 12:12:42" dtl="1739214762" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r00000EA8005941, PID [3752], TID [1112], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 125 9 0</Err>
  <Err dts="02/10/25 12:12:42" dtl="1739214762" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r00002B1000741B, PID [11024], TID [2264], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 130 9 0</Err>
  <Err dts="02/10/25 12:42:22" dtl="1739216542" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r000000E400813B, PID [228], TID [936], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 124 9 0</Err>
  <Err dts="02/10/25 12:42:32" dtl="1739216552" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r000027C4007C4B, PID [10180], TID [3188], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 126 9 0</Err>
  <Err dts="02/10/25 12:42:42" dtl="1739216562" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r000027F4006E64, PID [10228], TID [9932], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 125 9 0</Err>
  <Err dts="02/10/25 12:42:42" dtl="1739216562" source="drop160" priority="3" identifier="RAIMA">Killed Orphan User: r00002A38005C2F, PID [10808], TID [7712], Cmd: D:\OvHist\bin\OvhFaultAlert.exe FAULT 179 130 9 0</Err>
  
  Does this help you?
  
  Dean.

  • Cancel
• Dean Schneider

  

  • 10 Feb 2025 7:55 PM

  In reply to Andre Dicaire:

  This is not delta-v it is an Ovation system. The error log is the ovation error log from the historian drop, drop 160. I attempted to send you a snipit from the error file on drop 160, the historian drop. It did not seem to like the snipit.

  • Cancel
• Andre Dicaire

  

  • 10 Feb 2025 10:52 PM

  In reply to Dean Schneider:

  I have no exposure to the Ovation system so I'm afraid I cannot help you with this issue. If you have not done so, a GSC call is recommended.

  Andre Dicaire

  • Cancel