Stored_Procedure_0,0: Operator terminated abnormally: receiv

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
jimgowtham
Participant
Posts: 34
Joined: Thu Feb 16, 2006 8:34 am
Location: mumbai

Stored_Procedure_0,0: Operator terminated abnormally: receiv

Post by jimgowtham »

Hi,

I have used Stored Procedure stage in parallel jobs to run the stored procedure "PR_PROCEDURE_LOG".

Procedure name : PR_PROCEDURE_LOG
==================================

CREATE OR REPLACE PROCEDURE GPM_STG_ETL.pr_procedure_log(p_procedure_name IN VARCHAR2,
p_action_type IN VARCHAR2,
p_error IN VARCHAR2,
p_user IN VARCHAR2) AS
BEGIN

INSERT INTO MD_STG_PROCEDURE_LOG
(PROCEDURE_NAME, ACTION_TIME, ACTION_TYPE, ERROR, UPDATE_BY)
VALUES
(UPPER(p_procedure_name),
SYSTIMESTAMP,
p_action_type,
p_error,
p_user);
COMMIT;
END pr_procedure_log;
/



My DS_JOB director log :
========================

Stored_Procedure_0,0: Info: Stored_Procedure_0: BEGIN PR_PROCEDURE_LOG(); END;
Stored_Procedure_0,0: Operator terminated abnormally: received signal SIGBUS
main_program: Step execution finished with status = FAILED.


I have used search option in DSXchange and found solution as

"APT_DISABLE_COMBINATION =true"

Even after using this "APT_DISABLE_COMBINATION", job is aborted with fatal error as..

Stored_Procedure_0,0: Operator terminated abnormally: received signal SIGBUS


Thanks & Regards,
JIM
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Verify that you provided four argument values of appropriate data type to the stored procedure via the Stored Procedure stage.

Does the Stored Procedure stage expect a return value?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

modify your procedure to return a success/failure flag.
handle the exception in case the insert fail, return a failed flag.
jimgowtham
Participant
Posts: 34
Joined: Thu Feb 16, 2006 8:34 am
Location: mumbai

Post by jimgowtham »

I tried using four parameters in SP stage...

P_PROCEDURE_NAME VARCHAR2(200);
P_ACTION_TYPE VARCHAR2(200);
P_ERROR VARCHAR2(200);
P_USER VARCHAR2(200);

After the changes, now I am getting the fatal error like...

Stored_Procedure_0,0: Operator terminated abnormally: received signal SIGSEGV
main_program: Step execution finished with status = FAILED

This SP is running successfully in TOAD, However it is not not running through SP stage in Datastage.


Regards,
JIM
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

post the modified procedure?
what does the procedure returns??
have you handled the exceptions??
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

One simple 'solution' would be to use an Oracle stage for this, insert it directly. Why futz with a stored procedure just to insert a single record to a table? :?

If it is meant to be reusable across jobs, put it in a Shared Container.
-craig

"You can never have too many knives" -- Logan Nine Fingers
jimgowtham
Participant
Posts: 34
Joined: Thu Feb 16, 2006 8:34 am
Location: mumbai

Post by jimgowtham »

Thank you Very Much... :lol:
Post Reply