Postagens

Oracle Essbase 21c Production Readiness Assessment: What I Check Before an Environment Goes Live

Imagem
It Runs. But Is It Ready for Production? Every Essbase assessment I have performed starts with the same uncomfortable question, and it is rarely the question the client expects. They usually want to know why a calculation is slow, or why a Managed Server occasionally throws a memory warning. What they are really asking, without knowing it, is a bigger question: is this environment actually ready to carry production weight, or has it just been running long enough that nobody has stopped to check? Those are not the same thing. An Essbase Managed Server can start cleanly, applications can come online, Smart View can connect, and a calculation script can execute without error, and none of that proves the environment is production-ready. It proves the environment is currently functional under whatever conditions exist at that exact moment. Production readiness is a different claim. It means the environment has been observed under representative load, the configuration has been validated r...
Postar um comentário
Leia mais

Oracle Essbase Performance Tuning: Why More CPU and Memory Are Not Always the Answer

Imagem
  Introduction One of the most common reactions when Essbase becomes slow is also one of the easiest: Add more CPU. If that does not work: Add more memory. I have never liked starting an Essbase performance investigation that way. Before changing resources or tuning parameters, I want to know what the environment is doing while the problem is actually happening . Is CPU really saturated? Is Essbase waiting for storage? Are the caches undersized? Is Windows paging? Is a virtual machine competing for physical CPU? Is the JVM spending too much time in garbage collection? Is network latency affecting Smart View or communication between EPM components? Or is the infrastructure perfectly healthy and the real problem is inside the application or calculation design? Those situations can look very similar to the user: “Essbase is slow.” But they require completely different solutions. That is why my starting point for Essbase tuning is simple: Measure first. Tune secon...
Postar um comentário
Leia mais

When OCI Is Green but the Application Is Down

Imagem
Introduction A production incident does not always begin with alarms, failed Compute instances, or a dashboard full of red indicators. Sometimes, the situation is much more confusing. The Compute instances are running. The Load Balancer is available. CPU and memory look normal. Storage has capacity. The database is online. Network resources appear healthy. OCI Monitoring shows no obvious infrastructure failure. Everything is green. But users cannot access the application. This is one of the most challenging situations in production operations because the infrastructure and the user appear to be telling us two completely different stories. The infrastructure says: Healthy. The user says: The application is down. That exposes an important distinction: Infrastructure Health ≠ Service Health A healthy Compute instance does not guarantee a healthy application. An available database does not guarantee that the application can connect to it. A functioning VCN does not guarantee that every req...
Postar um comentário
Leia mais