Before you begin
Use the operating-system account that owns the OneView installation. Schedule a maintenance window before applying a repair and confirm current backups exist.
Generate a sanitized report
Run Installation report from the installed OneView operational tooling. The report is designed to include safe facts such as:
- installed version and host architecture;
- selected access mode and hostname;
- service health;
- whether required installation items are present and protected; and
- bounded warnings or failure codes.
Review the output before sharing it. Do not attach configuration contents, credentials, certificates' private material, setup or activation values, application keys, database details, or verification data.
Preview a repair
Use Repair installation → Dry run from the installed tooling. A dry run reports proposed corrections without changing the deployment.
Review:
- every item that would change;
- whether the affected item is generated and safe to repair;
- the available backup; and
- the expected service impact.
Do not continue when the report identifies missing secrets, an unknown installation identity, database loss, an unexpected version, or a software-update failure. Use the relevant recovery runbook instead.
Apply a reviewed repair
After approval, use Repair installation → Apply from the same installed tooling and record the safe outcome. Then:
- Generate a fresh sanitized report.
- Confirm the application opens at the approved HTTPS address.
- Confirm database and license status.
- Review activity logs.
- Run a safe synthetic verification when the repaired area could affect execution.
The repair workflow is not a database restore, software update, administrator reset, license change, network change, or secret-recovery tool.
If repair fails, stop and preserve the safe report. Do not run initial installation over the deployment or edit application data and generated settings to force a healthy result.