This section describes configuration issues and their workarounds. It includes the following topics:
On the Microsoft Windows platform, the libovdconfig.bat
script does not work if the path to your Java installation in the -jreLoc
option includes a space character. For example, C:\Program Files\Java\jdk1.7.0_21
.
The workaround is to provide the path to your Java installation in DOS 8.3 format.
For example:
-jreloc C:\Progra~1\Java\jdk1.7.0_21
If a user name is present in more than one LDAP repository and the virtualize
property is set to use LibOVD, then the data in only one of those repositories is returned when you query that user name with the User and Role API.
JNDI Connections throw the javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms
exception.
This issue is found in domains configured to use an Oracle Identity Directory security store, or when using the User Role API or IGF/IDS against an LDAP identity store on any of the following JDK versions: Java SE 6u85, 7u72, or 8u20.
Workaround
Update the JDK to a version supported in this release. For certified JDK versions, see Oracle Fusion Middleware 12c Certifications at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
commonIdAttr
of Group to commonname
Post UpgradeWhen you upgrade IDS from an earlier release to 12.2.1.1.0, then you must update the group attribute commonIdAttr
to commonname
in the ids-config.xml file.
Consider the following example:
The location of ids-config.xml file is as follows:
DOMAIN_HOME/config/fmwconfig/ids-config.xml
Consider the following sample entry:
<Entity name="Group" type="group" idAttr="commonname" create="true" modify="true" delete="true" search="true" guidAttr="guid" mailAttr="mail" displaynameAttr="displayname" descriptionAttr="description" commonIdAttr="cn">
In the preceding sample entry, you must update the commonIdAttr
to commonname
instead of cn
.
Therefore, the correct entry should be as follows:
<Entity name="Group" type="group" idAttr="commonname" create="true" modify="true" delete="true" search="true" guidAttr="guid" mailAttr="mail" displaynameAttr="displayname" descriptionAttr="description" commonIdAttr="commonname">
The Transaction Per Second (TPS) has decreased and the Response Time has increased for a search/operation by 40% in 12.2.1.1 compared to 12.2.1 release for IDS/IGF.
If you are upgrading a domain that you created using the Oracle Restricted JRF template, you do not need to run the Upgrade Assistant because there are no database schemas in the domain. If you do run the Upgrade Assistant and select to upgrade the Restricted JRF domain, OPSS and IAU schema failure messages are displayed. Because the schema upgrade functionality is disabled for restricted JRF domains, you can ignore these messages.
The following sections describe issues with security WLST commands:
The following sections describe issues with the Oracle Fusion Middleware Audit Framework:
Although Access Manager appears as a component in Fusion Middleware Control, you cannot configure auditing for Access Manager using Fusion Middleware Control.
The standard audit reports packaged with Oracle Business Intelligence Publisher support a number of languages. Business Intelligence Publisher can start in different locales and, at start-up, you can specify the language of choice by setting the preferred locale in Preferences.
zh_CN (simplified chinese)
zh_TW (traditional chinese)
pt_BR (portuguese brazilian)
then the entire report including labels, headers, titles shows in English.
This issue will be fixed in a future release of Business Intelligence Publisher.
The standard audit reports packaged with Business Intelligence Publisher support a number of languages, but report titles and descriptions are displayed in English even when they have been translated.
This issue will be fixed in a future release of Business Intelligence Publisher.