Forum Discussion

moritzbartram's avatar
moritzbartram
Frequent Visitor
10 months ago
Solved

Mirrored Oracle Error

Hi everyone,  I'm having trouble to create a mirrored oracle item. I've followed the set-up guide and configured my oracle database accordingly, but get the following error:    The message a...
data engineering
  • moritzbartram's avatar
    moritzbartram
    10 months ago

    Hi v-kpoloju-msft,

     

    thanks again for your reply. I've already been in contact with the fabric support team and they confirmed that the error I'm getting results from the amount of tables ~10000 that are in my database and they cannot be displayed. So this is just a UI error that can be circumvented by creating mirror items via Rest-API. 

    Thanks again for your help! 

    Best regards

tayloramy's avatar
tayloramy
Super User
10 months ago

Hi moritzbartram,

 

That “A task was canceled” message usually means Fabric gave up while trying to enumerate your Oracle objects after the connection was picked. In practice it’s a timeout/network/gateway issue during the “Choose data” step-not a credentials problem.

Troubleshooting steps

  1. Confirm prerequisites for Oracle mirroring and your gateway version. Oracle mirroring currently requires an On-premises Data Gateway (OPDG) and Microsoft documents minimum versions (e.g., 3000.282.5+) for Oracle support. Upgrade if you’re older. See Oracle limitations and the setup tutorial here.
  2. Gateway health + region check. In Power BI/Fabric Admin, verify your gateway cluster is online, no high CPU/memory, and its region matches your Fabric tenant region.
  3. Listener / network sanity checks. From the gateway machine, test tnsping to your Oracle service and connect with the same host/port/SID/ServiceName used in Fabric. Make sure port 1521 (or your custom) is reachable and no SSL/TLS interception is breaking the handshake.
  4. Reduce what Fabric has to enumerate. Create a dedicated Oracle user with default schema and only the tables you intend to mirror (or limit permissions to a small subset). The schema browse step is what usually times out.
  5. Retry after gateway restart. Restart the On-premises Data Gateway service to clear stale Oracle client state and try Create > Mirrored database > Oracle again.
  6. Collect details and try again. If it still fails ~30-60s after you select the connection, capture the Activity ID (you already have it), exact UTC time, and the gateway logs, then open a Microsoft support ticket.

 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.