Unable to add new groups to dimension '}Groups'

[sachin]

We have around 500 roles that need to be added to the '}Groups' dimension. There is a TI process that reads a csv file and updates this dimension. After adding about 20 roles, it throws this warning in the log file -

548 WARN 2010-09-30 20:36:55.810 TM1.Group Attempt to add a new group exceeded the limit on group creation.

And this repeats for many lines (possibly about 400 or more). I tried to manullay add groups and get the error (see attachment). There are no KB articles on IBM site that addresses this issue. Is there a setting on the server that needs to be altered to facilitate adding more groups?

We have hooked Cognos Access Manager to TM1 for authentication. 'Default' is the namespace under which all the ids and roles are present.

Thanks,
Sachin

[Michel Zijlema]

Hi,

There is a GroupsCreationLimit parameter that can be added to the tm1s.cfg file (if it's not there the default value is 20).
Did you use the AddGroup function in your TI process? According to the Operations Guide the limit should not be enforced when using this function in TI.

Michel

GroupsCreationLimit
This parameter is optional.
Sets the maximum number of groups that can be created in one TM1 server session. The GroupsCreationLimit parameter accepts a value of any positive integer. The maximum number of groups for GroupsCreationLimit is 65535. The maximum number of groups that can exist on a server is 65535. If you do not use the parameter, the default number of groups is 20.
For example, to create 50 groups per server session, enter the following line:
GroupsCreationLimit=50
Note: When TM1 allocates memory to store security information, the server calculates the amount of memory required based in part on the value of GroupsCreationLimit. In some circumstances when your TM1 model is large and the GroupsCreationLimit parameter is set to an exceptionally high value, the server will attempt to allocate memory beyond the available capacity on the server. The TM1 server will fail to load and will issue a Server Out of Memory message. To avoid this situation, set GroupsCreationLimit to a value that accurately reflects the maximum number of user groups you may need to create during a server session.
The GroupsCreationLimit value is not enforced when you create groups with the AddGroup function in TurboIntegrator.

[sachin]

Michel thanks for the tip. I wasn't aware of the config parameter. I will have to contact my infrastructure folks to change the parameter you mentioned on the server. Hopefully this should fix the problem.

I am not using the AddGroup function. When we manually add a group using the GUI, adds the CAMID as the the element and Cognos role name in 2 of the attributes 'en-us' and '}TM1_DefaultDisplayValue'. (See blue box in the attachment). If I use AddGroup and pass the CAMID, then it populates CAMID everywhere even in the attributes! (See red box).

Hence I have built an SDK program that fetches the CAMID and the role name into a .csv file. And in TI process I use DimensionElementInsert and AttrPutS to populate the '}Groups' dimension.

Thanks,
Sachin

[Michel Zijlema]

I am not using the AddGroup function. When we manually add a group using the GUI, adds the CAMID as the the element and Cognos role name in 2 of the attributes 'en-us' and '}TM1_DefaultDisplayValue'. (See blue box in the attachment). If I use AddGroup and pass the CAMID, then it populates CAMID everywhere even in the attributes! (See red box).

The attributes are of type alias. Like the element name an alias needs to have an unique value (and thus can't be blank), that's why the value is initialized with the element name. You can overwrite the 'default' values with the required values.

Michel

[sachin]

Based on your experience, is there an advantage of one (using DimensionElementInsert) over the other (AddFunction)? Thanks.

- Sachin

[tomok]

Based on your experience, is there an advantage of one (using DimensionElementInsert) over the other (AddFunction)? Thanks.

- Sachin

The difference is that those TI functions related to security automatically take effect without having to run a SecurityRefresh. If you modify a security dimension or cube directly, either through a TI, a rule assignment, or manual input, then you have to do a SecurityRefresh for the changes to take effect. Using those pre-defined TI functions, or using the security GUI screens takes care of that for you.

[sachin]

Michel, after adding the parameter to tm1s.cfg, TI process finished without errors.

Michel and Tomok ... thank you both for the inputs. Cheers!

- Sachin