packageDeploy(SQLcl)
- Karl Henselin
- Chandresh Patel
Executes a group of SQL files and copies "Other" files to specified destinations from a package created by the packageBuild(SQLcl) operation. See the appendix for information about the project file attributes.
Please note that the statements in the SQL files must be delimited properly.
Target Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Oracle Database User |
| Yes | The username that will be used to connect to the target Oracle Database. |
Oracle Database Password |
| Yes | The password for Oracle Database User. |
Oracle Database URL |
| Yes | JDBC URL for Oracle database. |
Oracle SQLcl Home |
| Yes | Folder where SQLcl is installed. ( Ex: Make sure that the endpoint Java Home is a high enough version for your SQLcl version. |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
SQL Extension Order |
| No | List SQL file extensions in desired order. Will be used for discover and sort. Files with these extensions will discover as type DB Object. |
SQL Retry Count Default |
| No | When discovering or evaluating files, default the Retry Count to this. |
Stop On Deployment Error |
| No | Stop deploying package files if any error occurs. If unchecked all files will be deployed even if one or more files fails. This is for package operations only. |
SQL Ignore Compile Warning Extensions |
| No | When discovering or evaluating files, set the Ignore SQL Compilation Warning attribute to true for files with these extensions. |
SQL Property Replacement Default |
| No | When discovering or evaluating files, default Property Replacement to this. |
SQL Root Target Folder |
| No | The path to store the delivered Sql files. Sql files will be run from here. Leave blank to run them from the |
Other Root Target Folder |
| No | The path to store the delivered Other files. Leave blank to store them in the |
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
User Profile (login.sql) |
| No | User Profile (login.sql) is intended to allow users to specifically customize their session. (see the Special considerations section for examples) |
Generate SQL Spool File |
| No | Check to generate report (Spool file) of SQL statement executions. |
Show DBMS Output |
| No | Check to print DBMS output in the log. |
Artifacts
This operation consumes packages of files created by the packageBuild(SQLcl) operation.
Endpoint Selection
This operation delegates the selection to the workflow developer to determine.
Endpoint Execution
This operation will randomly execute on one of the endpoints identified during selection.
Special Considerations
login.sql
The script provided in the input FDSQLCL_INP_LOGIN_SQL_FILE will be created as the login.sql file in the current working directory and will be deleted after execution. The login.sql script in SQLcl is automatically executed whenever you start SQLcl. It can be used to set up your SQLcl environment, including formatting options, environment variables, and other session settings.
Below is an example script that can be customized based on requirements.
-- Set the SQLcl environment settings
SET ECHO OFF
SET FEEDBACK ON
SET HEADING ON
SET LINESIZE 200
SET PAGESIZE 9999
SET SERVEROUTPUT ON
SET TERMOUT ON
SET TIMING ON
SET VERIFY OFF
-- Set default schema
ALTER SESSION SET CURRENT_SCHEMA=YOUR_SCHEMA_NAME;
-- Define common substitution variables
DEFINE my_variable = 'default_value'
-- Custom SQL*Plus prompt
SET SQLPROMPT "SQL> "
-- Display a welcome message
PROMPT Welcome to SQL*PlusPlease see below for information about the project file attributes
Supported Object Types
The SQLcl plugin partial deploy support allows for deploying File and Folder type objects. These links explain the three types and their attributes.
Object Types
Â
- style