Page 1 of 1
unexpected fatal while calling Store proc
Posted: Wed Jun 25, 2008 8:35 pm
by getsatish_gk
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
Posted: Wed Jun 25, 2008 9:04 pm
by keshav0307
there must be some other error, message, warnings
give more detail information
Posted: Wed Jun 25, 2008 9:25 pm
by getsatish_gk
This is only fatal error
Posted: Wed Jun 25, 2008 10:34 pm
by keshav0307
Operator terminated abnormally: received signal SIGSEGV
is not the actual error/cause.
you should provide more information .
like your job design,
what is there in two lines before and after this error message
Posted: Thu Jun 26, 2008 12:48 am
by 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
Posted: Thu Jun 26, 2008 12:50 am
by 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
Posted: Thu Jun 26, 2008 1:07 am
by ray.wurlod
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.