Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities
adctrl and the concurrent managers
Lesson 38 of 184 · 2 min
Controlling the managers from the command line WHEN THE APPLICATION WILL NOT LET YOU IN. Module 8 goes deeper. Concurrent managers are normally administered from inside the application, and that is fine right up until the moment it is not. THE SITUATIONS WHERE IT IS NOT ARE THE ONES YOU WILL MEET. The web layer is down, so there is no screen to log into. The managers are so overloaded that the administration form itself will not respond. Somebody has locked the account you would use. Or the system is in maintenance mode, so nobody can log in by design and you still need to stop a manager. adctrl IS THE ANSWER AND IT NEEDS NOTHING BUT A SHELL AND THE RIGHT ENVIRONMENT. It lists the manager processes, shows their status, and lets you stop, start and restart individual managers or the lot. THE OPTION WORTH KNOWING BEFORE YOU NEED…
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