Oracle BI Publisher troubleshooting starts by separating missing data from a failed report request. A blank CSV, an authorization error and a timeout have different causes. Capture the report path, selected parameters and Oracle environment before changing the query or increasing a timeout.
Run the same report in Oracle with the same account and parameter values. A browser session using an administrator account is a different test from an automated run using an integration account. Compare the effective access and report permissions. Finding an object in the catalog does not establish that the account can run it or read its data.
Check the complete catalog path and the report object type. A folder, a data model and a report are different targets. After a migration, verify the destination object and its references. The catalog export and import guide covers the separate checks for object existence and report behavior.
Inspect the report's parameter definitions before supplying values. Confirm internal parameter names, date formats and whether a parameter accepts multiple values. A displayed label can differ from the value expected by the service. Start with a narrow date range that returns known records, then widen one condition at a time.
For an invoice data model with a missing-column error, this CLHAPI metadata-query adaptation checks the visible header-table columns. It uses Oracle's column dictionary and a public table filter.
SELECT column_name,
data_type,
data_length
FROM all_tab_columns
WHERE owner = 'FUSION'
AND table_name = 'AP_INVOICES_ALL'
ORDER BY column_id;Compare the result with the failing column reference under the same reporting account. Dictionary visibility and report permissions are separate checks. This query cannot diagnose template layout or prove that the report's business filter should return rows.
If the data model returns rows but the document is blank, check the selected template and output format. A CSV export and a formatted PDF do not exercise the same layout. Review the report's available formats and run a small export in the required one. Avoid treating a locally created zero-byte file as proof that Oracle returned an empty result.
For a timeout, distinguish the client connection limit from report processing time. Oracle's BI report timeout guidance points to its performance recommendations. Narrow the reporting period and inspect expensive joins before increasing limits. A timeout after a request was accepted can leave server-side work running.
A reviewed CLI example is fusion-toolkit --profile report-test bi-publisher-run-report -p "/Custom/Finance Reports/AP Aging Report.xdo" -f csv -o output/ap-aging.csv. The path is illustrative. Use an existing report in your test catalog, confirm its required parameters and inspect the generated file. The report execution guide explains the surrounding export workflow.
This guidance was reviewed on 8 November 2026. Compare one failing automated run with a known report execution and keep the exact parameter values with the diagnostic evidence.
You can also use an LLM with the Fusion Toolkit AI Administrator skill and ask, "Which parameters does this BI Publisher report require?" It can inspect supported report metadata in plain language without requiring you to write the request. Start with the exact report path.