Managing the Oracle Instance

Posted on
Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone

These questions are derived from the Self Test Software Practice Test for 1Z0-042 – Oracle Database 10g: Administration I.

 

Objective: Managing the Oracle Instance
SubObjective: View the database alert log

Item Number: 1Z0-042.4.6.3
Multiple Answer, Multiple Choice

 

You view the alert log file regularly to keep track of important messages that may be generated.

 

Which problems can be identified by using the alert log file? (Choose all that apply.)

 

 

  1. Deadlocks occurring in the database
  2. The SYSTEM tablespace becoming full
  3. A control file missing from the database
  4. A redo log file missing from the database
  5. Users consuming a high amount of CPU
  6. Dropping of an important user from the database
  7. Using the SYSTEM tablespace as the temporary tablespace

 

Answer:
A. Deadlocks occurring in the database
C. A control file missing from the database
D. A redo log file missing from the database
G. Using the SYSTEM tablespace as the temporary tablespace

 

Tutorial:
The alert log file can be used to identify the following problems in a database:

 

 

  • A control file missing in the database
  • A datafile missing in the database
  • A redo log file or redo log member file missing in the database
  • The SYSTEM tablespace being used as the temporary tablespace
  • All internal, block corruption, and deadlock errors occurring in the database

 

The alert log file can also be used to determine information about the administrative operations occurring for a database, such as creating, altering, or dropping tablespaces or other database startup and shutdown activities.

 

The option stating you can identify the SYSTEM tablespace becoming full is incorrect because the alert log file cannot be used to identify this problem in the database. To check for space utilization in the SYSTEM tablespace, you can set a warning threshold that generates a warning alert when the SYSTEM tablespace is becoming full.

 

The option stating you can identify users consuming a high amount of CPU is incorrect because the alert log file cannot be used to identify the users who are using a high amount of CPU. To identify the users using a high amount of CPU time, you can use Automatic Database Diagnostic Monitor (ADDM).

 

The option stating you can identify dropping of an important user from the database is incorrect because the alert log file cannot be used to identify whether a user has been dropped from the database. The alert log file can identify when a tablespace, datafile, or redo log file has been dropped from the database, but it cannot identify when a user has been dropped from the database. You must use the data dictionary tables and views to determine whether users have been dropped from the database.

 

Reference:
1. Oracle University – Oracle Database 10g: Administration Workshop I – Chapter 5: Controlling the Database – Viewing the Alert Log
D17090GC10
Edition 1.0
March 2004
D39126

 

2. Oracle University – Oracle Database 10g: Administration Workshop I – Chapter 4: Managing the Oracle Instance – Viewing the Alert Log
D17090GC20
Edition 2.0
August 2005
D21638

 

3. Oracle Database Administrator’s Guide 10g Release 2 (10.2)
Part Number B14231-02
Chapter: 4 Managing Oracle Database Processes
Topic: Monitoring the Database Using Trace Files and the Alert Log
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/manproc.htm#sthref729

Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone
cmadmin

ABOUT THE AUTHOR

Posted in Archive|

Comment:

Leave a comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>