Introduction:
Migrating Oracle E-Business Suite from on-prem to OCI is often sold as a lift and shift and technically, a lot of it is. The application code, patching model, AD utilities, and concurrent manager architecture don’t change. But for the Apps DBA running the environment after go-live, a lot of daily muscle memory needs to be relearned. The tools are familiar; the terrain underneath them isn’t.
What Changes
- Infrastructure becomes something you provision, not request: On-prem, you filed a ticket for more disk or a new VLAN. On OCI, you provision compute shapes, VCNs, subnets, and Block Volumes yourself so basic networking and sizing knowledge is now part of the job.
- Storage is abstracted, and performance is now your call: Storage used to be tuned by a SAN admin behind the scenes. On OCI, you directly choose VPU performance tiers for redo logs, datafiles, and archive logs a decision that used to be invisible to the DBA.
- Backups move from tape/NAS to Object Storage: RMAN now typically targets OCI Object Storage instead of a media manager someone else configured. Retention and storage tier become cost levers you control directly.
- Patching is no longer tied to hardware maintenance windows: There’s no more waiting on SAN firmware updates or data center freezes. Patching cadence is now driven purely by RU cycles and your own discipline -more control, but also more responsibility to keep it on schedule.
- High availability options shift: Instead of RAC on physical clusters with an MPLS-linked DR site, you’re choosing between RAC on OCI, Data Guard across Availability Domains/Regions, or OCI Full Stack DR more automated, but it has to be designed and rehearsed, not just inherited.
- Monitoring becomes a two-world job. Enterprise Manager still covers the database/app layer, but it’s now paired with OCI-native monitoring (Monitoring, Logging, Alarms) for infrastructure health -knowing which to check first is its own skill.
- Cost becomes a daily variable, not a sunk annual cost:An oversized compute shape or an unnecessarily high storage tier now shows up on a monthly bill instead of disappearing into a one-time hardware purchase. Right-sizing becomes ongoing, not a one-time task.
Conclusion
EBS on OCI doesn’t shrink an Apps DBA’s scope it expands it. Responsibilities that used to belong to storage admins, network admins, and backup teams now sit with you, in exchange for far more direct control and fewer external dependencies. What stays the same is EBS itself adop, AD utilities, Workflow, concurrent managers. What changes is everything underneath it. DBAs who lean into that expanded scope tend to get a lot more out of the platform than those who try to treat OCI as just a new data center.
