Warning Message while records are rejected

sudharsanan · Post by **sudharsanan** » Mon Feb 28, 2005 4:00 am

Hello Gurus,

I need some help in my job design, i have a sequential file as input and a transformer and one seqential file and reject data as output.. in my transformer i use a constraint for moving the data.. whenever the job has some reject record i see the status in the director as Finished(See log) for the job...my job has successfully completed...i have a sequence which calls the job..i have given only to conditions.. either aborted or success.. now should i have to have another status as finished see log.. how to handle this?.. also is there is any way by which i can suppress this warning?.. please help me resolving this issue...

Thanks

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon Feb 28, 2005 4:06 am

If you have any rejects, it will show up as warning.

A way to avoid this is to remove the tick from the reject box and add a condition in its place. i.e. if the target says (A = B) then you can have your reject file created with the condition as (A <> B) rather than the tick in reject.

Alternatively, you can include an action in your sequencer for 'Finished with Warning'.

ArndW · Post by **ArndW** » Mon Feb 28, 2005 4:11 am

Hello - the warnings you are seeing in the log files are automatically generated when you activate the rejects check-box constraint in the transformer. If you only have one other output link you can simple put a NOT(<other-link-condition>) constraint on what you would consider the reject link. This adds a little bit of processing overhead, but you would not be getting any warnings written to your log file.

(I just edited this post and saw that Sainath posted simultaneously

)

phanee_k · Post by **phanee_k** » Mon Feb 28, 2005 6:00 am

Hi,
Say suppose you have 2 links A and B.
On Link A you gave some constraint.
On Link B , give a constraint as Link A.rejected.
This will pass all the records failed from A to B without any warnings.

IHTH,

Phani

ArndW · Post by **ArndW** » Mon Feb 28, 2005 6:27 am

Phani,

that's a good one - I'll have to try that next time as it's more efficient than putting in an additional and superfluous constraint!

Thanks,

-Arnd.

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon Feb 28, 2005 6:30 am

But we need to verify on how it handles if the target rejects the rows because of its ability (or inability). For e.g. loading into an RDBMS such as DB2 with data that does not match its constraints.

Also there are some sightings of link variables such as NOTFOUND returning incorrect results.

sudharsanan · Post by **sudharsanan** » Mon Feb 28, 2005 7:21 am

Thanks Phani for the input.. i tried that option it is working fine.. i have one more question if suppose i have more than two constraints in output which one i have to use for reject...is this the correct method to use.. does anybody has some other logic to avoid the warning of reject records.. please help..

Thanks

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon Feb 28, 2005 7:53 am

You need to combine both with an AND logical operator.

chulett · Post by **chulett** » Mon Feb 28, 2005 7:54 am

There's really only one way to avoid the warning of reject records - don't create any. In other words, don't send any records to your target that you know will be rejected.

Besides doing everything you can to ensure the data is 'clean', you can logically reject known problem records via a contraint as mentioned before pushing them to your target. The only way this should generate an error is if you also enable the 'Reject Row' check box.

If, when all is said and done, you write a record to your target stage and the target rejects it (for whatever reason) you will log a warning.

In your first post, you asked how to handle multiple triggers from this job. Either use two triggers - one Ran Ok and one Ran with Warnings - run them into a Sequencer set to 'Any' and then on to the next job. Either that or use a single Custom trigger like so:

Code: Select all

JobStage.$JobStatus=1 or JobStage.$JobStatus=2

'JobStage' needs to be the actual name of the Job Activity stage that runs the job you want checked. The '1' and '2' are the internal representations of the Ok and Warning status codes.

sudharsanan · Post by **sudharsanan** » Mon Feb 28, 2005 8:17 am

Thanks chulett, i will try to use the "Either use two triggers - one Ran Ok and one Ran with Warnings - run them into a Sequencer set to 'Any' and then on to the next job" option in my sequence so that i can get rid of this warning messages...this will also be useful all my jobs.. because in some jobs i get warning messages in the director. but the job would have completed successfully.. so i will use this option in the sequence to catch the warnings that happens..sometime i get printer memory segment error as warning..which usually my job will not catch i was wondering on how to catch such messages.. thanks for the input...and also thanks to everyone in this forum for helping me in solving problems....

chulett · Post by **chulett** » Mon Feb 28, 2005 8:26 am

If you are curious about the 'printer segment' messages, search the forum. The cause and possible solutions have been posted several times, from what I remember.

sudharsanan · Post by **sudharsanan** » Mon Feb 28, 2005 8:33 am

chulett,

I have seen the post given by Ray in December 2003..he has given the reason for this problem.. I am clear with that, i just want to give soem examples about some other warnings that i used to get in director...

Thanks..

arunverma · Post by **arunverma** » Sat Jun 03, 2006 12:35 am

Hi sudharsanan ,

I have gone throgh a lot of posted message and in 80% case reply found that go to search fourm ,

As Mr . Mr. Ray
" Every connected DataStage process is allocated a shared memory segment, called the "printer shared memory segment" because
the largest structure in it contains preset values for up to sixteen output c ... "

and some where advice to avid rejected condition in transformation .

We are geeting this error for last 2 days any one of job . as per or DS structure we having 190 application and 7000 ETL job .

SO can any body help me how to avoid this error .

Regards
Arun Verma

sudharsanan wrote:chulett,

I have seen the post given by Ray in December 2003..he has given the reason for this problem.. I am clear with that, i just want to give soem examples about some other warnings that i used to get in director...

Thanks..

DSguru2B · Post by **DSguru2B** » Sat Jun 03, 2006 11:09 am

You have picked up a post thats been dead since Feb 2005. You can see that info. in the date part of the header of the post.

ray.wurlod · Post by **ray.wurlod** » Sat Jun 03, 2006 3:59 pm

Nor did you mention exactly what error you are getting. It is helpful for diagnosis if you post the entire error messages.