nerdexam
Oracle

1Z0-064 · Question #19

You execute this query twice in a session: Then you query V$SQL_SHARED_CURSOR for details about child cursors as shown. Which two statements are true? (Choose two.)

The correct answer is B. A subsequent execution of the query in this session is likely to undergo a soft parse. C. The second execution of the query was hard parsed because the estimated cardinality was. See the full explanation below for the reasoning.

Question

You execute this query twice in a session:

Then you query V$SQL_SHARED_CURSOR for details about child cursors as shown. Which two statements are true? (Choose two.)

Exhibits

1Z0-064 question #19 exhibit 1
1Z0-064 question #19 exhibit 2

Options

  • ANo statistics were collected during the first execution of the query.
  • BA subsequent execution of the query in this session is likely to undergo a soft parse.
  • CThe second execution of the query was hard parsed because the estimated cardinality was
  • DA subsequent execution of the query in this session will undergo a hard parse.
  • EThe second execution of the query was hard parsed because extended statistics were collected

How the community answered

(24 responses)
  • A
    4% (1)
  • B
    83% (20)
  • D
    8% (2)
  • E
    4% (1)

Community Discussion

3
Ola B.Ola B.Mar 27, 2026

The answers are B and C. After the first execution Oracle gathered stats and found the cardinality estimate was off, so it created a new child cursor by hard parsing the second run, which is exactly what BIND_EQUIV_FAILURE or a stats change triggers in V$SQL_SHARED_CURSOR. From that point forward the session has a valid cursor in the shared pool, so any subsequent run will find it and soft parse right through.

16
Hiroshi T.Hiroshi T.Apr 13, 2026

I initially marked A and D because I assumed no re-parse would happen after the first execution, but the Oracle 12c documentation on adaptive cursor sharing and dynamic statistics (see the Database SQL Tuning Guide, chapter on cursor sharing) makes clear that the first execution can trigger statistics collection that changes the cardinality estimate, forcing a hard parse on the second execution, which is exactly what C describes. Once that second child cursor exists with accurate stats, the library cache lookup on any further execution succeeds and a soft parse follows, which is B.

1
Prof. SaraProf. SaraApr 1, 2026

What column in that view flagged the cardinality mismatch on execution two?

0
Full 1Z0-064 Practice