Oracle Apps DBA: Keeping E-Business Suite Alive · Module 4 · The application tier and the AD utilities
Compiling and generating
Lesson 37 of 184 · 2 min
Invalid objects, forms and reports. WHAT ACTUALLY NEEDS REGENERATING after a change and WHAT DOES NOT. The instinct after any change is to regenerate everything, because it is safe and it always works. It is also hours of outage bought to avoid five minutes of thinking, and on a real estate that trade is a bad one every time. INVALID DATABASE OBJECTS ARE THE MOST COMMON AND THE LEAST ALARMING. A package becomes invalid when something it depends on changes, and Oracle will recompile it automatically on first use. So invalid objects after a patch are normal rather than a fault — you recompile them deliberately so the cost is paid now instead of by whichever user hits it first, not because the system is broken. WHAT MATTERS IS WHETHER THEY RECOMPILE SUCCESSFULLY. An object that stays invalid after a recompile has a real error — a missing dependency, a…
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