Oracle Managed Services

Oracle Managed Services: AceMQ Runs Your Oracle Database in Your Environment or Ours

Last reviewed by Tyler Eastridge

AceMQ runs your Oracle Database estate for you: monitoring, backups with restore tests, Data Guard, Release Update patching and the pager. We work inside your data centre or cloud account (Tier 3) or on infrastructure AceMQ runs (Tier 4), with partner Oracle specialists behind the engineers. It covers the database engine only, not Oracle E-Business Suite, Fusion or other Oracle applications. If Oracle Autonomous Database or Amazon RDS for Oracle fits your workload better, this page says so.

Support quotes answered within 1 hour, by a senior engineer.

min fastest response target, by plan
15
across Americas, EMEA, APAC
24/7
hour quote response
1
managed tiers: your infrastructure or ours
2

Planning a build, upgrade or migration instead? See AceMQ Oracle Database consulting and services.

Customers

  • Microsoft
  • Henry Schein
  • Enbridge
  • Gojek

Partners

  • Broadcom
  • Redis
  • VMware Tanzu
  • OSSeva

What's Included

Everything in your Oracle Database managed services contract

RAC, Data Guard, ASM, RMAN, Release Updates and performance work are covered for 19c, 21c and 26ai, within the diagnostic tools your license permits.

  • 01

    Monitoring and On-Call

    We manage monitoring of what predicts Oracle incidents: tablespace and fast recovery area headroom, archive destination space, Data Guard transport and apply lag, failed RMAN jobs, listener status, blocking sessions and ORA- errors in the alert log. Then we take the pager, so an alert reaches an engineer who has your topology in front of them.

  • 02

    Backups, Restore Tests and Recovery

    RMAN backup and archived log policy matched to your recovery point and recovery time targets, restored into a scratch environment on a schedule and timed. Where Transparent Data Encryption is on, the wallet is backed up and restore-tested too, because a backup you cannot decrypt is no backup.

  • 03

    Data Guard and Failover

    On Enterprise Edition estates with Data Guard, we manage the standby: transport and apply lag, protection mode, standby redo logs, and a switchover rehearsal on a schedule so the failover runbook has been run. RAC node operations are in scope where you run it and your licences cover it.

  • 04

    Release Updates and Patching

    Release Updates planned, tested on a copy first and applied in agreed windows, with rollback steps written down. The patches themselves come from Oracle under your own Oracle support contract; AceMQ plans and applies them and produces none of its own.

  • 05

    Performance Work

    Top SQL, plan stability, statistics and memory sizing, reviewed on a schedule. We check which diagnostic packs your licence covers before using AWR or ASH, and use Statspack or SQL trace where it does not, so tuning never creates an obligation by accident.

  • 06

    Access and Security Baseline

    Privileges, roles and audit settings reviewed against least privilege, encryption and wallet handling checked, and Release Update level tracked against the releases you actually run. Access to your environment follows your change process and is logged.

Why AceMQ

What changes with dedicated Oracle engineers

  • Your Environment or Ours

    Run managed Oracle in your own data centre or account (Tier 3) when residency and compliance keep the data in your boundary, or have AceMQ host it (Tier 4) when you want endpoints and no infrastructure to run. The operator is an Oracle specialist under an AceMQ contract, not a generic hosting provider.

  • One Accountable Partner

    AceMQ holds the contract, the SLA and the escalation path, and brings partner Oracle specialists in as the work needs them. An incident starts with an engineer who has your topology and runbooks in front of them. Response targets from 15 minutes, by plan, are response times, not resolution times.

  • The Licence Shapes the Work

    Which packs and options you own decides which diagnostics we may use, whether RAC or Active Data Guard are on the table, and what a safe design looks like. We work inside your entitlements and tell you when a task needs something you do not hold.

  • Runbooks Stay Yours

    Restore, failover and patch runbooks, topology documentation and monitoring configuration are maintained as yours. If you bring operations back in-house, or move a database between your infrastructure and ours, there is a current handover pack.

Oracle estates we look after

Enterprise and Standard Edition 2, single instance, RAC and Data Guard, multitenant and non-CDB databases, on VMs, physical servers or cloud instances you run.

  • Your data centre, on physical servers
  • VMware vSphere and other hypervisors
  • Your AWS or Azure account, on virtual machines
  • Oracle Database 19c, 21c and 26ai
  • Enterprise Edition and Standard Edition 2
  • Data Guard standbys
  • RAC, where you run it and are licensed for it
  • Air-gapped sites
  • Dedicated Oracle hosts operated by AceMQ

Provider comparison

Managed Oracle from AceMQ, Oracle Autonomous Database or Amazon RDS for Oracle

Three different ways to stop running Oracle yourself. Autonomous Database and RDS for Oracle are platforms: the vendor runs the engine on its cloud and you work inside its limits. AceMQ's managed service is people: engineers who run standard Oracle on infrastructure you own, or on ours. The right answer depends on the workload, so each row answers one question.

Managed Oracle from AceMQ, Oracle Autonomous Database or Amazon RDS for Oracle
QuestionAceMQ managed Oracle (Tier 3 or 4)Oracle Autonomous DatabaseAmazon RDS for Oracle
Who operates the databaseAceMQ engineers with partner Oracle specialists, under a contract with response targets from 15 minutes, by plan.Oracle. Its documentation says the service handles provisioning, backups, patching and upgrading, and growing or shrinking the database.AWS runs the managed instance. You remain responsible for schema, SQL and performance.
Where it runsYour data centre or cloud account (Tier 3), or infrastructure AceMQ runs (Tier 4).Oracle's cloud. You manage no hardware or software.AWS only.
ReleasesThe release you run today, with Oracle's lifecycle dates planned around. 19c, 21c and 26ai are covered.Oracle decides when patching and upgrading happen.19c, 21c and 26ai. 26ai is Enterprise Edition only, and 21c and 26ai are multitenant-only.
Server and file system accessYes. AceMQ works with system access to the hosts, inside your change process.No server for you to manage.No host file system access.
RAC, ASM and Flashback DatabaseRAC and Data Guard run where your edition and licences allow them. Exadata is scoped case by case.The platform design is Oracle's. Check Oracle's documentation for any feature you rely on.RAC, ASM and Flashback Database are not supported. Read replicas use Active Data Guard, which needs Enterprise Edition and the option licence.
Best whenYou have an existing estate, depend on RAC, Data Guard or a specific release, need data to stay in your own boundary, or want one contract across several databases.You want Oracle to run the platform and your workload fits what the service allows.You are on AWS, your workload avoids the unsupported features, and you want AWS to run the instance.

Sources: AWS documentation, RDS for Oracle releases and RDS for Oracle features; Oracle documentation, About Autonomous AI Database Serverless (Oracle's name for the service now); all checked 31 October 2026. Vendor limits change, so check them before you commit.

Tier 3 and Tier 4

What Tier 3 and Tier 4 mean for an Oracle Database

Tiers 1 and 2 are AceMQ's Oracle support: you hold the pager and we respond and review. Tiers 3 and 4 are managed services: we hold it. The two managed tiers run the same operations. What differs is where Oracle runs and who owns what underneath it.

  • Tier 3: managed on your infrastructure

    AceMQ operates Oracle in your data centre or cloud account, with system access and your change process. You keep the hosts, the data, the Oracle licences and the Oracle support contract, and you pay the infrastructure bill.

  • Tier 4: managed on AceMQ infrastructure

    AceMQ hosts and operates Oracle on infrastructure it runs, with backups, standby and patching included. You get connection endpoints, not a server or an on-call rota. Licensing for Tier 4 is settled in the quote.

  • Oracle Support stays separate

    Release Updates and bug fixes come from Oracle under your own support contract, and a defect that needs Oracle code has to go to Oracle. AceMQ plans and applies patches, prepares the service request with the diagnosis done, and produces no Oracle patches of its own.

  • Starting at Tier 1 or 2 is fine

    Many estates start with support and a first review, then hand over operations once the backups, standby and patch level have been checked. Nothing about Tier 3 or 4 requires a big-bang handover.

Tiers 1 and 2 are set out on the Oracle support page. Third-party Oracle Database support

Remote DBA

What does a remote Oracle DBA service include?

A remote Oracle DBA service is DBAs who administer your Oracle Database estate from outside your building, on your own infrastructure, with scheduled routine care and on-call response. AceMQ runs it in your data centre or your own cloud account, under one contract, with response targets from 15 minutes, by plan. Teams that search for Oracle DBA managed services usually want this: the same hands, every month, without a full-time hire.

What does a remote Oracle DBA service include?
Part of the serviceWhat the DBA does
Routine administrationTablespace and fast recovery area headroom, users, roles and profiles, schema change requests, scheduler job failures
Monitoring and on-callAlert log, listener status, archive destination space, Data Guard transport and apply lag, failed RMAN jobs, with a pager
Backups and recoveryRMAN and archived log policy matched to your recovery objectives, restored into a scratch environment on a schedule and timed
PatchingRelease Updates tested on a copy first and applied in agreed windows with rollback steps written down; the updates come from your own Oracle support contract
PerformanceTop SQL, plan stability, statistics and memory sizing; AWR and ASH used only where your licence covers the diagnostic packs
ReportingA written review after each patch window or incident, and a regular health report

What stays with you: Oracle licences and support contract, the hosts or cloud account under the database, and application code. AceMQ works on your infrastructure and gives no licence advice. Oracle DBA and remote DBA services

Choosing honestly

When Autonomous Database or RDS for Oracle is the better buy

A managed platform is the right answer for some workloads. These are the differences that decide it.

  • Choose Autonomous Database when

    The application is new or already cloud-shaped, your DBA team is small, and you want Oracle to run provisioning, backups, patching and upgrades. You accept Oracle's limits on what you can configure and that patch timing is Oracle's.

  • Choose RDS for Oracle when

    You are already on AWS and the workload avoids what RDS does not support: RAC, ASM and Flashback Database are unsupported, and there is no host file system access. Active Data Guard read replicas need Enterprise Edition and the option licence.

  • Choose managed Oracle from AceMQ when

    The estate already exists in your data centre or cloud account, uses RAC, Data Guard, a specific release or file-system-level tooling, or has data that must stay in your boundary. Also when you want the same contract to cover PostgreSQL, Kafka or other engines.

  • What none of them removes

    Schema design, query plans, application behaviour and capacity planning still belong to whoever owns the workload. On a vendor platform that is your team; at Tier 3 or 4 an Oracle engineer owns them with you.

A move off Oracle is a different project: an exit assessment, then a migration scoped on its own. Oracle Database consulting and exit assessment

Releases

Managed Oracle on a release that is leaving support

Managed operations do not change Oracle's calendar. The dates below come from Oracle's Lifetime Support Policy effective 2 October 2026, and they decide when an upgrade has to be planned into the service.

  • Oracle Database 19c

    Premier Support to 31 December 2029 and Extended Support to 31 December 2032. The release most estates run, and the one most managed contracts are written around.

  • Oracle Database 21c

    Premier Support ends in July 2027 and it has no Extended Support. An estate on 21c has the shortest runway and needs an upgrade plan first.

  • Oracle AI Database 26ai

    Premier Support to December 2031. Moving to it from 19c converts non-container databases to multitenant, which changes patching and backup, so it runs as a project inside the service.

  • Upgrades are projects, not surprises

    Inventory, rehearsal on a copy with a fallback at each step, and a cutover window agreed with you. A platform change and a version change never share a production window.

The decision between staying on 19c and moving is set out on the 19c end-of-life article. Oracle 19c end of life: dates and options

Price drivers

What drives the price of managed Oracle services

AceMQ does not publish a price list for managed services. A managed Oracle quote is built from these inputs, and the written quote returns within 1 hour of your request.

  • Databases, size and edition

    How many databases and instances you run, how large they are, which are production, and whether they are Enterprise Edition or Standard Edition 2.

  • Availability and recovery targets

    Standalone, Data Guard or RAC, and the recovery point and recovery time objectives that set the backup, restore and standby work.

  • Cover hours

    From business hours to 24/7 on-call with response targets from 15 minutes, by plan.

  • Tier, and Tier 4 licences

    At Tier 3 you pay your provider for infrastructure and Oracle for licences and support, and AceMQ for operations. At Tier 4 the infrastructure is in the AceMQ quote, and licensing for Tier 4 is settled in the quote.

Not a fit for

When managed Oracle from AceMQ is the wrong tool

We would rather say so up front.

  • Oracle applications

    E-Business Suite, Fusion, HCM, ERP and EPM managed services are out of scope. This is Oracle Database operations. We can run the database tier underneath an application.

  • Licence advice or negotiation

    AceMQ does not resell Oracle licences, negotiate with Oracle, defend an audit or give legal advice on your agreement. Your reseller, your contract or your counsel does.

  • Self-service cloud console

    If you want to click to provision a database with no contract and no engineer, buy Autonomous Database or RDS from the vendor.

  • One small database with a good DBA

    A single healthy database run by a capable DBA may need only a health check and a current backup test.

Running other engines too? One contract can cover PostgreSQL, SQL Server and more. Managed PostgreSQL services

Escalation Path

Your first hour of an Oracle Database outage

A database that has stopped taking changes is answered before a request for tuning advice, and each clock follows your plan.

  1. From 15 min (by plan)first responseEmergencyProduction down: database stopped or refusing changes, archive destination full, standby far behind, or an application broken by a patch
  2. 1 hourfirst responseCriticalSevere degradation: log file sync waits across hundreds of sessions, cursor pin waits at peak, ASM disk group full during a load
  3. 4 hoursfirst responseHighPlan changes making the same SQL_ID slow, datapatch failing after a Release Update, temp space exhausted by a month-end job
  4. Next Dayfirst responseStandardQuestions on RMAN policy, Data Guard failover runbooks, memory and I/O settings and upgrade paths to 19c and 26ai

Response clocks depend on plan and severity: a standby hours behind and a tuning question never share one.

Looking for Oracle engineers who will know your RAC and Data Guard layout? Ask for a quote or write to us.

Contact Us

Typical engagements

How Oracle incidents get handled

Oracle work is scoped per estate. The options below show how an incident, a recovery review or a patch project is handled from first call to closure.

1 / 6 case studies

  • Assessment

    Oracle to PostgreSQL Assessment and Proof of Value

    Regional Insurer

    A typical engagement for a team weighing an exit from Oracle: classify every object by conversion effort, then convert and test one representative database before committing to the rest.

    PostgreSQLOracle DatabaseOra2PgAWS DMS
  • Remediation

    Debezium Oracle LogMiner Lag Remediation

    Regional Retail Bank

    Bringing an Oracle change data capture pipeline back inside its batch window after nightly jobs left the Debezium connector hours behind the source.

    DebeziumOracleKafkaKubernetes
  • Support

    Debezium MySQL Binlog Retention and Schema History Support

    Online Travel Platform

    Ongoing support for a MySQL change data capture pipeline that needed a full re-snapshot after a planned outage outlasted binlog retention and a trimmed schema history topic.

    DebeziumMySQLSQL ServerOracle DatabaseKafkaAmazon RDS
  • Assessment

    Oracle Data Guard Failover Readiness Review

    Regional Insurer

    A typical engagement to find out whether an Oracle Data Guard standby will really take over: transport and apply lag, protection mode, redo sizing, failover runbooks and client reconnection.

    Oracle DatabaseData GuardRMANLinux
  • Managed Services

    Remote Oracle DBA Cover for a Small Platform Team

    SaaS Platform Team

    A typical engagement where a lean platform team adds remote Oracle DBA cover: on-call, restore testing, patch windows and a monthly review, without hiring a second DBA.

    Oracle DatabaseRMANPrometheusLinux
  • Consulting

    Oracle 19c to 26ai Upgrade Planning

    Industrial Manufacturing Group

    A typical engagement to decide whether Oracle databases should stay on 19c or move to 26ai, and to plan the multitenant conversion, AutoUpgrade run and rollback for the ones that move.

    Oracle DatabaseAutoUpgradeMultitenantLinux
All use cases

Support options

Four tiers of Oracle Database support.

AceMQ offers Oracle Database support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and emergency response for databases your team runs, proactive reviews that find backup, standby and patch problems first, managed Oracle Database on your own infrastructure, and managed Oracle Database on AceMQ infrastructure. Oracle Database 19c, 21c and 26ai are covered by AceMQ engineers working with partner Oracle specialists. Oracle patches still come from Oracle.

  • Tier 1

    Oracle Database 24/7 Support & Incident Management

    Your DBAs run Oracle, we take the escalations

    Best for: DBA teams that handle daily operations and need senior help for a RAC, Data Guard or patching problem.

  • Tier 2

    Oracle Database 24/7 Support with Proactive Monitoring

    Scheduled reviews of backups, standby and top SQL

    Best for: Teams who want a timed restore and a Data Guard failover rehearsed before a real outage asks for them.

  • Tier 3

    Managed Oracle Database on Your Infrastructure

    We operate your databases on your servers

    Best for: Organizations that keep Oracle on their own hosts or cloud accounts and want specialists doing the operational work.

  • Tier 4

    Fully Managed Oracle Database on AceMQ Infrastructure

    We run your Oracle databases as a service

    Best for: Business units that need databases kept healthy without hiring and rostering DBAs.

FAQ

Oracle Database managed services questions

Still have questions about Oracle Database? Email an Expert

What does a remote Oracle DBA service include?

A remote Oracle DBA service includes routine administration (space, users, roles, schema changes, scheduler jobs), 24/7 monitoring and on-call with response targets from 15 minutes, by plan, RMAN backups with timed restore tests, Release Update planning and application on your own Oracle support contract, performance reviews and a written report after each patch window or incident. AceMQ runs it on your infrastructure, in your data centre or your own cloud account. It does not include Oracle licences, the hosts under the database or Oracle applications. The same scope answers searches for Oracle DBA managed services, and a quote returns within 1 hour of your request.

What is the difference between managed Oracle services, a remote DBA and a full-time DBA?

An Oracle managed service provider (MSP) operates your databases for you, and it is worth engaging when on-call, patching and restore testing compete with project work for the same people. A full-time DBA is one person you employ, with the cover gaps that implies. A remote DBA service usually supplies advice and ticket handling for databases your team still runs. Managed Oracle services mean AceMQ operates the databases: monitoring, backups, Release Update patching, Data Guard and on-call are ours under a contract with response targets from 15 minutes, by plan. Teams that keep a DBA often choose support (Tiers 1 and 2); teams that want Oracle to stop being their problem choose Tier 3 or 4.

Can you manage Oracle in our cloud account, on-premises, on OCI or on RDS?

Yes for your own data centre, VMware and virtual machines in your AWS or Azure account (Tier 3), or on infrastructure AceMQ runs (Tier 4). Oracle Cloud Infrastructure and Exadata are scoped case by case. Autonomous Database and Amazon RDS for Oracle are run by their vendors, so Tiers 3 and 4 do not apply to them; ask us about support for the SQL and schema work around them.

What happens to our Oracle licence position if AceMQ manages the database?

At Tier 3 the licences stay yours and nothing changes. At Tier 4, licensing is settled in the quote before work starts. AceMQ does not resell Oracle licences, negotiate with Oracle or give legal advice on your agreement, and your Oracle support contract stays the source of Release Updates.

What do Oracle managed services include (and what stays with your team)?

They include the operation of the database: 24/7 monitoring and on-call, RMAN backups with timed restore tests, Data Guard standby management, Release Update planning and application, and scheduled performance and security reviews. They do not include your Oracle licences or support contract, the hosts or cloud account under the database, Oracle applications such as E-Business Suite, or licence negotiation. AceMQ works in your data centre or cloud account with partner Oracle specialists behind the engineers, and a written quote returns within 1 hour of your request.

Do Oracle managed cloud services mean Oracle runs the database?

Not here. Oracle Autonomous Database and Amazon RDS for Oracle are platforms their vendors run, and the page's comparison table shows when each is the better buy. AceMQ's managed service is engineers who run standard Oracle in your own data centre or in virtual machines in your AWS or Azure account, which suits estates that use RAC, Data Guard, a specific release or file-system-level tooling, or data that must stay inside your boundary.

Can AceMQ take on a single Oracle task?

Yes. A performance review, a backup and restore test or a Release Update plan can be quoted as its own engagement. Teams that then want 24/7 response and engineers who already know their databases and standby layout move to the annual agreement without starting over.

What goes into pricing Oracle Database support?

Annual contracts typically run $24,000 to $72,000 (USD). The quote reflects the Oracle release and edition, whether you run RAC or Data Guard, how many databases and hosts are covered, and the response plan. Send those details and a quote reply arrives within 1 hour.

Let's talk

Hand Over the Oracle Pager. Choose Where Oracle Lives.

Reactive cover, proactive reviews, or AceMQ running Oracle Database for you on your infrastructure or ours. A senior engineer scopes it with you, and quote requests are answered within 1 hour.

A senior Oracle Database engineer, not a sales queueQuote requests answered within 1 hourAd hoc engagements or an annual partnership

Production incident right now?Email an Oracle Database Architect