This operation is deprecated in release 4.0.3.10, and will be removed in a future release. All functionality is merged into the runScript operation. Please use that operation instead in your workflows.
Executes an Oracle PL/SQL script. This operation takes the SQL script as an input and processes each statement in the database using JDBC.
Please note that each statement in the SQL files must be delimited by a forward slash (/) on its own line. Also this operation supports intermixed regular SQL statements (non PL/SQL statements), however, these statements must not end with a semi-colon. See the Appendix for sample PL/SQL script file:
Environment/Instance Properties
| Property Name | Property Code | Required | Description |
|---|---|---|---|
| JDBC URL |
| Yes | The JDBC URL of the database. |
| JDBC User |
| No | The username that will be used to connect with. |
| JDBC Password |
| No | The password of the username. |
| JDBC Driver Path |
| Yes | Classpath for locating the JDBC Driver (e.g. for Weblogic - {ORACLE_HOME}/oracle_common/modules/ oracle.jdbc_11.2.0/ojdbc6.jar). |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
| Input Name | Input Code | Required | Description |
|---|---|---|---|
| User |
| No | The username that will be used to connect with. This input takes precedence over the environment instance scoped |
| Password |
| No | The password for |
| Script File |
| Yes | The path to the script to execute. If a relative path is given, the path will be assumed to be in the |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation consumes one or more SQL files, and an optional sequence file, from the artifacts repository.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
Endpoint Execution
This operation will randomly execute on one of the endpoint identified during selection.
Special Considerations
The statements in the SQL files must be delimited by a forward slash (which must be on its own line).
Sequence File for multi-file processing:
If you want to execute multiple SQL scripts, instead of specifying a SQL file within the FDJDBC_INP_FILE_NAME input, a file containing an ordered list of SQL files to execute may be given. The plugin will detect whether a SQL file or a sequence file has been specified based on the format of the file. The format of a sequence file is as follows:
!SEQ /createDeptPackages.sql /createHRPackages.sql /GrantPackages.sql
The !SEQ line (must be the first line) at the top of the file indicates a sequence file. After the sequence line, an ordered list of files to run follows.
Replacement Properties
See Appendix.