Page 1 of 1

Rejected row

Posted: Fri Sep 08, 2006 6:58 am
by pkomalla
Hi All,

I have hash file as input to a transformer and two outputs( one for target table and one for target error table)

In transformer I gave constraints as link1.rejected for the error table

link1 is output to target table

I am not getting the rejected row in error table but a warning which says
"DSP.Close Error -100 in $DSP.Close."

Anyone has the idea about this warning...

Thanks

Posted: Fri Sep 08, 2006 8:10 am
by thumsup9
So you have some rows getting rejected but not getting inserted into Error Table. Do you have the insert privileges on that table, Is the metadata same and also are there any constraint violations.. I woud try inserting some rows into this table first.

Posted: Fri Sep 08, 2006 8:17 am
by kcbland
What are the stages (ODBC, OCI, database please) and can you view data (connections are proper) and what is the SQL action?

Posted: Fri Sep 08, 2006 8:20 am
by kumar_s
Is this the only warning?

Re: Rejected row

Posted: Sat Sep 09, 2006 6:32 am
by rachitha
pkomalla wrote:Hi All,

I have hash file as input to a transformer and two outputs( one for target table and one for target error table)

In transformer I gave constraints as link1.rejected for the error table

link1 is output to target table

I am not getting the rejected row in error table but a warning which says
"DSP.Close Error -100 in $DSP.Close."

Anyone has the idea about this warning...

Thanks
Hi.

what is ur target error table is it a database table or seq file ?,
use caps in link1.REJECTED
on error output link is it show'g you number of rows rejected?
are there any primary key violation in the target table.?
it will be helpfull if you provide above details

rachitha.

constraints is right, check your input link

Posted: Sun Sep 10, 2006 11:30 pm
by changming
I think nothing wrong with your constraints.
check your database and input data are matching.

Posted: Mon Sep 11, 2006 3:48 pm
by ray.wurlod
$DSP.Close is a function exposed by a plug-in stage. That is, the problem is not with the Hashed File stage or the Transformer stage. Get your DBA to trace what's happening on these connections.