• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 94 subscribers
  • Views 9301 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

D1IM(6.1.2): How to tell if History Archive DB is working?

ToddFendt
over 7 years ago

I have attempted to configure and activate the History Archive DB. Service installed and running, service configured with one queue. Config params set to export over 90 days for Process View, progress View, and PropertyLog. IsToExport set to 1 for all three. Export Policy set to HDB. I have warning logging set for history service. it i slogging to a log file. Here are entries for history service logging:

 <w>2016-11-01 12:45:50 -04:00 - Warning: No private key supplied. Running without encryption support.<x>
<w>2016-11-01 12:45:50 -04:00 - Warning: No private key supplied. Running without encryption support.<x>
<w>2016-11-01 12:45:50 -04:00 - Warning: Starting queue \QIDINFWWATV01.<x>
<w>2016-11-01 12:45:50 -04:00 - Warning: Starting queue \QIDINFWWATV01.<x>

 

I know I  have a duplicate queue and I'm not sure how to correct that.

I keep running the Export process history job manually and scheduled and nothing seem to be archiving. 

I am looking for ways to tell what is going on?

The doc is very incomplete.

Any help is appreciated.

  • 0 over 7 years ago
    After redoing the Job Server Configuration several times the duplicate queue has disappeared. I was given these queries to look for records marked for deletion or export:

    select ReadyForDeleteOrExport, count(*) from DialogProcess
    group by ReadyForDeleteOrExport
    select ReadyForDeleteOrExport, count(*) from JobHistory
    group by ReadyForDeleteOrExport
    select ReadyForDeleteOrExport, count(*) from DialogWatchOperation
    group by ReadyForDeleteOrExport
    select ReadyForDeleteOrExport, count(*) from DialogProcessChain
    group by ReadyForDeleteOrExport

    Run these against the Main Database.

    And here are the meanings of the ReadyForDeleteOrExport values:
    ReadyForDeleteOrExport = 0 (Not completed)
    ReadyForDeleteOrExport = 1 (Ready for delete)
    ReadyForDeleteOrExport = 2 (Ready for export)

    I am waiting for evidence that records have been archived.
  • 0 over 7 years ago
    Hi Todd

    Are you able to find any data in the DIalogWatchProperty / DialogWatchOperation tables in the ArchiveDB?

    Regards
    Carsten
  • 0 over 7 years ago
    Hi Carsten,

    I have no records in DialogWatchProperty and no records in DialogWatchOperation. I do have records in HistoryJob and HistoryChain.

    Is there a way to view the data using any of the tools? (Manager, Designer, etc)

    Thanks, Todd
  • 0 over 7 years ago
    There should be dedicated ArchiveDB tools, like HistoryDB Manager which should allow to take a unstructured look into the archived data. As for the DialogWatchProperty / DialogWatchOperation: did you configure any database tables / columns of your D1IM installation to archive data using the Designer tool? Did you configure the appropriate export policy for data history and job history?
  • 0 over 7 years ago
    I did configure the export for all three categories and I now have History records in these four tables marked for export:
    JobHistory
    DialogProcess
    DialogWatchOperation
    DialogProcessChain

    Thanks, Todd
  • 0 over 7 years ago
    So those are marked for export in the D1IM Main Database, right? What does the job service log of your HDB service (not the D1IM service) tell you about those marked entries?
  • 0 over 7 years ago
    I had to build a new 1IM system ( 6.1.2). it is running and I am runnign a Process Orchestration to create process records. I should have History exported tomorrow morning. I will share more. Thanks,
  • 0 over 7 years ago
    In the mean time, I am prepping for activating a Archive History DB in my Prod environment. Everything that I can see tells me that is it already active and running. The TimeTrace DB entry exists and is enabled. The Lifetime days (all 3 ) are set to 90, Export Policy is set to HDB. And the 'Export Process Information' Process has a schedule and is activated and has been running daily. However, I have no records in the HDB tables HistoryJob, WatchProperty, WatchOperation. I am wondering how they "stopped" the archiving. I was told by my predecessors that they had previously turned on History and it was very hard on the system performance so they turned it off. My intention was to activate it and very carefully reduce the Lifetime days numbers so that I can get some experience with how it will impact the system performance. Any ideas how it could have been "Disabled" without the obvious settings? Thanks, Todd