Skip to main content
Kofax

MarkView Advisor - Hotsync Troubleshooting

Summary 

Hotsync does not seem to be working, what steps can I take to troubleshoot the issue? 4927

Applies To

  • ERP System: Oracle, SAP
  • MarkView Version: MarkView 9.0 and Below

Behavior

  • Advisor uses JMS messaging to keep data in the Advisor schema up to date with the ERP and MarkView systems. There are currently three methods that Advisor uses to
    • Cold Sync whereby an Advisor schema devoid of user data is synchronized with MarkView. Depending upon the size of and activity within the database, this process can take a while to complete and in that time, updates may have happened in the MarkView schema that will need to be synchronized to Advisor. This is achieved with the Hotsync process.
    • Real-time updates. These occur whenever a qualifying event occurs within MarkView. Certain conditions can arise which may cause Advisor real-time message updates to be received out of order. In this scenario, the real-time update for the message received out of order will fail and will need to be retrieved by Hotsync.
    • Hotsync is scheduled to run periodically and should also be run as soon as possible after a Cold Sync operation. Hot Sync will update Advisor with event information that occurred after the Cold Sync process began. Hot Sync will also update Advisor with any missing real-time update information.

Troubleshooting Hotsync Steps

  • How do I tell if hotsync has been executed successfully?
    • First run the following query from the Advisor schema:
      select * from mvac_checkpoint;
    • The above query will return the date/time that hotsync last completed successfully. This record is only updated if hotsync is successful.
  • How does hotsync determine which events to process again?
    • Event information is stored in the mvam_event_message_sync and mvam_event_message_sync_detail tables in the MarkView Schema. When hotsync executes it will take the data from this table and create the necessary message to be processed by Advisor. By default this message is sent to the mv_advisor_hotsync_q_tab queue.
  • How long does hotsync keep data in the mvam_event_message_sync and mvam_event_message_sync_detail tables?
    • By default Advisor will store seven (7) days worth of records. This can be modified by changing the value of the MVAM_CLEAR_OLD_SYNC_RECORDS preference in MarkView and bouncing the Advisor OC4Js/Deployments.
  • How do I start the hotsync process?
    • Hotsync can be configured from MarkView Home -> Advisor -> Configuring -> Advisor. In the Hotsync hours to run field specify the times you would like Hotsync to run.
Please note that Hotsync can not be started via script or other means. It can only be executed when the specified time occurs.
  • How do I determine what URL hotsync is using when it begins processing?  If hotsync is not working correctly you will want to verify that this URL is correct. If it is incorrect you will need to manually update the table data and bounce the Advisor OC4Js/Deployments. The URL should be in the following format:http://Server:Port/hotsync/requestHotSync
    • MarkView 6.x
      • The following query will show you the URL that hotsync is using.
        select * from MVAC_MV_CALL where call_type in ('REQUEST_HOT_SYNCH');
    • MarkView 7.x and higher
      • ​​​​​​​Run the Support Tools Preference output and find the 'Advisor Call Types' section.
      • Alternatively you can also query the MVAC_MV_CALL table as instructed under the MarkView 6.x section above.

Keywords: hot-sync