Looking for Errors and Failures in SCC

If data in the Monitoring node reveals nothing unusual, extend your analysis to other nodes in Sybase Control Center (SCC). Look for explicit errors or failures that may be recorded elsewhere.

1. In Sybase Control Center, click the Packages node.
2. To check whether the problem exists in either the device or the EIS data source:
   1. Click the Client Log tab.
   2. Check the Operation and Message columns and look for any operation replays that failed with error code 500, and the reason for the failure. For example, the client log shows all logs on device. For failed operations on the device, check the details of error message and assess what kind of error may have occurred.
3. To check whether the problem exists in either the server or the EIS data source:
   1. Expand the package tree until MBOs and operations for the package complete the tree navigation for the package.
   2. For each MBO and operation, select the node in the navigation tree, then click the History tab.
   3. Set the Start Date, Start Time and Finish Date, Finish Time to restrict the data to the duration you require.
   4. Review the data and look for any errors and the potential causes of those errors. You can check the error history, the exception or error about the operation is listed in the details of that error. Use the message to reveal the issue and coordinate with the development team as required.