My Oracle Support Banner

Exalytics and OBIEE - Unable to Schedule or Edit Agents After Upgrade from OBIEE to (Doc ID 2232086.1)

Last updated on JANUARY 26, 2023

Applies to:

Business Intelligence Server Enterprise Edition - Version and later
Oracle Virtual Directory - Version and later
Oracle Exalytics Software - Version and later
Information in this document applies to any platform.
This problem can occur on any OBIEE server (those installed on Exalytics and standalone OBIEE servers).


After migrating from OBIEE to OBIEE, all users are unable to Schedule or Edit agents in OBIEE. Users are able to successfully login to OBIEE and can create and access dashboards and reports, but cannot edit or schedule any Agents.
Steps that lead to this issue are:

a. Open/create new dashboard or report in OBIEE.
b. Save report.
c. Then edit the report and go to Schedule.
d. When opening the Scheduling options, the Agent Editor opens, and the property tabs display, (i.e. General, Schedule, Content, Recipients, etc.) but none of the options are visible.
Where the properties would normally be displayed, it just shows a blue background.

This problem happens on both existing agents and when scheduling a new agent. There is no visible error in the web browser or user interface, but after enabling security logging, LIBOVD errors are seen in the biserver logs:

[<TIMESTAMP>] [bi_server1] [TRACE] [LIBOVD-00023]
I] [tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: ] [ecid:<ECID>] [APP: bisecurity#11.1.1]
[ bisecurity_11.1.1] [ bisecurity][ SecurityWebService]
oracle.ods.virtualization.engine.util.VDELogger] [SRC_METHOD: debug]
[#OVDAuthenticatorLDAP] JNDI Adapter Search using:[[
Base: ou=XXXX,o=enterprise
Scope: 2
Attributes: [uid, mail, sn, cn, description, orclguid, givenname,
objectclass, displayname, uid]
[<TIMESTAMP>] [bi_server1] [TRACE] [LIBOVD-00026]
[<TIMESTAMP>] [bi_server1] [WARNING] [LIBOVD-40066]
[oracle.ods.virtualization.engine.backend.jndi.OVDAuthenticatorLDAP] [tid:
[ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: ] [ecid:
<ECID>] [APP: bisecurity#11.1.1]
[ bisecurity_11.1.1] [ bisecurity]
[ SecurityWebService] [
SecurityWebServicePort] Remote Server
javax.naming.OperationNotSupportedException: [LDAP: error code 53 - LDAP
Error 53 : [LDAP: error code 53 - Function Not Implemented, search filter
attribute displayname is not indexed/cataloged]]; remaining name
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(



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.