OBIEE 12c: When Editing Agent And Making LDAP User Search On Catalog Or Via Permsissions It Triggers A Full Wildcard LDAP Search
(Doc ID 2214844.1)
Last updated on JANUARY 30, 2020
Applies to:Business Intelligence Suite Enterprise Edition - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In OBIEE 12c, when trying to edit /create Agent, it is trying to fetch all the users from LDAP server and server is timing out.
When opening New agent page, Delivers starts a search on all users in the LDAP server.
In most cases that's not a problem. But if your LDAP has over 100,000 users, this search takes too much time and ends up timing out.
The same issue occurs when trying to search users in Catalog or VA permissions or any kind of user search.
Other symptoms may include the following scenario:
In the LDAP there are user accounts created that have the following format: xxx, xxxA and xxxD.
Agents are scheduled with the user ID xxx ( without A or D ). After a run or saving the agent, the Specified user of the agents changes to A or D account of that user (if A or D account exist for the user) automatically. Agent Specified User is changing to A or D account during run time
Since these accounts will not have the required access setup, reports/agents are not running properly and edit access is also impacted for the user.
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