Performance Update to RSWWERRE

[Quenzer, Kenneth D]

I think that note 168045 is for versions 4.5 and 4.6.  The Select statement
was changed in the 4.5 and 4.6 versions of RSWWERRE and SAP added a "hint"
for Oracle to force it to use index C.  I don't think that this hint is
needed in the 4.0b version of RSWWERRE.
 
Kenny Quenzer
 
-----Original Message-----
From: Klemba, Michal [mailto:MKlemba at era.pl]
Sent: Wednesday, June 27, 2001 10:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Performance Update to RSWWERRE
 
Have you implemented a note 168045 as well? It says something about your
problem.
 
Michel Klemba
-----Original Message-----
From: Schroeter, Brad [mailto:BSchroeter at ti.com]
Sent: 27 czerwca 2001 17:14
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Performance Update to RSWWERRE
I am in the process of implementing note 136887 (Performance RSWWERRE with
Cost Based Optimizer).  We're on 4.0B and Oracle 8.0.4.3 (we're supposed to
be upgrading to 8.1.7 in August/September).  In the note it says "that you
must possibly update the database statistics so that your index works
correctly (see note 72873)".  I've talked to our Basis folks and they don't
currently do any reorgs on our system due to the size (we're the smaller of
two systems within our company and we normally run without any problems) but
that may change in the future.
After implementing the note I ran a test of RSWWERRE with the SQL trace
turned on.  I can see that instead of using index SWWWIHEAD~C (which it's
supposed to use), it's doing a full table scan.  It's happening on "SELECT *
FROM SWWWIHEAD INTO TABLE WI_ERRORS WHERE WI_TYPE EQ WI_BATCH AND WI_STAT EQ
WI_STATUS_STARTED" (wi_batch = 'B' and wi_status_started = 'STARTED').  Does
anyone have an idea why the index would not be used?
 
Thanks,
Brad
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20010627/9b7185a6/attachment.htm