Errors related to the initialization and usage of the back-end database.
To continue your troubleshooting investigations, select the error code signaled in the operation response replied by the SAP CC system:
| Error Code | Message | Action |
|---|---|---|
| SQL-1 | Incompatible database version ({0}). | Upgrade database to a compatible version. |
| SQL-2 | Cannot find JDBC driver ({0}). | Check your classpath. |
| SQL-3 | Bad URL syntax : {0}. Expected format: {1}. | URL must have the format {1}. |
| SQL-4 | Unable to finish the SQL IResultSet {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-5 | The SQLServer database is not in read committed snapshot mode | Set the SQLServer database in read committed snapshot mode. Use : 'alter database <DB NAME> SET READ_COMMITTED_SNAPSHOT ON' |
| SQL-6 | The SQL Exception due to {0} SQL state is not fatal and can be retried. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-7 | Cannot add statement to batch due to {0} SQL State | Consult your database documentation to get information about the {0} SQL state. |
| SQL-8 | Cannot set statement batch size due to {0} SQL State | Consult your database documentation to get information about the {0} SQL state. |
| SQL-9 | Cannot execute statement batch due to {0} SQL State | Consult your database documentation to get information about the {0} SQL state. |
| SQL-10 | Cannot set timestamp on prepareStatement due to {0} SQL State | Consult your database documentation to get information about the {0} SQL state. |
| SQL-11 | A failover is required by the SQL Exception due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-12 | The database is not ready to accept SQL query. SQL state {0} | Consult your database documentation to get information about the {0} SQL state. |
| SQL-13 | Unable to change transaction isolation level to {0} due to SQL state {1} | Consult your database documentation to get information about the {0} SQL state. |
| SQL-14 | Unable to reserve ID range for ids generation due to SQL state {0} | Consult your database documentation to get information about the {0} SQL state. |
| SQL-15 | Unable to get BigDecimal value from resultSet due to SQL state {0} | Consult your database documentation to get information about the {0} SQL state. |
| SQL-16 | The backup JDBC URI ({0}) must begin by {1} like the primary JDBC URI ({2}) | Consult your JDBC driver documentation to get information about the URI format |
| SQL-17 | Invalid JDBC URI ({0}) or related JDBC driver not found | Refer to the documentation of the SQLHELPER_JDBC_URI system parameter to check the syntax of the specified URI. In case your URI corresponds to an Oracle RDBMS, check that the corresponding JDBC driver is available within your landscape and matches the minimum required version. |
| SQL-18 | There is no SQL transaction opened for the current process. | A SQL transaction must be opened to use the database, please contact support. |
| SQL-19 | The SQL Manager is closed and cannot be used anymore. | Verify that your process is not shutting down. |
| SQL-20 | A shutdown has been called on this SQL connection pool. SQL connection cannot be delivered. | Verify that your process is not shutting down. |
| SQL-21 | This SQL transaction has been canceled and cannot be used anymore. | Open a new transaction for your process. |
| SQL-22 | Unable to execute the SQL operation due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-23 | Unable to commit the SQL transaction due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-24 | Unable to rollback the SQL transaction due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-25 | Unable to close the SQL prepared statement due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-26 | Unable to close the SQL statement due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-27 | Unable to close the SQL prepared statement due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-28 | Unable to close the ResultSet for Big Query statement due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-29 | Unable to commit the database connection for Big Query statement due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-30 | Unable to close the database connection for Big Query statement due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-31 | Unable to get the value of Microsoft SQLServer is_read_committed_snapshot_on parameters due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-32 | Unable to close the ResultSet used to get the value of Microsoft SQLServer is_read_committed_snapshot_on parameters due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-33 | Unable to create the {0} prepared statement due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-34 | Unable to close the prepared statement used by this query {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-35 | Unable to prepare statement for {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-36 | Unable to execute prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-37 | The driver and SQLServer database are not in sync regarding date management. {0} SQL state. | Consult your database or your driver documentation to get information about the {0} SQL state. |
| SQL-38 | Unable to execute the addBatch() method of the prepared statement using the Oracle JDBC driver due to {0} SQL state. | Consult your database or your driver documentation to get information about the {0} SQL state. |
| SQL-39 | Unable to use the SQL Connection pool as it has been shutdown. | Verify that the server instance is not shutting down. |
| SQL-40 | Unable to close prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-41 | Unable to execute the prepared statement {0} and build a ResultSet due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-42 | Unable to execute the DML prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-43 | Unable to cancel the prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-44 | Unable to set object {0} of type {1} at position {2} in the prepared statement {3} due to {4} SQL state. | Consult your database documentation to get information about the {4} SQL state. |
| SQL-45 | Unable to reserve ID range for ids generation because there is no line in ID_TABLE. | Check your database scripts to see if the original line has been inserted in ID_TABLE. |
| SQL-46 | Unable to add the current batch to the prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-47 | Unable to execute the batch of DML prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {1} SQL state. |
| SQL-48 | Unable to use the embedded ResultSet due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-49 | Unable to make a checkpoint on the SQL transaction due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-50 | Unable to revert the last checkpoint on the SQL transaction due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-51 | Unable to add batch on the prepared statement {0} due to {1} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-52 | Unable to execute the prepared statement {0} on a close SQL connection. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-53 | Unable to execute an update to the prepared statement {0} on a close SQL connection. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-54 | Unable to execute a batch to the prepared statement {0} on a close SQL connection. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-55 | Unable to set object to the prepared statement {0} on a close SQL connection. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-56 | Unable to add batch on the prepared statement {0} on a close SQL connection. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-57 | Unable to cancel the prepared statement {0} on a close SQL connection. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-58 | Unable to reconnect ID generation connection due to SQL state {0}. | Consult your database documentation to get information about the {0} SQL state. |
| SQL-59 | This database does not support to store strings which end with a space character ({0}). | Sanitize the data so that strings do not end with a space character. |
| SQL-60 | Unable to retrieve the size of the column {0} of the table {1} due to {2} SQL state. | Consult your database documentation to get information about the {2} SQL state. |
| SQL-61 | The server is not connected to the database using the URL {0}. | The database with the URL {0} is offline or it is not possible to connect to it. Check the status of the database and reconnect the server to the database using the adequate Admin+ command. |
| SQL-62 | Cannot process statement because a Server failure exception occurred. | Contact your SAP Support Team. |
| SQL-63 | Cannot process statement because the database update pool for the database {0} is not enabled. | Enable the database update pool. |
| SQL-64 | Unable to change the transaction isolation level due to {0} SQL state. | Consult your database documentation to get information about the {0} SQL state. |
The SAP CC system fills in the error message dynamically with relevant information. {0} marks such an information entry.
