This week, the Oracle E-Business Suite on OCI team released the latest release 23.1.1 of E-Business Suite Cloud manager: “Getting Started with Oracle E-Business Suite on Oracle Cloud Infrastructure (Doc ID 2517025.1)”.
Let’s have a quick look at the new features.
New Compute and Database Shapes
Finally, E-Business Suite Cloud Manager is supporting the latest AMD E4.Flex and Intel E3.Flex shapes not only for running the application server or the database tier “on compute” but also with the PaaS service for the database. This is especially important in situations where no / not enough tech licenses for the Database EE are available.
While still with the database PaaS service it is not possible to flexibly scale up and down the available memory as those new shapes have way better performance/price ratio than the previous VM.Standard.2 shapes. Furthermore, typically there is a little bit more memory available which comes in handy especially for small dev/test environments.
For performance measurements on the relevant CPU cores, see the article Benchmarking CPUs for Oracle E-Business Suite (Database).
The new shapes are nicely integrated into the provisioning flow:
Hopefully, in the future it will be possible to change the memory assigned flexibly there as well – this is something the Database team will need to implement first though.
Furthermore, the new release allows to use VM.Standard3.Flex for Compute instances (Apps- or Database tier). However I still think that E4.Flex provides the better performance/price ratio, so that is not so important for me and my customers so far.
Beside those new shapes, with the new release the regions Madrid and Chicago can be used.
Finally, when running the database on Exadata Database Service Dedicated it is now possible to do cloning using snapshots.
Especially the new database service shapes come in very handy for some upcoming projects of ours. I’m looking forward to using those services and will blog again on some insights during that usage soon.
From a stability point of view the 23.1.1 release luckily so far caused no new regression issues. 🙂