My Oracle Support Banner

E1: DB: Index And SQL Packages Have Wrong Security On AS400 After Regenerating The Indexes For A Table Or When An Index Is Created For A Table (Doc ID 2358834.1)

Last updated on FEBRUARY 05, 2019

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.2 and later
IBM i on POWER Systems


With application release 9.2, P986117 has been introduced, because the *PUBLIC role has been revoked for accessing E1 tables, and libraries, for the new objects created within an E1 library.

Although the proper settings have been defined in P986117, as noted in the instructions provided in JD Edwards EnterpriseOne Tools Security Administration Guide, chapter 7 Managing Data Source Security.

If a user is generating, or, regenerating the indexes for a table (on the AS400), the logical file which contains the index data is not created with the proper authority.

The physical file has the correct authority as defined in P986117:

The newly created/regenerated indexes (as shown below), are not accessible for the E1 users mapped to a different system/proxy user.

This is impacting the SQL packages, also.

Physical File Authority for a newly generated table:


Logical File Authority for a newly generated index:


 The Enterprise Server has been recently installed.


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

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