Automatic SQL Tuning in Oracle 10g

Automatic SQL Tuning in Oracle 10g. Dage Ville Benoit, Dinesh Das, Karl slides. Yagoub Khaled, Mohamed Zait, Mohamed Ziauddin. Oracle Corporation Oracle Database Tuning Guide ….

More PDF Content

Automatic SQL Tuning in Oracle 10g

  • 1. Introduction
  • 2. Automatic SQL Tuning Architecture
  • 3. SQL Profiling
  • 3.1 Statistics Analysis
  • 3.2 Estimates Analysis
  • 3.3 Parameter Settings Analysis
  • 3.4 SQL Profile
  • 4. Access Path Analysis
  • 5. SQL Structure Analysis
  • 6. Automatic SQL Tuning in the Oracle10g Self Managing Database
  • 6.1 Observe Phase
  • 6.2 Diagnose Phase
  • 6.3 Resolve Phase
  • 7. Experimental Results
  • 8. Related Work

In this paper, we have described the Automatic SQL Tuning feature introduced in Oracle10g. It is tightly integrated with the Oracle query optimizer, and is an integral part of the manageability framework for self-managing databases introduced in Oracle10g. The Automatic SQL Tuning is based on the Automatic Tuning Optimizer, the new generation Oracle query optimizer. The SQL Tuning Advisor tunes SQL statements and produces a set of comprehensive tuning recommendations including SQL Profiles. The user decides whether to accept the recommendations.

Download Automatic SQL Tuning in Oracle 10g pdf from, 12 pages, 262.19KB.
Related Books

3 Responses to “Automatic SQL Tuning in Oracle 10g”

  1. I have these errors inP6.2 When I tried start db coinfg:Bad public user name or password. Database Server Error: Named Pipes Provider: Could not open a connection to SQL Server [2]. ;And the same time inSQL Server Configuration Manager: the request failed or service not respond in a timely fashion event log.-2010-07-30 11:19:20.28 Server Microsoft SQL Server 2005 9.00.3080.00 (Intel X86)Sep 6 2009 01:43:32Copyright (c) 1988-2005 Microsoft CorporationExpress Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 3)2010-07-30 11:19:20.28 Server (c) 2005 Microsoft Corporation.2010-07-30 11:19:20.28 Server All rights reserved.2010-07-30 11:19:20.28 Server Server process ID is 3324.2010-07-30 11:19:20.28 Server Authentication mode is MIXED.2010-07-30 11:19:20.28 Server Logging SQL Server messages in file C:\Program Files\MSSQL\Primavera\MSSQL.1\MSSQL\LOG\ERRORLOG’.2010-07-30 11:19:20.30 Server This instance of SQL Server last reported using a process ID of 1044 at 30/07/2010 11:14:01 a.m. (local) 30/07/2010 04:14:01 p.m. (UTC). This is an informational message only; no user action is required.2010-07-30 11:19:20.30 Server Registry startup parameters:2010-07-30 11:19:20.30 Server -d C:\Program Files\MSSQL\Primavera\MSSQL.1\MSSQL\DATA\master.mdf2010-07-30 11:19:20.30 Server -e C:\Program Files\MSSQL\Primavera\MSSQL.1\MSSQL\LOG\ERRORLOG2010-07-30 11:19:20.30 Server -l C:\Program Files\MSSQL\Primavera\MSSQL.1\MSSQL\DATA\mastlog.ldf2010-07-30 11:19:20.30 Server Error: 17113, Severity: 16, State: 1.2010-07-30 11:19:20.30 Server Error 2(error not found) occurred while opening file C:\Program Files\MSSQL\Primavera\MSSQL.1\MSSQL\DATA\master.mdf’ to obtain coinfguration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.

Leave a Reply