5af33fc217
Critical fix for service auto-start behavior: Problem (identified by user): - When Oracle service starts, it automatically tries to start instance - Uses configured PFILE which references control files - After cleanup, control files don't exist - Instance ends up in partial/error state - STARTUP NOMOUNT may fail or behave unexpectedly Root Cause: - Oracle service on Windows has auto-start behavior - Service startup takes ~30s trying to start instance - Without valid control files, instance is partially started - This interferes with manual STARTUP NOMOUNT Solution: Before STARTUP NOMOUNT, explicitly clean any existing instance: ```sql SHUTDOWN ABORT; -- Clean any partial instance STARTUP NOMOUNT PFILE='...'; -- Fresh clean start ``` Implementation: - Use WHENEVER SQLERROR CONTINUE (SHUTDOWN may error if no instance) - Explicit SHUTDOWN ABORT before NOMOUNT - Ensures clean instance state for RMAN restore - Service running + clean NOMOUNT instance = ready for restore User requirement met: Instance in NOMOUNT state (not mounted/open) Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>