Page 1 of 1
Dimension element deleted, any log to show why?
Posted: Tue May 06, 2014 1:17 pm
by mr j
It is Express 10.1.1 and the main question is if there's a dimension element deleted is there a way to find out why and when this happened? Log, control cube, any?
All I can tell there was a server restart to activate something on the operating system, ie. nothing to do with Express. The Cognos Express services did not start up correct after server restart, but there was a need to delete the tm1s.log and then restart the services (
http://www-01.ibm.com/support/docview.w ... wg21641890)
Now, in one dimension there is an element missing entirely which was there before the server reboot. In control cube }DimensionProperties there's LAST_TIME_UPDATED which suggests the particular dimension has NOT been edited at the time of the reboot.
Re: Dimension element deleted, any log to show why?
Posted: Tue May 06, 2014 8:20 pm
by Duncan P
The only thing I know of that can do this is a change to the config setting
UnicodeUpperLowerCase. If this has changed from false to true then on the next server restart two items which differed by upper and lower cases of the same unicode character (e.g. É and é) would now be treated as the same. TM1 would only load the first one from the dimension file and you would not be told about the one that it thought was a duplicate.
Re: Dimension element deleted, any log to show why?
Posted: Wed May 07, 2014 6:17 am
by mr j
Thanks Duncan,
Case is not the case (ha-ha..) and the mentioned parameter is not applied, but your input reminded of what could be the cause. It seems that there have been duplicate element names in two different dimensions. However, I'm confident to say that these have been ok (ie. neither got deleted) in previous server restart, so... is this sort of duplicacy the cause, or not?
Re: Dimension element deleted, any log to show why?
Posted: Wed May 07, 2014 6:24 am
by Duncan P
No. The same named element in two different dimensions is perfectly fine.
If you haven't already done so have a look at the time-stamp on the dim file and see if that corresponds with the time in }Dimension_Properties.
Then I would take the dim file into a new server by itself and see if it has the same elements.
Re: Dimension element deleted, any log to show why?
Posted: Wed May 07, 2014 8:22 am
by mr j
Ok, that's what I thought too about same names.
As mentioned there was an issue with restarting the Express services. I noticed this when I was looking at cube data via a previously created Cognos Insight widget. There was an error message related to connection to server which directed me to check in Express Manager what's going on. Then, as mentioned, I deleted the tm1s.log file and restarted the service. With all the clients closed etc.
Now, the dim time stamp "Date modified" says 10:48 am. I initiated the above said service restart at 11:33 am. Therefore - assuming Express Manager time is in sync with the server time

- something's happened to the file prior to restart of service.
The dim file timestamp does not match with the LAST_TIME_UPDATED in }Dimension_Properties, the latter is a couple of months older which in a way makes sence as the dimension has not been touched in a long time. (For a while it seemed that the LAST_TIME_UPDATED does not update immediately after a change to a dimension, but now it seems to work... tested by adding/deleting elements in a test dimension.. odd).
Sorry for not mentioning the Insight in the first place, I didn't think it would make a difference, but now when looking at timestamps I'm thinking it must be. Just don't understand how.
I also took the dim file to another server as you suggested and the content of the dimension is the same in both environments.
EDIT:
Just looked at tm1server.log. At the time of dim file timestamp (considering UTC) there's (I've edited CUBENAME? and "ElementName"):
---
544
ERROR 2014-05-06 07:48:56.554 TM1.Dimension CUBENAME? Dimension Update Fail. Rule Is Invalid: Error compiling rule, line number 17: Element not found "ElementName"
---
referring to the deleted element. Nothing else in the log before this with a reference to the element. No other rows at the same point of time.