VIEWDATA ROW LIMITER HIT Error when query return no rows

[angelovaira]

Hi,

I am working with ibm information server 8.1.
In a parallel job, when I execute a user defined query from an oracle enterprise stage, if the query returns rows there are no problems. If the table from which I am extracting records is empty, the view data returns the error VIEWDATA ROW LIMITER HIT. If I try to execute the job, it aborts with some warnings. The first one is:

SQL*Loader-500: Impossible to open file (\.\pipe\ora.5688.915000.fifo.0)

The fatal error is: The call to sqlldr failed; the return code = 256;
please see the loader logfile: D:/IBM/InformationServer/Server/Scratch/ora.5688.915000.0.log for details.

I think these are false errors because if the dataset is empty, the job should just start and terminate without loading any row.

Please can anyone help me with this issue ?

Thank a lot,

Angelo.

[chulett]

I think you are *basically* correct about the "false errors", you'll get that message from the data viewer whenever it runs out of records to display... it's just that you run out of them right away when whatever you are viewing is empty.

The load/sqlldr issue is a whole 'nuther kettle of fish AFAIK. I'll let others pipe in here, but from what I recall it is not like most of the other processes that will happily consume an empty file or record set. I seem to recall it needing a non-empty source in order to function, and that people would typically need a pre-step to check their source and branching job control to only call the loading job when there is in fact something to load.

Can anyone confirm or deny?

[ArndW]

There might be more involved here as well, since MKS Toolkit requires that named pipes must be located at "$ROOTDIR/fifos", where the rootdir is the installation directory, usually "c:\Progra~1\MKS Toolkit\"