Running Stored Procedure in Oracle Enterprise Stage
Moderators: chulett, rschirm, roy
Running Stored Procedure in Oracle Enterprise Stage
I am trying to convert a server job to a parrallel job and in the server job in oracle oci stage one stored procedure is triggered before the sql query.Similar option is not present in Oracle Enterprise Stage.
If someone has any information on how to do this in parrallel job then please reply.
If someone has any information on how to do this in parrallel job then please reply.
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
I have tried executing the command 'call schemaname.procedurename();' in Open command option. It is not exceuting the procedure and not giving any error message also. Is there any other way to call the procedure in this option.DSguru2B wrote:Open command is equivalent to 'Before Sql' in Server and Close command is equivalent to 'After Sql'. ...
Suman
I have tried with exec without the semicolon. Still the procedure is not getting executed.We are using datstage version 7.5.2.DSguru2B wrote:Try it with exec schemaname.procedurename(). Also try without the trailing semicolon. We had different results on different versions in the recent past. ...
Suman
I did a quick search and you were using the correct syntax. Forget the exec and lets put call back. So now your OPEN statement should be
call schemaname.storedprocedurename(). Try getting rid of the trailing semicolon. If that doesnt work get your dba involved, ask him to monitor if the stored procedure really did or did not get fired. Maybe it did but something happened to it half way.
call schemaname.storedprocedurename(). Try getting rid of the trailing semicolon. If that doesnt work get your dba involved, ask him to monitor if the stored procedure really did or did not get fired. Maybe it did but something happened to it half way.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Finally the procedure is working with the syatax 'call schemaname.storedprocedurename()' without semicolon. The problem was there was no commit in the procedure. Thanks to all of you for your valuable suggestion and Happy New Year to all.DSguru2B wrote:I did a quick search and you were using the correct syntax. Forget the exec and lets put call back. So now your OPEN statement should be
call schemaname.storedprocedurename(). Try getting rid of the trailing semicolon. If that doesnt work get your dba involved, ask him to monitor if the stored procedure really did or did not get fired. Maybe it did but something happened to it half way.
Suman