TR3311 error in transformer

[camjai]

I'm getting a mysterious error message while building a powercube. (see below). I'm trying to build a cube from a couple of IQD's. I know it's the IQD that shows some data on projects that's causing the problem. When I use a filter in Impromptu to show just a couple of projects and I save it in IQD there's no problem when trying to build a cube. But when I remove the filter to show more projects in the IQD, Transformer is unable to read the data in that IQD (when using data source viewer) and the error msg appears.

I've already tried zeroing down the error to a certain row in the IQD but it seems to be a combination of rows.

Any ideas? Thanks.

-----------------

(TR3311) An error occurred during data retrieval from the database. Refer to Details for
more information.

Details:
DMS-E-SECURITY, Tried to execute an operation during 'fetch' without the proper authorisation.
DMS-I-INFORMATION, The target-database has delivered information regarding the 'fetch' operation.
[IBM]iSeries Access ODBC-driver][DB2 UDB]SQL 7963 - 564 rows retrieved from cursor SQL_CUR04874FF0 (with FETCH-instruction)
[IBM]iSeries Access ODBC-driver]Error in row.

 

[camjai]

Forgot to mention there are no error message when viewing the data (IQD) in Impromptu.

 

[drlex]

How may rows are you retrieving in Impromptu? Is it possible that the error is after the initial 100 rows of the default retrieval?

soi la, soi carre

 

[DoubleD]

Check your datatypes in your MDL to ensure they match your database. If for instance, you've got a field that contains mostly numbers, except for a couple entries which are varchar. Transformer might be assuming this is a numeric field since it uses the first 100 records to set the default field properties.
It looks like you're working against an Access database, are you sure there aren't corrupt records in your database?


Pain is stress leaving the body.

DoubleD

 

[camjai]

I'm retrieving well over 100 rows of data. Why would that cause an error? I'm using an Oracle database.

I've somehow stopped the error from occuring. It may have something to do with the joins in the catalog underlying the .iqd files? Thanks for that tip on datatypes DoubleD. I'm sure it'll come in handy.