My Oracle Support Banner

E1: DB: Optimizer Strategy, Index Seek VS Table Scan (Doc ID 2540887.1)

Last updated on FEBRUARY 06, 2020

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

 When running a Report, multiple database connections are opened, however the first DB connection is still locking F0911.

This occurs when there is a small number of records in F0911, or no index to be used. The problem occurs when table scan seeking is being utilized.

Currently, there is a workaround to supply a number of dummy records in the F0911, which causes a different algorithm to be used when accessing the table. This currently forces use of an index seek algorithm.

The usage of a custom index has also prevented this, however the database administrator should be consulted before adding indexes.

for SQL Server: CREATE NONCLUSTERED INDEX   SNC_CUSTOM_F0911_PERFORMANCE_01   ON      CPDTA.F0911 (GLICU, GLICUT, GLPOST, GLCO);

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.