Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OBIEE 12c: "A comparison is being carried out between non-compatible types" error (Doc ID 2290231.1)

Received Response
4
Views
9
Comments
3334354
3334354 Rank 2 - Community Beginner

Hello,

I am referring to to fix the rpd errors while upgrading to OBIEE 12.2.1.4.

Solution provided is-

[Removed by Moderator (BluShadow) - DO NOT post MOS Support content on the public community as this breaches your support terms with Oracle]

Can somebody help what would be the query/sql for Init block (as mentioned in #1) for the session variable OBIS_RECURSIVE_DATA_TYPE_CHECKING=0  ?

Thanks

Answers

  • Hi,

    Please delete the "solution" part which is a copy/paste from the MOS document. This is a public forum and MOS content is restricted to users with a valid support contract, therefore it's against the rules of the forum to post content of MOS documents in the public forum.

    If you want to post MOS documents content you need to post in   .

  • 3334354 wrote:Can somebody help what would be the query/sql for Init block (as mentioned in #1) for the session variable =0 ?

    SELECT 0 FROM dual;
    This will be more than enough to get the 0.

  • 3334354
    3334354 Rank 2 - Community Beginner

    Thanks for the quick reply .. let me try and get back to you in case issue is not resolved

  • 3334354
    3334354 Rank 2 - Community Beginner

    Hi Gianni, It is not working. Can you please provide the steps? Thanks

  • What is not working? What did you do?

  • 3334354
    3334354 Rank 2 - Community Beginner

    Created a session variable

     

    OBIS_RECURSIVE_DATA_TYPE_CHECKING

    with

    select 0 from dual; as init block sql.

    But still the errors remain same in the rpd.

  • This doesn't mean the session variable isn't set. You are changing your question...
    At the beginning you wanted to know how to set the variable, now you are saying that the MOS document didn't change anything in your case.

    You maybe misread the document: it is stated that the variable, either local in an analysis or as session variable, simply prevent the error in the analysis. So your analysis will work and will not return that error.

    But it doesn't mean it will either fix or hide errors in the RPD, this is a different level. When you are connected to the RPD the variable isn't going to change the messages of the consistency check. You are supposed to correct those issues in the RPD. OBIEE 11g accepted things which weren't really clean, now 12c force you to do a clean work (a lot more at least). It's a one-time activity: clean up the RPD, fix errors and you are ready to go for many more years.

    Hiding the error or telling OBIEE to ignore a check and accept models which aren't really clean isn't really a long term solution. This variable is there to make the front end work and your users able to use the platform, but it is also expected that you fix the RPD in the background in the meantime.

  • 3334354
    3334354 Rank 2 - Community Beginner

    I was trying the solution provided by MOS doc. For this reason, i asked for the init block query for that variable.

    Yes, it did not change anything after trying out the solution.

    I already have workaround for the rpd errors. But, I wanted the solution to work as per MOS document.

    Thanks.

  • But you didn't say, so far, that the MOS document solution doesn't work.

    The document clearly says that the variable affect analysis, you reported above that the errors remain the same in the RPD. The MOS document never stated it would do anything for the errors in the RPD.

    Are you now affirming that even with the variable set you have some analysis not working and returning you the error?