![data pump in oracle 10g documentation data pump in oracle 10g documentation](https://i0.wp.com/mikedietrichde.com/wp-content/uploads/2021/10/fakurian-design-Glel-RswQqM-unsplash.jpg)
The collection of types defined for use with the GET_STATUS procedure are version-specific and include version information in the names of the types. The way in which these types are defined and used may be different than what you are accustomed to. The types described in this section are defined in the SYS schema for use by the GET_STATUS function. The DBMS_DATAPUMP package defines OBJECT types. KU$_DUMPFILE_TYPE_TEMPLATE CONSTANT BINARY_INTEGER := 3
![data pump in oracle 10g documentation data pump in oracle 10g documentation](https://slideplayer.com/slide/14385438/89/images/5/Data+Pump+Overview%3A+Background.jpg)
KU$_DUMPFILE_TYPE_DISK CONSTANT BINARY_INTEGER := 0 The following definitions are used for identifying types of dump files returned through the DBMS_DATAPUMP. KU$_STATUS_JOB_ERROR CONSTANT BINARY_INTEGER := 8 KU$_STATUS_JOB_STATUS CONSTANT BINARY_INTEGER := 4 KU$_STATUS_JOB_DESC CONSTANT BINARY_INTEGER := 2 KU$_STATUS_WIP CONSTANT BINARY_INTEGER := 1 The following mask bit definitions are used for controlling the return of data through the DBMS_DATAPUMP. and followed by the symbols in the following lists: Mask Bit Definitions
![data pump in oracle 10g documentation data pump in oracle 10g documentation](https://image3.slideserve.com/7106335/operation-fundamentals-l.jpg)
Any references to these constants must be prefixed by DBMS_DATAPUMP. All such constants are defined as part of the DBMS_DATAPUMP package. There are several public constants defined for use with the DBMS_DATAPUMP. Import objects (for example, DIRECTORY definitions) that unprivileged users cannot createĪlthough the SYS schema does not have the IMP_FULL_DATABASE role assigned to it, all security checks performed by Data Pump that require the IMP_FULL_DATABASE role will also grant access to the SYS schema. It allows users running these operations to do the following: The IMP_FULL_DATABASE role affects only Import and SQL_FILE operations. Monitor jobs that were initiated by another userĮxport objects (for example, TABLESPACE definitions) that unprivileged users cannot referenceĪlthough the SYS schema does not have the EXP_FULL_DATABASE role assigned to it, all security checks performed by Data Pump that require the EXP_FULL_DATABASE role will also grant access to the SYS schema. Perform the operation outside of the scope of their schema The EXP_FULL_DATABASE role affects only Export operations. The Data Pump API will use these roles to determine whether privileged application roles should be assigned to the processes comprising the job.
Data pump in oracle 10g documentation full#
The existing EXP_FULL_DATABASE and IMP_FULL_DATABASE roles will be used to allow privileged users to take full advantage of the API. Security for the DBMS_DATAPUMP package is implemented through roles. The resources applied to an export or import job can be modified.ĭata in an Oracle proprietary format can be unloaded and loaded. Previously aborted export and import jobs can be restarted without duplicating or omitting any data or metadata from the original job. Schema names, datafile names, and tablespace names can be transformed at import time. The source and target databases can have different hardware, operating systems, character sets, and time zones.Īll object types and datatypes existing in Oracle Database 10 g are supported.ĭata and metadata can be transferred between databases without using any intermediary files.Ī subset of a database can be moved based upon object type and names of objects. The support and functionality provided by DBMS_DATAPUMP is as follows: This section contains topics that relate to using the DBMS_DATAPUMP package.