The SAP CC system or a subcomponent can recover from anomaly, and fulfill the desired task, but needs later follow-up activity by a system administrator or an SAP CC SAP CC application administrator to avoid erroneous terminations in the future.
The administrators plan a follow-up activity to take into account the anomaly and to determine the appropriate timeframe to perform preventive actions.
Recommendation
In a production system landscape, contact your SAP Support Team at support.sap.com/incident.
The administrators of the SAP CC systems may perform troubleshooting operations relating to the following warning log messages:
| Warning Log Message | Possible Impacts |
|---|---|
| Request sent by the remote client {0} has caused an internal error. Reason is: {1}. |
The remote client will not get any service from the server. |
| SQL manager has lost connection to database {0} |
No database operation will be available until SAP Convergent Charging successfully reconnects to a database. |
| SQL manager is switching from {0} to {1} because database is no longer available |
During the time of the switch, no database operation can be executed. |
| SQL manager is switching from {0} to {1} because database is not ready during reconnection |
During the time of the switch, no database operation can be executed. |
| Switching connection dedicated to the generation of unique identifiers, from database {0} to {1}. |
During the time of the switch, no database operation can be executed. |
| Timeout occurred on SQL connection: SQL manager has lost connection to database {0}. |
A part or the whole of the current operations could not be recorded. |
| Timeout occurred on SQL connection: The connections to {0} are closed. |
A part or the whole of the current operations could not be recorded. |
