MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 1 · What an Apps DBA does, and what Fusion took away

Where the DBA role went in Fusion

Lesson 7 of 184 · 3 min · Free preview

In SaaS, ORACLE OWNS the database, the schema and the patch calendar. What you can still do, what you cannot, and THE HONEST ANSWER IF YOUR ESTATE IS ALREADY THERE. This is the lesson that decides whether the rest of the course is for you, which is why it is a free preview. WHAT YOU CANNOT DO IS MOST OF THIS COURSE. There is no SQL*Plus session against the production schema. You do not take the backups, you do not schedule the patching, you do not size the instance, you do not tune the database, and you do not have a file system to look at. Oracle does all of it, and the schema is not documented for you to query directly — the OIC course says the same thing from the integration side. WHAT REMAINS IS REAL AND IS A DIFFERENT JOB WITH A DIFFERENT NAME. Environment management: which

This lesson is free

Watch the full lesson, with its written notes, without an account. It is one of the free lessons this course opens with.

Watch the full lesson

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 1 · What an Apps DBA does, and what Fusion took away

  1. 1The job, described honestly
  2. 2Apps DBA versus core DBA
  3. 3Where the DBA role went in FusionFree preview
  4. 4What transfers, and what does not
  5. 5On-premises, IaaS, and the middle ground
  6. 6Who else touches this system
  7. 7What breaks: the estate nobody owned
  8. 8Lab briefing · Describe an estate you have not seen