The move-to-asm.sh script procedure, documented here, provides the ability to move virtual Oracle non-multitenant databases to ASM. This procedure does not support Oracle multitenant databases.
The Oracle V2ASM CLI export features that shipped in Continuous Data 18.104.22.168 and 22.214.171.124 and later now cover the functionality of move-to-asm.sh in its entirety and additionally support Oracle multitenant databases. The legacy script is now less feature-rich and unnecessary.
The following note was previously added to the Continuous Data deprecated features list at 126.96.36.199 GA (March 2023):
Oracle move-to-asm.sh scripted procedure has been deprecated in favor of the new feature ”Export an Oracle virtual DB or virtual PDB to a physical Oracle ASM or Exadata database”. For more details on this new feature, refer to the Export an Oracle VDB or vPDB to a Physical ASM or Exadata Database section. The move-to-asm.sh scripted procedure is still supported in 188.8.131.52, but is discouraged by Delphix and will be eventually removed in future versions of the Delphix Continuous Data Engine.
In addition, we have also added the following Deprecation Notice in https://cd.delphix.com/docs/latest/move-an-oracle-vdb-to-a-physical-asm-or-exadata-da:
Frequently Asked Questions
When did Delphix deprecate the move-to-asm.sh?
The move-to-asm.sh script was deprecated with Continuous Data engine version 184.108.40.206 (GA: March 2023), therefore only critical bug-fixes will be provided by Delphix until Continuous Data engine version 220.127.116.11 (with an expected GA of April 2024, though this could change).
When will the script reach end-of-life?
The move-to-asm.sh script will reach end-of-life and will no longer be available in Continuous Data engine 18.104.22.168 and later versions.
Can I continue to use the move-to-asm.sh script?
You will be able to stay on Continuous Data version 22.214.171.124, if you need to use the move-to-asm.sh deprecated script. But, you are strongly encouraged to use the more feature-rich and supported export CLI feature, documented in the following locations:
Export an Oracle VDB or a vPDB to a physical ASM or Exadata database
Export an Oracle non-multitenant or a PDB snapshot to a physical ASM or Exadata database