Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

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

[nQSError: 22024] A comparison is being carried out between non-compatible types BIT and VARCHAR. (H

Received Response
481
Views
4
Comments
User_V7A4J
User_V7A4J Rank 1 - Community Starter
edited Aug 13, 2024 5:18PM in Oracle Analytics Cloud and Server

Hello All,

After migrate reports from OBIEE 11g to OBIEE 12c(12.2.2.1.4) Few reports are throwing error ([nQSError: 22024] A comparison is being carried out between non-compatible types BIT and VARCHAR. (HY000)) in OBIEE 12c.

Can anyone please help me how to resolve above issue in OBIEE 12c.

Thanks & Regards,

Subhankar Mahanti

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    1.) "reports"? Are you really talking about BI Publisher report objects or are you talking about OBIEE Answers "analyses" objects.

    Two different technologies. Two different objects. NOT the same thing. Words and terminologies have meaning. Please use them correctly if you expect help and don't want to waste everybody's time. You also don't tell your doctor that your foot needs to be amputated if your hand has gangrene just because both are limbs.

    2.) That error is quite clear. You have data type mismatches. You can't compare BIT to VARCHAR. Just like you can't compare DATE to BLOB or DOUBLE to DATE.

    CASE WHEN 'Fish' = 42 THEN 1 else 0 end <== this doesn't work for example as "fish" will never equal 42.

  • User_V7A4J
    User_V7A4J Rank 1 - Community Starter

    Thank you Christian for your reply.

    Sorry for my mistake I was talking about OBIEE answers analysis object but the same analysis is working fine in OBIEE 11g version.

    Thanks,

    Subhankar

  • SteveF-Oracle
    SteveF-Oracle Mod

    12c (and onwards, including Oracle Analytics Server) has tighter type enforcement

    You can relax the enforcement, but it better to identify the formula, filter, etc that is the root cause -- as mentioned by @Christian Berg

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    +1'000'000

    The harder enforcements were overdue. All the things there are now much more explicit and require things to be as they always should have been have - for many, many clients - lifted the lid on just how shoddy a lot of implementations have been over the years. I've spent months cleaning RPDs and catalogs of things that shouldn't exist.

    @4146774 Solve the real issue. Compare things that are comparable. Use correct data types. it will save you a lot of pain.