Database Reference
In-Depth Information
--------------------------------------------
| Id | Operation | Name |
--------------------------------------------
| 0 | SELECT STATEMENT | |
| 1 | TABLE ACCESS BY INDEX ROWID| T |
| 2 | INDEX FULL SCAN | T_PK |
--------------------------------------------
Note
-----
-
SQL profile "import_sql_profile" used for this statement
For a cursor stored in the library cache, the
sql_profile
column of the
v$sql
view shows the name of the SQL
profile that was used during the generation of that cursor's execution plan. The column is set to
NULL
when no SQL
profile was used.
Moving SQL Profiles
The
dbms_sqltune
package provides several procedures to move SQL profiles between databases. As shown in
Figure
11-7
, the following features are provided:
create_stgtab_sqlprof
procedure.
•
You can create a staging table through the
•
You can copy a SQL profile from the data dictionary to the staging table through the
pack_stgtab_sqlprof
procedure.
•
You can change the name and the category of a SQL profile stored in the staging table
through the
remap_stgtab_sqlprof
procedure.
•
You can copy a SQL profile from the staging table into the data dictionary through the
unpack_stgtab_sqlprof
procedure.
Figure 11-7.
Moving SQL profiles with the
dbms_sqltune
package
