Issuuing abort after 50 logs

kumar_s · Post by **kumar_s** » Sun Aug 07, 2005 9:19 am

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

vmcburney · Post by **vmcburney** » Sun Aug 07, 2005 6:59 pm

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.

kumar_s · Post by **kumar_s** » Sun Aug 07, 2005 11:20 pm

yes,
iam getting null handling warnings and that too in thousands.
this was just exported from development environment to testing environment. And this error came up only in testing environment.

regards
kumar

dsxdev · Post by **dsxdev** » Sun Aug 07, 2005 11:56 pm

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

Code: Select all

$DSHOME/dsjob -run -warn <no of warnings> <project> <job name>

This will abort the job after specified no of warnings have ocured.

ray.wurlod · Post by **ray.wurlod** » Mon Aug 08, 2005 12:22 am

If running a job from Director you can set the number of warnings before an abort on the Limits tab of the Job Run Options dialog.

kumar_s · Post by **kumar_s** » Mon Aug 08, 2005 2:36 am

Hi,
May i know how to set this limit from unix command prompt.
from dsjob -run ...command.
(it does not gives me error when i call from director, mised this vital information.)

regards
kumar

kumar_s · Post by **kumar_s** » Mon Aug 08, 2005 2:49 am

Hi,

I could find the command is
dsjob ... -warn n...
Cant we set that n to no limt, as we have in director.

regards
kumar

kumar_s · Post by **kumar_s** » Mon Aug 08, 2005 4:17 am

It also gives me some more error like

XFM010,0: Failure during execution of operator logic.

Which was not in while we run from client director.

regards
kumar

chulett · Post by **chulett** » Mon Aug 08, 2005 6:59 am

kumar_s wrote:Cant we set that n to no limt, as we have in director.

-warn 0

(That's a zero, btw)

kumar_s · Post by **kumar_s** » Mon Aug 08, 2005 7:26 am

chulett wrote:
kumar_s wrote:Cant we set that n to no limt, as we have in director.
-warn 0

(That's a zero, btw)

Thanx chulett,
That really worked. Thanks

regards
kumar

kumar_s · Post by **kumar_s** » Mon Aug 08, 2005 7:31 am

kumar_s wrote:It also gives me some more error like

XFM010,0: Failure during execution of operator logic.
Which was not in while we run from client director.

regards
kumar

Is there any input to this

regards
kumar

ray.wurlod · Post by **ray.wurlod** » Mon Aug 08, 2005 6:12 pm

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:

XFM010

,0

operator logic

vmcburney · Post by **vmcburney** » Tue Aug 09, 2005 12:05 am

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.

ameyvaidya · Post by **ameyvaidya** » Wed Aug 10, 2005 3:06 am

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.

kumar_s · Post by **kumar_s** » Wed Aug 10, 2005 5:56 am

Hi Amey,
I toggled beteen enabling and disabling RCP

Atlast Disabled in both the project

regards
kumar

DSXchange

Issuuing abort after 50 logs

Issuuing abort after 50 logs

Switch off RCP flag at the project level.