Delphix Products

The original question read:  "Is there a plan to support move-to-asm as a part of V2P functionality in the engine? We believe this bring customer that ease of use in migrating data into Exadata."

From the wording of the original question, it appears that the partner asking the question is aware of, and has already reviewed, this page HERE in the Delphix online documentation, which describes the use of the "move-to-asm.sh" script, as well as a link to download this script template.

While this functionality is not currently built into the Delphix virtualization, embedding a call to this script into a Configure Clone hook of a VDB can make the provisioning of the "physical" database in ASM seamless and fully automated.

However, as noted in the documentation page referenced above, if this script is embedded into a Configure Clone hook for automation, then the Prerequisite and Postrequisite steps noted in the documentation should also be automated.  Delphix has not provided scripting for those steps, as several of these involve decisions which may be different from one place to another.

So, as noted by the questioner, move-to-asm.sh is generally called manually from outside the Delphix virtualization engine on the target database server after a VDB is provisioned to export the VDB to a physical database running Oracle ASM.  If the Prerequisite and Postrequisite steps can indeed be automated, then running move-to-asm.sh from a hook is perfectly feasible.

Please let me know what you think?

Thanks!

-Tim