Understanding Change Migration Procedures

Monthly Update Migration flow is as follows:

• Tested and approved monthly update from Oracle Development to customer test environments

  If no regression is found, Oracle updates all production environments. Subsequently, customers may migrate applications from test to production.

  If Oracle development confirms a customer reported issue as a regression, Oracle applies a one-off patch to test environment.

• One-off patch
  • Oracle Development confirms a customer reported issue as a regression.
  • Oracle Development creates a one-off patch and sends it to Quality Engineering for testing.
  • After testing the one-off patch, Quality Engineering certifies it by signing off.
  • One-off patch is applied to test environments.
  • One-off patch is applied to production environment after the customer approves the fix. Environments are brought back to the main code line patch once the regression is fixed in a monthly patch.
• Skip automatic update

  A customer, citing a justification for the request, may seek to skip automatic updates of a production environment. See Requesting to Skip Automatic Updates for Environments for details.

• Emergency patch

  Deployment of emergency patches requires the approval of a Vice President in Oracle Enterprise Performance Management Cloud Development.

  • Oracle Development confirms a customer reported issue as a regression or blocker issue.
  • Oracle Development creates an emergency patch and sends it to Quality Engineering for testing.
  • After testing the patch, Quality Engineering certifies it by signing off.
  • The emergency patch is applied to test environment, production environment, or both as appropriate.