OVD 11g ODSM Client View Shows No Entries For One Database Adapter's Table, Log: Operations Error / Adapter Browser Shows: No information currently available, Log: ORA-00903: invalid table name (Doc ID 1369715.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Virtual Directory - Version 11.1.1.2.0 and later
Information in this document applies to any platform.

Symptoms

Oracle Virtual Directory (OVD) 11g, i.e., 11.1.1.3.

All other functionality is working, including other OVD Database (DB) Adapters against this one same backend Oracle Database.


However, for one single table only, the Database Adapter returns no entries in the Oracle Directory Services Manager (ODSM) > Data Browser > Data Tree > Client View.

The wls_ods1_diagnostic.log shows the following error for the above Client View attempt:

...<snip>...

[2011-10-19T16:19:13.279-04:00] [wls_ods1] [NOTIFICATION] [] [oracle.ldap.odsm.model.ovd.browser.APLdapTreeNode] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0007HQSlpCiFKAWFLz3V8A0000de0002Qp,0:1] [APP: odsm#11.1.1.2.0] [dcid: cc9a9dc0fb6e6c36:7e143a1a:13317817918:-8000-0000000000002a73] [URI: /odsm/faces/odsm.jspx] doCommand[[
java.lang.Exception: LDAPException: other (1) Operations Error
LDAPException: Server Message: Operations Error

at oracle.ldap.odsm.model.ovd.browser.APLdapTreeNode.retriveChildren(APLdapTreeNode.java:1447)
at oracle.ldap.odsm.model.ovd.browser.APLdapTreeNode.getProp(APLdapTreeNode.java:607)
at oracle.ldap.odsm.model.ovd.browser.APLdapTreeNode.refresh(APLdapTreeNode.java:1568)
at oracle.ldap.odsm.model.ovd.browser.APLdapTreeNode.doCommand(APLdapTreeNode.java:1496)
at oracle.ldap.admin.common.CommandProp.run(CommandProp.java:486)
at oracle.ldap.admin.common.CommandProp.getProp(CommandProp.java:403)
at oracle.ldap.odsm.ui.common.Action.doAction(Action.java:277)
at sun.reflect.GeneratedMethodAccessor646.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1259)

...<etc, etc>...




If instead going to ODSM > Data Browser tab > Data Tree > Adapter Browser and expanding the same table, on the right the Table Details tab shows columns but no data under it, just the following message:

No information currently available


The wls_ods1_diagnostic.log then shows the following error for the above Adapter Browser attempt:

...<snip>....

[2011-10-20T09:49:30.304-04:00] [wls_ods1] [NOTIFICATION] [] [oracle.ldap.odsm.model.ovd.browser.APDbTable] [tid: [ACTIVE].ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0007IL8lIACFKAWFLz3V8A0000de0003Ds,0:1] [APP: odsm#11.1.1.2.0] [dcid: cc9a9dc0fb6e6c36:7e143a1a:13317817918:-8000-00000000000038a1] [URI: /odsm/faces/odsm.jspx] getTableRows[[
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name

faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:<hostname>

java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name

at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1358)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:375)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:321)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:173)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)

...<etc, etc>....

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms