+++ This bug was initially created as a clone of Bug #467512 +++
# su - oracle
backup - Backup the RHN Oracle Instance
examine - Display information about an RHN Oracle Instance backup
extend - Increase the RHN Oracle Instance tablespace
gather-stats - Gather statistics on RHN Oracle database objects
help - Display command summary
report - Show database space report
report-stats - Show tables with stale or empty statistics
restore - Restore the RHN Oracle Instance from backup
shrink-segments - Shrink RHN Oracle database segments
start - Start the RHN Oracle Instance
status - Show database status
stop - Stop the RHN Oracle Instance
tablesizes - Show space report for each table
verify - Verify an RHN Oracle Instance backup
So the db-control has 14 possible commands. The man page lists 14 options in the OPTIONS section.
However, the SYNOPSIS section only shows 13, with tablesizes missing.
Fixed in Spacewalk master, de26a40ec4086b3e5cddb463ac60eaec7e0b3f22. Commit 7971549590d162a98e3de3e9ac54008edc5209bf is also kinda related.
Cherry picked to SATELLITE-5.4 as
Fixing POD formatting.
Hey! The above document had some coding errors, which are explained below:
Around line 129:
You forgot a ’=back’ before ’=head1’
(cherry picked from commit 7971549590d162a98e3de3e9ac54008edc5209bf)
517455 - adding tablesizes to SYNOPSIS section of db-control man page.
(cherry picked from commit de26a40ec4086b3e5cddb463ac60eaec7e0b3f22)
verified on all platforms
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, the synopsis of the manual page for the db-control utility did not include the description of the "tablesizes" command. With this update, this description has been added, and the synopsis now covers all available commands.
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.