You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/userguide/install.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ cd source
70
70
sqlplus sys/sys_pass@db as sysdba @install_headless.sql utp3 my_verySecret_password utp3_tablespace
71
71
```
72
72
73
-
The script needs to be executed by SYSDBA, in order to grant access to DBMS_LOCKsystem package.
73
+
The script needs to be executed by `SYSDBA`, in order to grant access to `DBMS_LOCK` and `DBMS_CRYPTO`system packages.
74
74
75
75
76
76
# Recommended Schema
@@ -88,7 +88,7 @@ If the installation and utPLSQL owner user is one and the same, the user must ha
88
88
- CREATE SYNONYM
89
89
- ALTER SESSION
90
90
91
-
In addition the user must be granted the execute privilege on `DBMS_LOCK`package.
91
+
In addition the user must be granted the execute privilege on `DBMS_LOCK`and `DBMS_CRYPTO` packages.
92
92
93
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.
94
94
The uninstall process will **not** drop profiler tables, as they can potentially be shared and reused for profiling PLSQL code.
0 commit comments