Deploy Objects

This dialog box is displayed when you click the Deploy or Deploy Cloud icon in the Cart window (described in Deploying Objects Using the Cart).

Deploy Objects

You can specify the output file (such as a .zip file) to contain the script files that can be used to deploy the selected objects to the schema of another Oracle Database connection.

The generated script files include a master script that invokes the other scripts. This master script has a name in the format Generated-yyyymmddhhmmss.sql, where yyyymmdd is the master script file creation date and hhmmss is the creation time.

The default values for many options in this dialog box are determined by the Database: Utilities: Export user preferences.

File: Location and name of the output file to contain the generated scripts, plus any before and after scripts that you specified for the deployment. (You can click Browse to find a location.)

Format: Format for the output file (such as ZIP for a .zip file).

Export DDL: If this option is checked, the data definition language (DDL) statements for the database objects to be deployed are included in the output file, and the other options in this group affect the content and format of the DDL statements.

For explanations of specific options, see the Export DDL options under Database: Utilities: Export.

Data: If this option is checked, the output file or files contain appropriate statements or data for inserting the data for deployed tables and views. If this option is not checked, the data for deployed tables and views is not included; that is, only the DDL statements are included.

Truncate Destination Data: Causes any data in any destination tables or views with the same names to be deleted before the deployed data is inserted. If this option is not selected, the deployed data is appended to any existing data.

Apply: Creates a single file containing the deployment script files, including the master script that invokes the other scripts.

Deploy Objects to Cloud

You can deploy objects to the Cloud, except as noted in Unsupported Type Error for Cloud Deployment.

Cloud

Connection: Name of a previously created Cloud connection.

Title: A short descriptive string identifying this deployment.

Server: Server for the Cloud service (for example, a WebLogic Server system).

Port: Port to be used for the deployment. For example: 2222

Authorization

SFTP User: Secure FTP user name that you received in email when you signed up for the Cloud service.

SFTP Password: Password for the SFTP user.

Transfer

File: .zip file to contain the files to be used by SQL Developer for the deployment.

Deploy DDL

Specify whether not to replace or to replace existing destination objects that have the same schema name and object name combination.

Deploy Data

Truncate destination data: If you specified not to replace existing destination objects, then for each existing destination table, this controls whether any existing data is truncated (deleted) before the source table data is appended.

Disable constraints before moving data: Controls whether to disable referential integrity constraints before deploying data to destination tables. (You may want to disable constraints to expedite the deployment, and then reapply the constraints after the deployment.)

Format

Delimiter: Identifies the character used to separate the data into columns. The delimiter character is not included in the data loaded. If the preview page does not show the data separated into columns, the correct delimiter is probably not specified. Examine the data in the preview area to determine the correct delimiter.

Line Terminator: Identifies the terminator for each line. The line terminator is not included in the data loaded. If the preview page shows the data in one single row, the correct terminator is not specified.

Left Enclosure and Right Enclosure: Enclosures are used for character data and are optional. Enclosures are not included in the data loaded.

Unsupported Type Error for Cloud Deployment

An error box is displayed if any of the following conditions apply on an attempt to deploy objects from the Cart to the Cloud:

  • The objects include any of the following object types: database link, directory, external table, materialized view, materialized view log, or synonym.

  • The objects include any with a data type that is not supported for Cloud deployment (such as SDO_GEOMETRY).

  • The objects are from a non-Oracle database connection.