DBIF_DSQL2_NATIVE_CR_ERROR is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: D - Error in Database Interface
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Triggering SQL statement: <runtime parameter>
Database error code...: <runtime parameter>
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal call code for more details about the possible cause of this runtime error and how it could be avoided.
Error with COMMIT/ROLLBACK on Native SQL database connection.
For a detailed description of the error, see the SAP system log. There
is probably an error with the database.
Any remaining open transactions (for example from the "DEFAULT"
connection) were rolled back.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
The error occurred in the current database connection "<runtime parameter>".
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
DBIF_DSQL2_NATIVE_CR_ERROR - dbif dsql2 native cr error DBIF_DSQL2_MIXED_CR_ERROR - dbif dsql2 mixed cr error DBIF_DSQL2_KEY_NOT_FOUND - dbif dsql2 key not found DBIF_DSQL2_KEY_ALREADY_EXISTS - dbif dsql2 key already exists DBIF_DSQL2_INVALID_REQUEST - dbif dsql2 invalid request DBIF_DSQL2_INVALID_CURSOR - dbif dsql2 invalid cursor