Logo-Icon
HOMEABOUTSERVICESHOW WE WORKBLOGInstagram-Icon Talk To an Expert
RadixTrie-image
Oracle database support in South Africa
Support Models

Oracle Database Support in South Africa: Keeping Licensed Estates Healthy and Compliant

Oracle rewards discipline and punishes drift, in performance, in availability and in licensing. What good Oracle database support covers, and the questions to ask of whoever provides yours.
By RadixTrie3 September 20263 min read
Oracle Database runs a large share of South Africa's most important systems: banking cores, billing platforms, ERP back ends, insurance and government workloads. These estates are rarely small or simple, and they carry a second dimension that most other databases do not: a licence position that has to be understood and defended. Good Oracle support therefore has two jobs at once, keeping the databases healthy and keeping the estate compliant. This article covers both.

What breaks in Oracle estates, and why it is usually avoidable

Oracle rarely fails suddenly. It drifts. Quarterly patches get deferred because the change window is hard to get. Backups run every night but nobody has restored one this year. A standby database exists on paper, but the last real switchover was during the original project. Tablespaces grow into their limits at month-end. A plan changes after statistics are gathered and a batch job that took an hour now takes six. Each of these is well understood and preventable, provided a competent person is looking at the estate regularly with a plan.

What good Oracle database support includes

  1. Patching with a cadence. Oracle publishes Critical Patch Updates quarterly. Good support means an agreed schedule for testing and applying them, with a documented position on any instance that must lag behind and why.
  2. Backups proven by restores. RMAN backups, retention that matches the business requirement, and regular restore and recovery tests with a measured recovery time. Backup success reports are not evidence of recoverability; restores are.
  3. Standby and failover that are exercised. Where Data Guard is in place, switchovers are performed deliberately on a schedule so that a real failover is routine rather than a first attempt under pressure.
  4. Performance management as continuous work. Regular review of wait events and top SQL using Oracle's own diagnostic data, statistics gathering that is planned rather than accidental, and plan stability for the SQL that matters.
  5. Capacity and housekeeping. Tablespace growth, archive log destinations, audit trail volume, temp usage and undo retention watched before they cause an outage.
  6. Security basics done properly. Least-privilege accounts, profiles and password policies, network encryption where needed, and auditing configured to a purpose.
  7. Licence-aware operations. Knowing which edition and options are licensed, which features are actually in use, and ensuring that a helpful DBA does not switch on an unlicensed option to solve a Tuesday problem.

Licensing: the part of Oracle support most providers avoid

Oracle licenses its database by processor or by named user, and the rules around cores, virtualisation, standby servers and separately licensed options are detailed. Oracle also audits its customers. None of this is a reason to panic, but it is a reason to keep an accurate inventory: which databases exist, which edition each runs, which options and packs are enabled, and where each instance physically or virtually runs. A support team that manages Oracle every day is well placed to keep that inventory current and to flag configuration changes that would have licence consequences. Formal licence advice belongs with a specialist, but operational awareness is part of good support.
A single question exposes the health of most Oracle estates: when did we last restore a production backup to a test server, and how long did it take? If the answer is a date more than a quarter old, start there.

Standard Edition or Enterprise Edition changes the playbook

Many features that people associate with Oracle resilience and performance, Data Guard among them, are Enterprise Edition capabilities. Estates on Standard Edition need a different high-availability and recovery design, and support that understands what is and is not available on that edition. Good support does not assume one playbook fits every instance; it documents the edition and the design per database and tests accordingly.

Questions to ask your Oracle support provider

  • Which named engineers work on our estate, and how many years of Oracle production experience do they have?
  • When was our last RMAN restore test, what was recovered, and how long did it take?
  • When was our last Data Guard switchover, and was the application tested against the standby?
  • What is our patch position against the latest Critical Patch Update, per instance?
  • Do you maintain an inventory of editions, options and packs in use, and would you notice if that changed?
  • How is performance work handled: continuously, or only when someone complains?
  • What happens overnight and over weekends, and who answers?

How RadixTrie supports Oracle

RadixTrie is a South African database specialist with senior engineers across Oracle, Microsoft SQL Server, PostgreSQL and MySQL/MariaDB, with offices in Randpark Ridge and Stellenbosch. The model is direct access to senior database experts, no service desk and no escalation loops. For Oracle that covers 24/7 support, managed DBA services, performance tuning, health checks, upgrades and migrations, high availability and disaster recovery, and security and monitoring. The <a href="/services">services page</a> describes each in more detail.
Organisations also come to us when they are weighing up whether to stay on Oracle or move certain workloads to PostgreSQL. We support both, so the advice is about the workload rather than the licence. Our <a href="/blog/reskilling-to-postgresql-how-to-navigate-the-challenges">note on reskilling from Oracle to PostgreSQL</a> is a useful starting point for teams considering that path.
<strong>Related reading:</strong> <a href="/blog/oracle-to-postgresql-migration">Oracle to PostgreSQL Migration: What Actually Takes the Time</a> &middot; <a href="/blog/high-availability-disaster-recovery">High Availability and Disaster Recovery: Tested Beats Configured</a> &middot; <a href="/blog/managed-dba-services-explained">Managed DBA Services Explained: What You Hand Over, What You Keep</a> &middot; <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
Want an honest view of your Oracle estate's health and risk?
TAGSOracleDatabase SupportManaged DBASouth Africa
RadixTrie-image
Oracle database support in South Africa
Support Models

Oracle Database Support in South Africa: Keeping Licensed Estates Healthy and Compliant

Oracle rewards discipline and punishes drift, in performance, in availability and in licensing. What good Oracle database support covers, and the questions to ask of whoever provides yours.
By RadixTrie3 September 20263 min read
Oracle Database runs a large share of South Africa's most important systems: banking cores, billing platforms, ERP back ends, insurance and government workloads. These estates are rarely small or simple, and they carry a second dimension that most other databases do not: a licence position that has to be understood and defended. Good Oracle support therefore has two jobs at once, keeping the databases healthy and keeping the estate compliant. This article covers both.

What breaks in Oracle estates, and why it is usually avoidable

Oracle rarely fails suddenly. It drifts. Quarterly patches get deferred because the change window is hard to get. Backups run every night but nobody has restored one this year. A standby database exists on paper, but the last real switchover was during the original project. Tablespaces grow into their limits at month-end. A plan changes after statistics are gathered and a batch job that took an hour now takes six. Each of these is well understood and preventable, provided a competent person is looking at the estate regularly with a plan.

What good Oracle database support includes

  1. Patching with a cadence. Oracle publishes Critical Patch Updates quarterly. Good support means an agreed schedule for testing and applying them, with a documented position on any instance that must lag behind and why.
  2. Backups proven by restores. RMAN backups, retention that matches the business requirement, and regular restore and recovery tests with a measured recovery time. Backup success reports are not evidence of recoverability; restores are.
  3. Standby and failover that are exercised. Where Data Guard is in place, switchovers are performed deliberately on a schedule so that a real failover is routine rather than a first attempt under pressure.
  4. Performance management as continuous work. Regular review of wait events and top SQL using Oracle's own diagnostic data, statistics gathering that is planned rather than accidental, and plan stability for the SQL that matters.
  5. Capacity and housekeeping. Tablespace growth, archive log destinations, audit trail volume, temp usage and undo retention watched before they cause an outage.
  6. Security basics done properly. Least-privilege accounts, profiles and password policies, network encryption where needed, and auditing configured to a purpose.
  7. Licence-aware operations. Knowing which edition and options are licensed, which features are actually in use, and ensuring that a helpful DBA does not switch on an unlicensed option to solve a Tuesday problem.

Licensing: the part of Oracle support most providers avoid

Oracle licenses its database by processor or by named user, and the rules around cores, virtualisation, standby servers and separately licensed options are detailed. Oracle also audits its customers. None of this is a reason to panic, but it is a reason to keep an accurate inventory: which databases exist, which edition each runs, which options and packs are enabled, and where each instance physically or virtually runs. A support team that manages Oracle every day is well placed to keep that inventory current and to flag configuration changes that would have licence consequences. Formal licence advice belongs with a specialist, but operational awareness is part of good support.
A single question exposes the health of most Oracle estates: when did we last restore a production backup to a test server, and how long did it take? If the answer is a date more than a quarter old, start there.

Standard Edition or Enterprise Edition changes the playbook

Many features that people associate with Oracle resilience and performance, Data Guard among them, are Enterprise Edition capabilities. Estates on Standard Edition need a different high-availability and recovery design, and support that understands what is and is not available on that edition. Good support does not assume one playbook fits every instance; it documents the edition and the design per database and tests accordingly.

Questions to ask your Oracle support provider

  • Which named engineers work on our estate, and how many years of Oracle production experience do they have?
  • When was our last RMAN restore test, what was recovered, and how long did it take?
  • When was our last Data Guard switchover, and was the application tested against the standby?
  • What is our patch position against the latest Critical Patch Update, per instance?
  • Do you maintain an inventory of editions, options and packs in use, and would you notice if that changed?
  • How is performance work handled: continuously, or only when someone complains?
  • What happens overnight and over weekends, and who answers?

How RadixTrie supports Oracle

RadixTrie is a South African database specialist with senior engineers across Oracle, Microsoft SQL Server, PostgreSQL and MySQL/MariaDB, with offices in Randpark Ridge and Stellenbosch. The model is direct access to senior database experts, no service desk and no escalation loops. For Oracle that covers 24/7 support, managed DBA services, performance tuning, health checks, upgrades and migrations, high availability and disaster recovery, and security and monitoring. The <a href="/services">services page</a> describes each in more detail.
Organisations also come to us when they are weighing up whether to stay on Oracle or move certain workloads to PostgreSQL. We support both, so the advice is about the workload rather than the licence. Our <a href="/blog/reskilling-to-postgresql-how-to-navigate-the-challenges">note on reskilling from Oracle to PostgreSQL</a> is a useful starting point for teams considering that path.
<strong>Related reading:</strong> <a href="/blog/oracle-to-postgresql-migration">Oracle to PostgreSQL Migration: What Actually Takes the Time</a> &middot; <a href="/blog/high-availability-disaster-recovery">High Availability and Disaster Recovery: Tested Beats Configured</a> &middot; <a href="/blog/managed-dba-services-explained">Managed DBA Services Explained: What You Hand Over, What You Keep</a> &middot; <a href="/blog/database-health-check">The Database Health Check: What a Good One Covers and What It Finds</a>
Want an honest view of your Oracle estate's health and risk?
TAGSOracleDatabase SupportManaged DBASouth Africa