* Applications are generally slow. If the situation is intense, usually the root cause is harsh enough to affect nearly all application areas on the system. So not only do you have people screaming about specific key business processes, but there is also a grumbling application user chorus. This is when you must prioritize and communicate to people what you are doing and why.

* Extreme pressure exists. In a firefighting situation, it is not uncommon for jobs to be on the line. When this occurs, people freak out. Their fear turns to anxiety, and they panic. People express this in different ways. I've seen people break down and cry. I've seen a distraught chief information officer (CIO) physically grab another person and drag him across the room. People become unstable. You need a way to methodically move forward to avoid becoming trapped.

* Olympic-level finger-pointing occurs. Oracle database administrators (DBAs) are not trained like salespeople. Salespeople are amazing at deflecting responsibility. If a salesperson tells you the problem is with a module, you may say something like, "I can look into that." And to your surprise, the salesperson's response is, "Oh, so it's your fault! We all hope you can fix it." See how easily the situation turned from your willingness to help to being your fault? This is what I'm talking about. Try to clarify what you say, so the expectations of the company do not rest on your shoulders.