A Quick Report scheduled via an Application Server Task fails with a WebLogic transaction-rollback error deep in the stack (referencing a heuristic/XA transaction issue), while the same report runs fine when executed interactively — what could cause a report to fail specifically when run as a scheduled background task?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check the report's SQL for a 'Fetch First N Rows' clause — this specific construct has been found to trigger an ORA-44201 ('cursor needs to be reparsed') condition that surfaces as a transaction-rollback failure specifically in the background/scheduled execution context, even though the exact same query runs fine interactively. Removing 'Fetch First N Rows' from the report's SQL (restructuring the row-limiting logic another way if you still need it) resolves the scheduled-execution failure.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions