You are not logged in.

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

ap_OM

Professional

  • "ap_OM" started this thread

Posts: 17

Date of registration: May 21st 2009

  • Send private message

1

Tuesday, June 9th 2009, 2:26am

Problem with palo.data function

I have a problem with the palo.data function. I thought I knew the difference between the data, datac and datav function (i looked it up in the manual and here, but now I have a problem with palo.data and a rule.

If something didn't work I previously always switched from datav or datac to data. But in the following case I had to switch from data to datac to get a result.

As you can see in the attached pics, I use a very simple rule to write a value into ['Aufwaende der IVM','kalk. Parameter','IVM']. I simplified it, just to test the palo.data problem. All other rules are deactivated.

As you can see in the attached pics I get the right results with datav (and also with datac) for this rule, but no result with palo.data. In my real model I can't use datac or datav, because they do not work with the other rules.

in the palo.ini I turned the cache-size and the rule-cache to 0.

Any idea how to solve this problem? Is this a bug?

kind regards

Alex

This post has been edited 1 times, last edit by "ap_OM" (Jun 9th 2009, 2:39am)


dominik_l

Jedox Team

  • "dominik_l" is male

Posts: 344

Date of registration: May 7th 2008

Location: Freiburg / Germany

  • Send private message

2

Tuesday, June 9th 2009, 12:24pm

Does an anlogue rule for the Demo DB, like
['2009','Stationary PC''s','Qtr. 1'] = 100000
work as expected with PALO.DATA ?

ap_OM

Professional

  • "ap_OM" started this thread

Posts: 17

Date of registration: May 21st 2009

  • Send private message

3

Tuesday, June 9th 2009, 5:00pm

No. same strange behavior in the demo database!

but I copied my database from localhost to our Server and recalculated the whole Excel-Sheet. There it also works with data.

But after 3 calculations (with all rules-not only the one mentioned above) PALO crashed on the server.

I looked in the palo.ini on the server and there are the following specifications:
#palo.ini created by Palo Server Setup
user-login
verbose info
log "D:\Daten\Paloserver\PaloServer.log"
data-directory "D:\Daten\Paloserver"
http 10.0.0.200 1235
template-directory "C:\Programme\Jedox\Palo-Server\Api"
cache-barrier 5000
cache-size 100000000
clear-cache 2
clear-cache-cells 1000

So I deactivated the cache size 0 entry on localhost and the problem with palo.data disappeared but not all calculations of my rules were executed. And above all after some calculations PALO crashed. (this problem I already discussed here in the forum)

on localhost the palo.ini now looks like this:

cache-barrier 5000
cache-size 0
rule-cache-size 0

user-login

verbose info

log "C:\Programme\Jedox\Palo\Log\PaloServer.log"
http "127.0.0.1" 7777
template-directory "C:\Programme\Jedox\Palo\Api"



So now I don't know what to do. If I set the cache size to 0, PALO does not crash but this one rule is not calculated or I don't set the cache size to 0 and this one rule is calculated correct, but PALO crashes....

I have no idea...

This post has been edited 1 times, last edit by "ap_OM" (Jun 9th 2009, 5:01pm)


  • "realquo" is male

Posts: 255

Date of registration: Mar 11th 2009

Location: Italy

Occupation: BI Consultant

  • Send private message

4

Tuesday, June 9th 2009, 5:59pm

Hi,


maybe setting the proper row in palo.ini as

"
verbose debug

"
and then looking at the PaloServer.log could provide some additional information...

I would also suggest to try to adopt cache setting "With no cache on the client" using the button on the right-bottom in the main Modeler window. This, together with setting cache-size to 0 in palo.ini, solved my problems with rules.

However, some bugs exist for sure in Palo rules management, e.g. http://bugs.palo.net/mantis/view.php?id=3230 and http://bugs.palo.net/mantis/view.php?id=3249

Kind regards,

RQ

ap_OM

Professional

  • "ap_OM" started this thread

Posts: 17

Date of registration: May 21st 2009

  • Send private message

5

Tuesday, June 9th 2009, 7:29pm

Hi

if you mean the general database settings in the Modeller then I always had there the cache settings at "no client cache".

in the log-file I have found no interesting entry until now with the debug-mode.

kind regards Alex

This post has been edited 1 times, last edit by "ap_OM" (Jun 9th 2009, 7:35pm)


Rate this thread