.NET/Java PDF, Tiff, Barcode SDK Library

As in the case of the traditional export and import utilities, Data Pump uses dump files and other log files, but there are significant differences. You ll use three types of files for Data Pump operations: Dump files: These hold the table data as well as the metadata that s being loaded or unloaded. Log files: These are the standard files for logging the messages and results of Data Pump operations. SQL files: Data Pump Import uses a special parameter called SQLFILE, which will write all the DDL statements it will execute during the import job to a file. Data Pump doesn t actually execute the SQL, but merely writes the DDL statements to the file specified by the SQLFILE parameter. You use SQL files only to hold the output of the SQLFILE command during a Data Pump Import job. This parameter is discussed in the Data Pump Import Parameters section later in this chapter. As in the case of the older export/import utilities, all new log files and (and SQL files) will overwrite any older files with the same name. If an older dump file of the same name already exists, you ll get an error. Unlike with the traditional export and import utilities, you use directories and directory objects to store the Data Pump files. The following section explains how to use directory objects.

free online barcode generator excel, how to make barcode in excel sheet, barcode in excel einlesen, barcode add in for excel 2003, barcode activex control for excel 2010, how to add barcode in excel 2007, excel barcode inventory, excel barcode generator, barcode font for excel 2010, barcode generator excel download,

A Data Pump job creates all its dump files on the server, not on the client machine where a job may have originated. Oracle background processes are responsible for all dump file set I/O, on behalf of the Oracle software owner (usually, the user oracle). This means that for security reasons, you can t let any user specify an absolute file path on the server. In addition to a possible violation of security, there is the matter of safety, as you can unwittingly overwrite a server file if you are given the power to write dump files anywhere on the system. Similarly, you ll be able to read all files that the server has access to, even though you may not have been granted specific privileges to do so. To avoid these types of problems, Data Pump uses directory objects.

SSH_CLIENT=172.16.5.199 3433 22 USER=rbpeters MAIL=/var/mail/rbpeters HOME=/home/rbpeters SSH_TTY=/dev/ttyp1 PAGER=more ENV=/home/rbpeters/.shrc LOGNAME=rbpeters BLOCKSIZE=K TERM=xterm PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:\ /usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:\ /home/rbpeters/bin SHELL=/bin/sh

Your Data Pump Export and Import jobs will not run unless you create a directory object first. Subsequently, you must also ensure that the user has the necessary file and directory access privileges on that file system.

Directory objects are named objects that Data Pump maps to a specific operating system directory For example, a directory object named dpump_dir1 can point to the /u01/app/oracle/admin/ export directory on the server You can then access this directory by simply using the dpump_dir1 directory object name Oracle creates a default directory object, DATA_PUMP_DIR, when you create a new Oracle Database 10g Release 2 database or if you upgrade a database to that version This default DATA_PUMP_DIR directory object points to a directory named dpdump The default data pump directory is automatically created by Oracle in one of the following locations: ORACLE_BASE/admin/SID ORACLE_HOME/admin/SID If you have defined the ORACLE_BASE directory, Oracle uses the location based on it Otherwise, Oracle will create the default directory under the ORACLE_HOME directory Data Pump will write all dump files, SQL files, and log files to the directory specified for the default DATA_PUMP_DIR object.

To see exactly where your default DATA_PUMP_DIR directory object is located, you can use the following query, based on the DBA_DIRECTORIES view: SQL> SELECT * FROM dba_directories; OWNER DIRECTORY_NAME DIRECTORY_PATH -----------------------------------------------------------------------------SYS DATA_PUMP_DIR /u01/app/oracle/product/1020/db_1/admin/orcl/dpdump/ SQL> Only privileged users like SYS and SYSTEM can use the default directory object DATA_PUMP_DIR Thus, user SYSTEM can start a Data Pump Export job without providing a directory name However, before a nonprivileged user can use Data Pump Export or Import, the DBA must create a directory object or grant privileges to use an existing directory In addition to the DBA, any user with the CREATE ANY DIRECTORY privilege can create a directory object Here s how you create a directory object: SQL> CREATE DIRECTORY dpump_dir1 AS '/u01/finance/oradata/dump_dir'; In order for a user to use a specific directory, the user must have access privileges to the directory object.