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	`FDORA_USER`	Yes	The username that will be used to connect to the target Oracle Database.
Oracle Database Password	`FDORA_PASSWORD`	Yes	The password for Oracle Database User.
Oracle Database URL	`FDORA_URL`	Yes	JDBC URL for Oracle database. Connecting to Oracle Autonomous Database You will need client credential zip file (wallet) to connect with Oracle Autonomous Database on Oracle cloud. You can download wallet zip file from Oracle Cloud, you will need admin userid and password to perform this download. See Download Client Credentials (Wallets) for more details on how to download wallet file. Since FlexDeploy 9.0.0.9 with Oracle Wallet Credential Type : Instead of maintaining the wallet zip file under the file system, you can now store the wallet zip as an Oracle Credential Type in FlexDeploy. This allows for secure storage and use of the wallet. Use the URL syntax in the following format: `jdbc:oracle:thin:@service_low?TNS_ADMIN= $\{\{FDORACLE_WALLET_FILE\}\}</code></p></li><li><p>We must select valid oracle wallet credential for <code>FDORACLE_WALLET_FILE</code> property on target group.</p></li><li><p>Here, <code>$ {{FDORACLE_WALLET_FILE}}` is replaced with the temporary wallet folder path during execution. Once execution is completed, the temporary file is cleaned up automatically. Before FlexDeploy 9.0.0.9 You must make sure that only authorized users have access to these wallet files. Unzip the client credentials zip file (wallet_databasename.zip) on FlexDeploy server and/or endpoint where it will be used. For example, /home/flexdeploy/.wallets/<wallet_databasename> is folder where specific wallet file was unzipped. Make sure to secure this folder to FlexDeploy and/or Endpoint user, so that it is not readable by all users. We recommend using Oracle Wallet Credential Type for better security and easier management of Wallet usage. Database URL Syntax : jdbc:oracle:thin:@service_high?TNS_ADMIN=/home/flexdeploy/.wallets/<wallet_databasename> service_high is one of the entries in the tnsnames.ora file where client credentials zip file was unzipped. See Predefined Database Service Names for Autonomous Database for details on services. TNS_ADMIN value in URL points to the location of the unzipped client credentials zip file. Database URL Long Connection String Format Syntax : `jdbc:oracle:thin:@(description= (retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=<hostname>))(connect_data=(service_name=<serice_name>))(security=(ssl_server_cert_dn=“CN=<hostname>,OU=Oracle BMCS US,O=Oracle Corporation,L=Redwood City,ST=California,C=US”)))` Examples for the same can be found here. If using the Oracle Database Plugin with ADW or ATP databases , use the _low connection. The _medium and _high connections can sometimes throw error ORA-12839: cannot modify an object in parallel after modifying it.
Oracle Wallet File	`FDORACLE_WALLET_FILE`	No	Since 9.0.0.9 - Provide the Oracle Wallet file, seeCredential Type - Oracle Wallet for more details.
Oracle SQLcl Home	`FD_SQLCL_HOME`	Yes	Folder where SQLcl is installed. ( Ex: `/u01/install/sqlcl`) 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	`FDSQLCL_SQL_EXTENSIONS`	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	`FDSQLCL_RETRY_COUNT_DEFAULT`	No	When discovering or evaluating files, default the Retry Count to this.
Stop On Deployment Error	`FDSQLCL_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	`FDSQLCL_IGNORE_COM_ERR_EXT_DEF`	No	When discovering or evaluating files, set the Ignore SQL Compilation Warning attribute to true for files with these extensions.
SQL Property Replacement Default	`FDSQLCL_PROPERTY_REPLACEMENT_DEFAULT`	No	When discovering or evaluating files, default Property Replacement to this.
SQL Root Target Folder	`FDSQLCL_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 `FD_TEMP_DIR`.
Other Root Target Folder	`FDSQLCL_OTHER_ROOT_TARGET_FOLDER`	No	The path to store the delivered Other files. Leave blank to store them in the `FD_TEMP_DIR`.

Inputs

Input Name	Input Code	Required	Description
User Profile (login.sql)	`FDSQLCL_INP_LOGIN_SQL_FILE`	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	`FDSQLCL_INP_GENERATE_SPOOL_FILE`	No	Check to generate report (Spool file) of SQL statement executions.
Show DBMS Output	`FDSQLCL_INP_SHOW_DBMS_OUT`	No	Check to print DBMS output in the log.

Input Name

Input Code

Required

Description

User Profile (login.sql)

FDSQLCL_INP_LOGIN_SQL_FILE

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

FDSQLCL_INP_GENERATE_SPOOL_FILE

Check to generate report (Spool file) of SQL statement executions.

Show DBMS Output

FDSQLCL_INP_SHOW_DBMS_OUT

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

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*Plus

Please 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.

FlexDeploy 10.0 Documentation

packageDeploy(SQLcl)

Target Properties

Connecting to Oracle Autonomous Database

Project Properties

Inputs

Artifacts

Endpoint Selection

Endpoint Execution

Special Considerations

Supported Object Types

Object Types

FlexDeploy 10.0 Documentation

​Target Properties

Connecting to Oracle Autonomous Database

​Project Properties

​Inputs

​Artifacts

​Endpoint Selection

​Endpoint Execution

​Special Considerations

​login.sql

​Supported Object Types

​Object Types

Target Properties

Project Properties

Inputs

Artifacts

Endpoint Selection

Endpoint Execution

Special Considerations

login.sql

Supported Object Types

Object Types