If SQL Statements use literal values for the WHERE clause conditions, there will be many versions of almost identical SQL stored in the library cache. For each different SQL statement, the optimizer must perform all the steps for processing a new SQL$.$ statement. This may also cause a library cache to fill up quickly because of all the different statements stored in it$.$

Identify on how can avoid this issue?

Select an option

Cursor sharing

Index clustering factor

Enabling automatic statistics enabling

None of the above