OLEDB read failed

[#1]

Hi Folks,

I have an oracle query that runs fine in TOAD but when I try to run it in Qlikview I get the error "OLEDB read failed". The connection string is fine as I can run other queries against in the same application. Has anyone seen this error before and if so did you find a solution.

Thanks and Regards,

Footsie

[#2]

Some records are Chinese charactors. But they are in messy code. I deleted these messy code. Then "no error"

[#3]

I have the same issue. Sometimes the reload works and sometimes not even though the data is exactly the same.

I especially found this issue to occur when using the timestamp datatype and date functions such as from_tz.

It sounds like an oledb driver issue rather than qv issue when googling it. sadly that does not help I guess.

[#4]

Same thing happended to me!

What is even more frustrating is that I have seen error messages before saying duplicate column names, and thus, the error was VERY easy to find.

I think I know why, in my case at least, I didn't get this "duplicate columns" error message.

My load statement which was giving me the error was below;

LOAD DateId,

    HoursWorked,

    LaborHourType,

    LocationNum,

    ShiftCount,

    0                                                  as tODS_TransactionType_Key,

    1                                                  as tODS_TransactionSuperChannel_Key,

    0                                                  as tODS_LocationType_Key_Global,

    0                                                  as PlanFlag,

    0                                                  as StoreOpsGoal,

    0                                                  as SalesTranCountGoal,

    0                                                  as SoldSalesGoal,

    0                                                  as SoldUnitsGoal,

    0                                                  as VisitsGoal,

    0                                                  as GmPlan,

    0                                                  as SalesPlan,

    0                                                  as SalesForecast,

    1                                                  as PlanFlag;      

SQL SELECT DateId,

    HoursWorked,

    LaborHourType,

    LocationNum,

    ShiftCount

FROM EDW.Logical."vEDW_R_TimeAttend_v2"

where DateId >= 20100131;

You notice thw two "PlanFlag" columns are both "derived", and I think this may be why the error message I was received was the cryptic OLE DB error.  Previously, I had the duplicate columns in the actual SQL select..

Anyone else seen this?

[#5]

Hello there,

I am experirnceing the same error and as I am quite new to QV I gather that in my case the solution is elementary...

I have noticed that this message occurs ONLY when I add this line in the expression

"Count(DISTINCT(OrderID)) AS OrderIDRecordCounter"

is the expression wrong or are there other factors to be considered?

Thanks!

[#6]

Ok, this is how I fixed my rendition if this error:

!)  When into my SQL Server Management Studio and highlighted the SQL code into the 'Design' option to visually see the stored procedure in the design grid.  When I did I noticed a field had 'Expr1' in the alias column.  So I realized Qlikview was getting a datatype mismatch because my: 

CASE

WHEN OE.WORK_PERMIT_FLAG = 1 THEN 'Yes' ELSE 'No' END AS

WORK_PERMIT_FLAG

column was missing the '

AS 

WORK_PERMIT_FLAG'  alias declaration in the code.  Once I properly aliased the field the error was gone.  I hope this helps.  Make sure your columns are aliased properly or your datatypes in your calculated fields are properly declared to match.  Thanks, again.

[etay_netintent]

Hi Chris.

Are you sure you are getting an OLEDB message ?? Your duplicate column is in the LOAD section.

Try running the select WO the LOAD section.

[etay_netintent]

Hi There.

We have run into issues like this in the past.

Sometimes you get an oledb message, and when you press OK there is still data coming in.

If you limit the number of rows selected the query works.

OLEDB and ODBC both may encounter s record containing a non standard character and raise an exception.

Is any one aware of a limit on the number of lines that can be extracted via OleDB from LDAP ??

[SunilChauhan]

i have seen that if some field user more than one time in select query  then its throwing error.

as i am facing this i have commented duplicate columns.its running now .

i have done one more thing but i am not sure that imapacting

i have changed sql comment(-------) to Qlikview Comment(//)

hope this helps

[ThornOfCrowns]

This is a very old thread, several years old, in fact and your reply is to a post from several months ago.

[SunilChauhan]

i know that . i has just reply. so that it might be refrence for others

and help to some extents

Thanks