error while running the job
Moderators: chulett, rschirm, roy
error while running the job
Hi ,
When I run the job I am getting the following error
"Operator terminated abnormally: received signal SIGSEGV"
my database connections are good. it is running 3 minutes and after that my job is aboring with the above error.
can any one suggest me please. I am hoping its memory error, so I changed scrach desk path as well. but it won't work.
When I run the job I am getting the following error
"Operator terminated abnormally: received signal SIGSEGV"
my database connections are good. it is running 3 minutes and after that my job is aboring with the above error.
can any one suggest me please. I am hoping its memory error, so I changed scrach desk path as well. but it won't work.
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Hi , looks like no issue in the code. here are the things
- I am running my jobs on grid environment.
- getting data from oracle database.
- lookup with db2 database based on the key.
- using transwarmenr loading data into oracle table.
This is the code.
if I run the job it is running 3 min. and aborting . Is there any issue with look up? but lookup throughing data. But from source I am getting 1 record.
- I am running my jobs on grid environment.
- getting data from oracle database.
- lookup with db2 database based on the key.
- using transwarmenr loading data into oracle table.
This is the code.
if I run the job it is running 3 min. and aborting . Is there any issue with look up? but lookup throughing data. But from source I am getting 1 record.
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
There's no magic answer. I would suggest that you search for SIGSEGV here and concentrate first on any that are marked Resolved, see if anything in them helps. Then go through the allegedly unresolved ones.
Then experiment. Does the grid node the job runs on matter? Does it work if you constrain it to one node? Can you 'work around' the issue by breaking the job up into two logical halves? Are you hash partitioning the data going into the Lookup based on the lookup keys to minimize the amount of data each node processes? Etc, etc, etc. Don't just sit around and wait for The Answer to fall from the sky.
Then experiment. Does the grid node the job runs on matter? Does it work if you constrain it to one node? Can you 'work around' the issue by breaking the job up into two logical halves? Are you hash partitioning the data going into the Lookup based on the lookup keys to minimize the amount of data each node processes? Etc, etc, etc. Don't just sit around and wait for The Answer to fall from the sky.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers