Question Abhinav Shukla · May 2, 2023

Table synchronization state: Waiting

Sync operation in registry is not receiving any request from ODS. I have tried to synchronize from Registry management however, sync operation doesn't receive any request.

HSODS>w ##Class(Ens.Director).StartProduction()

09:51:49.297:Ens.Director: Production 'HSODSPKG.FlashGatewayProduction' starting...
09:51:49.472:...GatewayProduction: Table synchronization state: Waiting
09:52:04.483:...GatewayProduction: Table synchronization state: Waiting
09:52:19.493:...GatewayProduction: Table synchronization state: Waiting
09:52:34.504:...GatewayProduction: Table synchronization state: Waiting
09:53:34.516:...GatewayProduction: Table synchronization state: Waiting

 

Did any one face this issue before? 

Product version: IRIS 2020.1
$ZV: IRIS for UNIX (Red Hat Enterprise Linux for x86-64) 2020.1 (Build 217_1_20418U) Mon Dec 21 2020 11:57:50 EST

Comments

Zachary Nowicki · May 2, 2023

Hi Abhinav -

The SYNC issues can happen for a number of reasons, but one you should ensure is that the REGISTRY instance is up and running and that all of the REGISTRY's 'Sync' components are not producing any errors.

Please reach out to the WRC +1(617)621-0700 or support@intersystems.com about this issue.  

Cheers,
Zachary N

0
David.M · May 2, 2023

The best place to start is to look at the HS.Sync.Operations business operation in the Registry. Look at the Interoperability/Ensemble Event Log and the Interoperability/Ensemble traces for the messages. Note that errors that occur on the non-Registry instance when loading the sync file are passed back to the HS.Sync.Operations in the Registry, but not put in the Interoperability/Ensemble Event Log. However, they should appear in the Interoperability/Ensemble trace in a message sent to the HS.Util.Trace.Operations component, assuming the TraceOperations setting of the HS.Sync.Operations component is not blank (it is *ERRORSONLY* by default). If TraceOperations is off, then you can look at the SendStatus property of the HS.Message.Sync response.

0