Etatrans Log Error Message - InclusionSubordinate 'eTRole' read failed: DB Read failed: No such object
search cancel

Etatrans Log Error Message - InclusionSubordinate 'eTRole' read failed: DB Read failed: No such object

book

Article ID: 245881

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

When IDM is restarted or some admin adds/removes a Provisioning Role from a user, the provisioning log keeps generating several errors like the one below:

20220702:102201:TID=7c4b70:Search    :E882:----:F: FAILURE: External Search (eTSubordinateClass=eTRole)

20220702:102201:TID=7c4b70:Search    :E882:----:F:     rc:  0x0020 (No such object)

20220702:102201:TID=7c4b70:Search    :E882:----:F:     msg: :ETA_E_0019<RXX>, InclusionSubordinate 'eTRole' read failed: DB Read fai

20220702:102201:TID=7c4b70:Search    :E882:----:F:+led: No such object (ldaps://ca-prov-srv:20391)

Environment

All Identity Manager

Cause

There is a search made under the eTSuperiorClass=eTRole,eTInclusionContainerName=Inclusions,eTNamespaceName=CommonObjects,dc=im,dc=etadb branch in the Provisioning Repository to look for nested provisioning role links but the sub-container won't exist right away and will get created the first time such a container is needed to store a nested provisioning role.

Resolution

This is a benign error and can be ignored. But if you wanted to trigger the creation of the container to avoid these error then you could just log into the Provisioning Manager and or IM User Console and modify an existing Provisioning in order to set another Provisioning Role as a Included Role or Including Role that would trigger the creation of the container. You could then undo the modification you performed and that would leave the below container in the system and avoid the error:

eTSubordinateClass=eTRole,eTSuperiorClass=eTRole,eTInclusionContainerName=Inclusions,eTNamespaceName=CommonObjects,dc=im,dc=etadb