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
i am getting this fatal error
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 111
- Joined: Thu Jun 01, 2006 5:12 am
- Location: Detroit
i am getting this fatal error
kOTI,
1586-738-7785
1586-738-7785
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 397
- Joined: Wed Apr 12, 2006 2:28 pm
- Location: Tennesse
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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
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