Running Oracle Database?

Oracle Database slow or too expensive to keep? We clear the backlog.

A twenty-year-old schema is still at the heart of the business, the license renewal came in higher than the server it runs on, and the one person who remembers how the materialized views were built retired last spring. We stabilize the database, document it, and work through whether it stays, gets tuned, or moves to Postgres on a timeline you can actually meet.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

oracle-alert.log

still failing

What it is

Oracle Database at a glance

Oracle Database is the enterprise relational database that has sat under finance, telecom, utilities and government systems for more than forty years. It runs on Linux, Windows and Oracle's own engineered systems such as Exadata, and the editions range from the free Express Edition through Standard Edition 2 to Enterprise Edition with a long list of paid options. Core capabilities include PL/SQL, partitioning, materialized views, advanced analytics, Real Application Clusters for shared-everything high availability, and Data Guard for replication.

The license model is where Oracle differs most from the rest of the database world. Options such as Partitioning, Advanced Security, Diagnostics Pack and Tuning Pack are priced separately, and features that are visible in the product may not be licensed on your contract. Teams routinely find out during an audit that work they did years ago used an unlicensed option. The database itself is reliable and powerful, which is why migrations to Postgres or to Oracle Autonomous Database in OCI are planned events rather than casual ones.

Type
Enterprise relational database
First released
1979
License
Proprietary, per-core and named-user pricing
Maintained by
Oracle Corporation
Typically used for
ERP, banking and finance, telecom, government and utility systems, large OLTP and reporting workloads

The honest version

Oracle Database pros and cons

No technology is all upside. This is where Oracle Database earns its place and where it tends to cause trouble.

Where Oracle Database is strong

  • Mature and extremely capablePartitioning, parallel query, materialized views, bitmap indexes and PL/SQL cover workloads that would need several products in other ecosystems.
  • Real Application Clusters for availabilityRAC gives active-active shared-storage high availability, which is still unusual in the database world and is a reason some workloads cannot leave.
  • Data Guard for replicationPhysical and logical standby configurations give proven disaster recovery, with role transition that actually works when it has been practiced.
  • Deep tuning tools in the boxAWR, ASH, SQL Tuning Advisor and the various tuning packs give performance information that is hard to match on any other platform, when they are licensed.
  • PL/SQL is a proper languageServer-side logic in PL/SQL is strongly typed, debuggable and performant. Many business rules have lived there for decades for good reason.
  • The ecosystem knows how to support itHiring DBAs, buying tooling and finding consultants who have worked on Oracle is straightforward in a way it is not for every database.

Where Oracle Database bites

  • Licensing is the real cost centerPer-core pricing on Enterprise Edition plus paid options plus audits that look for incidental use mean the invoice often dwarfs the hardware. Teams who did not plan for this are routinely surprised.
  • Audits are a serious eventOracle's License Management Services does audit, and features that were enabled by accident count. Preparing for an audit is an engineering project, not a paperwork task.
  • Upgrades require rehearsalMajor release upgrades involve compatibility settings, optimizer changes and deprecated features, and they need a tested path. Rushing an upgrade will usually break at least one report.
  • Hiring is getting harderNew developers learn Postgres, MySQL or SQL Server first. Finding engineers with real PL/SQL and Oracle internals experience is slower every year.
  • Cloud strategy is tilted toward OCIRunning Oracle on AWS or Azure is possible but the better integrations, pricing and features arrive first on Oracle Cloud Infrastructure, which affects multi-cloud plans.
  • Migrations off are large projectsPL/SQL stored procedures, Oracle-specific SQL extensions, sequences, triggers and partitioning all need to be translated. Moving to Postgres is possible and common, but it is not quick.

Sound familiar?

Common Oracle Database problems we fix

The Oracle Database problems that bring people to us, and what you have once each one is fixed.

ORA-01555: snapshot too old

Long-running queries fail on undo

A report that runs for hours against a busy table hits the undo retention limit and dies with ORA-01555. Undo tablespace sizing, retention policy and the shape of the query all play a part.

Undo sized and query reshaped

ORA-04031: unable to allocate shared memory

The shared pool is fragmented

SGA pressure, too many unique SQL statements from an ORM without bind variables, or a leak in a PL/SQL package. The database runs out of contiguous shared memory even though the total looks fine.

Shared pool stable, bind variables in use

license audit scheduled

An Oracle license audit is coming

Partitioning, Advanced Compression or Diagnostics Pack were turned on at some point and never checked against the contract. The audit will find it if nobody looks first.

Usage reconciled before the audit arrives

enq: TX - row lock contention 42%

Row-lock contention is dominating wait time

A heavy transaction holding rows other sessions want, or an application pattern that serializes everything through one row. AWR says the database is waiting on itself.

Hot rows redesigned, contention gone

ORA-01653: unable to extend table

A tablespace ran out of space

Autoextend reached its ceiling, or the datafile was never set to autoextend in the first place. Writes start failing until space is reclaimed or added.

Tablespaces monitored, extensions planned

Data Guard standby last applied: 3 days ago

A standby database has fallen behind

Archive logs not shipping, redo transport interrupted by a network change, or the standby managed recovery process stopped and nobody noticed. Failover would not be clean right now.

Standby current, failover rehearsed

ORA-12514: TNS:listener does not currently know of service

Clients cannot connect through the listener

A service name mismatch, a listener that did not pick up the database on restart, or a dynamic registration that stalled. Applications see TNS errors even though the database is up.

Listener registered and connections clean

PL/SQL: last developer retired 2022

A large PL/SQL codebase has nobody minding it

Packages, triggers and jobs that run the business, written long enough ago that the author is gone and nobody remembers which object owns which schedule.

Code inventoried, ownership assigned

What we do

Oracle Database help, from tuning to migration

Call us for one slow report, or let us plan the whole migration.

Performance tuning
AWR and ASH reviewed against the real workload, SQL plans stabilized, indexes and partitioning checked, with wait-event evidence before and after.
Licensing review
A clear-eyed look at which options are actually in use, what the contract covers, and what to shut off or formalize before Oracle asks.
Upgrades and patching
Major release upgrades rehearsed on a copy, with optimizer changes and deprecated features identified and addressed before the live cutover.
Migrations to Postgres or OCI
PL/SQL converted to PL/pgSQL, data migrated with change capture, and applications retested against the new platform. Honest about what moves cleanly and what has to be rewritten.
High availability
Data Guard set up or repaired, RAC reviewed, and failover tested so the standby is more than a hope.
Managed Tech
Day-to-day care of the database and its instance, with someone who reads the alert log, watches tablespaces and keeps the backup catalog honest.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Oracle Database alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Oracle Database questions

Something else? Call+1 737 727 7327

How do we reduce our Oracle license bill?

Start by finding out exactly which options and packs are in use, which cores are counted on which machines, and which named-user counts reflect reality rather than ancient estimates. Once that is on paper, the conversation changes. Sometimes the answer is turning off an option that was never needed, sometimes it is restructuring hardware so fewer cores are licensed, and sometimes it is planning a migration to a different platform over 12 to 24 months. We have been through this with teams at every scale.

Should we migrate from Oracle to PostgreSQL?

Often, yes, and most often it is a two-year project rather than a quarter. PL/SQL converts to PL/pgSQL with tooling and manual review, sequences and partitioning map over with care, and the application code almost always needs adjustments. The savings on licensing and support fees typically justify the work, but only if the plan is realistic. We will show both the migration cost and the ongoing savings before the project starts.

Why is our Oracle database slow all of a sudden?

In most of the cases that reach us, the optimizer has chosen a worse plan for one or two important statements after a statistics change, a patch, or a data skew. AWR and ASH show which queries moved and where the time is going. Occasionally it is contention, occasionally it is a missing index, and occasionally it is a storage or memory configuration change that was made months ago and has just now become a problem.

Can you prepare us for an Oracle license audit?

Yes. We inventory the databases, record which options and packs are actually used, reconcile that against your contract, and recommend changes before the audit begins. Where there is exposure, we help plan how to address it rather than discovering it in a meeting with Oracle.

Can you take over an Oracle database from a retiring DBA?

Yes. We shadow the existing DBA where possible, document the schemas, jobs, backup and recovery procedures, and bring the configuration into version control. Once the handover is complete we can continue to run it or step back while your team takes over.

How much does Oracle Database help cost?

Estimates are free. Describe the database and the problem, including the edition and any options in use, and we come back with a price before any work is scheduled.

Free estimate

Oracle Database giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.