Jun 12 (edited) • Technical
Oracle on Prem to LH (NUMBER)
Seeking Advice on Handling Oracle NUMBER Data Type in Fabric
I am trying to parameterise the loading of tables from an on-prem Oracle database into a Lakehouse in Microsoft Fabric. However, I have encountered a known issue: Copy activity from Oracle to Lakehouse fails due to NUMBER type.
This issue prevents me from automating the process using Will's parameter-driven parent-child loop. My approach involves populating a configuration table with table names and other metadata that need to be loaded. The loop then processes each table from this configuration.
The problem arises because some of the source tables uses the NUMBER data type with no precision, which causes the load to fail with the error:"Invalid Decimal Precision or Scale. Precision: 38, Scale: 127."
As a result, I cannot automatically load such tables into the Lakehouse. Has anyone encountered this issue? If so, what workarounds or solutions have you implemented to overcome it?
UPDATED:
I am currently automating this, for each table, bring in as a csv then copying to a LH table, but by doing so all datatypes become varchar.
0
0 comments
Chris Adams
3
Oracle on Prem to LH (NUMBER)
Learn Microsoft Fabric
skool.com/microsoft-fabric
Helping passionate analysts, data engineers, data scientists (& more) to advance their careers on the Microsoft Fabric platform.
Leaderboard (30-day)
Powered by