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: optimizer/spm_plan_control/SE/README.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,15 @@ Based on <a href="https://blogs.oracle.com/optimizer/using-sql-plan-management-t
4
4
5
5
The example_se.sql calls "proc_se.sql" (proc_se.sql is essentially the same as ../proc2.sql)
6
6
7
-
Scripts create utility procedure called "add_my_plan" (see proc_se.sql) that allows you to take a SQL execution plan from a test query and apply it to an application query.
7
+
Scripts create utility procedures called "set_my_plan" and "add_my_plan" (see proc_se.sql) that allows you to take a SQL execution plan from a test query and apply it to an application query.
8
8
9
-
Example output is shown in example_se.lst.
9
+
Example output is shown in example.lst.
10
10
11
11
Note that example_se.sql creates a new user called SPM_TESTU.
12
12
13
-
Scripts tested in Oracle Database 18c Standard Edition
13
+
See also example_outln.sql for an example of how to migrate a stored outline
14
14
15
-
There is an outstanding parsing issue with SE - see directory 27500184
15
+
Scripts tested in Oracle Database 18c Standard Edition
16
16
17
17
DISCLAIMER:
18
18
<br/>-- These scripts are provided for educational purposes only.
0 commit comments