OUD12c - OUDSM GUI Error - "An unresolvable error has occured." and / or Extended Schema Becomes BASE64 Encoded After Restart
(Doc ID 2539007.1)
Last updated on JANUARY 30, 2023
Applies to:
Oracle Unified Directory - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, Configuration
After the schema was extended it was noted that the OUDSM GUI throws the following error message:
An unresolvable error has occured. Please contact your administrator for more information.
From the AdminServer-diagnostic.log:
[2018-09-26T18:52:57.511+02:00] [AdminServer] [WARNING] [] [oracle.adfinternal.view.faces.context.RichExceptionHandler] [tid: [TID].ExecuteThread: '<TID#>' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: <ECID>] [APP: oudsm] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: <DSID>] ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase INVOKE_APPLICATION 5[[javax.el.ELException: java.lang.NullPointerException
at com.sun.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:187)
at com.sun.el.parser.AstValue.invoke(AstValue.java:289)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:304)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodExpression(UIXComponentBase.java:2032)
at com.sun.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:187)
at com.sun.el.parser.AstValue.invoke(AstValue.java:289)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:304)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodExpression(UIXComponentBase.java:2032)
The issue can be reproduced at will with the following steps:
1. Extend the schema
2. Create / add new user which utilizes new schema
3. Try to view new user in OUDSM
4. OUDSM goes blank, eventually comes back with error
5. NPE error is observed in adminserver-diagnostic log coinciding with the issue in OUDSM
2. Create / add new user which utilizes new schema
3. Try to view new user in OUDSM
4. OUDSM goes blank, eventually comes back with error
5. NPE error is observed in adminserver-diagnostic log coinciding with the issue in OUDSM
Due to this issue, users cannot utilize OUDSM for user management if the user contains extended schema. It was also noticed that the schema file when viewed, contained base64 encoding for the schema attribute, ie;
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1501 NAME ( 'CustomApplicationName' ) DESC 'Az elsõdleges alkalmazás megnevezése' SINGLE-VALUE )
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1502 NAME ( 'CustomRoleType' ) DESC 'Bekapcsolható vagy nem bekapcsolható a szerepkör' SINGLE-VALUE )
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1503 NAME ( 'CustomIsBaseRole' ) DESC 'Alapértelmezett szerepkör-e az alkalmazás esetén' SINGLE-VALUE )
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1505 NAME ( 'CustomPrereq' ) DESC 'A szerepkör elõfeltétele' )
objectClasses: ( 1.3.6.1.4.1.26027.1.2.1501 NAME ( 'CustomDBRole' ) DESC 'Sémabõvítés a db role csoportokhoz' SUP top AUXILIARY MAY ( CustomApplicationName $ CustomRoleType $ CustomIsBaseRole $ CustomPrereq ) )
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1502 NAME ( 'CustomRoleType' ) DESC 'Bekapcsolható vagy nem bekapcsolható a szerepkör' SINGLE-VALUE )
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1503 NAME ( 'CustomIsBaseRole' ) DESC 'Alapértelmezett szerepkör-e az alkalmazás esetén' SINGLE-VALUE )
attributeTypes: ( 1.3.6.1.4.1.26027.1.1.1505 NAME ( 'CustomPrereq' ) DESC 'A szerepkör elõfeltétele' )
objectClasses: ( 1.3.6.1.4.1.26027.1.2.1501 NAME ( 'CustomDBRole' ) DESC 'Sémabõvítés a db role csoportokhoz' SUP top AUXILIARY MAY ( CustomApplicationName $ CustomRoleType $ CustomIsBaseRole $ CustomPrereq ) )
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |