For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
I'm looking for the way to testing my application to see if there is any nagative impact due to patching before patch is applied with ATP-S(Serverless) instance.
In my understanding, ATP-D(Dedicated) allows us to controll software version,schedule and which CDB the patch to be applied.
Does anyone have good idea?
Comment
As of today, you pick a patching schedule for the entire Autonomous Exadata Infrastructure (AEI) and not at a container (CDB) level. In the next few weeks you will be able to patch at a CDB level in dedicated. A good way to test impact of patching is to do a CDB restart while your workload runs in dedicated. If you have planned your OCPU capacity well then you should see no visible impact of a CDB restart or similarly, a patching operation.
A way to test this in serverless is to simulate your workload in a test environment and actually see it go through a patching cycle. Since you do not have control of the underlying CDBs, I don't see another way you can test the impact.
Kris
Be the first to rate this
|
Sign in to rate this
Thank you for your response, anyway.
Be the first to rate this
|
Sign in to rate this