Hi
i am calling store proc from oracle db using stored procedure stage
can anyone tell whats the meaning of below error?
Stored_Procedure_0,0: Operator terminated abnormally: received signal SIGSEGV
Thanks in adv
unexpected fatal while calling Store proc
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
-
- Participant
- Posts: 104
- Joined: Sat Dec 24, 2005 1:26 am
- Location: Bengaluru
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
When no of connection to database from Datastage server increases the job gets aborted due to this fatal error.Please check whether you are able to connect database from datastage.
This happens due to connection problem.
It happened with me when DB2 tables ere used in lookup .
Please check the connection.
Thanks
Shaonli
This happens due to connection problem.
It happened with me when DB2 tables ere used in lookup .
Please check the connection.
Thanks
Shaonli
When no of connection to database from Datastage server increases the job gets aborted due to this fatal error.Please check whether you are able to connect database from datastage.
This happens due to connection problem.
It happened with me when DB2 tables ere used in lookup .
Please check the connection.
Thanks
Shaonli
This happens due to connection problem.
It happened with me when DB2 tables ere used in lookup .
Please check the connection.
Thanks
Shaonli
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Somewhere - maybe in DataStage, maybe in the database server, maybe in the middleware - a segmentation violation has occurred. There are many possible causes; a search of DSXchange will help you to find the more common ones.
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.