This card is a step in the planned number of rows processed. cost refers to the cbo in the resources spent on this step, this value is a relative value. This step refers to the cbo bytes to process all records of the number of bytes, is estimated from a set of values. http://blog.itpub.net/post/385/45197
■ Cost The cost assigned to each step of the query plan by the CBO. The CBO works by
generating many different execution paths / plans for the same query and assigns a cost to
each and every one. The query plan with the lowest cost wins. In the full outer join example,
we can see the total cost for this query is 10.
■ Card Card is short for Cardinality. It is the estimated number of rows that will flow out
of a given query plan step. In the full outer join example, we can see the optimizer expects
there to be 327 rows in EMP and 4 rows in DEPT.
■ Bytes The size in bytes of the data the CBO expects each step of the plan to return.
This is dependent on the number of rows (Card) and the estimated width of the rows.
This card is a step in the planned number of rows processed.
cost refers to the cbo in the resources spent on this step, this value is a relative value.
This step refers to the cbo bytes to process all records of the number of bytes, is estimated from a set of values.
In PL / SQL see the SQL statement execution plan
Many tools can be seen by the general PL / SQL statement execution plan to analyze the performance.
Here through PL / SQL view sql execution plan in several ways:
Method one. Set AutoTrace on;
Then when you execute the sql statement when the execution plan is displayed automatically.
Do not want to see the implementation of planned, set autoTrace off;
Method Two. Execute statement: explain plan for [your sql statement]
For example: explain plan for select * from table1
Then do: select * from table (DBMS_XPLAN.DISPLAY) can see it's implementation plan.
Method three: similar to method two, the former a sql unchanged, the second sentence should read the following sql can also display the execution plan (the same principle):
select plan_table_output from table (dbms_xplan.display ('plan_table', null, 'serial'));
Followed by the two methods is the display table function dbms_xplan bag to get the latest implementation plan.
Also in sql * plus in sql view with set timing on execution time.