child categories exceeds 65536) ause This message indicates that an internal limit has been reached.

The current rule is that no one category can have more than 65,000 (approximately) categories attached to it. Cognos suggests a ratio of category to children to be between 1:7 to 1:10 Resolving the problem There are two Solutions for this problem 1) Resructuring the model as below 2) Archiving the data Restructure the model so that the limit is no longer an issue. This is possible by adding levels within the dimension where the limit occurs. You can view the log file to see which approximate dimension is causing this issue. Here is an example of The structure of the Hierarchy in a Model. Dimension Category Count Level 1 2 Level 2 2 Level 3 10 Level 4 187,000 Although it looks like a limit is being hit with the lowest level at 187,000 categories, if you divide this number by the number of parents (which is 10) at the next level, there are only 20,000 categories per parent. There are two other instances where this error will occur. 1. The model has levels suppressed. When suppressing a category in a model Transformer essentially attaches any children of the suppressed category to its parent. We still have to put the leaf level in the cube (even if it is suppressed) but they are marked as hidden and then attached to the visible parents higher up in the hierarchy. 2. If your organization changes, your model may contain inactive categories that are no longer needed. Delete these inactive categories as follows: From the Tools menu, click Clean House. In the Date field, type a date in YYYYMMDD format. All categories that have been inactive from the specified date to the present are deleted The limit of 65536 categories is a limit that you cannot change through the INI file or any other way. I seem to remember seeing the reasons for this limit soew here, it something to do with storing numbers in 16 bits - yes I know these days we have 32 and 64 bit hardware but PowerPlay was originally written for 16 bit hardware, its a similar limitation that exists (or existed) in Excel! The only s olution is to restructure your dimensions