TM1 Forum

We have installed Fix Pack3 on Cognos Tm1 9.5.2 (after having FP1 and FP2 installed). We are using Contributor as major client for our users. After installation users cannot enter numeric values into Contributor. Can anybody help us with this issue? We turned our questions to IBM support, but are still waiting for reply. It is urgent. Thank you in advance.

Do you get an error message when you try to enter numbers? Can you post a screenshot showing how it looks before and after you try to enter a number?

Does this problem occur with new contributor applications or all applications regardless of whether they were created before or after applying the fix pack?

Is this just one cube or all cubes? You specify that you can't enter numeric values, which suggests you can enter text values? I wonder if perhaps your cube order has got messed up somehow and all your cells are now text.

Have you checked that you can enter the values ok directly in the cube via the cube viewer? I.e. contributor is the problem? Also, have you checked using an administrator login?

We have this same problem. I posted about it somewhere on this forum, but can't seem to find the post right now, but was going to post an update anyway. We reported this to IBM and I heard back last week, they have indicated it's a defect - the APAR is PM81369: https://www-304.ibm.com/support/entdocv ... wg1PM81369

Specifically for us it was numeric data in TM1 Web (both using cube views in TM1 Web, and using TM1 Contributor) where the problem occurred, for both non-admin and admin users. The same cubes worked fine in Architect, for all users. Most of our input cubes had this problem for all numeric data, although one cube allowed some numeric data to be entered, but not all, but I have yet to find a reason for the difference with that cube.

The support contact I was in touch with said development told him it would be fixed in the 10.2 stream, which I questioned, given the defect is in 9.5.2 FP3. That has caused him to look into it further. Currently I'm waiting to hear back as he is testing if the issue occurs in 10.1 as well. However for us upgrading to 10.1 right now isn't an option (even if it does work ok there), so when we encountered this problem after installing FP3 on our dev server, we reverted back to our previous install (9.5.2 FP2).

Just to understand correctly: both of you have upgraded to FP3 and cannot enter numeric values in TM1 Web and Contributor anymore in most of your cubes?! Any idea if this only happens under certain circumstances? Please do not tell me that IBM released FP3 without testing entering numeric values.

I've checked FP3 fix list and was pleased to read that so many "*server crash*" entries should become solved with this upgrade. However, after reading your post, I'm think I should rather stay with FP2.

foogy

Thanks for the reminder to provide an update!

I can't tell you the exact circumstances this occurs under, since I assume some people did not have this problem, otherwise IBM would have had to fix it at a more global level. However they did get back to me and acknowledge it was a defect and provided a hotfix to fix the the problem. So we recently installed FP3 and the hotfix and no longer have any issues with entering numeric data.
As for other fixes with FP3 it's hard for me to say if it has a lot of benefit, it depends on what issues you're seeing. We tried to test for some of the things it said it fixed that we had seen problems with, and some did appear fixed, while others didn't, but we may have misunderstood what the problem was in the first place. Also we did encounter one change that didn't make sense, where suddenly found ourselves getting logged out of Architect frequently. We eventually removed the ClientPingCAMPassport parameter from the tm1s.cfg file and that fixed that problem, however we had not changed that parameter (or others related to session timeouts) so it seemed unusual that it stopped working properly after FP3 and the hotfix.

If you do install FP3, I'd recommend making sure you have a backup you can revert to, in case you encounter the problems we did. We always have our data center do a snapshot for a backup, but I'll be honest that until now it definitely seemed like it wasn't necessary, as we never saw any problems with previous fix packs. But I'm really glad we did it this time too! As soon as we saw the issues with numeric data after doing the install on our dev server, we just reverted to the snapshot, and then waited until IBM provided the hotfix and it was a more appropriate time for us, to reattempt the install. Although we wasted time and it was frustrating, at least we didn't actually have any downtime because of the FP3 problem.