Oracle9i Supplied PL/SQL Packages and Types Reference Release 2 (9.2) Part Number A96612-01 |
|
DBMS_OUTLN , 2 of 2
This procedure drops outlines that belong to a specified category.
DBMS_OUTLN.DROP_BY_CAT cat VARCHAR2);
Parameter | Description |
---|---|
cat |
Category of outlines to drop. |
This procedure purges a category of outlines in a single call.
This example drops all outlines in the DEFAULT
category:
DBMS_OUTLN.DROP_BY_CAT('DEFAULT');
This procedure drops an outline with an ol$.hintcount
value that does not match the number of hints for that outline in ol$hints.
DBMS_OUTLN.DROP_COLLISION;
A concurrency problem can occur if an outline is created or altered at the same time it is being imported. Because the outline must be imported according to its original design, if the concurrent operation changes the outline in mid-import, the outline will be dropped as unreliable based on the inconsistent metadata.
This procedure cleans up after an import by dropping extra hint tuples not accounted for by hintcount.
DBMS_OUTLN.DROP_EXTRAS;
The OL$-tuple of an outline will be rejected if an outline already exists in the target database, either with the same name or the same signature. Hint tuples will also be rejected, up to the number of hints in the already existing outline. Therefore, if the rejected outline has more hint tuples than the existing one, spurious tuples will be inserted into the OL$HINTS table. This procedure, executed automatically as a post table action, will remove the wrongly inserted hint tuples.
This procedure drops hint tuples that have no corresponding outline in the OLSable.
DBMS_OUTLN.DROP_UNREFD_HINTS;
This procedure will execute automatically as a post table action to remove hints with no corresponding entry in the OL$ table, a condition that can arise if an outline is dropped and imported concurrently.
This procedure drops outlines that have never been applied in the compilation of a SQL statement.
DBMS_OUTLN.DROP_UNUSED;
You can use DROP_UNUSED
for outlines generated by an application for one-time use only, created as a result of dynamic SQL statements. These outlines are never used and take up valuable disk space.
This procedure changes the category of all outlines in one category to a new category. If the SQL text in an outline already has an outline in the target category, it is not merged into the new category.
DBMS.OUTLN.UPDATE_BY_CAT ( oldcat VARCHAR2 DEFAULT 'DEFAULT', newcat VARCHAR2 DEFAULT 'DEFAULT');
Parameter | Description |
---|---|
oldcat |
Current category to be changed. |
newcat |
Target category to change outline to. |
Once satisfied with a set of outlines, you can move outlines from an experimental category to a production category. Likewise, you may want to merge a set of outlines from one category into another pre-existing category.
This example changes all outlines in the DEFAULT
category to the CAT1
category:
DBMS_OUTLN.UPDATE_BY_CAT('DEFAULT', 'CAT1');
This procedure generates a signature for the specified SQL text.
DBMS_OUTLN.GENERATE_SIGNATURE ( sqltxt IN VARCHAR2, signature OUT RAW);
Parameter | Description |
---|---|
sqltxt |
The specified SQL. |
signature |
The signature to be generated. |
|
Copyright © 2000, 2002 Oracle Corporation. All Rights Reserved. |
|