The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

SQLPlus Script Runner

View this plugin on the Plugins site

step([$class: 'SQLPlusRunnerBuilder']): SQLPlus Script Runner

  • credentialsId : String
  • user : String
    Inform schema user information (example: SCOTT) or schema user and password (example: SCOTT/TIGER). You can use global variable like ${USER}.
  • password : String
  • isSysdba : String
  • instance : String
    Inform instance information (example: ORCL). You can use global variable like ${INSTANCE}.
  • scriptType : String
  • script : String
    This is the name of SQL script, expected at src/main/resources folder.
    Example:
    update.sql or sql/update.sql
  • scriptContent : String
    This is a custom SQL script.
    Example:
     SELECT sysdate from dual; 
     show user; 

  • customNLSLang : String (optional)
    NLS_LANG is an environment variable used to define language, territory and character set properties. Example: AMERICAN_AMERICA.US7ASCII or FRENCH_CANADA.WE8ISO8859P1 Source: ORAFAQ
  • customOracleHome : String (optional)
    Using custom ORACLE_HOME will override global ORACLE_HOME. Leave this field blank to use global ORACLE_HOME. ORACLE_HOME refers to either a directory where the Oracle software is installed or an environment variable pointing to the directory where the Oracle software is installed. Source: ORAFAQ
  • customSQLPath : String (optional)
    SQLPATH contains the name of your directory for your SQL script collection. Example: c:\u01\app\sql_scripts or /oracle/app/sql Source: DBA Oracle
  • customSQLPlusHome : String (optional)
    Using custom SQL*Plus will help find SQL*Plus executable file, this helps if you are working with Jenkins agent machines. Example: C:\Oracle\App\Server\Oracle\bin\sqlplus.exe or /oracle/app/oracle/product/12.1.0/dbhome_1/bin/sqlplus Learn more about distributed builds
  • customTNSAdmin : String (optional)
    Using custom TNS_ADMIN refers to a directory where the Oracle SQL*Net configuration files (like sqlnet.ora and tnsnames.ora) are located. Example: C:\Oracle\App\Server\Oracle\network\admin or /oracle/app/oracle/product/12.1.0/dbhome_1/network/admin Source: ORAFAQ

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.