|
1 | 1 | # Downloading latest version of utPLSQL |
2 | 2 |
|
3 | | -It is quite easy to download latest version of utPLSQL from github on both Unix/Linux as well as Windows machines. |
4 | | -Below are little snippets that can be handy for downloading latest version. |
| 3 | +To download latest version of utPLSQL from github on both Unix/Linux as well as Windows machines use the below smippets. |
5 | 4 |
|
6 | 5 | ## Unix/Linux |
7 | 6 |
|
@@ -52,42 +51,51 @@ foreach ($i in $urlList) { |
52 | 51 |
|
53 | 52 | # Headless installation |
54 | 53 |
|
55 | | -To simply install the utPLSQL into a new database schema and grant it to public, execute the script `install_headless.sql` as SYSDBA. |
| 54 | +To install the utPLSQL into a new database schema and grant it to public, execute the script `install_headless.sql` as SYSDBA. |
56 | 55 |
|
57 | | -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. |
| 56 | +The script accepts three optional parameters that define: |
| 57 | +- username to create as owner of utPLSQL (default `ut3`) |
| 58 | +- password for owner of utPLSQL (default `XNtxj8eEgA6X6b6f`) |
| 59 | +- tablespace to use for storage of profiler data (default `users`) |
58 | 60 |
|
59 | 61 | Example invocation of the script from command line: |
60 | 62 | ```bash |
61 | 63 | cd source |
62 | 64 | sqlplus sys/sys_pass@db as sysdba @@install_headless.sql |
63 | 65 | ``` |
64 | 66 |
|
65 | | -SYSDBA is needed to grant access to DBMS_LOCK. |
| 67 | +Invoking script with parameters: |
| 68 | +```bash |
| 69 | +cd source |
| 70 | +sqlplus sys/sys_pass@db as sysdba @@install_headless.sql utp3 my_verySecret_password utp3_tablespace |
| 71 | +``` |
| 72 | + |
| 73 | +The script needs to be executed by SYSDBA, in order to grant access to DBMS_LOCK system package. |
66 | 74 |
|
67 | 75 |
|
68 | 76 | # Recommended Schema |
69 | | -It is recommended to install utPLSQL in it's own schema. You are free to choose any name for this schema. |
| 77 | +It is highly recommended to install utPLSQL in it's own schema. You are free to choose any name for this schema. |
| 78 | +Installing uPLSQL into shared schema is really not recommended as you loose isolation of framework. |
70 | 79 |
|
71 | | -The installation user/schema must have the following Oracle system permissions during the installation. |
| 80 | +If the installation and utPLSQL owner user is one and the same, the user must have the following Oracle system permissions before you can proceed with the installation. |
72 | 81 |
|
73 | 82 | - CREATE SESSION |
74 | 83 | - CREATE PROCEDURE |
75 | 84 | - CREATE TYPE |
76 | 85 | - CREATE TABLE |
| 86 | + - CREATE SEQUENCE |
77 | 87 | - CREATE VIEW |
78 | 88 | - CREATE SYNONYM |
79 | 89 | - ALTER SESSION |
80 | 90 |
|
81 | | -In addition it must be granted execute to the following system packages. |
82 | | - |
83 | | - - DBMS_LOCK |
| 91 | +In addition the user must be granted the execute privilege on `DBMS_LOCK` package. |
84 | 92 |
|
85 | 93 | utPLSQL is using [DBMS_PROFILER tables](https://docs.oracle.com/cd/E18283_01/appdev.112/e16760/d_profil.htm#i999476) for code coverage. The tables required by DBMS_PROFILER will be created in the installation schema unless they already exist. |
86 | 94 | The uninstall process will **not** drop profiler tables, as they can potentially be shared and reused for profiling PLSQL code. |
87 | 95 |
|
88 | 96 | It is up to DBA to maintain the storage of the profiler tables. |
89 | | - |
90 | | -# Installation Procedure |
| 97 | + |
| 98 | +# Manual installation procedure |
91 | 99 |
|
92 | 100 | ### Creating schema for utPLSQL |
93 | 101 | To create the utPLSQL schema and grant all the needed privileges execute script `create_utplsql_owner.sql` from the `source` directory with parameters: |
|
0 commit comments