Updating sas datafiles
For example, direct path load cannot be used on clustered tables or on tables for which there are transactions pending.See for a complete discussion of situations in which direct path load should and should not be used.The input for a typical SQL*Loader session is a control file, which controls the behavior of SQL*Loader, and some data, located either at the end of the control file itself, or in a separate datafile.The output of a SQL*Loader session is an Oracle database (where the data is loaded), a log file, a "bad" file, and potentially, a discard file.When you run the Export utility against an Oracle database, objects (such as tables) are extracted, followed by their related objects (such as indexes, comments, and grants), if any.The extracted data is written to an export dump file.This method can sometimes be slower than other methods because extra overhead is added as SQL statements are generated, passed to Oracle, and executed.It can also be slower because when SQL*Loader performs a conventional path load, it competes equally with all other processes for buffer resources.
The version of the Import utility cannot be earlier than the version of the Export utility used to create the dump file.
The discard file contains records that were filtered out of the load because they did not match any record-selection criteria specified in the control file.
SQL*Loader uses three different methods to load data, depending on the situation: conventional path, direct path, and external tables.
Because the dump files are written by the database, rather than by the Data Pump client application, you must create is a database object that is an alias for a directory in the host operating system's file system.
Data Pump Export and Import enable you to move a subset of the data and metadata.