e4df4c11d8
Critical fix for service preservation: Problem: - After cleanup, Oracle service is stopped - Start-Service attempts to start the instance automatically - Without database files, service startup hangs indefinitely - PowerShell Start-Service blocks waiting for service to start Root Cause: - Oracle service on Windows tries to auto-start the instance - With no controlfile/database files, it cannot start - Start-Service waits forever (user reported 25+ warnings) Solution: - Do NOT attempt to start the stopped service - SQL*Plus can connect '/ as sysdba' even if service is stopped - STARTUP NOMOUNT will manually start the instance - This is the correct Oracle workflow for restore from zero Windows SQL*Plus requirements: ✓ ORACLE_SID set (we set this) ✓ Service exists in registry (preserved after cleanup) ✓ ORACLE_HOME set (we set this) ✗ Service running NOT required for NOMOUNT startup The service will naturally transition to Running state when STARTUP NOMOUNT successfully starts the instance. Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>