Skip to main content

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ].

Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.)

NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems.

For me I needed to add a launch listener on my LOV and clear the cache of my vo.

LOV
<af:inputListOfValues id="NameId"
  popupTitle="#{bindings.Name.hints.label}"
  value="#{bindings.RolName1.inputValue}"
  label="#{bindings.RolName1.hints.label}"
  model="#{bindings.RolName1.listOfValuesModel}"
  required="#{bindings.RolName1.hints.mandatory}"
  columns="#{bindings.RolName1.hints.displayWidth}"
  shortDesc="#{bindings.RolName1.hints.tooltip}"
  launchPopupListener="#{backingBeanScope.backingBean.launchPopup}">

CODE

public void launchLOVPopup(LaunchPopupEvent launchPopupEvent){
clearVOCache("YourAMDataControl", "ViewNameVO");
}

public void clearVOCache(String amName, String voName){
ApplicationModule appModule = getApplicationModule(amName);
ViewObject vo = appModule.findViewObject(voName);
vo.clearCache();
}

Comments

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...

Util code

public static MethodExpression getMethodExpression( String expr, Class returnType, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); ExpressionFactory elFactory = fc.getApplication().getExpressionFactory(); return elFactory.createMethodExpression( elctx, expr, returnType, argTypes); } public static javax.faces.el.MethodBinding getMethodBinding( String expr, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); return fc.getApplication().createMethodBinding(expr, argTypes); } SetPropertyListener listener = new SetPropertyListener( ActionEvent.class.getName()); listener.setFrom(link.getRoute()); listener.setValueExpression("to", JSFUtils.getValueExpression("#{pageFlowScope.route}", String.class)); action.addActionListener(listener); AdfFacesContext.getCurrentInstance().getPageFlowScope() .put("route", lin...

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]