Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Tuning (MOSC)

NO_CPU_COSTING hint - when not to use it

May 17, 2012 3:30AM edited Jun 5, 2012 8:51AM in Database Tuning (MOSC) 8 comments

Some of our larger queries have benefited by using the NO_CPU_COSTING hint.

Would you consider to change database optimizer default to no_cpu_costing which may help overall reporting performance?

When should we not use this hint?

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month