Bug 674806

Summary:	Satellite with embedded database: supported mechanisms to check and set correct database optimizer settings
Product:	Red Hat Satellite 5	Reporter:	Milan Zázrivec <mzazrivec>
Component:	Server	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED ERRATA	QA Contact:	Martin Minar <mminar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	540	CC:	cperry, mkoci, mminar, slukasik, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-web-1.2.7-16	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-17 02:43:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	677501, 677507

Description Milan Zázrivec 2011-02-03 12:29:24 UTC

Description of problem:
To prevent problems caused by customers using rule based database optimizer
(e.g. slow / stalled database queries), we need to implement several
mechanisms which will allow for checking and setting database optimizer
settings in a supported manner.

We need to implement the following:

* Installer (spacewalk-setup) will check for optimizer settings (if possible)
and warn in case it's set to rule based.

* Oracle database upgrades (not schema upgrades!) will restore cost based
optimizer if needed.

* db-control tool (spacewalk-dobby package available in embedded db variants)
will be able to check and set database optimizer settings.


Version-Release number of selected component (if applicable):
Satellite 5.4

How reproducible:
Always

Steps to Reproduce:
1. Check whether the Satellite contains the functionality described above.
  
Actual results:
The above functionality is not present in Satellite.

Expected results:
The above functionality is present in Satellite.

Additional info:
N/A

Comment 1 Milan Zázrivec 2011-04-14 09:45:00 UTC

New db-control commands: get-optimizer / set-optimizer

spacewalk.git master: 7fd21d78c151cb824228e4f744020e9d61b64291
satellite.git SATELLITE-5.4: d0f2abac66d9138d713398068e5a32589aa59862

Comment 2 Milan Zázrivec 2011-04-14 11:39:27 UTC

In the end, only the db-control get-optimizer / set-optimizer functionality
will be implemented as a part of this bug.

Comment 5 Šimon Lukašík 2011-06-01 09:07:00 UTC

Verified in stage with spacewalk-dobby-1.2.7-18.el5sat

Good:
 - The cost based modes are identified as supported
 - The rule based optimizer is identified as unsupported
 - The correction is advised
 - 'db-control set-optimizer' alters system to all_rows

Note:
 - A new option get-optimizer/set-optimizer is not described in the man
   page. However, the 'db-control help' shows a short description.

Comment 6 Clifford Perry 2011-06-17 02:43:23 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

https://rhn.redhat.com/errata/RHEA-2011-0875.html