Hi,
We recently upgraded our model with Latest TM1 10.2.2FP1,When we click the generate feeders option(All rules option in drop down ) in performance modeler,we are getting the error.Please find the attachment for the details.
Please give some suggestions to solve this issue.
Getting error while Generate Feeders option in PM
-
ram123
- Posts: 38
- Joined: Sun May 19, 2013 10:06 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2007
Getting error while Generate Feeders option in PM
- Attachments
-
- Java error.docx
- Getting error while Generate Feeders option in PM
- (25.92 KiB) Downloaded 290 times
Re: Getting error while Generate Feeders option in PM
When you go to TM1 Perspectives/Architect and you make a change to a rule in some/all of the cubes, do you get a rule error? If your server takes only a short time to start up, you can just restart it and look at the log file.
The reason I ask this is because we ran into some similar issues where if you make a change to anything (even whitespace, or formatting) within the #region areas of the rules, PM starts to get confused and throws rules at the bottom of the rule file which is below the feeder section. Then the results in the UI become unpredictable.
The reason I ask this is because we ran into some similar issues where if you make a change to anything (even whitespace, or formatting) within the #region areas of the rules, PM starts to get confused and throws rules at the bottom of the rule file which is below the feeder section. Then the results in the UI become unpredictable.
-
ram123
- Posts: 38
- Joined: Sun May 19, 2013 10:06 am
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2007
Re: Getting error while Generate Feeders option in PM
We are not getting any error,while we are editing in architech/perspective.....
Re: Getting error while Generate Feeders option in PM
ram123,
Unfortunately, because it is a canned application, you can't really get in the middle and identify where the problem is. All we can do is surmise what the problem is based on the routine names in the exception trace. Which indicates that it is trying to script a DB statement and it is having trouble.
Can you identify which cube is causing the problem? Perhaps by removing rules from each cube one by one you can track down which cube, and then start removing rule lines until you can narrow down the source of the issue.
Other than that, your best bet is at this point might be to check with IBM to see if there are some tracing/logging you can turn on to see if it provides more insight or send them the model and see if they can reproduce.
Unfortunately, because it is a canned application, you can't really get in the middle and identify where the problem is. All we can do is surmise what the problem is based on the routine names in the exception trace. Which indicates that it is trying to script a DB statement and it is having trouble.
Can you identify which cube is causing the problem? Perhaps by removing rules from each cube one by one you can track down which cube, and then start removing rule lines until you can narrow down the source of the issue.
Other than that, your best bet is at this point might be to check with IBM to see if there are some tracing/logging you can turn on to see if it provides more insight or send them the model and see if they can reproduce.