PLAN_TABLE_DATA
PLAN_TABLE_DATA stores plan information collected by EXPLAIN PLAN. Different from the PLAN_TABLE view, the system catalog PLAN_TABLE_DATA stores EXPLAIN PLAN information collected by all sessions and users.
| Name | Type | Description |
|---|---|---|
| session_id | text | Session that inserts the data. Its value consists of a worker thread start timestamp and a worker thread ID. Values are constrained by NOT NULL. |
| user_id | oid | ID of the user who inserts the data. Values are constrained by NOT NULL. |
| statement_id | varchar2(30) | Query tag specified by a user. |
| plan_id | bigint | Query ID The ID is automatically generated in the plan generation phase and is used by kernel engineers for debugging. |
| id | integer | Node ID in a plan |
| operation | varchar2(30) | Operation description. |
| options | varchar2(255) | Operation action. |
| object_name | name | Name of an operated object. It is defined by users. |
| object_type | varchar2(30) | Object type. |
| object_owner | name | Schema to which the object belongs. It is defined by users. |
| projection | varchar2(4000) | Returned column information. |
| cost | double precision | Execution cost estimated by the optimizer for an operator |
| cardinality | double precision | Number of rows estimated by the optimizer for an operator |
- PLAN_TABLE_DATA records data of all users and sessions on the current node. Only administrators can access all the data. Common users can view their own data in the PLAN_TABLE view.
- Data is automatically inserted into PLAN_TABLE_DATA after EXPLAIN PLAN is executed. Therefore, do not manually insert data into or update data in PLAN_TABLE_DATA. Otherwise, data in PLAN_TABLE_DATA may be disordered. To delete data, you are advised to use the PLAN_TABLE view.
- Information in the statement_id, object_name, object_owner, and projection columns is stored in letter cases specified by users and information in other columns is stored in uppercase.
