VDB WAS SHUTDOWN ABORTED via SQLPLUS, how does this affect the VDB and GUI?

  • 0
  • 1
  • Problem
  • Updated 3 years ago
  • Solved

Our VDB was shutdown by a tester via sqlplus (oracle user). I did not know what was being done and it was taking a long time so another user issued a shutdown abort. We are starup mounting it but it is taking a long time. How does this affect the VDB since these were not performed via the GUI? In case our data got corrupted can we just stop the current VDB, and provision a new VDB using the snapshot a few minutes before it was shutdown? Thank you.

Photo of Mark


  • 160 Points 100 badge 2x thumb

Posted 3 years ago

  • 0
  • 1
Photo of Jaclyn Schoof

Jaclyn Schoof

  • 5,332 Points 5k badge 2x thumb
Official Response
Hi Mark,

Oracle will typically need to perform some recovery work after an instance failure or in this case a shutdown abort. How long this takes is dependent on what activity in terms of DML (insert,updates, deletes) were occurring at the time the instance was aborted.

Under normal circumstances, you would not need to provision a new VDB as the Oracle databases recovery mechanisms would resolve any inconsistencies in the data and any transactions that were in a live and uncommitted state at the time of the abort would be rolled back.

The Delphix Engine should detect the instance was shut down and adjust the status of this VDB accordingly moving it to an INACTIVE state. Upon restarting it whether this be through sqlplus or through the Delphix GUI the VDB Status should return to RUNNING.

(I saw that you also created a support case for the same issue and have posted the answer here for continuity)