How To Fix FDT_QUERY018 - There is still an open DB cursor for the old selection

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_QUERY - FDT: Query

• Message number: 018

• Message text: There is still an open DB cursor for the old selection

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 FDT_QUERY018 - There is still an open DB cursor for the old selection ?

  The SAP error message FDT_QUERY018 ("There is still an open DB cursor for the old selection") typically occurs in the context of using the SAP Fiori Design Studio or when working with SAP HANA views and queries. This error indicates that there is an open database cursor that has not been properly closed before a new selection or query is attempted. 
  Cause:
  
  Open Database Cursor: The error is primarily caused by an open database cursor from a previous query that has not been closed. This can happen if the application logic does not properly handle the closing of cursors after executing a query.
  Multiple Queries: If multiple queries are executed in succession without closing the previous ones, it can lead to this error.
  Long-Running Transactions: If a transaction takes too long to complete, it may leave cursors open longer than expected.
  
  Solution:
  
  Close Open Cursors: Ensure that all database cursors are properly closed after their use. This can often be done by explicitly closing the cursor in the application code.
  Review Application Logic: Check the application logic to ensure that it is not attempting to execute a new query while a previous one is still active. This may involve adding checks to see if a cursor is still open before executing a new query.
  Transaction Management: If you are using transactions, ensure that they are being committed or rolled back properly, which can help in closing any open cursors.
  Debugging: Use debugging tools to trace the execution flow and identify where the cursor is being left open. This can help pinpoint the exact location in the code that needs to be fixed.
  Database Connection Pooling: If applicable, review the database connection pooling settings to ensure that connections are being managed properly.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific patches or updates related to this error. Sometimes, SAP releases notes that address known issues with specific versions of their software.
  Documentation: Review the SAP documentation for the specific module or technology you are using (e.g., SAP HANA, Fiori, etc.) for best practices on managing database connections and cursors.
  Community Forums: Engage with SAP community forums or support channels where other users may have encountered and resolved similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance, providing them with detailed information about the context in which the error occurs.