Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Pipelined table and Ref Cursor

Re: Pipelined table and Ref Cursor

From: Harry Ramp <harry.ramp_at_hotmail.co.uk>
Date: 24 Apr 2006 01:00:48 -0700
Message-ID: <1145865648.008972.240860@v46g2000cwv.googlegroups.com>


All,

Our vendor has suggested a fix that seems to work so far and is listed in Oracle's knowledge base. The gist of it is ...

ODP.Net by default sets the OCI parameters OCI_ATTR_EXTERNAL_NAME and OCI_ATTR_INTERNAL_NAME to be used if the application enlists in distributed transactions coordinated by Microsoft Transaction Server(COM+ enterprise services). Direct path insert (with +append hint) can not be used in distributed transactions. Are distributed transactions used through COM+ enterprise services? If not, the internal and external names can be disabled by setting the enlist=false connection string option.
Setting enlist=false on the connect string will get rid of this problem.

Thanks to everyone for their help.

Harry. Received on Mon Apr 24 2006 - 03:00:48 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US