SIGSEGV error in a PX job that has been running normally
Posted: 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
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