Fatal Errors of com.sap.SCC.infra (SAP CC 5.0 Log Messages)

Fatal Errors of com.sap.SCC.infra

Fatal Errors

The SAP CC system or a subcomponent cannot recover from error, and the severe situation causes its fatal termination. The SAP CC system is not usable anymore and cannot be started without corrective actions by experts (administrators, support specialists).

Resolution Plan and Troubleshooting

Immediate Correction Actions

The administrators do an immediate follow-up activity to analyze the logs and traces to determine further investigations before being able to identify the correction actions to be performed.

Recommendation

In a production system landscape, contact your SAP Support Team at support.sap.com/incident.

Fatal Error Messages

The administrators of the SAP CC systems may perform troubleshooting operations relating to the following log messages with a fatal severity:

Log Message (Fatal Error) Possible Impacts

Cannot be connected to the database. URI is: {0}. Properties are: {1}.
Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.

Cannot be connected to the database. URI is: {0}. User login is: {1}.
Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.

Connection with the remote client {0} is closing because an error occurred with the connection selector thread. Reason is: {1}.
The remote client will not get any service from the server.

Connection with the remote client {0} is closing because an error occurred with the socket network. Reason is: {1}.
The remote client will not get any service from the server.

Connection with the remote client {0} is closing because it has sent an invalid request. Reason is: {1}.
The remote client will not get any service from the server.

Connection with the remote client {0} is closing because it has sent an invalid request. Reason is: {1}.
The remote client will not get any service from the server.

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 remote client will not get any service from the server.

New remote connection from address {0} is refused for out of memory reason: {1}
The remote client will not get any service from the server.

Transaction {0} cannot execute the query {1}. Parameters: [{2}]. Error reason: {3}.
A part or the whole of the current operation could not be recorded.

Transaction {0} cannot execute the query {1}. Parameters: [{2}]. Error reason: {3}.
A part or the whole of the current operation could not be recorded.

Transaction {0} cannot perform a checkpoint operation. Error message: {1}.
A part or the whole of the current operation could not be recorded.

Transaction {0} cannot perform a commit operation. Error message: {1}.
A part or the whole of the current operation could not be recorded.

Transaction {0} cannot perform a reset checkpoint operation. Error message: {1}.
A part or the whole of the current operation could not be recorded.

Transaction {0} cannot perform a rollback operation. Error message: {1}.
A part or the whole of the current operation could not be recorded.

Log Message (Fatal Error)	Possible Impacts
Cannot be connected to the database. URI is: {0}. Properties are: {1}.	Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.
Cannot be connected to the database. URI is: {0}. User login is: {1}.	Some instances of the SAP CC Core Server system will not be fully functional. Unexpected behavior of the system may occur.
Connection with the remote client {0} is closing because an error occurred with the connection selector thread. Reason is: {1}.	The remote client will not get any service from the server.
Connection with the remote client {0} is closing because an error occurred with the socket network. Reason is: {1}.	The remote client will not get any service from the server.
Connection with the remote client {0} is closing because it has sent an invalid request. Reason is: {1}.	The remote client will not get any service from the server.
Connection with the remote client {0} is closing because it has sent an invalid request. Reason is: {1}.	The remote client will not get any service from the server.
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 remote client will not get any service from the server.
New remote connection from address {0} is refused for out of memory reason: {1}	The remote client will not get any service from the server.
Transaction {0} cannot execute the query {1}. Parameters: [{2}]. Error reason: {3}.	A part or the whole of the current operation could not be recorded.
Transaction {0} cannot execute the query {1}. Parameters: [{2}]. Error reason: {3}.	A part or the whole of the current operation could not be recorded.
Transaction {0} cannot perform a checkpoint operation. Error message: {1}.	A part or the whole of the current operation could not be recorded.
Transaction {0} cannot perform a commit operation. Error message: {1}.	A part or the whole of the current operation could not be recorded.
Transaction {0} cannot perform a reset checkpoint operation. Error message: {1}.	A part or the whole of the current operation could not be recorded.
Transaction {0} cannot perform a rollback operation. Error message: {1}.	A part or the whole of the current operation could not be recorded.

Note

Consult the other error log messages in com.sap.SCC.infra and their associated resolution plans.