Oracle Fusion AI Data Platform Forum

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

Impact on Last extract date for Errored PVO's in a BICC Job

Accepted answer
12
Views
2
Comments

I have a BICC JOb with 12 PVO and for some reason , some PVO has ended in error. Below is the error we have received for certain PVO's

Caused by: java.sql.SQLException: java.io.IOException: execute query failed[nQSError: 43113] Message returned from OBIS.
[nQSError: 43119] Query Failed:
[nQSError: 60009] The user request exceeded the maximum query governing execution time.
at oracle.bi.jdbc.AnaJdbcStatementImpl.executeQuery(AnaJdbcStatementImpl.java:387)
at oracle.obiacm.queryprocessing.BIServerQuery.runQuery(BIServerQuery.java:1656)
... 15 more

In such scenario , Will the last extract date not be updated for these PVO's ? Ideally it should not be updated so that the data will be pulled up in the next run for the errored PVO's. Just wanted confirmation of my understanding.

Best Answer

  • RVohra
    RVohra Mod
    Answer ✓

    @fusionenthu , Welcome to the Oracle Analytics Community!

    For any PVO that ends in ERROR, the “Last Extract Date” is not updated.
    As a result, the data for those errored PVOs will be re-extracted in the next successful run.

    Above error indicates that the OTBI / BI Server query timed out while extracting data for specific PVOs. This is a query execution failure, not a data completion event.

    So in your job with 12 PVOs:

    • PVOs that completed successfully …. last extract date advanced
    • PVOs that failed with timeout …. last extract date remains unchanged

    When you rerun the BICC job:

    • Only the failed PVOs will re-pull data from the previous extract date
    • Already successful PVOs will continue from their updated extract watermark
    • No data loss occurs for the failed PVOs

    This is exactly how BICC ensures data consistency and no gaps.

    Hope it helps!

Answers