SIGSEGV error in a PX job that has been running normally

nkumar_home · Post by **nkumar_home** » Tue Nov 02, 2004 11:56 am

The PX job reads from a partitioned Oracle table and then copies the data set using the copy stage after which there is a lookup stage followed by a aggregator stage and finally the oracle upsert stages.

The job has run fine until Oct 31st when it aborted with the " Operator terminated abnormally: received signal SIGSEGV" error. It had committed rows to the target table.

When it was restarted it ran fine. The volume was high because it was the end of the month but nothing that the job had not dealt with in the past.

Any ideas?

thanks

gh_amitava · Post by **gh_amitava** » Tue Nov 02, 2004 12:37 pm

Hi,

This is happening due to insufficient resource.

Regards
Amitava

Eric · Post by **Eric** » Thu Nov 04, 2004 11:35 am

Can you try running the job again with a Configuration.apt file with less nodes configured?

pravesh_kushwaha · Post by **pravesh_kushwaha** » Fri Nov 05, 2004 8:03 am

Hi,
This error is mainly due to unavailability of memory while the process is running. Depending on your system configuration you should use the config file. If you use default configuration file i.e. with one node your job might run.

Regards,
Pravesh