The only default deployment procedure available in ACMP 4.0 is "Patch Oracle E-Business Suite". As you know this shutdowns the application processes before the patch and starts them after the patch.
We don't want to stop applications for code migrations, as simple as a SQL script or a custom report RDF migration.
Is the only way to create a new deployment procedure by making a copy of "Patch Oracle E-Business Suite" and deleting un wanted steps ?
Are there any other options ?
I am sure that ACMP also supports the hot patch mode. In this mode the environment will not go down. This mode I use by my own for all the not production environments.
But keep in mind that any environment in use may just lock an object and therefore your patch may fail. So our advise is it to log out any user when patching starts (at least).