I am trying to use your tool the PRM Schema Databridge to recover data from a crashed Oracle 12 server.

It works great for tables that don’t have any CLOB or BLOB fields but all the tables that have LOB data fails to transfer.

I’ve attached a log from a failed transfer of one such table.

Am I doing something wrong or do I need to do anything specific to make it work for LOB fields?

If I could get this to work that would be fantastic news for me.

Feedback

Download DBRECOVER for Oraclehttps://s.dbrecover.com/dbrecover-for-oracle-latest-dist.zip

Are you using 11g new feature securefile LOB? this kind of lob storage is not prm-dul build-in function . If you are using classic basicfile lob (before 11g), maybe there is heavy corruption in lob location blocks.

If you are using classic basicfile lob, then try non-dictionary mode, it will scan the whole database, and list lob and tables.

We can also provide a recovery service to your emergency case, We can recover it ASAP . Please let me know if you are interested in service or prm-dul product .

We are not using Secure File explicitly but I now see that it is the default storage setting in Oracle 12.

Anyway, thanks for your quick response.

Also, I think that you have a very useful tool. If I get into similar problems with another system in the future I will look you up and see if you have been able to implement support for these LOBs.

DBRECOVER Recovery Options

For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.

When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.

Archive ParnassusData Blog Migration Archive