Oracle9i Database Administration: Manage an Instance

Audience

The intended audience for this course include Database administrators System administrators Network administrators and Technical support professionals. Suggested prerequisites include Oracle SQL: Basic SELECT Statements (61110) Oracle SQL: Data Retrieval Techniques (61111) Oracle SQL: DML and DDL (61112) Oracle PL/SQL: PL/SQL Basics (61113) Oracle PL/SQL: Procedures Functions and Packages (61114) Oracle PL/SQL: Database Programming (61115).

Objective

Upon completion of this course the student will understand:

• Identify the memory structures of the SGA and the information stored in the database and nondatabase files.
• Identify the connection procedures and the processes generated during database connection.
• Identify the stages in processing a query and the memory structures used in query processing.
• Identify the steps of DML processing and the memory structures involved in DML processing.
• Identify the uses of SCN and the features of a process commit.
• Identify the tasks of a DBA and the Oracle Enterprise Manager tools used by a DBA.
• Identify the OEM console components steps to set up these components and the functions of the OEM DBA tools.
• Identify the default DBA user accounts and set up authentication methods to validate users.
• Identify the parameters stored in the parameter file their uses and the rules followed while specifying the parameters.
• Identify the tasks performed in the stages of instance startup and shutdown.
• Identify the characteristics and parameters of dynamic performance views and display the current parameter values by using V$PARAMETER.
• Modify a dynamic initialization parameter by using the Oracle Instance Manager and manage user sessions by using the Oracle Instance Manager.
• Identify the characteristics of trace and alert files the parameters controlling the trace files and the contents of alert files.
• Identify the character-encoding schemes and the reasons for choosing the national character sets for the database.
• Identify the database initialization parameters the derived NLS parameters and the way to control the sort sequence.
• Retrieve the data dictionary information about the character sets and the NLS settings.

Topics Include

Unit 1: Oracle Architecture Components 1 - 2 hours

• Match the memory structures of the SGA with the information that they store.
• Match the mandatory background processes with their functions.
• Match the different types of files existing in a database with the information that they store.
• Match database-related files with the information that they store.
• Match the terms associated with establishing a database connection with their descriptions.
• Identify the characteristics of a user process.
• Identify the characteristics of a server process.
• Match the Oracle security types with their functions.
• Sequence the stages in processing a query.
• Identify the information stored in the shared pool components.
• Identify the characteristics of the database buffer cache.
• Identify the features of buffer cache advisory.
• Match the contents of the Program Global Area with their uses.
• Identify the steps in the execute phase of a given DML statement.
• Identify the uses of a rollback segment.
• Identify the characteristics of a redo log buffer.
• Identify the events that cause the Database Writer to write to the data files.
• Identify the events that cause the Log Writer to write to the redo log files.
• Identify the uses of system change numbers during commit processing.
• Sequence the steps that occur during the process of commit processing.
• Identify the advantages of the fast commit process used by the Oracle server.

Unit 2: Administration Tools 1 - 2 hours

• Identify the tasks of a database administrator.
• Match the utilities used by the DBA with the administrative tasks that they enable the DBA to perform.
• Identify the features of the Universal Installer.
• Match the features of the OEM architectural components with their functions.
• Match the OEM Console components with the tasks that they perform.
• Match the OEM services with their tasks.
• Sequence the steps performed to set up OEM for use.
• Match the OEM DBA Management Pack applications with the tasks that they enable you to perform.
• Match the components in the additional management packs with their functions.

Unit 3: Managing an Oracle Instance 2 hours

• Identify the characteristics of the default DBA user accounts.
• Set up a NT log on to the Oracle database without a password by using NT User Manager.
• Match the REMOTE_LOGIN_PASSWORDFILE parameters with their functions.
• Set up a password file authentication on an NT platform by using the ORAPWD utility.
• Change the SYS password by using the ORAPWD utility.
• Identify the uses of the parameters included in the parameter file.
• Identify the rules that govern the parameter values specified in the parameter file.
• Identify the essential parameters for an Oracle instance.
• Match the undo mode initialization parameters with their functions.
• Match the license parameters with their functions.
• Identify the commonly modified parameters of a parameter file.
• Identify the features of SPFILE.
• Identify the guidelines that you use to create a SPFILE.
• Identify the features of SPFILE in Real Application Clusters.
• Match the stage of instance startup with the correct description.
• Identify the methods that are used to start an instance.
• Start an Oracle instance by using the OEM Console.
• Change a database state by using the OEM Console.
• Identify the features of a quiesced database state.
• Match the shutdown stages with the tasks performed in each stage.
• Identify the conditions with which the instance is shutdown in each shutdown mode.
• Identify the features of dynamic performance views.
• Match the columns of the V$SPPARAMETER view with the data they store.
• Match the associated dynamic performance view with a given description.
• Display the current parameter values by using the V$PARAMETER dynamic performance view.
• Match the dynamic buffer cache parameters with the values they store.
• Modify a dynamic initialization parameter by using the OEM Console.
• Change the database mode by using the OEM Console.
• Terminate a user session by using the OEM Console.
• Identify the differences between an alert file and a trace file.
• Match the trace file parameters with the values that they store.
• Identify the information stored in a given alert file.

Unit 4: Globalization Support 2 hours

• Identify the features of Globalization Support.
• Match the character-encoding scheme classes with their descriptions.
• Identify the features of the character sets.
• Identify the combinations of the Globalization Support parameters used for specifying the default conventions and session characteristics.
• Match the derived Globalization Support parameters with their descriptions.
• Override the default Globalization Support behavior for an individual session by using the NLS_LANG environment variable.
• Change the Globalization Support settings for a session by using the ALTER SESSION command.
• Specify the linguistic sort type by using the NLS_SORT parameter.
• Identify the SQL statement that uses an SQL function and a Globalization Support parameter to generate the given output on its execution.
• Identify the features of various semantics.
• Select the tests that are performed on data during the scan.
• Identify the steps that are used in the scanning process.
• Retrieve the character sets for the database by using the nls_database_parameters view.
• Retrieve information about Globalization Support settings by using views.

Duration

6

Minimum Requirements

The CDROM version of this course requires:

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).
• At least a double speed CDROM drive.
• An MPC compliant sound card with attached speakers or headphones is recommended (Currently only the CDROM version supports audio).

• At least a 486DX 33Mhz CPU.
• Microsoft Windows 3.1 or higher and a Microsoft compatible mouse.
• At least 8MB RAM and 22MB available hard disk space or file server space.
• At least VGA graphics capability with a minimum 512K video RAM (1MB video RAM recommended).

Media