Migration from Oracle LogMiner to Binary Log Reader in Boston Consulting Group is blocked because NUMBER datatypes are mapped differently in BLR, converting NUMBER with no precision and scale to FLOAT or VARCHAR in the destination.
LogMiner previously preserved NUMBER, which they rely on for downstream compatibility.
BLR’s current behavior is by design, but it introduces breaking schema changes for existing pipelines with multiple downstream consumers.
For BCG, downstream changes are not feasible due to operational risk.
This limits the ability to migrate customers off LogMiner, despite LogMiner being deprecated.
A configurable option to control NUMBER datatype mapping would close this gap.