Fabric Data Days Monthly is back. Join us on March 26th for two expert-led sessions on 1) Getting Started with Fabric IQ and 2) Mapping & Spacial Analytics in Fabric. Register now
I am replicating data from an Oracle 19c database to a mirrored database in Fabric. All Oracle tables are successfully replicating, but I'm getting the same error message on two tables. Neither table has a NVARCHAR(MAX) column (as I've heard this causes issues).
Here's the schema of one of the failing Oracle tables and the actual error message is below.
| lineitemamt | number |
| lineitemusage | float |
| adddttm | date |
| moddttm | date |
| paidstat | nvarchar2(1) |
| pendflag | nvarchar2(1) |
| pendtype | nvarchar2(1) |
| lineitemkey | number |
| billkey | number |
| lineitemunits | float |
| addby | nvarchar2(30) |
| modby | nvarchar2(30) |
| penaltypayorder | number |
| principalpayorder | number |
| printtext | nvarchar2(300) |
| discountexpiredate | date |
| commentskey | number |
| lineitemsetupkey | number |
| penaltydate | date |
| penalizedflag | nvarchar2(1) |
| accountservicekey | number |
| printorder | number |
| legacylineitemno | number |
| actualamt | number |
| budgetedamountflag | nvarchar2(1) |
| variantflag | nvarchar2(1) |
Table (subtask 0 thread 1) is suspended. The Fabric Mirrored database indicate an error, errorStatus: 'Replicating', errorCode: '', errorMessage:
'We encountered an error while parsing data file being used, please fix the file and try again.
The error is: Exception reading the data file. Exception: No data rows available.
Appreciate any suggestions, tips.
Thanks
Hi @mrrozhall ,
Just checking, have you had a chance to open a support ticket, as suggested. If so, we'd love to hear the current status or any updates from that.
If the issue was resolved through the support ticket, it would be great if you could share the solution here as well. It could really help other community members find answers more quickly.
Warm regards,
Chaithra E.
Hi @mrrozhall ,
Thank you for your response. If the issue still persists, I’d recommend raising a support ticket with Microsoft. The support team can look into the backend and provide more in-depth assistance tailored to your environment.
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
Regards,
Chaithra E.
Send to support
Hi @mrrozhall ,
Thank you for reaching out to Microsoft Community.
This error typically occurs when Fabric is able to detect the table schema, but cannot extract readable change data from Oracle during the initialization phase. As a result, Fabric receives an empty or non-readable result set and suspends replication with the message “Exception reading the data file. No data rows available.”
Based on similar scenarios, this is usually related to how redo/logging or storage is configured on the Oracle table rather than a datatype issue.
Common causes to validate:
Table was empty when mirroring started. Fabric expects at least one readable rowset during initialization.
SELECT COUNT(*) FROM <schema>.<table_name>;
If the count is 0, insert a temporary row, commit, then delete it and commit again to generate redo.
Table is set to NOLOGGING
NOLOGGING operations do not emit sufficient redo for mirroring.
SELECT table_name, logging
FROM all_tables
WHERE table_name = '<TABLE_NAME>';
If LOGGING = NO, enable it:
ALTER TABLE <schema>.<table_name> LOGGING;
No DML activity since table creation
If no redo was generated, LogMiner cannot capture changes. You can force redo generation with a no-op update:
UPDATE <schema>.<table_name>
SET <any_column> = <same_value>;
COMMIT;
Compression or unsupported storage attributes enabled
Certain compression settings can prevent Fabric from parsing the data blocks.
SELECT table_name, compression, compress_for
FROM dba_tables
WHERE table_name = '<TABLE_NAME>';
If compression is enabled, move the table:
ALTER TABLE <schema>.<table_name> MOVE NOCOMPRESS;
High-watermark issue (table previously emptied)
Rebuilding the segment can help:
ALTER TABLE <schema>.<table_name> MOVE; or ALTER TABLE <schema>.<table_name> SHRINK SPACE;
Supplemental logging not enabled at the database level
SELECT supplemental_log_data_min FROM v$database;
If NO, enable it:
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
If the issue continues, please share the following so we can investigate further:
Row count of the table
Table DDL (DBMS_METADATA.GET_DDL)
Logging and compression status from DBA_TABLES
Hope this helps,
Thank you.
Hello, and thanks for the reply. After verifying all suggestions, the problem persists. Below is the requested information.
Row count:
2,046,449,413 records
DDL:
| TABLE_NAME | LOGGING | COMPRESSION | COMPRESS_FOR |
| ACCTTRAN | YES | DISABLED |