SQL Interface - Error in Loading the data from SQL data source

Question

Hello,
We have been using SQl data source for loading the dimensions and the data for so many years. Even using Essbase 11.1.1.0, it's been quite a while (more than one year). For the past few days,we are getting the below error when trying to load the data.
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Info(1021013)
ODBC Layer Error: [S1000] ==> [[DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]CURSOR IDENTIFIED IN FETCH OR CLOSE STATEMENT
IS NOT OPEN (DIAG INFO: ).]
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Info(1021014)
ODBC Layer Error: Native Error code [4294966795]
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Error(1021001)
Failed to Establish Connection With SQL Database Server. See log for more information
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Error(1003050)
Data Load Transaction Aborted With Error [7]
[Mon Jan 10 11:02:56 2011]Local/{App Name}///Info(1013214)
Clear Active on User [Olapadm] Instance [1]
Interestingly, after the job fails thru our batch scheduler environment, when I run the same script that's being used in the batch scheduler, the job completes successfully.
Also, this is first time, I saw this kind of error message.
Appreciate any help or any suggestions to find a resolution. Thanks,

Answer 1

Hii Priya,
The reasons may be the file is open, the format/flatfile structure is not correct, the mapping/transfer structure may not be correct, presence of invalid characters/data inconsistency in the file, etc.
Check if the flatfile in .CSV format.
You have to save it in .CSV format for the flatfile loading to work.
Also check the connection issues between source system and BW or sometimes may be due to inactive update rules.
Refer
error 1
Find out the actual reason and let us know.
Hope this helps.
Regards,
Raghu.