Page 1 of 1
title element not found - application validation problem
Posted: Thu Feb 14, 2013 8:48 pm
by kastellu
Did anyone get this kind of error. It happend on all applications ,... all the dimensions and subsets have visible elements. I think it happend after links in dimension hierarchy were broken, dimension was updated once again, but we didn't do delete all elements.
Thanks!
Re: title element not found - application validation problem
Posted: Thu Feb 14, 2013 10:30 pm
by kastellu
I figured out that when creating a dimension in TM1 modeler i get the same error with some additional informations
com.cognos.pmta.api.exceptions.PMTAException.mapException(PMTAException.java:128)
com.cognos.pmta.api.modelmanagement.query.execution.SubsetCache.readAxes(SubsetCache.java:62)
com.cognos.pmta.api.modelmanagement.query.execution.SubsetCache.get(SubsetCache.java:49)
com.cognos.pmta.api.modelmanagement.query.ViewPageReader.getPageSelections(ViewPageReader.java:92)
com.cognos.pmta.api.modelmanagement.query.execution.ViewReader$CubeViewReader.getPageSelectionsImpl(ViewReader.java:342)
com.cognos.pmta.api.modelmanagement.query.execution.ViewReader.getPageSelections(ViewReader.java:123)
com.cognos.pmta.api.modelmanagement.query.TM1OperationExecutor.readFromModel(TM1OperationExecutor.java:280)
com.cognos.pmta.api.modelmanagement.query.TM1OperationExecutor.getOriginalQuery(TM1OperationExecutor.java:354)
com.cognos.planning.common.query.OperationExecutor.initialize(OperationExecutor.java:363)
com.cognos.planning.common.query.OperationExecutor.getQueryState(OperationExecutor.java:350)
com.cognos.planning.common.query.OperationExecutor.getOrientation(OperationExecutor.java:400)
com.cognos.planning.common.query.AbstractQuery.getOrientation(AbstractQuery.java:259)
com.cognos.pmta.api.modelmanagement.model.cube.TM1Cube.getDefaultDimensionOrientation(TM1Cube.java:1050)
com.ibm.cdf.pmmodel.state.FacetChangeBridge.updateDefaultFacetModels(FacetChangeBridge.java:2266)
com.ibm.cdf.pmmodel.state.FacetChangeBridge.access$9(FacetChangeBridge.java:2258)
com.ibm.cdf.pmmodel.state.FacetChangeBridge$BridgeDimensionStateChangeListener.afterOperation(FacetChangeBridge.java:875)
sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
com.cognos.utils.events.EventSupport$MulticastHandler.invoke(EventSupport.java:274)
$Proxy3.afterOperation(Unknown Source)
com.ibm.cdf.pmmodel.state.StateChangeNotifier.fireAfterDimensionOperation(StateChangeNotifier.java:262)
com.ibm.cdf.pmmodel.state.DimensionState.modify(DimensionState.java:245)
com.ibm.mdt.ui.contentpane.operations.NewDimensionOperation.saveDimension(NewDimensionOperation.java:48)
com.ibm.mdt.ui.contentpane.operations.NewDimensionOperation.modify(NewDimensionOperation.java:34)
com.ibm.cdf.pmui.contentpane.models.ModelTreeState.modify(ModelTreeState.java:84)
com.ibm.cdf.pmui.utilities.BusyWaitUtilities$10.run(BusyWaitUtilities.java:282)
com.ibm.cdf.pmui.utilities.CustomBusyIndicator.showWhile(CustomBusyIndicator.java:63)
com.ibm.cdf.pmui.utilities.BusyWaitUtilities.showWhile(BusyWaitUtilities.java:139)
com.ibm.cdf.pmui.utilities.BusyWaitUtilities.runModelTreeOperation(BusyWaitUtilities.java:288)
com.ibm.mdt.ui.contentpane.actions.NewModelObjectAction.executeOperation(NewModelObjectAction.java:27)
com.ibm.mdt.ui.contentpane.actions.NewDimensionAction.run(NewDimensionAction.java:40)
com.ibm.cdf.cui.utilities.popup.CDFBaseMenuItem.runAction(CDFBaseMenuItem.java:482)
com.ibm.cdf.cui.utilities.popup.CDFBaseMenuItem.mouseUp(CDFBaseMenuItem.java:506)
org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213)
org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
com.ibm.mdt.app.Application.start(Application.java:84)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
java.lang.reflect.Method.invoke(Method.java:611)
org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
org.eclipse.equinox.launcher.Main.run(Main.java:1408)
Re: title element not found - application validation problem
Posted: Fri Feb 15, 2013 6:01 am
by lotsaram
Extra data maybe. Additional useful information no.
Check for empty subsets.
The error message in the application builder is implying there is a problem with an empty view because a title dimension is empty due to it being assigned a subset that has no members. When dimensions are updated you need to be careful that static subsets don't get cleared. Typically doing DimensionDeleteAllElements is not a very good idea and it is better to unwind without deleting. Put members back in the subset and your issue should be fixed.
Re: title element not found - application validation problem
Posted: Fri Feb 15, 2013 6:42 am
by kastellu
But, even if i create new dimension or cube with new dimension i get this error.
Dimension and cube are simple and there is no difference. If I create dimension in TM1 modeler , I get the same error at the time dimension is created. Like I wrote there is no empty subsets and all views looks just fine.
Any other ideas?
Thanks!