Session ID: 11181

Abstract: One of the challenges of Oracle Cloud implementations is environment/pod usage and the impact on data conversion activities. The implementation schedule must account for the advance notice that Oracle requires to create a new environment, as well as the monthly Oracle patching / maintenance schedule that can affect data conversion activities. This session will focus on how pod usage and implementation scheduling can minimize the risk in your implementation.

Objective 1: Discuss Oracle requirements for creation of a new environment/pod

Objective 2: Outline options for "backing out" data that has been loaded to the Cloud

Objective 3: Highlight the impact of Oracle's monthly patching/maintenance from one test cycle to the next

Objective 4: Provide recommendations on minimizing risk related to pod usage

Audience: Technical