Skip to content

Force hard parse with flashback? #3

@jonheller1

Description

@jonheller1

Instead of using using sys.dbms_shared_pool.purge, which requires extra privileges, would it be easier to always use a flashback query to force hard parsing? Similar to the solution used here: https://stewashton.wordpress.com/2021/11/09/sql-table-macros-5-dynamic-but-dangerous/

The downside is that flashback also requires:
EXECUTE on DBMS_FLASHBACK
FLASHBACK on all the tables accessed by the query.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions