Bug 674800

Summary:	Upgrade documentation: mention requirement to check database optimizer settings before schema upgrade
Product:	Red Hat Satellite 5	Reporter:	Milan Zázrivec <mzazrivec>
Component:	Upgrades	Assignee:	Milan Zázrivec <mzazrivec>
Status:	CLOSED ERRATA	QA Contact:	Martin Minar <mminar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	540	CC:	agouny, cperry, mhuth, mkoci, mminar, slukasik, xdmoon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhn-upgrade-5.4.0.23-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-06-16 17:30:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	677507

Description Milan Zázrivec 2011-02-03 12:18:57 UTC

Description of problem:
Satellite upgrade documentation needs to explicitly mention requirement
to check Oracle database optimizer settings before commencing with schema
upgrade.

This is to make sure the database uses supported & tested optimizer and to
avoid stalled schema upgrades caused by the database being set to use
unsupported (rule based) optimizer.

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

How reproducible:
Always

Steps to Reproduce:
1. Read the upgrade documentation (rhn-upgrade package).
  
Actual results:
The upgrade documentation does not say one needs to check database optimizer
settings before proceeding with schema upgrade.

Expected results:
The upgrade documentation says one needs to check database optimizer
settings before proceeding with schema upgrade.

Additional info:
N/A

Comment 2 Mark Huth 2011-03-16 00:11:01 UTC

The query optimizer issue affected one of our GPS guys while he was onsite doing an upgrade to 5.4 for a customer.  They let the schema upgrade run for 24 hours and in the end they had to kill it, restore the db from backup, set the correct optimizer and restart the schema-upgrade.  Having information in the documentation about the need to change the optimizer would have saved them a day of waiting.  So here's hoping this information can make it into the satellite documentation as soon as possible.

-- Mark

Comment 3 Aurelien Gouny 2011-03-16 00:32:34 UTC

Indeed Mark thanks we now completed the schema-upgrade in 26mins instead of >24h.
Looking forward to have this sort of info included in the upgrade documentation.

Cheers,
Aurelien.

Comment 4 Milan Zázrivec 2011-04-14 09:54:40 UTC

Instructions to check / set database optimizer settings were added to
satellite-upgrade.txt and satellite-and-os-upgrade.txt (schema upgrade part).

satellite.git SATELLITE-5.4: 8049b4ff341618ce4d445e1701b3f82ad367e970

Comment 7 Šimon Lukašík 2011-05-31 11:03:42 UTC

Verified in stage with rhn-upgrade-5.4.0.25-1

Comment 8 Clifford Perry 2011-06-16 17:30:37 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.

http://rhn.redhat.com/errata/RHEA-2011-0876.html