Re: Using EXTPROC to then make a system call to EXP hangs the EXP

I would not say I know all about Oracle, quite the opposite. Anyone who says they do is fooling themselves.

You are entirely correct, and I can understand your point totally, but I have an old system I need to fix. I can only reiterate our standing.

    Oracle replication was a fine solution, but required constant connectivity between all nodes - this is not so for our infrastructure. We had connection to the LAN 25% of the time, at 9600 bps on a good day. We found Oracle replication falling behind most of the time.

    Our customer *mandated* we use email to deliver a replication solution.     We have been asked to port an old system, where our original solution was a stop gap - we no longer use extproc in our new systems.

Our 'solution' worked on NT4, and added a single extra connection. It now doesn't work on Win 2000.

Unless there is any further useful info on this thread, I now consider this closed, and will pursue it via alternative routes.

Thanks to all who contributed.

Steve

>
> Apparently you think you know everything better. Dismissing
> replication as useless inevitably results in 'solutions' like you
> have implemented.
> The external procedure facility was designed to call dll's. It was not
> designed to call Oracle utilities through the system command. You get
> 2 connections , you get 2 times all resources, etc etc.
> To imagine this 'solution' is more 'viable' than using replication is
> utterly ridiculous. You are using a sledgehammer to kill a mouse and
> you know it.
>
>
> --
> Sybrand Bakker, Senior Oracle DBA
Received on Mon Jan 05 2004 - 04:49:46 CST