Re: unique violation on SELECT???

From: Sybrand Bakker <postbus_at_sybrandb.demon.nl>
Date: Fri, 12 Jan 2001 20:17:48 +0100
Message-ID: <93nm1o$atl0q$4@ID-62141.news.dfncis.de>

Yeah, but the error message is telling you the problem is in the remote database, as stated in the ORA-02063.
So apparently this is a DB2 problem.

Regards,

Sybrand Bakker, Oracle DBA

"Ed Stevens" <ed.stevens_at_home.com> wrote in message news:93na4c$hv1$1_at_nnrp1.deja.com...
> I found several occurances of the following in my <sid>alrt.log file:
>
> Errors in file e:\Oradmin\nmms\udump\ORA00476.TRC:
> ORA-00001: unique constraint (%s.%s) violated
> ORA-02063: preceding line from LN_DB2T
>
> When I checked the referenced trace file, the "Current SQL statement
> for this session:" was a SELECT. So how does a SELECT create a unique
> constraint violation? That should only occur on INSERT and UPDATE.
>
> FWIW, the SELECT statement was an inner join of 3 tables, and two of
> those tables were actually synonyms for a link which in turn pointed
> through the Oracle Transparent Gateway to a DB2-MVS database.
>
>
>
> --
> - Ed Stevens
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Fri Jan 12 2001 - 13:17:48 CST