Re: Pro*C From Windows

yitbsal_at_yahoo.com (Salaam Yitbarek) wrote

> The reason I wanted to move away from external procedures is that I
> have found them unstable, especially when dealing with file i/o. I do
> successfully use external procs in production, but they have been a
> headache to create. For example, just the other day, I was creating
> one to run call a shell script to run sqlloader, and it just wouldn't
> work. It returned the usual extproc error, and I traced the error to
> the call to sqlloader. The C code worked, but when called from a
> stored proc, it wouldn't.

Quite likely because the environments are different. Simply put. If calls FOO() works in C program ABC, then it will also work in Oracle external proc DEF.. if it fails, there must be external (no pun intended ;-) factors that are causing the failure.

Or to put it in another perspective - it is similar to writing an executable versus a shared object/DLL. The actual code runs in a different environment in a SO/DLL than an executable.

Does this make an executable stabler than a SO/DLL? Nope. Both are as robust as what *you* choose to make them. :-)

--
Billy