Re: Help insert with a select using a DB Link - ORA-03106: fatal two-task communication protocol error

Well, excuse me, Mr. Smarty (aka Sybrand). I don't suppose you care to look in the Oracle doc set, where they tell you that it was designed for non-Oracle databases. Or do you just pull all your info out of your feeble brain?

I wonder, after reading a lot of your posts, if anyone at your office ever comes to you for help. If your attitude at the office is anything like it is in this NG, you must be the lonliest DBA on the planet.

Chill out Sybrand. Go outside, take a deep breath. Then come back inside and answer people's questions without all the sarcasm. OK.

Have a nice life!
Roger Crowley - DBA - LearningFramework

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:8n8ijuo0oshf2m00r82qeei01cilguni12_at_4ax.com...
> On Fri, 19 Jul 2002 23:44:06 GMT, Enkidu Utnapishtim
> <utnapishtim43NOSPAM_at_hotmail.com> wrote:
>
> >they suggested we replace the "INSERT ... SELECT FROM remote(s)" with a
> >"COPY FROM remote ... SELECT ... FROM remote(s)" statement (don't recall
> >the exact syntax). We didn't think it would help (after all, the goal in
> >life for the COPY command is to copy stuff from a non-Oracle database).
> >But there must be something in the COPY command that doesn't stumble
> >over requests like the INSERT statement does.
>
>
> COPY is a SQL*PLUS statement, it is NOT a SQL statement.
> Hence the syntax can be found in the sql*plus reference manual.
> Your assertion about the goal of the COPY command being designed to
> transfer data from non-Oracle databases is nonsense.
>
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Sat Jul 20 2002 - 10:30:19 CDT