Re: Sql with too many Gets

Couple of questions:

version?
execution plan?
size of table (blocks/rows)?
indexes available?
how many gets do you think is appropriate?

Peter

"danths" <d_sameer_at_yahoo.com> schreef in bericht news:78e940e1.0211041634.2d12c539_at_posting.google.com...
> "SQL with returning has too many gets"
>
> I have a sql statement which shows up as a statement with too many
> gets. This statement is executed multiple times thru out the day in an
> OLTP application. The table is pretty simple and so is the
> functionality. Is there any thing obviously wrong with this.
>
> UPDATE BUYER_REQUESTFOLLOWUP
> SET brf_statusid = 2,
> brf_guid = :b1
> WHERE brf_statusid = 1
> AND brf_lastupdtime < SYSDATE - 1
> AND ROWNUM = 1
> returning brf_apt_appointmentID, brf_statusid, brf_lastupdtime INTO
> :b0,:b1,:b2
> =====================================================
>
> SQL> desc buyer_requestfollowup
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> BRF_APT_APPOINTMENTID NOT NULL NUMBER(20)
> BRF_STATUSID NOT NULL NUMBER(2)
> BRF_Q1 VARCHAR2(1)
> BRF_Q2 VARCHAR2(1)
> BRF_Q3 VARCHAR2(1)
> BRF_QLIKE VARCHAR2(2000)
> BRF_QIMPROVE VARCHAR2(2000)
> BRF_PUBLIC CHAR(1)
> BRF_LASTUPDTIME DATE
> BRF_GUID NUMBER(38)
> =================================================================
Received on Tue Nov 05 2002 - 01:07:21 CST