IOP ORDER PROGRESS not syn

  IOI_ORDER_PROGRESS records are created via direct-db write by the IMAR_ORD_OSUB process. Thus, they are not journalled and are not mirrored between the primary and standby.

  Please ensure that the following settings are defined properly:

  ! Should point to OMAR_IMAR_RDS on TOP   

     IMAR_PRIMARY_OMAR_RDS_HOST    IMAR_STANDBY_OMAR_RDS_HOST    IMAR_OMAR_RDS_ID    IMAR_OMAR_RDS_PORT

  ! Should point to OMAR_DS_PUB on TOP

     IMAR_OMAR_PRIMARY_HOST <span style="font-family: arial, helvetica, sans-serif">   IMAR_OMAR_STANDBY_HOST <span style="font-family: arial, helvetica, sans-serif">   IMAR_OMAR_DS_PUB_ID <span style="font-family: arial, helvetica, sans-serif">   IMAR_OMAR_DS_PUB_PORT

<p style="margin: 0in 0in 0pt"> <span style="font-family: arial, helvetica, sans-serif"> These OA connections are used to update the IOI_ORDER and IOI_ORDER_PROGRESS tables, respectively. The IOI_ORDER records are updated via transaction by the IMAR_ORDER_IN process, so they should be consistent between primary and standby. The IMAR_ORD_OSUB then fires off subscriptions to OMAR_DS_PUB for all active orders in IOI_ORDER table. It uses said subscription to perform the writes to IOI_ORDER_PROGRESS. Thus, in event of a failover, IMAR should refresh all the order progress data based on any active IOI_ORDER records.