Troubleshooting › CA Catalyst Troubleshooting › Synchronization Errors

Synchronization Errors

Symptom:

You experience problems with the synchronization functionality. Synchronization errors usually appear as failed inbound to connector operations or mismatches between projections and reconciled sheets. Synchronization errors may be caused by the following issues:

• Sync Planner failed
• Sync Executor failed
• Synchronization not enabled

Solution:

Try the following to fix synchronization errors:

Review the "Working with CA Catalyst Synchronization" section in the Administration Guide. The section provides detailed information about making sure that everything is configured correctly from the connector configuration to UCF Broker to CA Catalyst registry.

• Verify that the Synchronizer is enabled. Enabling the maintenance mode synchronization automatically enables the Synchronizer.
• Verify that the connector to which you are trying to synchronize is configured properly. Open the CA SOI Administration UI, select the connector, and review the following information:
  • In the Connector Controls section, verify that the isRemotable connector control is enabled.
  • In the InboundToConnectorTypes section, verify that a list of all USM types that are supported for synchronization exists. To synchronize on a particular CI, its type must be included in the list.
• Verify the correct location of the UCF Broker.

  Note: For more information about how to configure the UCF Broker location, see the Administration Guide.

• Verify that all applicable connectors support inbound to connector operations.
• Verify that all connectors have inbound to connector operations enabled.
• Verify that sor.application started correctly.
• Verify that the CI on which synchronization is required has been reconciled with CA SOI. Check for mismatches between projections and reconciled sheets using the USM Web View interface:
  • Find the reconciled view of the CI in USM Web View (for example, CA:00030, tenent0).
  • Get different projections for the CI using the By Data Source drop-down list.

  Note: For more information about these points, see Trace a CI Using USM Web View for Diagnosing Synchronization Errors.

• Verify that the Synchronizer is executing the synchronization transactions.
  • Get the internal CA Catalyst notebook ID for the CI using the USM Web View interface.
  • Use the CA Catalyst Trace UI (http://host:7090/sor.application/trace.jsp) to track events on the notebook using the notebook ID.
• Review the related log file. CA Catalyst uses log4j for logging. By default, only Errors and Warnings are logged to the SOI_HOME\tomcat\logs\soimgr.log file. Enable the debug logging in CA Catalyst by editing the SOI_HOME\tomcat\lib\log4j.xml file. Update the existing logger entry in the file by changing the debug level from “INFO” to “DEBUG” and restart the CA SAM Application Server service:

  <logger name="com.ca.ssa.sor" additivity="false">
      <level value="DEBUG" />
      <appender-ref ref="CAT" />
  </logger>
  
  

  CA Catalyst debug log entries start appearing in the soimgr.log file.

  Failures can also occur in connectors when fulfilling the update request. Review the individual connector logs to view the request and any errors that occur.