Skip to main content

Forcing Execution Plans Through Profiles

  • Chapter
Oracle SQL Tuning with Oracle SQLTXPLAIN
  • 745 Accesses

Abstract

Sometimes it’s best to fix a problem and figure out afterward what went wrong and determine the root cause. By this I mean that when there are production time pressures to get something done, any way that works is good enough. The idea is to get the business back up and running, then sit at your leisure and work out what went wrong, figure out how to stop it from happening again, and develop a plan to implement the permanent fix in a controlled manner during a planned outage if required. Management is not usually very tolerant of perfectionists who want to understand every detail of a problem and its solution before acting: and if they are tolerant, it’s because they have another system in their pocket that’s keeping the lights on and the business going.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2013 Stelios Charalambides

About this chapter

Cite this chapter

Charalambides, S. (2013). Forcing Execution Plans Through Profiles. In: Oracle SQL Tuning with Oracle SQLTXPLAIN. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4810-1_6

Download citation

Publish with us

Policies and ethics