Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities
adadmin, and what it is for
Lesson 36 of 184 · 2 min
Maintenance tasks, and the menu options that are SAFE ON A LIVE SYSTEM against the ones that ARE NOT. adadmin is the application tier's maintenance utility and it is a menu, which is precisely what makes it dangerous. Every option looks equivalent — a number you type — and they range from "read something" to "take the system down for two hours". THE SAFE ONES ARE THE ONES THAT REPORT. Listing invalid objects, checking the state of things, verifying files. They read and change nothing, and running one on a live system costs a little CPU. THE UNSAFE ONES REGENERATE OR RELINK, AND THE DANGER IS THAT THEY ARE NOT DESTRUCTIVE — THEY ARE SLOW AND EXCLUSIVE. Regenerating forms or reports, relinking executables, recompiling large volumes: each rewrites files that the running system is using, so the correct state to do it in is with the services down. Started on…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.
In this module: Module 4 · The application tier and the AD utilities
- 1What the application tier does
- 2Starting and stopping the services
- 3adadmin, and what it is for
- 4Compiling and generating
- 5adctrl and the concurrent managers
- 6Reading an AD log
- 7Worker processes, and the one that failed
- 8Custom top, and where your code belongs
- 9What breaks: three application-tier failures
- 10Lab briefing · Operate the tier by hand