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 253<br />

rated<br />

by a hyphen. The DBA must learn <strong>to</strong> identify which <strong>Oracle</strong> error codes<br />

indicate problems with the database infrastructure and which codes indicate<br />

errors made by a user or a problem with an application. The named exceptions<br />

defined by PL/SQL are examples of error codes that indicate problems in the<br />

application, not in the database infrastructure.<br />

error message means that the query has taken so<br />

long that the undo information required <strong>to</strong> re- create the required read- consistent<br />

snapshot of the database has been overwritten by other transactions—that is, the<br />

snapshot is <strong>to</strong>o old <strong>to</strong> be reconstructed.<br />

error message means that <strong>Oracle</strong> detected that<br />

two transactions are blocking each other and picked one of them as a victim. The<br />

appropriate action that the victim must take is <strong>to</strong> issue the command and<br />

retry its transaction.<br />

error message indicates that <strong>Oracle</strong> encountered<br />

an unexpected condition and s<strong>to</strong>pped processing the query in question.<br />

ORA- 00600 errors should always be investigated, and the DBA should confirm that<br />

they were not triggered by corrupted data blocks.<br />

error message means that the <strong>Oracle</strong> server<br />

process attempted <strong>to</strong> perform an illegal operation and was forced <strong>to</strong> terminate<br />

itself by the operating system.<br />

Exercises<br />

<br />

in this chapter. Use any of the resources listed in this chapter <strong>to</strong> determine the<br />

root cause of the problem and find the permanent fix.<br />

<br />

messages are recorded in the alert log. Check whether a trace file is produced and<br />

review it. What happens if the victim simply retries its last SQL command instead<br />

of issuing the command and retrying its entire transaction?<br />

<br />

session B, but <strong>Oracle</strong> cannot take any action because this is not yet a deadlock<br />

scenario. Use a GUI <strong>to</strong>ol such as SQL Developer, Enterprise Manager, Toad, or<br />

DBArtisan <strong>to</strong> identify the blocking process and terminate it.

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

Saved successfully!

Ooh no, something went wrong!