How do I refresh my upgrade site?
Environment:
Oracle B2C Service
Resolution:
Refreshing the upgrade site is rarely necessary and should never be part of "the plan". The existing upgrade site is destroyed and a new production clone is created if a refresh is deemed necessary. Small development projects which include modifying PHP are automatically handled by File Sync. Production database changes are automatically retained. Here are a few corner case examples of where a refresh is appropriate. Example one, part of your business is unaware that an update is underway so they update the production Customer Portal Framework version. Example two, part of your business is unaware that an update is underway so they release a new Add-In in production. Example three, you find a showstopper defect while testing the new version. Oracle delivers a patch several weeks later and your business is ready to restart update testing.
How can I refresh an upgrade site?
- Use the "Manage My Update" feature in the Configuration Assistant. The "Refresh Upgrade Site" button will be displayed for all eligible sites under the Update Information page.
Requirements for upgrade site refresh:
- Initial upgrade site creation has completed; cutover has not occurred.
- The cutover date must be 8+ days into the future. You should delay cutover if a refresh is deemed necessary and cutover is approaching.
Conditions:
- Cutover will automatically be rescheduled if the refresh does not complete in time for cutover.
- It is not possible to determine exactly how long a refresh will take. Generally it is approximately the same duration required to build the original upgrade site.
Notes:
- File sync function might be sufficient to copy your changes on the production site. Refer File Sync for Oracle B2C Service Update.
- Details of changes carried forward at cutover can be found in Changes carried forward at update cutover.
- Upgrade site refresh can take days depending on the database size and the server load.
