3713677 - Import Job fails with "SAP DBTech JDBC: [1299]: no data found" when acquiring data from SAP HANA

• You are running an Import Data Job (Master Data or Transaction Data) in SAP Analytics Cloud (SAC). 
• The job fails consistently. 
• When checking the Rejection Summary or the error details in the Job Monitor, you see an error message similar to the following:
  • SAP DBTech JDBC: [1299]: no data found: search table error: "SCHEMA"."PACKAGE::FUNCTION_NAME": [1299] (range 3) no data found exception: no data found: "SCHEMA"."PACKAGE::FUNCTION_NAME": line XX col X
• Creating a new import job with the exact same settings may succeed, while the existing job continues to fail.

SAP Analytics Cloud 2025.21.11 

1. Log on to SAP Analytics Cloud.
2. Navigate to the Modeler or Data Management screen.
3. Select a model and run an existing Import Job from an SAP HANA source. 
4. The job fails after a few seconds or minutes.
5. Click on the Failed status to view the error details.
6. Observe the SAP DBTech JDBC: [1299]: no data found error.

• This issue is not caused by a defect in SAP Analytics Cloud. It is a SQLScript execution error occurring within the source SAP HANA database.
• The error [1299]: no data found indicates that a specific logic flow inside the HANA Table Function or Stored Procedure attempted to fetch a value into a variable (e.g., using a SELECT ... INTO ... statement) but the query returned empty results (0 rows).
• Because the custom logic in the HANA backend expects a value and does not handle the empty result set, the execution crashes. This typically happens due to:
  • Data Changes: The data in the source tables has changed, causing a specific filter or join condition to return no results for the "Old Job's" query scope. 
  • Structural Changes: A column name, view definition, or data type was modified in the backend, breaking the logic flow at the specific line number mentioned in the error.

To resolve this issue, the correction must be applied in the Source System , as SAC is merely reporting the exception thrown by the database. 

Step 1: Identify the Location 

Review the error message in SAC to identify the exact HANA object and line number.

• Example: "MySchema.MyPackage::MyFunction": line 23''

Step 2: Debug HANA Logic

• Review the code at the specified line number.
• The developer must identify the SQL statement causing the no data found exception.
• The logic should be adjusted to handle NULL values or empty result.

Step 3: Workaround

•  If the backend fix cannot be applied immediately, creating a New Import Job in SAC works
• A new job typically retrieves a fresh metadata snapshot or applies default filters that might bypass the specific data combination triggering the crash in the old job 

• KBA 3400311 -  Error: "Error in executing SQL conversion stored procedure, cause: SAP DBTech JDBC: [xxxx]: no data found" occurs in tasks - SAP Cloud Integration for data services 
• KBA 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
• KBA 2487011 - What information do I need to provide when opening a case for SAP Analytics Cloud?
• KBA 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
• SAP Analytics Cloud Connection Guide
• SAP Analytics Cloud Get More Help and SAP Support
• Need More Help? Contact Support 

Your feedback is important to help us improve our knowledge base.

SAC, Import, Failure, HANA, JDBC, 1299, no data found, SQLScript, Table Function, Stored Procedure, Backend. , KBA , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem