Issue with subset

[winsonlee]

The following are the subset file for a dimension. Production and development box has exactly the same content. But the issue i am facing is when i click on the subset on production box, there isnt any element display on the subset editor. When i click on the subset on the development box, the element is displayed as what is mention on the text below. The only thing i can think of is the security. But I have checked the security and there isnt any cube with the name of }ElementSecurity_dimensionname. So i presume everyone has full write permission to that dimension. has anyone encounter this issue before ?

Code: Select all

283,100
11,20110727225720
274,Name
18,0
275,
278,0
281,0
270,17
A
B
C
D
E
F
G
H
I

[Gregor Koch]

Hi
My first guess would be the security as well and I take it that you have the same rights on both servers and have also checked that there is no }ElementSecurity_dimensionname.cub file in the data directory and/or have refreshed the display of the cubes in server explorer.

What strikes me though and this might not be the problem, is that in the file you are showing has this in it:

270,17
A
B
C
D
E
F
G
H
I

The 17 is actually the counter of the elements in the subset when it is saved and that doesn't match up with the elements you show. Incomplete code, corruption or manual change of the text (.sub) file?

The other thing I notice is that you use the "Name" alias for this subset. Unfortunately I cannot test this in Cognos Express at the moment as to what would happen but maybe double check whether this Alias still exists on the prod server and is not corrupted.

All a bit far fetched and I still think security might be the most likely issue.

[winsonlee]

thanks for the reply. I modified the element with something else. There are 17 element on the text file. I would eliminate the possibility of corrupted file as the development and production server has the identical file. Not unless if the data has been changed in the memory and it isnt save to the text file yet. I am login as administrator. Is there an instance that administrator lost permission to certain?

How can i go about checking if this Alias still exists on the prod server ?

270,17
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q



The other thing I notice is that you use the "Name" alias for this subset. Unfortunately I cannot test this in Cognos Express at the moment as to what would happen but maybe double check whether this Alias still exists on the prod server and is not corrupted.

All a bit far fetched and I still think security might be the most likely issue.

[winsonlee]

I have tried Edit element Attribute for the dimension. Name still exist as Alias and data for the name are still there.

I find it unusual that the application is not giving me the outcome mention on the text file.

[Gregor Koch]

It is, sorry I don't have a solution for you.

[jstrygner]

Did you try to rebuild this subset manually on prod?
Or if you are afraid to overwrite anything on prod, did you try to build the same subset, but with different name on prod, just to check?
After that you can try to compare old and new subset file, maybe this will give you the hint.
HTH

[John Hammond]

I know its obvious but did you restart the server after you copied the subset to the directory of the production server? It wont be picked up into memory otherwise.

[paulsimon]

Again another thing that might be obvious but are you sure that the elements in the subset actually exist in the underlying dimension in production? If not, as soon as you open the subset in Architect/Perspectives, TM1 will reduce the subset down to the list of valid elements and if none exist it will show an empty subset

Regards

Paul Simon

[winsonlee]

thanks for the reply guys. It is just one subset that is missing. So doesnt worry me much as i can just recreate it.
The more serious issue i am facing is the views. When i open the views it mention "No values available". When i try opening the dimension, there isnt any element there. So I got to manually show all element and re select the element from the list and save the view.
When i try opening the *.vue file, the element that was selected previously actually exist on the file.
There are more then 50 views that uses that particular dimension and I got to compare with the development server to re add the element manually on every single view which are taking me a long time.

It works previously. if on the *.vue file if it is stated x, y, z, wouldnt it be the case that x,y,z should be displayed when i open the view on Architech ?

what causes the element on a dimension save on view to go missing out of a sudden ? When i try re adding the elements, the elements actually still do exist.