Re: Module go-live

Posted by ErmanArslansOracleBlog on
URL: http://erman-arslan-s-oracle-forum.114.s1.nabble.com/Module-go-live-tp8391p8392.html

Good.. The changes cannot be rolled back once they are committed in the cutover phase.  So you need to take a backup before patching.

A cold backup could work, but there is a big downtime there..
An online backup could work, but it is also timeconsuming process .  
You can use flashback Database feature of Oracle Database in the database tier. This is fast

But in any case, you should think of estarting the application services from the relevant file system edition. So once you restore the database before the cutover phase, you may need to restart the application services from "the relevant file system edition" -- in case you fail after some time cutover switches the filesystems.

And yes, you can stop the apps services and shutdown your database before cutover.
I already recommend the same for using flashback restore point option.

For ex:
Stop the web services.
Stop the concurrent managers or put the schedule concurrent requests on hold.
Stop database-bound third-party applications or cut off their database connections.  
Force a log switch.
Create a guaranteed restore point.
Force another log switch

This subject is address in our book Practical Oracle E-Business Suite
"https://www.amazon.com/Practical-Oracle-Business-Suite-Implementation/dp/1484214234"
Section : "Backup Best Practices for EBS 12.2 Patching"