01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CHAPTER 11 FIXING PROBLEMS 231<br />

One Week Later<br />

When the problem occurred again, very little diagnosis and resolution time was required.<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Opportunities for Improvement<br />

The database administra<strong>to</strong>r in this example has considerable <strong>Oracle</strong> experience and good<br />

problem- solving skills, but there are nevertheless several opportunities for improvement:<br />

<br />

problem started. There were no moni<strong>to</strong>ring mechanisms in place <strong>to</strong> au<strong>to</strong>matically<br />

alert the database administra<strong>to</strong>r about the loss of service.<br />

<br />

fixed, but the root cause had not been determined. In this case, the listener log<br />

file contained many occurrences of the following message: <br />

. This would have been a good place <strong>to</strong> start the<br />

investigation.<br />

Incident Management vs. Problem Management<br />

An incident is a single occurrence of a problem. Incident management and problem<br />

management are therefore separate aspects of IT management. Incident management<br />

is concerned with res<strong>to</strong>ring service as rapidly as possible. Problem management is concerned<br />

with permanently fixing defects so the incidents are not repeated.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!