Page 1 of 1

i am getting this fatal error

Posted: Thu Oct 26, 2006 12:41 pm
by bollinenik
Hi,
I am getting below fatal error any body has idea help me
"APT_CombinedOperatorController,0: Operator terminated abnormally: received signal SIGSEGV [processmgr/rtpexecutil.C:161]"

My design is i am reading data from Oracle and loading into SAP by using of SAP-BAPI pack in data stage.Pls help me

Posted: Thu Oct 26, 2006 12:55 pm
by samsuf2002
this is because u r accessing memory which is not owned by the process, add an environment variable

add APT_DISABLE_COMBINATION AND set it as true and try.

Posted: Thu Oct 26, 2006 1:34 pm
by ray.wurlod
The message suggests that your process has used up all its allocated memory and is trying to access some more. This might be at a micro level (for example trying to load 14 characters into a Char(10) column) or at a much larger, whole-of-process, level. Without monitoring it's really difficult to tell.

Investigate the reporting environment variables. You can have the player processes document their process IDs and memory consumption. This ought to be the starting point of your detective work.

Posted: Thu Oct 26, 2006 1:35 pm
by meena
Hi Koti,
SIGSEGV is "segmentation violation", where an attempt is made to access a memory address not owned by the process.You need to add an environment variable as suggested by Sam.

Posted: Fri Oct 27, 2006 11:26 am
by splayer
Can any of you tell me how you know that SIGSERV is "segmentation violation" of a memory access error? Is this documented anywhere other than this forum?

Posted: Fri Oct 27, 2006 1:07 pm
by samsuf2002
it should be in the Datastage online document if not then go for google

Posted: Fri Oct 27, 2006 1:37 pm
by ray.wurlod
It's one of the basic UNIX signals. Try man signal or man -k SIGSEGV command to learn more.

Posted: Fri Oct 27, 2006 1:50 pm
by phanee_k
Hi ,

This could have caused because of the DataStage monitor process.
We used to face the same issue. Once the APT_MONITOR_SIZE variable is set to some value , we did not face this error again.
Please set the APT_MONITOR_SIZE to some value ( in our case we set to 10000) to overcome this issue.

Thanks,
Phani