none
Disaster Recovery Test / Some Services doesn't start ( Error 2: The system cannot find the file specified) RRS feed

  • Frage

  • Hi

    we did an Disaster Recovery Test with an application server, and it brought some problems of course for us... :|

    After the full recovery with legato everything seems to be fine, except some services that can't be started. When trying to start them I get the error code (Error 2..) in the Subject above.

    I suspect something happened with the 8.3 file names during the recovery process, as I can 't open exe files, located under hklm\system\currentcontrolset\services\Oracle ClassicDomain_AdminServer. The variable 'ImagePath' holds "D:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin\beasvc.exe" as information, and I cannot open this path in Explorer?!

    I can start the service Oracle Process Manager though, and this one has "D:\Oracle\Middleware\fr11g\opmn\bin\opmn.exe -S -I D:\Oracle\Middleware\fr11ginstance" as value in variable 'ImagePath', without any 8.3 conversion in it!

    Any experience anybody with this?!

    cheers

    Dave

    Mittwoch, 25. Februar 2015 13:45

Antworten

Alle Antworten

  • > I suspect something happened with the 8.3 file names during the recovery
    > process, as I can 't open exe files, located under
    > hklm\system\currentcontrolset\services\Oracle ClassicDomain_AdminServer.
    > The variable 'ImagePath' holds
    > "D:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin\beasvc.exe" as information,
    > and I cannot open this path in Explorer?!
     
    Seems the restore process didn't create short names, since short name
    creation is disabled on servers by default. An installer, on the other
    hand, can create short names through API functions...
     
    PS: This is a german forum.
     

    Martin

    Mal ein GUTES Buch über GPOs lesen?

    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))
    Mittwoch, 25. Februar 2015 14:24
  • nur um das noch aufzuklären...

    Der Grund für die fehlenden 8.3 Namen war eine Option im Legato zur Sicherung von 8.3 Namen, welche auf disabled (system default) gesetzt war! :(

    Leider konnte ich keinen Weg finden, die 8.3 Namen nachträglch erzeugen zu lassen. Sprich wir werde einen neuen Recovery Prozess anstarten, mit einem neuen Backup des Original Servers.

    Freitag, 27. Februar 2015 06:49
  • > Leider konnte ich keinen Weg finden, die 8.3 Namen nachträglch erzeugen
    > zu lassen. Sprich wir werde einen neuen Recovery Prozess anstarten, mit
    > einem neuen Backup des Original Servers.
     
    Ja, das geht nicht - bei 8.3 wird ja bei identischem Namensanfang hinten
    eine fortlaufende Nummer angehängt, und die orientiert sich natürlich an
    der Reihenfolge der Erstellung.
     
    Aber ok, gelöst, gut :)
     

    Martin

    Mal ein GUTES Buch über GPOs lesen?

    NO THEY ARE NOT EVIL, if you know what you are doing: Good or bad GPOs?
    And if IT bothers me - coke bottle design refreshment :))
    Freitag, 27. Februar 2015 10:57