Introduction
This job is used to execute SQL statements and SQL procedures in a database.
- The job makes use of JDBC connections and a Hibernate layer.
- The job can be used to access any database for which a JDBC Driver is available with the Agent.
- For supported DBMS products see JS7 - Database. The JS7 includes a number of JDBC Drivers for supported DBMS.
- For other DBMS you can provide an individual JDBC Driver and store the Driver's .jar file with the .
/lib/user_lib
directory of the Agent installation.
- Delimitation
- Consider that specific SQL language extensions such as Oracle PL/SQL for use with anonymous functions are not supported by Hibernate.
- For Oracle PL/SQL use the JS7 - JITL SOSPLSQLJob
- For Oracle SQL*Plus use the JS7 - JITL SOSSQLPlusJob
Usage
The SOSSQLExecutor job accepts the following arguments:
Name | Required | Default Value | Purpose |
---|---|---|---|
| no | ./config/hibernate.cfg.xml | Specifies the configuration file (XML) format for Hibernate connections, see JS7 - Database. |
| yes | Carries the SQL statements. | |
| no | Raises a warning if the SQL statement creates a result set. | |
| no | If stored procedures are called that return a result set then this argument has to be set to | |
| no | Specifies if and how a result set is forwarded to order variables:
|
In the above configuration the resultset_as_warning
parameter is set to true to ensure that the result is written to the log file. The log file would then appear as shown in the following listing
Note that it is possible to define more than one instruction in the command argument.
Such instructions are then carried out in the order in which they are written and must be separated by a semicolon and a subsequent newline.
You can use
as a newline.
For example
update MY_TABLE set a='foo' where b='bar';
commit;
Note also that order variables could be used to overwrite the job arguments explained with the above example.
Further information
- Job Documentation:
- tbd