Jump to

• Request
• Response
• Examples

Create an import data pump job

post

/database/datapump/import

Create a Data Pump import job with the specified parameters and start it. Data and object structures can be imported from a directory in the Oracle database server or from Oracle Object Store. Refer to Oracle Data Pump documentation for a more detailed explanation of parameters. A client requires SQL Administrator or SQL Developer role to invoke this service.

Request

Supported Media Types

• application/json

Header Parameters

• Content-Type(optional): string
  Allowed Values: [ "application/json" ]

Body ()

Root Schema : DatabaseDatapumpImportRequest

Type: object

Title: DatabaseDatapumpImportRequest

Show Source

• credential_name(optional): string
  Specify the name of the credential, owned by the database user, to be used to import from object storage.
• datapump_dir(optional): string
  Default Value: DATA_PUMP_DIR

  Specify the database directory to use.
• file_name: string
  The file name pattern to use for Data Pump import. Required when operation is IMPORT. When credential_name is specified the file_name must be a URI format for an Oracle Object Store location.
• job_mode(optional): object job_mode
• name_expressions(optional): array name_expressions
  Used to define Metadata Filter parameters for a Data Pump job.
• remap_schemas(optional): array remap_schemas
  Used to define Remap Schema parameters for an import job.
• schema_expressions(optional): array schema_expressions
  Used to define Metadata Filter parameters for a Data Pump job.
• tablespace_expressions(optional): array tablespace_expressions
  Used to define Metadata Filter parameters for a Data Pump job.
• threads(optional): integer(int32)
  The maximum number of worker processes that can be used for the job. Set this parameter to adjust the amount of resources used for a job.

{
    "title":"DatabaseDatapumpImportRequest",
    "type":"object",
    "properties":{
        "credential_name":{
            "description":"Specify the name of the credential, owned by the database user, to be used to import from object storage.",
            "type":"string"
        },
        "datapump_dir":{
            "description":"Specify the database directory to use.",
            "type":"string",
            "default":"DATA_PUMP_DIR"
        },
        "job_mode":{
            "type":"object",
            "allOf":[
                {
                    "$ref":"#/definitions/JobMode"
                },
                {
                    "description":"Specify the Data Pump job mode.",
                    "default":"SCHEMA"
                }
            ]
        },
        "threads":{
            "description":"The maximum number of worker processes that can be used for the job. Set this parameter to adjust the amount of resources used for a job.",
            "type":"integer",
            "format":"int32"
        },
        "file_name":{
            "description":"The file name pattern to use for Data Pump import. Required when operation is IMPORT. When credential_name is specified the file_name must be a URI format for an Oracle Object Store location.",
            "type":"string"
        },
        "remap_schemas":{
            "description":"Used to define Remap Schema parameters for an import job.",
            "type":"array",
            "items":{
                "$ref":"#/definitions/RemapSchema"
            }
        },
        "name_expressions":{
            "description":"Used to define Metadata Filter parameters for a Data Pump job.",
            "type":"array",
            "items":{
                "$ref":"#/definitions/NameExpression"
            }
        },
        "schema_expressions":{
            "description":"Used to define Metadata Filter parameters for a Data Pump job.",
            "type":"array",
            "items":{
                "$ref":"#/definitions/SchemaExpression"
            }
        },
        "tablespace_expressions":{
            "description":"Used to define Metadata Filter parameters for a Data Pump job.",
            "type":"array",
            "items":{
                "$ref":"#/definitions/TablespaceExpression"
            }
        }
    },
    "required":[
        "file_name"
    ]
}

Nested Schema : job_mode

Type: object

Match All

Show Source

• string
  Title: JobMode

  Allowed Values: [ "FULL", "SCHEMA", "TABLE", "TABLESPACE" ]

  Specify the Data Pump job mode.
• Default Value: SCHEMA

  Specify the Data Pump job mode.

{
    "type":"object",
    "allOf":[
        {
            "$ref":"#/definitions/JobMode"
        },
        {
            "description":"Specify the Data Pump job mode.",
            "default":"SCHEMA"
        }
    ]
}

Nested Schema : name_expressions

Type: array

Used to define Metadata Filter parameters for a Data Pump job.

Show Source

• Array of: object NameExpression
  Title: NameExpression

{
    "description":"Used to define Metadata Filter parameters for a Data Pump job.",
    "type":"array",
    "items":{
        "$ref":"#/definitions/NameExpression"
    }
}

Nested Schema : remap_schemas

Type: array

Used to define Remap Schema parameters for an import job.

Show Source

• Array of: object RemapSchema
  Title: RemapSchema

{
    "description":"Used to define Remap Schema parameters for an import job.",
    "type":"array",
    "items":{
        "$ref":"#/definitions/RemapSchema"
    }
}

Nested Schema : schema_expressions

Type: array

Used to define Metadata Filter parameters for a Data Pump job.

Show Source

• Array of: object SchemaExpression
  Title: SchemaExpression

{
    "description":"Used to define Metadata Filter parameters for a Data Pump job.",
    "type":"array",
    "items":{
        "$ref":"#/definitions/SchemaExpression"
    }
}

Nested Schema : tablespace_expressions

Type: array

Used to define Metadata Filter parameters for a Data Pump job.

Show Source

• Array of: object TablespaceExpression
  Title: TablespaceExpression

{
    "description":"Used to define Metadata Filter parameters for a Data Pump job.",
    "type":"array",
    "items":{
        "$ref":"#/definitions/TablespaceExpression"
    }
}

Nested Schema : NameExpression

Type: object

Title: NameExpression

Show Source

• expression: string
  An SQL clause to be used as a Name Expression filter.

{
    "title":"NameExpression",
    "type":"object",
    "properties":{
        "expression":{
            "description":"An SQL clause to be used as a Name Expression filter.",
            "type":"string"
        }
    },
    "required":[
        "expression"
    ]
}

Nested Schema : RemapSchema

Type: object

Title: RemapSchema

Show Source

• source: string
  Source schema to remap from.
• target: string
  Target schema to remap to.

{
    "title":"RemapSchema",
    "type":"object",
    "properties":{
        "source":{
            "description":"Source schema to remap from.",
            "type":"string"
        },
        "target":{
            "description":"Target schema to remap to.",
            "type":"string"
        }
    },
    "required":[
        "source",
        "target"
    ]
}

Nested Schema : SchemaExpression

Type: object

Title: SchemaExpression

Show Source

• expression: string
  An SQL clause to be used as a Schema Expression filter.

{
    "title":"SchemaExpression",
    "type":"object",
    "properties":{
        "expression":{
            "description":"An SQL clause to be used as a Schema Expression filter.",
            "type":"string"
        }
    },
    "required":[
        "expression"
    ]
}

Nested Schema : TablespaceExpression

Type: object

Title: TablespaceExpression

Show Source

• expression: string
  An SQL clause to be used as a Tablespace Expression filter.

{
    "title":"TablespaceExpression",
    "type":"object",
    "properties":{
        "expression":{
            "description":"An SQL clause to be used as a Tablespace Expression filter.",
            "type":"string"
        }
    },
    "required":[
        "expression"
    ]
}

Back to Top

Response

Supported Media Types

• application/json

201 Response

Description of the Data Pump import job that has been created.

Body ()

Root Schema : DataPumpJobsItem

Type: object

Title: DataPumpJobsItem

This object represents a specified Data Pump job in the database.

Show Source

• attached_sessions(optional): integer(int32)
  Number of sessions attached to the job.
• datapump_sessions(optional): integer(int32)
  Number of Data Pump sessions participating in the job.
• degree(optional): integer(int32)
  Number of worker processes performing the operation.
• job_mode(optional): string
  Mode of job.
• job_name(optional): string
  User-supplied name for the job (or the default name generated by the server).
• links(optional): array links
• operation(optional): string
  Type of job.
• owner_name(optional): string
  User that initiated the job.
• state(optional): string
  Current job state.

{
    "title":"DataPumpJobsItem",
    "description":"This object represents a specified Data Pump job in the database.",
    "type":"object",
    "properties":{
        "owner_name":{
            "description":"User that initiated the job.",
            "type":"string"
        },
        "job_name":{
            "description":"User-supplied name for the job (or the default name generated by the server).",
            "type":"string"
        },
        "operation":{
            "description":"Type of job.",
            "type":"string"
        },
        "job_mode":{
            "description":"Mode of job.",
            "type":"string"
        },
        "state":{
            "description":"Current job state.",
            "type":"string"
        },
        "degree":{
            "description":"Number of worker processes performing the operation.",
            "type":"integer",
            "format":"int32"
        },
        "attached_sessions":{
            "description":"Number of sessions attached to the job.",
            "type":"integer",
            "format":"int32"
        },
        "datapump_sessions":{
            "description":"Number of Data Pump sessions participating in the job.",
            "type":"integer",
            "format":"int32"
        },
        "links":{
            "type":"array",
            "items":{
                "$ref":"#/definitions/LinkRelation"
            }
        }
    }
}

Nested Schema : links

Type: array

Show Source

• Array of: object LinkRelation
  Title: LinkRelation

{
    "type":"array",
    "items":{
        "$ref":"#/definitions/LinkRelation"
    }
}

Nested Schema : LinkRelation

Type: object

Title: LinkRelation

Show Source

• href: string
• rel: string

{
    "title":"LinkRelation",
    "type":"object",
    "properties":{
        "rel":{
            "type":"string"
        },
        "href":{
            "type":"string"
        }
    },
    "required":[
        "rel",
        "href"
    ]
}

Back to Top

Examples

The following example shows how to create Data Pump import job by submitting a POST request on the REST resource using cURL.

curl -i -X POST -u username:password 
-d @request_body.json 
-H "Content-Type:application/json" https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/import

Example of Request Body

Note:

The URL structure https://rest_server_url/resource-path, used in the preceding command has the following components:

• rest_server_url is the REST server where Oracle Rest Data Server is running
• The remainder of the URL includes the ORDS context root, the database identifier, the schema identifier, the version of ORDS Database API to use, and the path for this operation.

The following is an example of a request body for submitting a Data Pump request to import objects from the USERS tablespace and remap SCOTT schema objects to HR schema. In this example, the default DATA_PUMP_DIR database directory is used and it is expected that there are dump files matching the EXPDAT%U-13_12_45.DMP file name pattern.

{
  "job_mode": "SCHEMA",
  "file_name": "EXPDAT%U-13_12_45.DMP",
  "tablespace_expressions": [
    {"expression": "= 'USERS'"}
  ],
  "remap_schemas": [
    {"source": "SCOTT","target": "HR"}
  ]
}

Example of Response Header

The following example shows the response header. The Location header returns the URI that can be used to view the status of the job:

HTTP/1.1 201 Created
Content-Type: application/json
Content-Location: https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/jobs/PDBADMIN,DATAPUMP_REST_IMPORT_20190906154258/
ETag: "onyB9moowJVhrJQrJ80tk3VyP3HZ9QqXHvwsmKrvnhNk/mOZF9CRFKJXIXWkKAnLtmJHssYdJ83KBCJUgqBtbQ=="
Location: https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/jobs/PDBADMIN,DATAPUMP_REST_IMPORT_20190906154258/
Transfer-Encoding: chunked

Example of Response Body

The following example shows the response body with 201 returned in JSON format:

{
    "job_name": "DATAPUMP_REST_IMPORT_20190906154258",
    "owner_name": "PDBADMIN",
    "operation": "IMPORT",
    "job_mode": "SCHEMA",
    "state": "EXECUTING",
    "degree": 1,
    "attached_sessions": 0,
    "datapump_sessions": 2,
    "job_state": "EXECUTING",
    "links": [
        {
            "rel": "collection",
            "href": "https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/jobs/"
        },
        {
            "rel": "describedby",
            "href": "https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/metadata-catalog/"
        },
        {
            "rel": "related",
            "href": "https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/jobs/PDBADMIN,DATAPUMP_REST_IMPORT_20190906154258/EXPDAT-2019-04-19-14_11_39.LOG"
        },
        {
            "rel": "related",
            "href": "https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/jobs/PDBADMIN,DATAPUMP_REST_IMPORT_20190906154258/IMPDAT-2019-09-06-15_42_58.LOG"
        },
        {
            "rel": "self",
            "href": "https://rest_server_url/ords/orcl/pdbadmin/_/db-api/stable/database/datapump/jobs/PDBADMIN,DATAPUMP_REST_IMPORT_20190906154258/"
        }
    ]
}

Back to Top