Skip to content

Downloading latest version of utPLSQL

It is quite easy to download latest version of utPLSQL from github on Unix machines. Here is a little snippet that can be handy for downloading latest version.

#!/bin/bash
# Get the url to latest release "zip" file
DOWNLOAD_URL=$(curl --silent https://api.github.com/repos/utPLSQL/utPLSQL/releases/latest | awk '/browser_download_url/ { print $2 }' | grep ".zip" | sed 's/"//g')
# Download the latest release "zip" file
curl -Lk "${UTPLSQL_DOWNLOAD_URL}" -o utPLSQL.zip
# Extract downloaded "zip" file
unzip -q utPLSQL.zip

You may download with a one-liner if that is more convenient. 

#!/bin/bash
curl -LOk $(curl --silent https://api.github.com/repos/utPLSQL/utPLSQL/releases/latest | awk '/browser_download_url/ { print $2 }' | grep ".zip" | sed 's/"//g')

Headless installation

To simply install the utPLSQL into a new database schema and grant it to public, execute the script install_headless.sql as SYSDBA.

This will create a new user UT3 with password XNtxj8eEgA6X6b6f, grant all needed privileges to that user and create PUBLIC synonyms needed to use the utPLSQL framework.

Example invocation of the script from command line: 

cd source
sqlplus sys/sys_pass@db as sysdba @@install_headless.sql

SYSDBA is needed to grant access to DBMS_LOCK.

Recommended Schema

It is recommended to install utPLSQL in it's own schema. You are free to choose any name for this schema.

The installation user/schema must have the following Oracle system permissions during the installation.

  • CREATE SESSION
  • CREATE PROCEDURE
  • CREATE TYPE
  • CREATE TABLE
  • CREATE VIEW
  • CREATE SYNONYM
  • ALTER SESSION

In addition it must be granted execute to the following system packages.

  • DBMS_LOCK

utPLSQL is using DBMS_PROFILER tables for code coverage. The tables required by DBMS_PROFILER will be created in the installation schema unless they already exist. The uninstall process will not drop profiler tables, as they can potentially be shared and reused for profiling PLSQL code.

It is up to DBA to maintain the storage of the profiler tables.

Installation Procedure

Creating schema for utPLSQL

To create the utPLSQL schema and grant all the needed privileges execute script create_utplsql_owner.sql from the source directory with parameters:

  • user name - the name of the user that will own of utPLSQL object
  • password - the password to be set for that user
  • tablespace name - the tablespace name to hold data created during test execution

Example invocation: 

cd source
sqlplus sys/sys_password@database as sysdba @create_utPLSQL_owner.sql ut3 ut3 users

Installing utPLSQL

To install the utPLSQL framework into your database run the /source/install.sql script and provide schema_name where utPLSQL is to be installed.
Schema must be created prior to calling the install script. You may install utPLSQL from any account that has sufficient privileges to create objects in other users schema.

Example invocation: 

cd source
sqlplus admin/admins_password@database @install.sql ut3

Allowing other users to access utPLSQL framework

In order to allow other users to access utPLSQL, synonyms must be created and grants need to be added. You have two options:

  • use grants and synonyms to public, to allow all users to access the framework
  • use synonyms and grants for individual users to limit the access to the framework

To grant utPLSQL to public execute script source/create_synonyms_and_grants_for_public.sql and provide schema_name where utPLSQL is installed.

Example invocation: 

cd source
sqlplus admin/admins_password@database @create_synonyms_and_grants_for_public.sql ut3
To grant utPLSQL to individual user execute script source/create_synonyms_and_grants_for_user.sql, provide schema_name where utPLSQL is installed and user_name to grant access for.

Example invocation: 

cd source
sqlplus admin/admins_password@database @create_synonyms_and_grants_for_user.sql ut3 hr

The following tools that support the SQL*Plus commands can be used to run the installation script:

Additional requirements

In order to use Code Coverage functionality of utPLSQL, users executing the tests must have the CREATE privilege on the PLSQL code that the coverage is gathered on. This is a requirement of DBMS_PROFILER package.

In practice, user running tests for PLSQL code that he does not own, needs to have CREATE ANY PROCEDURE/CREATE ANY TRIGGER privileges. Running code coverage on objects that the user does not own will not produce any coverage information without those privileges.

Uninstalling utPLSQL

To uninstall run /source/uninstall.sql and provide schema_name where utPLSQL is installed.

The uninstall script will remove all the objects installed by the install script. Additionally, all the public and private synonyms pointing to the objects in utPLSQL schema will be removed.

If you have you have extended any utPLSQL types such as a custom reporter, these will need to be dropped before the uninstall, otherwise the uninstall script might fail.

In order for the uninstall to be successful, you need to use the uninstall script, that was provided whit the exact version that was installed on your database. The uninstall script provided with version 3.0.1 will probably not work, if you want to remove version 3.0.0 from your database.

Version upgrade

Currently, the only way to upgrade version of utPLSQL v3.0.0 and above is to remove the previous version and install new version

Working with utPLSQL v2

If you are using utPLSQL v2, you can still install utPLSQL v3. The only requirement is that utPLSQL v3 needs to be installed in different schema than utPLSQL v2.

utPLSQL v3 and utPLSQL v2 do not collide on public synonym names.

Last update: May 17, 2017 20:51:52
Created: October 23, 2016 20:53:00