Re: Configure Oracle IDBC to not wait for locks

Do you mean for update? I believe you put in the sql statement nowait update mytable set myfield=7 where ... nowait. I don't know where you set it up in ODBC.
But you say access which means read, and I have never seen readers get blocked in Oracle (SQL Server, DB2 sure). I would look at the ODBC api documentation 'cause I don't know.
Jim

"Mark E. Hansen" <meh_at_NOSPAMunify.com> wrote in message news:3A267074.42EB577E_at_NOSPAMunify.com...
>
>
> Barbara Kennedy wrote:
> >
> > I think you mean for update. Readers don't wait for writers in Oracle.
> > Jim
>
> So do you know how to configure the cursor so it won't block waiting
> for the lock conflict to subside?
>
>
> > "Mark E. Hansen" <meh_at_NOSPAMunify.com> wrote in message
> > news:3A2585C5.FE2E976_at_NOSPAMunify.com...
> > >
> > > I would like to configure my ODBC application to not block when
> > > attempting to access rows in the Oracle database that have conflicting
> > > locks.
> > >
> > > In an OCI application, I make a call to "oopt" to set two options on
> > > the cursor: ROW_RLBACK and DONOT_WAIT (these get or'ed together). This
> > > causes the operation to return immediately with an error if a lock
> > > conflict is encountered.
> > >
> > > However, I can't find any way to do this from my ODBC application.
> > > Can anyone tell me how to accomplish this?
> > >
> > > Regards,
Received on Fri Dec 01 2000 - 01:54:52 CET