REVERSE_LTS_PRIORITY has no effect on LTS Priority Group in OBIEE v 12.2.1.2.0

3345606

Hello all,

I'm having an issue regarding REVERSE_LTS_PRIORITY variable. I set it's value to 0 in the initialization block and I'm overwriting it as a request parameter, setting it to 1 using goURL. When this value is set the correct LTS should be selected, based on its LTS Priority Group.

This works as it should in OBIEE 12.2.1.0.0, but it stopped working in OBIEE 12.2.1.2.0. The cause seems to be the fact that REVERSE_LTS_PRIORITY has effect on LTS Priority Group only if it's a numerical data type, while from the request parameter is set as a string.

If in OBIEE 12.2.1.0.0 I could set its default value to 1 using both "select '1' from dual" and "select '1' from dual" and it would apply the reversion, in OBIEE 12.2.1.2.0 it can be only "select 1 from dual", "select '1' from dual" has no effect.

As a workaroud for not being able to set the value to 1 using a request variable, I set the default value to 1 in the initialization block and tried to overwrite its value using the request variable, giving a string value like "no" to cancel the REVERSE_LTS_PRIORITY effect on LTS Priority Group.

This workaround works only for one OBIEE instance, the new value "no" cancels the reversion. On a second instance this doesn't work anymore, even if both OBIEE instances have the same version (12.2.1.2.0). On the second instance, setting the variable to "no" using a request variable does not cancel the effect of the default value set in the initialization block (1), even if the value is actually set. The new value is "no", but it behaves as it would be 1.

Both LTS have the same columns, I can't select one LTS or another based on a specific column, because the criteria for selecting the right LTS should not appear in any analysis.

Any idea about what changed between OBIEE 12.2.1.0.0 and OBIEE 12.2.1.2.0 regarding the REVERSE_LTS_PRIORITY behaviour, or why REVERSE_LTS_PRIORITY is not behaving the same on two instances having the same version (12.2.1.2.0) ?

Thank you

[Deleted User]

Sounds weirdly familiar