Index	Log Message	Description	Impacts	Actions	Information
0 (FATAL)	Transaction {0} cannot perform a commit operation. Error message: {1}.	The JDBC connection cannot perform a commit operation. This database access error mainly occurs when the connection was closed.	A part or the whole of the current operation could not be recorded.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
1 (FATAL)	Transaction {0} cannot perform a rollback operation. Error message: {1}.	The JDBC connection cannot perform a rollback operation. This database access error mainly occurs when the connection was closed.	A part or the whole of the current operation could not be recorded.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
2 (FATAL)	Transaction {0} cannot execute the query {1}. Parameters: [{2}]. Error reason: {3}.	The SELECT statement is invalid or the query execution is in error.	A part or the whole of the current operation could not be recorded.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
3 (FATAL)	Transaction {0} cannot execute the query {1}. Parameters: [{2}]. Error reason: {3}.	The UPDATE or DELETE statement is invalid or the query execution is in error.	A part or the whole of the current operation could not be recorded.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
4 (WARNING)	Switching connection dedicated to the generation of unique identifiers, from database {0} to {1}.	The SAP CC Core Server system handles a particular connection to the database system dedicated to the management of unique identifiers for its data objects. The database is used to provide these unique identifiers. This message indicates that this dedicated connection to the primary database is not possible. An attempt to create a connection to the backup database system will be done by the SAP CC system.	During the time of the switch, no database operation can be executed.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
5 (ERROR)	Multiple entries found in table {0}. A single result is expected.	SAP Convergent Charging data identification relies on this unique identifier mechanism to internally identify its objects. Only one single entry is expected that indicates the latest next available object identifier. If several entries are available corrupted identifiers can be generated.	SAP Convergent Charging will encounter master data corruption since some data objects may end up having the same identifier.	Stop all SAP Convergent Charging activity. Contact SAP Support Services to help in restoring the unicity of this entry.
6 (ERROR)	Connection to database is refused. URI is: {0}. User login is: {1}.	An attempt to create a connection to database was not successful. The creation of this connection will be attempted several times, according to configuration.	Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.	Check the previous error messages and verify the database configuration
7 (FATAL)	Cannot be connected to the database. URI is: {0}. User login is: {1}.	Several attempts to create a connection to database was not successful. The creation of a connection to the database is not possible.	Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.	Check the previous error messages and verify the database configuration
8 (INFO)	SQL manager is connected to {0} as {1} ({2} connections in pool, {3} statements in cache).	SAP Convergent Charging is connected to the database. Several connections have been created and the statement cache is configured.			Relates to two former messages: SQL_MANAGER_CONNECTED used to indicate which database is connected and SQL_MANAGER_RUNNING to indicate how connections are configured.
9 (ERROR)	SQL manager is not able to connect to {0} as {1}	SAP Convergent Charging cannot be connected to the database.	Some instances of SAP Convergent Charging will not be fully functional. Unexpected behavior of the system may occur.	Check the previous error messages Verify the configuration of the database parameters Verify the status of the database
10 (WARNING)	SQL manager has lost connection to database {0}	The connection to the database is not available anymore.	No database operation will be available until SAP Convergent Charging successfully reconnects to a database.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
11 (WARNING)	SQL manager is switching from {0} to {1} because database is not ready during reconnection	SAP Convergent Charging is switching from its primary database to its backup database because it cannot be reconnected to the database it was previously connected to.	During the time of the switch, no database operation can be executed.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
12 (WARNING)	SQL manager is switching from {0} to {1} because database is no longer available	SAP Convergent Charging is switching from its primary database to its backup database using the database failover mechanism.	During the time of the switch, no database operation can be executed.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
13 (ERROR)	Connection refused from {0} because the maximum count of simultaneous connections ({1}) has been reached	The server will not accept any new incoming client connection because the maximum number of simultaneous connections has been reached.	No new client will be able to connect until existing clients release their connections.	Increase the maximum number of simultaneous connections, Connect your client again, or Try to connect your client again as soon as some concurrent clients release their connections
14 (ERROR)	New remote connection from address {0} is refused for IO exception reason: {1}	The remote client is not authorized to connect because of an I/O exception during socket creation and initialization.	The remote client will not get any service from the server.	Check the previous error messages
15 (FATAL)	New remote connection from address {0} is refused for out of memory reason: {1}	The remote client is not authorized to connect because of an out of memory exception during socket creation.	The remote client will not get any service from the server.	Check the previous error log messages and verify the database configuration.
16 (ERROR)	New remote connection from address {0} is refused for the connection error reason: {1}	The remote client is not authorized to connect because of an IO exception during socket registration.	The remote client will not get any service from the server.	Check the previous error messages
17 (INFO)	Request from remote connection from address {0} has caused a buffer underflow error. Reason is: {1}.	This message is expected when the request is not completely received. The request will be read again later when new bytes will be received.	The remote client will not get any service from the server.
18 (FATAL)	Connection with the remote client {0} is closing because it has sent an invalid request. Reason is: {1}.	This message occurs when client and server are using the same protocol version but there is a header error in the request. The server rejects the request by sending an answer to the remote client indicating a bad protocol is used.	The remote client will not get any service from the server.	Check the previous error log messages and verify the database configuration.
19 (FATAL)	Connection with the remote client {0} is closing because it has sent an invalid request. Reason is: {1}.	This message occurs when client and server are not using the same protocol version. Then server rejects the request without answering the client. Since the protocol versions differ, the client would not be able to understand the answer.	The remote client will not get any service from the server.	Check the previous error log messages and verify the database configuration.
20 (WARNING)	Request sent by the remote client {0} has caused an internal error. Reason is: {1}.	This message occurs on the server when the processing of the request leads to an unexpected error. The server will recover and will handle next requests.	The remote client will not get any service from the server.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
21 (FATAL)	Connection with the remote client {0} is closing because an error occurred with the socket network. Reason is: {1}.	The connection will be closed because the socket reached an illegal state that may prevent server to handle further requests.	The remote client will not get any service from the server.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
22 (FATAL)	Connection with the remote client {0} is closing because an error occurred with the connection selector thread. Reason is: {1}.	The connection will be closed because the socket reached an illegal state that may prevent server to handle further requests.	The remote client will not get any service from the server.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
23 (FATAL)	Connection with the remote client {0} is closing because the server ran out of memory when writing the answer in the socket. Reason is: {1}.	The connection will be closed because the socket reached an illegal state that may prevent server to handle further requests.	The remote client will not get any service from the server.	Archive the log messages and the trace messages Contact your SAP Support Team Recommendation Contact your SAP Support Team at support.sap.com/incident. You can create a customer message and report an incident in SAP Support Portal. Use IS-CC as SAP Component identifier dedicated to your SAP Convergent Charging software product.
24 (FATAL)	Transaction {0} cannot perform a checkpoint operation. Error message: {1}.	The JDBC connection cannot perform a checkpoint operation. This database access error mainly occurs if the connection was closed.	A part or the whole of the current operation could not be recorded.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
25 (FATAL)	Transaction {0} cannot perform a reset checkpoint operation. Error message: {1}.	The JDBC connection cannot perform a reset checkpoint operation. This database access error mainly occurs if the connection was closed.	A part or the whole of the current operation could not be recorded.	Check the previous error log messages Verify the configuration of the database parameters Verify the status of the database
26 (WARNING)	Timeout occurred on SQL connection: SQL manager has lost connection to database {0}.	The connection to the database system is not available anymore. As a consequence no database operation is available until the SAP CC system successfully reconnects to the back-end database system.	A part or the whole of the current operations could not be recorded.	Check the previous error log messages Verify the status of the database
27 (WARNING)	Timeout occurred on SQL connection: The connections to {0} are closed.	The connection to the database system is not available anymore. As a consequence no database operation is available until the SAP CC system successfully reconnects to the back-end database system.	A part or the whole of the current operations could not be recorded.	Check the previous error log messages Verify the status of the database
28 (ERROR)	Connection to database is refused. URI is: {0}. Properties are: {1}.	An attempt to create a connection to database was not successful. The creation of this connection will be attempted several times, according to configuration.	Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.	Check the previous error messages and verify the database configuration
29 (FATAL)	Cannot be connected to the database. URI is: {0}. Properties are: {1}.	Several attempts to create a connection to database were not successful. The creation of a connection to the database is not possible.	Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.	Check the previous error messages and verify the database configuration
30 (INFO)	SQL manager is connected to {0} using properties {1} ({2} connections in pool, {3} statements in cache).	SAP Convergent Charging is connected to the database. Several connections have been created and the statement cache is configured.			Relates to two former messages: SQL_MANAGER_CONNECTED used to indicate which database is connected and SQL_MANAGER_RUNNING to indicate how connections are configured.
31 (ERROR)	SQL manager is not able to connect to {0} using properties {1}	SAP Convergent Charging cannot be connected to the database.	Some instances of SAP Convergent Charging will not be fully functional. Unexpected behavior of the system may occur.	Check the previous error messages Verify the configuration of the database parameters Verify the status of the database
32 (INFO)	Connecting SQL manager to {0} as {1} ({2} connections in pool, {3} statements in cache).	SAP Convergent Charging is connecting to the database.
33 (INFO)	Connecting SQL manager to {0} using properties {1} ({2} connections in pool, {3} statements in cache).	SAP Convergent Charging is connecting to the database.
34 (INFO)	SQL manager is disconnected from {0}.	SAP Convergent Charging is disconnected from one database node.