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

after upgrading OBIEE to OAS we have an error on some of the action links

Accepted answer
30
Views
2
Comments
Maniki
Maniki Rank 1 - Community Starter
in Oracle Analytics Cloud and Server

Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65PState: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)State: HY000. Code: 43275. [nQSError: 43275] Message returned from OBIS [ecid: ts:2025-04-02T13:34:52.638+02:00]. (HY000)State: HY000. Code: 17001. [nQSError: 17001] Oracle Error code: 904, message: ORA-00904: "SYS_TBL_$1$"."EARNED_VALUE_COST": invalid identifier at OCI call OCIStmtExecute. (HY000)State: HY000. Code: 17010. [nQSError: 17010] SQL statement preparation failed. (HY000)

what could be the cause of this error?

Action links were working fine on OBIEE and we now have this issue

Best Answer

  • SteveF-Oracle
    SteveF-Oracle Mod
    Answer ✓

    To add, Action Links in OAS are configured differently than in OBI (scripts to update the entries in the database vs. file system xml files)

    How To Configure Action Framework In Oracle Analytics Server (OAS) (Doc ID 2775835.1)

Answers

  • Gianni Ceresa
    Gianni Ceresa Mod

    Hi,

    Welcome to the Oracle Analytics community and forum.

    The error is an Oracle Database error, there is something in your query, maybe in how the query itself is built that isn't valid.

    ORA-00904: "SYS_TBL_$1$"."EARNED_VALUE_COST": invalid identifier at OCI call OCIStmtExecute.

    What you should do is to look at your logs to get the full (physical) SQL statement, and from there you can start evaluating how to fix it. Is that query correct? Is it a wrong object or something like that? Does the query work if executed directly in the database?

    It's maybe also an uncommon design in your RPD, because every version does introduce more rules limiting the modelling errors.

    Well, start from your query, that's how you will be able to find the real cause.