Issuuing abort after 50 logs
Moderators: chulett, rschirm, roy
Issuuing abort after 50 logs
Hi,
Iam getting huge number of warnings.
Once it reaches more that 50 number of log error (warnings) it spits out with an Fatal error of "issuuing abort after 50 logs".
This all happens in our new project and which was not there i previous project.
I understant there is some settings to be chaged.
May i know how?
regards
kumar
Iam getting huge number of warnings.
Once it reaches more that 50 number of log error (warnings) it spits out with an Fatal error of "issuuing abort after 50 logs".
This all happens in our new project and which was not there i previous project.
I understant there is some settings to be chaged.
May i know how?
regards
kumar
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
It all depends on what warning messages you are getting.
You shouldn't be getting any warnings. At worst you should be getting a handful of warnings due to a null handling or implicit conversion clash that doesn't cause any harm.
You shouldn't be getting any warnings. At worst you should be getting a handful of warnings due to a null handling or implicit conversion clash that doesn't cause any harm.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Hi,
You can reduce the number of warning by changing the metadata.
if you still get lot of warnings you can abort the job after 50 or more warnings.
For this
you can set limit on warnings while runing from Designer or Director by setting limits in limits page of window that pops up when you run the job.
if you run the job using dsjob utility from Unix command lline then use -warn option with dsjob command
This will abort the job after specified no of warnings have ocured.
You can reduce the number of warning by changing the metadata.
if you still get lot of warnings you can abort the job after 50 or more warnings.
For this
you can set limit on warnings while runing from Designer or Director by setting limits in limits page of window that pops up when you run the job.
if you run the job using dsjob utility from Unix command lline then use -warn option with dsjob command
Code: Select all
$DSHOME/dsjob -run -warn <no of warnings> <project> <job name>
Happy DataStaging
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's completely unrelated to the thread topic. Please start a new thread.
When posting, please include any diagnostic approach you may already have taken, so that you're not wasting our time repeating the same.
What is the message telling you? In particular, what do you understand by:
When posting, please include any diagnostic approach you may already have taken, so that you're not wasting our time repeating the same.
What is the message telling you? In particular, what do you understand by:
- XFM010
,0
operator logic
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I couldn't see a new thread for your "Failure during execution of operator logic" however it is almost certainly related to your NULL value problem. When you moved to test you started to see a huge number of NULL value warning messages, probably because your test database has different data to your dev database. The warning is telling you that a null was found in a field where one was not expected. If you then try to use this field in a transformer calculation you can get the operator logic error.
You need to analyse your test data to work out why you are getting so many null values. If those null values are valid you need to add null handling to your job such as transformer NullToValue functions or Modify stage handle_null functions.
As I said originally you should not be getting 50+ warnings in your job, this is a poorly designed job that is not production ready, you need to keep your 50 warning limit in place and fix the source of the warnings.
You need to analyse your test data to work out why you are getting so many null values. If those null values are valid you need to add null handling to your job such as transformer NullToValue functions or Modify stage handle_null functions.
As I said originally you should not be getting 50+ warnings in your job, this is a poorly designed job that is not production ready, you need to keep your 50 warning limit in place and fix the source of the warnings.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Charter Member
- Posts: 166
- Joined: Wed Mar 16, 2005 6:52 am
- Location: Mumbai, India
Switch off RCP flag at the project level.
Hi kumar_s,
Check if both projects have the same setting for Enable Runtime Column Propogation for Parallel Jobs. I suspect that this may have been switched off in the Dev Project and on in the testing project.
If this is true, recompiling jobs in the testing project would have removed all modify operators present in the compiled jobs in the Dev project and would be the source of the warnings.
Amey.
Check if both projects have the same setting for Enable Runtime Column Propogation for Parallel Jobs. I suspect that this may have been switched off in the Dev Project and on in the testing project.
If this is true, recompiling jobs in the testing project would have removed all modify operators present in the compiled jobs in the Dev project and would be the source of the warnings.
Amey.