参考MOS文档：Reasons for a SELECT to have a PLAN_HASH_VALUE of Zero (文档 ID 1587381.1)
The V$SQL view externalises various information about SQL statements that are being stored in the shared pool to users and one of these is the PLAN_HASH_VALUE which is a reference to the access path that has been generated for the a query. This is usually a large number but sometimes it is zero. When you are looking at a DELETE or an INSERT without a query, then a zero PLAN_HASH_VALUE is quite normal as there is no plan. In these cases no access path has been calculated and none is needed.
However it is possible to sometimes see a SELECT with a zero PLAN_HASH_VALUE which is less easy to explain.
The main reason for this is key to this is that the query uses bind variables and the cursor has been parsed BUT the generation of an execution plan has been deferred until execution time since that is when the bind values will be supplied (which may have a significant bearing on the access path generated). Until the query is 'bound' and executed, there is no plan and so the PLAN_HASH_VALUE will be zero.