Parallel job reports failure (code 139)

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Parallel job reports failure (code 139)

Post by kavuri »

Hi,
I am using a simple job to read data from Netezza database and have a copy stage and load into a different Netezza database. To read from Netezza database in the first stage I am using ODBC Enterprise stage. I am getting the following error when I run the job.

Parallel job reports failure (code 139)

When I tried to view data, It is throwing some message which is not an error.

##I TFCN 000001 13:29:29(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5.2
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved


##I TOSH 000002 13:29:29(001) <main_program> orchgeneral: loaded
##I TOSH 000002 13:29:29(002) <main_program> orchsort: loaded
##I TOSH 000002 13:29:29(003) <main_program> orchstats: loaded
##I TFSC 000001 13:29:29(004) <main_program> APT configuration file: /opt/IBM/Ascential/DataStage/Configurations/default.apt

Please tell me how to resolve this. I tried the following settings as I searched the previous ones

APT_MONITOR_SIZE=100000 and
APT_MONITOR_TIME=5.

Thanks
Bhargava
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Re: Parallel job reports failure (code 139)

Post by ArndW »

kavuri wrote:...When I tried to view data, It is throwing some message which is not an error. ..
What is the message (it might be pertinant)?
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Re: Parallel job reports failure (code 139)

Post by kavuri »

Hi,
Below is the message I am getting.

No rows were returned from the View Data Server Command. Would you like to view the command's output?

If I say yes, following message appears.

##I TFCN 000001 16:17:10(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5.2
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved


##I TOSH 000002 16:17:10(001) <main_program> orchgeneral: loaded
##I TOSH 000002 16:17:10(002) <main_program> orchsort: loaded
##I TOSH 000002 16:17:10(003) <main_program> orchstats: loaded
##I TFSC 000001 16:17:10(004) <main_program> APT configuration file: /opt/IBM/Ascential/DataStage/Configurations/default.apt

I am having one doubt is we are having 2 database servers. On both we have 2 instances with same name and credentials ( i.e username and passwords). In ODBC Enterprise stage we are not giving any server name or ip. we are passing only database instant. So datastage is not able to resolve the instance, I think.

Please correct me if I am wrong. If I am correct please let me know, how we can resolve the database instances?

Thanks
Bhargava
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Do you have a SELECT clause? If yes, does it return data when used in your favorite SQL tool? What happens if you run the job instead of using view-data?
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

What you posted here consists of five informational messages. Was there any more?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
priyadarshikunal
Premium Member
Premium Member
Posts: 1735
Joined: Thu Mar 01, 2007 5:44 am
Location: Troy, MI

Re: Parallel job reports failure (code 139)

Post by priyadarshikunal »

first of all try switching off the job monitor (set APT_NO_JOBMON = True)if setting the monitor time and monitor size doesn't work.

and tell us the result.
Priyadarshi Kunal

Genius may have its limitations, but stupidity is not thus handicapped. :wink:
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Re: Parallel job reports failure (code 139)

Post by kavuri »

Here are answers to the questions.

ArndW,
Do you have a SELECT clause? If yes, does it return data when used in your favorite SQL tool?

I am able to select the data from command prompt.

What happens if you run the job instead of using view-data?

That gave me the following error.

Parallel job reports failure (code 139)

Ray,
What you posted here consists of five informational messages. Was there any more?

There are no other messages.

Kunal,
first of all try switching off the job monitor (set APT_NO_JOBMON = True)if setting the monitor time and monitor size doesn't work.

As a developer can I do it? or do I need admin preveleges? If I can can you tell me where I can do it?

Thanks
Bhargava
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Re: Parallel job reports failure (code 139)

Post by kavuri »

Here are answers to the questions.

ArndW,
Do you have a SELECT clause? If yes, does it return data when used in your favorite SQL tool?

I am able to select the data from command prompt.

What happens if you run the job instead of using view-data?

That gave me the following error.

Parallel job reports failure (code 139)

Ray,
What you posted here consists of five informational messages. Was there any more?

There are no other messages.

Kunal,
first of all try switching off the job monitor (set APT_NO_JOBMON = True)if setting the monitor time and monitor size doesn't work.

As a developer can I do it? or do I need admin preveleges? If I can can you tell me where I can do it?

Thanks
Bhargava
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Re: Parallel job reports failure (code 139)

Post by kavuri »

Further,
I am seeing the following info when I run the job.

Contents of phantom output file =>
RT_SC609/OshExecuter.sh: line 20: 31321 Segmentation fault (core dumped) $APT_ORCHHOME/bin/osh "$@" -f $oshscript >$oshpipe 2>&1

Parallel job reports failure (code 139)

Job test_copy_table aborted.

Let me know if there are any setting need to be made.

Thanks
Kavuri
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

After the job aborts with 139, do a reset in the director and see if you get a message titled "From previous run..."
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Post by kavuri »

ArndW wrote:After the job aborts with 139, do a reset in the director and see if you get a message titled "From previous run..."
No ArndW,
There is no message like that. It simply says
Resetting Job test_copy_table.
Job test_copy_table has been reset.

Thanks
Kavuri
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Post by kavuri »

ArndW wrote:After the job aborts with 139, do a reset in the director and see if you get a message titled "From previous run..."
No ArndW,
There is no message like that. It simply says
Resetting Job test_copy_table.
Job test_copy_table has been reset.

Thanks
Kavuri
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Can you post the select statement (and tell us which DB you are using ODBC to go to). Are there any data types or sizes that aren't common?
kavuri
Premium Member
Premium Member
Posts: 161
Joined: Mon Apr 16, 2007 2:56 pm

Post by kavuri »

Hi ArndW,
we are using Netezza database. Here below is a snapshot.


Thanks
Kavuri
Last edited by kavuri on Thu Apr 10, 2008 6:32 pm, edited 1 time in total.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

What if you try the select on just one column, PSD_STR_ID, do you get the same error?
Post Reply