Infinite Recursion

We have a PL/SQL web application that runs under Oracle.

We have created an Oracle Job that runs through the PL/SQL code and comes to a call to an external procedure... to where it crashes. Manually, this external procedure executes fine. However, this process needs to be ran in the job but it isn't linking the call to the external C procedure.

Does anyone know if Oracle has problems with running External Procedures from jobs?

__________________
http://jasonpowers.net

"There are a thousand hacking at the branches of evil to one who is striking at the root."

Mjordan2nd

I don't really know oracle, so I doubt I could be of much help. I did find this link, though: http://www.hk8.org/old_web/oracle/prog2/ch21_01.htm

Perhaps it will help

__________________
"Every gun that is made, every warship launched, every rocket signifies, in the final sense, a theft from those who hunger and are not fed, from those who are cold and are not clothed. The world in arms is not spending money alone. It is spending the sweat of its laborers, the genius of its scientists, the hopes of its children." - Dwight D. Eisenhower

Infinite Recursion

Thanks for the link Mjordan2nd...
Unfortunatley, I didn't find any information regarding running external procedures within oracle jobs. However, I did find that I could piggy-back the C debugger (gdb) to the external procedure and follow it through the process. Perhaps this will assist in discovering why the job is failing and on which part of the algorithm.

__________________
http://jasonpowers.net

"There are a thousand hacking at the branches of evil to one who is striking at the root."

big_k105

i know a guy that is knows some oracle i will pm him on another forum and ask him to come over and help out. he is a member here but doesnt get much time here cause he runs linuxforums.org and what not

__________________
BIG K aka Kyle
Programming Forums
Kyle K Online

Please do not PM or email me programming questions. Post them in the forums instead.

kurifu

The only thing I could think of is to make sure that you are actually exporting the function properly (C style, __cdecl calling type), and make sure that you are actually calling the function with that style.

It is possible that data going onto and comming off the stack is not happening properly due to incompatible calling conventions, this seems to be what causes crashes most time I have had problems calling external modules functions... bearing in mind of ourse I have never actually done it from PL/SQL.

Hope this helps.

__________________
Clifford Matthew Roche <geek@cliffordroche.com>
Web Hosting: http://www.crd-hosting.com
Consulting: http://www.crdev-consulting.com