|
|
|
Questions and answers for Installation/Configuration
|
5. Installation/Configuration
|
| 5.1 Define OFA.
|
| 5.2 How do you
set up your tablespace on installation?
|
| 5.3 . What
should be done prior to installing Oracle (for the OS and the disks)?
|
| 5.4 You have
installed Oracle and you are now setting up the actual instance. You have been
waiting an hour for the initialization script to finish, what should you check
first to determine if there is a problem?
|
| 5.5 When
configuring SQLNET on the server what files must be set up?
|
| 5.6 When
configuring SQLNET on the client what files need to be set up?
|
| 5.7 What must
be installed with ODBC on the client in order for it to work with Oracle?
|
| 5.8 You have
just started a new instance with a large SGA on a busy existing server.
Performance is terrible, what should you check for?
|
5.9 What OS
user should be used for the first part of an Oracle installation (on UNIX)?
|
| 5.10 When
should the default values for Oracle initialization parameters be used as is?
|
| 5.11 . How
many control files should you have? Where should they be located?
|
| 5.12 How many
redo logs should you have and how should they be configured for maximum
recoverability?
|
| 5.13 WYou have
a simple application with no "hot" tables (i.e. uniform IO and access
requirements). How many disks should you have assuming standard layout for
SYSTEM, USER, TEMP and ROLLBACK tablespaces?
|
5.1 Define OFA.
|
|
OFA stands for Optimal Flexible Architecture. It is a method of placing
directories and files in an Oracle system so that you get the maximum
flexibility for future tuning and file placement.
|
5.2 How do you set up your tablespace on installation?
|
|
The answer here should show an understanding of separation of redo and rollback,
data and indexes and isolation os SYSTEM tables from other tables. An example
would be to specify that at least 7 disks should be used for an Oracle
installation so that you can place SYSTEM tablespace on one, redo logs on two
(mirrored redo logs) the TEMPORARY tablespace on another, ROLLBACK tablespace
on another and still have two for DATA and INDEXES. They should indicate how
they will handle archive logs and exports as well. As long as they have a
logical plan for combining or further separation more or less disks can be
specified.
|
5.3 What should be done prior to installing Oracle (for the OS and the disks)?
|
|
adjust kernel parameters or OS tuning parameters in accordance with installation
guide. Be sure enough contiguous disk space is available.
|
5.4 You have installed Oracle and you are now setting up the actual instance.
You have been waiting an hour for the initialization script to finish, what
should you check first to determine if there is a problem?
|
|
Check to make sure that the archiver isn?t stuck. If archive logging is turned
on during install a large number of logs will be created. This can fill up your
archive log destination causing Oracle to stop to wait for more space.
|
5.5 When configuring SQLNET on the server what files must be set up?
|
|
INITIALIZATION file, TNSNAMES.ORA file, SQLNET.ORA file
|
5.6 When configuring SQLNET on the client what files need to be set up?
|
|
SQLNET.ORA, TNSNAMES.ORA
|
5.7 What must be installed with ODBC on the client in order for it to work with
Oracle?
|
|
SQLNET and PROTOCOL (for example: TCPIP adapter) layers of the transport
programs.
|
5.8 You have just started a new instance with a large SGA on a busy existing
server. Performance is terrible, what should you check for?
|
|
The first thing to check with a large SGA is that it isn?t being swapped out.
|
5.9 What OS user should be used for the first part of an Oracle installation
(on UNIX)?
|
|
You must use root first.
|
5.10 When should the default values for Oracle initialization parameters be
used as is?
|
|
Never
|
5.11 How many control files should you have? Where should they be located?
|
|
At least 2 on separate disk spindles. Be sure they say on separate disks, not
just file systems.
|
5.12 How many redo logs should you have and how should they be configured for
maximum recoverability?
|
|
You should have at least three groups of two redo logs with the two logs each on
a separate disk spindle (mirrored by Oracle). The redo logs should not be on
raw devices on UNIX if it can be avoided.
|
5.13 . You have a simple application with no "hot" tables (i.e. uniform IO and
access requirements). How many disks should you have assuming standard layout
for SYSTEM, USER, TEMP and ROLLBACK tablespaces?
|
|
At least 7, see disk configuration answer above.
|
|