DSXchange

Hi Guys,

We are facing a problem in production environment. The job is having only one stage. The stage is a stored procedure which calls the stored procedure.
The job was running fine all these days. Suddenly it is giving this error

"Operator terminated abnormally: received signal SIGSEGV"

Could anybody help me out with this?
i tried to reset the job and ran it and i am getting the same error.even after compilation am getting the same errro.

its very urgent as it is a production environment?

Thanks for ur help in advance.
mac

Is there any CLOB. BLOB or BFILE datatype?

No there is no such datatype.

Try force compling the job.

If that does not work then I would start looking at the connection which is made to the database server to execute the stored proc.

The info provided here is too limited to point to a better resolution.

I go this error once when i tried loading the data to a column which was not big enough to handle the incoming size, may you can get some idea with this.

samunik,,

Compiling is taking place fine.. then why we need to do force compiling?
and wat more information do u need to solve this issue??Please inform me..i ll post them..
wat are the connections do we need to check?? cud you please explain more..


nagaraj,,

This job was running fine all these days.. if the data type of the input is large as ur saying then it wud have created a problem way back... anywy i ll check into it..

thanks for ur reply guys.. hope to solve this issue with ur help sooner

point taken ray.. sorry guys this is the first time i am using any forum..
I will see to it in the future..

IF U HAVE A 'DRS' STAGE IN A JOB,AND IF THERE IS A LOT OF LINKS CONNECTED TO THE 'DRS' THEN SPLIT LINKS INTO 2 DRS STAGES AND RUN THE JOB. GOOD LUCK

Was the Procedure or tables it referes/writes to are modified recently?

Its the segmentation error. Procedure may not have write access to some of the tables or table size is full or database file size is not defined as incremental or may be it tries to write in non-nullable column. (I am assuming Oracle Procedure)

Please check if any of these is causing the problem.

I wonder whether it's still very urgent three months on?