The ScriptRunner is a tool for installing database objects in Oracle databases, and for the parameterized execution of any other desired program sequences. It displays the execution status graphically in a hierarchical form.



The execution is specified in ASCII format item lists. These item lists define the order and types of items (e.g. loading SQL scripts, loading Java sources/resources and classes, executing any desired program files, displaying messages, writing files) and their conditions of execution. A monolith can be formed from this item list, which automatically contains all Java and SQL objects. Other types of files (e.g. executable program files and command files) can be explicitly integrated. SQL scripts can also be handled with the Oracle Wrap Utility.

The type of installation can be defined by an external error level file. This file is present in ASCII format. Depending on the type of installation, it lists Oracle function codes and those error messages which are to be suppressed. For example, this enables those annoying error messages to be suppressed which are generated when an attempt is made to delete non-existent objects. The ScriptRunner then only enters the "genuine" error messages in the automatically generated error file. This makes it considerably easier to interpret.

The supply of monoliths, for example with schema installations, enables one to ensure that no scripts are forgotten, and that the installation runs in the customer system in exactly the same way as it runs in the test system. The ScriptRunner itself or the ScriptRunner "RunTime" version execute these monoliths. The RunTime version, which is included in the scope of supply, can only handle these types of monoliths, whereas the ScriptRunner itself can also handle the individual item lists.

The script execution is logged in log and error files. These show which items have actually been executed, and the errors that have occurred.