Exalytics and OBIEE 11.1.1.9 - Unable to Schedule or Edit Agents After Upgrade from OBIEE 11.1.1.7.1 to 11.1.1.9.X
(Doc ID 2232086.1)
Last updated on JANUARY 26, 2023
Applies to:
Business Intelligence Server Enterprise Edition - Version 11.1.1.9.0 and laterOracle Virtual Directory - Version 11.1.1.9.0 and later
Oracle Exalytics Software - Version 1.0.0.5.0 and later
Information in this document applies to any platform.
This problem can occur on any OBIEE 11.1.1.9.X server (those installed on Exalytics and standalone OBIEE servers).
Symptoms
After migrating from OBIEE 11.1.1.7.1 to OBIEE 11.1.1.9.161018, 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:
[oracle.ods.virtualization.engine.backend.jndi.OVDAuthenticatorLDAP.BackendJND
.
I] [tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default
(self-tuning)'] [userId: ] [ecid:<ECID>] [APP: bisecurity#11.1.1]
[J2EE_APP.name: bisecurity_11.1.1] [J2EE_MODULE.name: bisecurity][WEBSERVICE.name: SecurityWebService]
[WEBSERVICE_PORT.name:SecurityWebServicePort] [SRC_CLASS:
oracle.ods.virtualization.engine.util.VDELogger] [SRC_METHOD: debug]
[#OVDAuthenticatorLDAP] JNDI Adapter Search using:[[
BindDN:
Base: ou=XXXX,o=enterprise
Scope: 2
Attributes: [uid, mail, sn, cn, description, orclguid, givenname,
objectclass, displayname, uid]
Filter:
(&(|(uid=<NAME>*)(displayname=<NAME>*))(objectclass=inetorgperson))
]]
[<TIMESTAMP>] [bi_server1] [TRACE] [LIBOVD-00026]
[oracle.ods.virtualization.engine.backend.jndi.OVDAuthenticatorLDAP.BackendJND
...
[<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]
[J2EE_APP.name: bisecurity_11.1.1] [J2EE_MODULE.name: bisecurity]
[WEBSERVICE.name: SecurityWebService] [WEBSERVICE_PORT.name:
SecurityWebServicePort] Remote Server
Failure:<HOSTANEM>:<PORT>.[[
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
'ou=XXXX,o=enterprise'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3140)
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 |
| Cause |
| Solution |
| References |