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

How to customize OBIEE Error Message

Received Response
103
Views
6
Comments
Anirban1
Anirban1 Rank 4 - Community Specialist
edited Aug 13, 2024 5:30PM in Oracle Analytics Cloud and Server

Hi,

We have a requirement to customize one of the Error message in OBIEE 12c.

If any of the report is running more than 10 minutes we are killing that particular query from Database (with a trigger). As soon as the query get killed in OBIEE front end we are able to see below error message -

message: ORA-00028: your session has been killed ORA-00028: your session has been killed

I want to customize this message to "Query has been killed as time limit has been exhausted"

Is it possible to do? Which XML file contain below message, so that I can modify that XML.

Thanks

Anirban

Answers

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

    "ORA" means that the message is being sent from the database engine and OBI just hands it forward to the interface.

    So no chance unless you want to try and change the source code of the database.

  • Anirban1
    Anirban1 Rank 4 - Community Specialist

    Hi Christian,

    Thanks for your reply, Is it possible to conditionally write that message, so that user will be able to understand, the report stops due to exhaust of time not for any other reason. Can you please suggest any thing.

    Thanks

    Anirban

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

    OBIEE doesn't parse backend error messages but hands them forward as-is.

    The reason for this is simple: If you change the actual error message and fumble it into something different your administrators will never know what's happening in case of an error. Googling your "custom error message" won't provide any meaningful results while googling "ORA-00028" yields precise and pertinent results.

    It's simply an extremely bad and conceptually very wrong things to do.

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

    Sorry if this isn't what you wanted to hear, but that's it.Does that conclude the issue for you?

  • Joel
    Joel Rank 8 - Analytics Strategist

    I might be missing something here but in my very humble opinion, shouldn't you be looking at the underlying issue of the query performance in your database? A query taking over 10 minutes doesn't sound right.

  • Anirban1
    Anirban1 Rank 4 - Community Specialist

    Hi Joel,

    Thanks for your reply, we will definitely look into the problem, but meanwhile do not want database resource should be consume for those queries which is taking more than 10 minutes, that is while we will kill those queries from back end and further look into it.

    Thanks

    Anirban