Whilst working for a client with a large Oracle estate, supporting high transaction systems, we found that the in-built auto-extend feature, designed to increase the size of the tablespaces automatically was actually making Operational Capacity Management harder.
Given nothing but the size of the database it was difficult to apportion the amount of growth due to real business demand and how much was just auto-extend kicking in. This made it harder to accurately predict the amount of life left in the system, the critical question we were trying to answer in order to ensure service continuity.
In databases exhibiting high storage utilisation auto-extend was even more dangerous as there was a strong likelihood of it trying to claim a larger block of space than was needed or available and bringing down the system as a result.
The solution in this scenario? Just switch it off for highly utilised databases.
It makes me wonder what other foes might be lurking out there with friendly capacity management masks on…
About the author
Team Capacitas
FinOps and AI: Financial Discipline for Enterprise AI
Learn how FinOps extends to enterprise AI, connecting financial, technical and product decisions to manage spending and measure returns. blogs-(new)-post
Confidence Under Load: How We Verified AKS Readiness for Peak
How Capacitas verified AKS readiness for peak demand by validating workload performance, autoscaling, cluster capacity, monitoring, and incident response. blogs-(new)-post
Building Cloud Resilience: Lessons from the AWS Outage
Learning from the Latest Outage. Events like this week’s AWS disruption highlight one clear truth: resilience must be designed, not assumed. blogs-(new)-post
Bringing Order to Chaos: A Practical Guide to Chaos Testing in the Cloud
Build a structured approach to cloud chaos testing with the right tools, realistic failure scenarios, clear hypotheses and focused analysis of results. blogs-(new)-post