This chapter describes the known issues and their workarounds.
Issue
JNDI Connections throw the javax.naming.NamingException: LDAP response read timed out , timed out : —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
For example:
-jreloc C:\Progra~1\Java\jdk1.8.0_21
Issue
Due to the limitation on the maximum column length of index in MS SQL Server, when using MS SQL Server as the OPSS security store, the OPSS policy artifact names and OPSS application policy stripe names cannot exceed 147 characters and 226 characters, respectively.
Workaround
Currently, there is no workaround for this issue.
Issue
In Oracle Edition-based redefinition (EBR) environment, after creating an edition, OPSS recommends that you explicitly grant the USE privilege on the edition to OPSS schemas and Audit schemas, rather than granting the USE privilege on the edition to PUBLIC. For information about EBR, see Using Edition-Based Redefinition in Oracle Database Development Guide.
Workaround
GRANT USE ON EDITION in the following manner.
GRANT USE ON EDITION edition_name TO OPSS_SCHEMA; GRANT USE ON EDITION edition_name TO IAU_SCHEMA; GRANT USE ON EDITION edition_name TO IAU_APPEND_SCHEMA; GRANT USE ON EDITION edition_name TO IAU_VIEWER_SCHEMA; """