Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 911808

Summary:	Missing chapter on embedded database health
Product:	Red Hat Satellite 5	Reporter:	matthew patton <pattonme>
Component:	Docs User Guide	Assignee:	Dan Macpherson <dmacpher>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Dan Macpherson <dmacpher>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	540	CC:	cperry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-13 14:54:21 UTC	Type:	Bug
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:	924180

Description matthew patton 2013-02-16 03:05:08 UTC

Description of problem:

Absolutely no discussion of maintaining database health (esp. when using embedded Oracle). There is a passing reference to 'db-control' in the "Backup and Restore" chapter but no attention paid to regular use of 'db-control report' and 'db-control extend'. For any sufficiently large Satellite repository I'm sure it doesn't take too much to blow thru the allocated DBF files. I did just by loading one EPEL and two RPMFORGE repositories; about 12,000 packages.

Would recommend an Appendix which shows examples and maybe some sample CRON jobs that sysadmins (I'm sure many don't know the first thing about Oracle nor have to devine the zillion places Satellite stashes files) can use to keep abreast of the database and not suffer surprise outages and inexplicable failures.


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

5.4

How reproducible:

always

Steps to Reproduce:
1. n/a
  
Actual results:


Expected results:


Additional info:

Comment 1 Dan Macpherson 2013-09-11 13:40:39 UTC

Two points on this bug for Satellite 5.6:

1. This section has been included in the Monitoring chapter of the User Guide.
2. The embedded db for 5.6 is PostgreSQL. The "extend" command has been removed since it was Oracle-specific. Have documented the "reports" and "tablesizes" commands have been documented.

Rebrewing guide on our devel server

Comment 3 Clifford Perry 2013-10-13 14:54:21 UTC

https://access.redhat.com/site/documentation/en-US/Red_Hat_Satellite/5.6/html-single/User_Guide/index.html

5.1. Monitoring Tablespaces
Beginning with Satellite Server 5.6, the default database configuration is an embedded PostgreSQL database. PostgreSQL does not require that you manually allocate more space for the Satellite schema as it grows; PostgreSQL expands the schema of its own accord, provided that free disk space is available.
To check the database's size, run the db-control report command as the root user.
To check the size of each table in the database, run the db-control tablesizes command as the root user.