For Incremental exports, the flag indirects whether a record will be stores data dictionary tables recording the export.

 Name of the parameter file to be passed for export.

 A flag to indicate whether statistical information about the exported objects should be written to export dump file.

 A  flag  to indicate whether  a read consistent version of all the exported objects should be maintained. 

 The name of the file which log of the export will be written.

 The name of the file from which import should be performed.

 A flag to indicate whether file content should be displayed or not.

 A flag to indicate whether the import should ignore errors encounter when issuing CREATE commands.

 A flag to indicate whether grants on database objects will be imported.

 A flag to indicate whether import should import index on tables or not.

 A flag to indicate whether rows should be imported. If this is set to 'N' then only DDL for database objects will be executed.

Migration and Changing are two distinctly different types of problems that can exist when a row is too large to fit into a single data block.Row Changing:: Row changing occurs when a row is too large to fit into a single empty data block. When this occurs, Oracle will spread the row across as many blocks as are needed. Changing the row from from one block to the next.Row Migration:: Row migration occurs...

What is meant by Shared pool fragmentation.

Hi All,I have a Materialized views Group, on this group I have 57 MVs these are all created on Master data (OLAP) log files and we have dependency schedule to run this jobs. Load dependency is like (MD tabs Then  Log files MVs) this is not a problem with us.For 57 views to get updated (refreshed) in 4 hours in these views one view is taking nearly 2 hours to update. We are updating this group...