Subsets locked by phantom views

[steve_h]

I've encountered this problem for years, and am wondering if anyone has come up with a solution for this.

Here's an example.

I create a drill through process that will create a unique view and unique set of subsets upon execution.

I've created a nightly cleanup chore to delete all unique views and subsets.

All views destroy correctly.

All subsets do not destroy and process will error out. The error being the subset can not be deleted because it is being used by a view. Which, of course, it is not.
This tends to occur more often when I'm using MDX to create the subsets.

Has anyone found a solution to this issue that doesn't require restarting the service?

Thanks.

[John Hammond]

I have also encountered the ghost in the machine.

Unloading and reloading the cube that owns the view may be less drastic than restarting the service.

[steve_h]

Thanks John. Good suggestion. Unfortunately the cube would take about 15 minutes to come back up, by as last resort, might not be another option.

Was hoping the issue had been addressed by now, or at least have some type of workaround to be able to delete them.

[John Hammond]

Just remembered something - I think if you use a TI function to do the delete,as opposed to the user interface, the subset will go. I not 100% sure but it might be worth a try...

[steve_h]

I am attempting to destroy via TI. I submitted a bug to IBM.

Thanks for the help.

[Alan Kirk]

I've encountered this problem for years, and am wondering if anyone has come up with a solution for this.

Here's an example.

I create a drill through process that will create a unique view and unique set of subsets upon execution.

I've created a nightly cleanup chore to delete all unique views and subsets.

All views destroy correctly.

All subsets do not destroy and process will error out. The error being the subset can not be deleted because it is being used by a view. Which, of course, it is not.
This tends to occur more often when I'm using MDX to create the subsets.

Has anyone found a solution to this issue that doesn't require restarting the service?

I've found instances of this when I've been testing the creation of a view via TI, and have looked at the view and possibly exported it in the process of doing so. (This isn't always the trigger, but as a "for instance".) It appears that somehow my client session gets ahold of the subset. As long as that client session remains alive, I can't delete the subset. Not manually, not by TI. As soon as I kick over my Excel session, the TI code to delete it will run without errors.

[cycleman83]

I'm having this same issue... Using v9.5.2

I dynamically create subsets and views as part of a drill process, then I have a process scheduled to delete all of the views and subsets that have been created.

The views delete without any issues. Then when I try to delete the subsets, I get an error saying the subsets are used by a view.

Has anyone had any luck with resolving this issue since the last post?

[Steve Rowe]

This is a version related bug that has dropped in out of the system over the years. If you are on a version that suffers from the issue you don't have too many options.
Of course you need to be 100% sure that your aren't using the subset in view, but if you are creating all the objects dynamically in a TI you can be sure.
Current version don't suffer from the issue, but different version of 9 did an didn't....

[Boas]

Hi everybody,

although this topic is very old and claimed to be solved, I struggled this issue several times in several versions.
Looks like IBM did not really solve this bug in a sustainable way:
https://www.ibm.com/support/pages/apar/PI97815

Currently, I got this issue in version 11.8.01200.7, i.e. 2.0.9.13.

Cube unload and reload did not help...

I'm afraid, there is no smart idea by someone in the community?

[Wim Gielis]

That version is 2 years old, maybe it’s solved in the meantime ?

[Boas]

HI community,

meanwhile I was in contact with the IBM support. We examined that it was possible to delete the subsets after a re-login. And a chore was also able to delete the subsets.

But the whole issue was fixed in version Workspace version 2.0.94:
https://www.ibm.com/support/pages/apar/PH58579