filmov
tv
How to fast restore oracle database without backup
Показать описание
dictionary mode load database oracle 18c
It is a utility that can unload data from “badly damaged” databases. It will scan a database file, recognize table header blocks, access extent information, and read all rows .
Read the Oracle data dictionary if the SYSTEM tablespace files are available
Analyze all rows to determine number of columns, column datatypes and column lengths
It can handle all row types normal rows, migrated rows, chained rows, multiple extents, clustered tables, etc.
The utility runs completely unattended, minimal manual intervention is needed.
Cross platform unloading is supported
It can open other datafile(s) if there are extents in that datafile(s).
Recovers data directly from Oracle data files
the Database (RDBMS) is bypassed
Does dirty reads, it assumes that every transaction is committed
Does not check if media recovery has been done
DATABASE CORRUPT - BLOCKS OK
Support for Locally Managed Tablespaces
PRM does not require that media recovery be done.
Since PRM reads the data directly from datafiles, it reads data that is committed as well as uncommitted. Therefore the data that is salvaged by PRM can potentially be logically corrupt. It is upto the DBA and/or the Application programmers to validate the data.
Supports all database constructs:
row chaining, row migration, hash/index clusters, longs, raws, rowids, dates, numbers, multiple free list groups, segment high water mark, NULLS, trailing NULL columns etc...
It is a utility that can unload data from “badly damaged” databases. It will scan a database file, recognize table header blocks, access extent information, and read all rows .
Read the Oracle data dictionary if the SYSTEM tablespace files are available
Analyze all rows to determine number of columns, column datatypes and column lengths
It can handle all row types normal rows, migrated rows, chained rows, multiple extents, clustered tables, etc.
The utility runs completely unattended, minimal manual intervention is needed.
Cross platform unloading is supported
It can open other datafile(s) if there are extents in that datafile(s).
Recovers data directly from Oracle data files
the Database (RDBMS) is bypassed
Does dirty reads, it assumes that every transaction is committed
Does not check if media recovery has been done
DATABASE CORRUPT - BLOCKS OK
Support for Locally Managed Tablespaces
PRM does not require that media recovery be done.
Since PRM reads the data directly from datafiles, it reads data that is committed as well as uncommitted. Therefore the data that is salvaged by PRM can potentially be logically corrupt. It is upto the DBA and/or the Application programmers to validate the data.
Supports all database constructs:
row chaining, row migration, hash/index clusters, longs, raws, rowids, dates, numbers, multiple free list groups, segment high water mark, NULLS, trailing NULL columns etc...