DBA · EBS · Intermediate
Oracle Apps DBA: Keeping E-Business Suite Alive
Nineteen modules, nineteen labs, and a system you could hand to somebody else
Nobody notices a DBA until something is down, and by then the decisions that mattered were taken months earlier — when the backup was configured and never restored, when the patch was applied without a rollback, when the test environment was refreshed with real salaries in it. This course is about those decisions. It covers Oracle E-Business Suite and the database underneath it: the architecture, the AD utilities, cloning, patching, concurrent processing, performance, and the security of a system that holds a company's payroll. It assumes you can use a shell and read SQL. It does not assume you have administered a database before.
Live cohort · registration open
Live teaching starts 28 December 2026
One hour daily, Sunday to Thursday · 19:00 Riyadh, 18:00 Cairo · 9 weeks
Taught live by an Oracle consultant, with every session recorded for anyone who misses one. Places are limited — we teach these in small groups so questions get answered.
Your access starts the day you enrol, not the day the cohort starts. The written lessons, the quizzes and the final assessment open straight away, so you can come to the first session having already read the ground.
The sessions run online, and the joining details reach you by email before the first one.
Watch a free lesson
All free lessons in this course · 9 free lessons
EGP 8,625EGP 11,500Save 25%
184 lessons · 290 min
Buying for a team? See seat pricing.
Bundle · save 25%
Oracle Technical Track
All 4 courses together for EGP 34,500 instead of EGP 46,000.
Includes
Who this is for
- Apps DBAs and system administrators running Oracle E-Business Suite and the database under it.
- Developers and technical consultants who keep being asked to clone, patch or refresh an environment and would rather not learn it during an incident.
- Anyone who has inherited a backup nobody has ever restored.
- This course is about E-Business Suite. In Fusion SaaS there is no DBA role — Oracle owns the database, the schema and the patch calendar — so if your estate is entirely SaaS, the first module tells you to stop.
What you will be able to do
- Say what an Apps DBA is responsible for, and what changes the day an estate moves to Fusion.
- Read the architecture of a running EBS instance and name every process you find.
- Take a backup you have actually restored, and know how long the restore takes before you need it.
- Clone an environment, and know what a clone does not copy.
- Run a patching cycle with a rollback that exists rather than one you hope for.
- Diagnose a slow system by measuring rather than by tuning what you already suspect.
- Keep a test environment usable without putting real payroll in it.
- Hand a system to somebody else with documentation they can act on.
What you should know first
- You can move around a Linux shell and read a log file without being talked through it.
- You can read SQL. You do not need to have written PL/SQL or administered a database.
- An EBS environment you are allowed to break. A personal or training instance is ideal; a client production system is not.
- No prior DBA experience is assumed. This is not an Oracle certification course and does not follow its syllabus.
What you will cover
Watch a free lesson
1. Module 0 · Orientation
What this course covers, what it deliberately does not, and how to set up an environment you are allowed to destroy.
4 lessons8 min
2. Module 1 · What an Apps DBA does, and what Fusion took away
The boundary of this course, drawn in the first hour rather than discovered in module 9. If your estate is entirely Fusion SaaS, this says so.
8 lessons16 min
3. Module 2 · The stack you are responsible for
Every process, file and port in a running EBS instance, named. Almost every diagnostic in this course starts with knowing what should be there.
10 lessons20 min
4. Module 3 · The database itself
For people who did not come from a database background. Enough to reason about what is happening, without pretending to be a course on database internals.
11 lessons22 min
5. Module 4 · The application tier and the AD utilities
The tools you will spend most of your time in, and the conventions that make them predictable rather than frightening.
10 lessons20 min
6. Module 5 · Backup and recovery
FLAGSHIP. The only module where a mistake is unrecoverable in the literal sense. A backup nobody has restored is a belief, not a backup.
13 lessons26 min
7. Module 6 · Cloning
The most-requested DBA task, and the one where the interesting question is what a clone does NOT copy.
11 lessons22 min
8. Module 7 · Patching
FLAGSHIP. Where most unplanned downtime comes from, and where a rollback either exists or is discovered not to at the worst moment.
14 lessons28 min
9. Module 8 · Concurrent processing
How work actually gets done in EBS, and the single most common thing a user will ring you about.
11 lessons22 min
10. Module 9 · Users, responsibilities and access
Who can do what, why a user cannot see what they expect, and the requests you will be asked to fulfil that you should refuse.
9 lessons18 min
11. Module 10 · WebLogic and the technology stack
The layer between the browser and the application. Unfamiliar to most people arriving from the database side, and the source of a whole class of outage.
10 lessons20 min
12. Module 11 · Performance: finding the actual problem
FLAGSHIP. Where a DBA is judged, and where most effort is spent tuning things that were never the problem.
12 lessons24 min
13. Module 12 · Space, growth and purging
Unglamorous, entirely predictable, and the cause of a large share of unplanned outages — because a full disk stops everything at once.
9 lessons18 min
14. Module 13 · Monitoring, and knowing before the client does
The difference between a professional service and a reactive one is who notices first. That is a design decision, not diligence.
9 lessons18 min
15. Module 14 · Upgrades and platform moves
A project rather than a task. The DBA work inside it, and the parts where the answer is that this is somebody else's decision.
10 lessons20 min
16. Module 15 · Security, credentials and audit
FLAGSHIP. A DBA holds the credentials to a system containing payroll and bank details. That concentration is the security story, not any single setting.
10 lessons20 min
17. Module 16 · Environments: what test must not have
How many environments, what each is for, and the rule that a test system holding real personal data is a production system with weaker controls.
9 lessons18 min
18. Module 17 · When it is not the database
The database is blamed first because it is the part with a name. Establishing where a problem actually is, and saying so without an argument.
8 lessons16 min
19. Module 18 · Capstone: a system handed over
One estate taken from inherited and undocumented to something somebody else could run, with every module in this course applied where it belongs.
6 lessons12 min