How To Fix S1379 - Activate new Native SQL Interface(using abap/no_dsql95=OFF)

SAP Error Message - Details

• Message type: E = Error

• Message class: S1 - Statistik / SAP-Monitor

• Message number: 379

• Message text: Activate new Native SQL Interface(using abap/no_dsql95=OFF)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message S1379 - Activate new Native SQL Interface(using abap/no_dsql95=OFF) ?

  The SAP error message S1379, which states "Activate new Native SQL Interface (using abap/no_dsql95=OFF)," typically occurs when there is an issue with the configuration of the Native SQL interface in the ABAP environment. This error is related to the use of Native SQL statements in ABAP programs.
  Cause:
  The error is triggered when the system is configured to use an older version of the Native SQL interface, which may not support certain features or syntax that your ABAP code is trying to use. The specific cause can be due to:
  
  Configuration Settings: The system parameter abap/no_dsql95 is set to ON, which means the system is using the older SQL interface.
  Code Compatibility: The ABAP code may be written using features that are only available in the newer SQL interface.
  System Version: The SAP system version may not support the features being used in the Native SQL statements.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Change System Parameter:
  
  You need to change the system parameter abap/no_dsql95 to OFF. This can typically be done by an administrator with access to the SAP system settings.
  You can do this by using transaction RZ10 to modify the instance profile or the default profile. Look for the parameter abap/no_dsql95 and set it to OFF.
  After making this change, you will need to restart the application server for the changes to take effect.
  
  
  
  Review ABAP Code:
  
  Review the ABAP code that is causing the error. Ensure that it is compatible with the newer Native SQL interface. If necessary, refactor the code to use supported syntax and features.
  
  
  
  Check SAP Notes:
  
  Check for any relevant SAP Notes that may provide additional guidance or patches related to this error. SAP Notes can provide fixes or workarounds for known issues.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation for the version you are using to understand the differences between the SQL interfaces and any specific requirements for using Native SQL.
  
  
  
  Related Information:
  
  Native SQL: Native SQL allows you to execute database-specific SQL statements directly in ABAP. It is important to ensure that the SQL statements are compatible with the database being used.
  ABAP Development: When developing ABAP programs, it is essential to be aware of the SQL interface being used and to write code that is compatible with the system's configuration.
  Performance Considerations: Using Native SQL can have performance implications, so it is advisable to use it judiciously and only when necessary.
  
  If you continue to experience issues after following these steps, consider reaching out to your SAP Basis team or SAP support for further assistance.