| |
Postinstallation Tasks
Module Objectives
Purpose
In this module, you will learn how to perform the postinstallation tasks
which configure your environment for some of the later courses in this
series.
Objectives
After completing this module, you should be able to:
 |
Create
a shortcut to your working directory |
 |
Configure
the Oracle Management Server |
 |
Log in to the Oracle Enterprise Manager Console |
 |
Set up the NT access privileges |
 |
Set the temporary tablespace to extend automatically
|
Prerequisites
Before starting this module, you should have:
Reference Material
The following is a list of useful reference material if you want additional
information about the topics in this module:
 |
Oracle Enterprise Manager Configuration Guide
|
Creating a Shortcut to Your Working Directory
Throughout the Oracle9i
by Example series, you will use many files and run quite a few SQL files
in SQL*Plus. To make it easier for you, you should create a shortcut to
SQL*Plus on your desktop that looks for files in your working directory.
To create this shortcut, perform the following steps:
| 1. |
Right-click on your desktop and create a shortcut. Enter
a pathname of D:\oracle\ora92\bin\sqlplusw.exe
or browse to that file, then click Next.

|
| 2. |
Specify a name for your shortcut and click Finish.

|
| 3. |
Right-click the new shortcut icon, open the Properties window,
and click the Shortcut tab.
|
| 4. |
Enter /nolog
after the target file, enter the SQL*Plus working directory D:\wkdir
in the "Start in" field, and then click OK.

|
Configuring the Oracle Management Server
To use some of the Oracle Enterprise Manager capabilities in later modules,
you need to configure the Oracle Management Server. To do so, perform
the following steps:
| 1. |
Select Start > Programs > Oracle - OraHome92
> Configuration and Migration Tools > Enterprise
Manager Configuration Assistant.
|
| 2. |
At the Welcome window, click Next.

|
| 3. |
Click Next to accept the default choice (Configure local
Oracle Management Server).

|
| 4. |
Make sure that Create a new repository is selected and click
Next.

|
| 5. |
Because you want to specify the name of the repository instance
that is created, click Custom and then Next.

|
| 6. |
Select In a new local database instance and click Change
SID....

|
| 7. |
Enter oms for the Global Database Name and the SID and click
OK.

|
| 8. |
Click Next.

|
| 9. |
Specify the username and password as oem
and click Next.

|
| 10. |
Click Yes to create the user. This username must be unique
across the environment.

|
| 11. |
Click Finish to create the database and the repository.

|
| 12. |
The Database Configuration Assistant will be invoked to create
the database.

|
| 13. |
Enter a password for SYS and SYSTEM. In the examples oracle
will be used as the password for both SYS and SYSTEM. After enter
your passwords click OK.

|
| 14. |
Next, the repository will be created.

|
| 15. |
When the repository creation is complete, click Close.

|
Change Initialization Parameters for OMS Database
Because you are running everything locally and you want to optimize the
performance of the OMS Database, you will want to change the spfileoms.ora
file for the OMS database instance you just created. Perform the following:
| 1. |
Open Enterprise Manager Console running Standalone. Logon to the
OMS database as sys/oracle
as sysdba.
Expand Instance, then select Configuration. Then click
the Memory tab.

|
| 2. |
Change the following parameters as follows then click Apply:
Shared Pool: 24 MB
Buffer Cache: 8 MB
Large Pool: 8 MB
Java Pool: 16 MB
Aggregate PGA Target: 10 MB
|
| 3. |
You will need to stop and start the database for the changes to
take effect. Click Yes.

|
| 4. |
Make sure that Immediate is selected and click OK:

|
| 5. |
After the shutdown is completed, click Close.

|
| 6. |
Click File > Exit.
|
| 7. |
Before you can connect to Enterprise Manager through the Oracle
Management Server, you need to make sure that the OracleOraHome92Agent
and OracleOraHome92ManagementServer services in your
Control Panel Services are running. Note: When an OMS Repository
is created, the services are started, but you may want to verify
that they are indeed running before moving on to the next task.

|
Logging In to the Enterprise Manager Console and Discovering your Node
Now that your Management Server has been created, you can log in to the
Oracle Enterprise Manager Console and discover your node.. To do this,
perform the following steps:
| 1. |
Select Start > Programs > Oracle- OraHome92
> Enterprise Manager Console.
|
| 2. |
At the login window, select Login to the Oracle Management Server
and specify sysman
as the administrator and oem_temp
as the password. The management server you just created is entered
by default in the Management Server field. Click OK.

|
| 3. |
Specify the new password as sysman
and click Change.

|
| 4. |
The Oracle Enterprise Manager Console will appear and the Discovery
Wizard will appear automatically. Click Next.
Note: When running the OMS and Agent locally, the local node will
automatically be discovered so the Discovery Wizard will not appear.

|
| 5. |
Enter your hostname as your node and click Next.

|
| 6. |
Your node will be discovered. When done, click Finish.

|
| 7. |
You will see your node in the console.

|
| |
 |
Configure the OMS for Comprehensive Reporting
The installation of the Oracle Management Server provides a preconfigured
HTTP Server, and all components required for reporting. You need only
to configure the OMS to enable communication between the HTTP Server and
OMS. As a result, the HTTP Server will know which OMS it needs to connect
to and the password of the administrator as well as which HTTP Server
is configured to run against the repository. Perform the following to
setup OMS for Report Publishing:
| 1. |
You will need to change the report user administrator password.
From the Console, select the Configuration pulldown then
select Manage Administrators. Select the REPORTS_USER
and click Edit.

|
| 2. |
Change the default password (oem_temp) to reports_user and
click OK. Then click Close.

|
| 3. |
Click Close.

|
| 4. |
Now you will need to configure the Web Server for Enterprise Manager
Reporting. If you HTTP Server is not already started, you can start
it by selecting Start -> Programs -> Oracle
- OraHome92 -> Oracle HTTP Server -> Start Oracle
HTTP Server powered by Apache.
|
| 5. |
Open a DOS Command prompt and enter the following command:
oemctl configure rws
|
| 6. |
Follow the instructions to configure the HTTP Server for Enterprise
Manager Reporting by providing the following:
Webserver Name: your node name
Port Number: 3339
Oracle Management Server: your node name
Password for the REPORTS_USER Administrator: reports_user
Would you like to specify an alternate location for historical data
[Y/N, default is N]: n
Enter Y to configure the Web Server

|
| 7. |
To see the Oracle Enterprise Manager Reporting Home Page, open
a browser and enter the following URL:
http://<hostname>:3339/
Then click Access Reports.


You will examine this reporting capability in a later module.
|
Setting Up Access Privileges
The Job system requires a user with the Log On As Batch Job privilege.
To set up this privilege, select the Operating System below for the list
of steps:
Setting Up the NT Access Privileges
The Job system requires a local NT user with the Log On As Batch Job
privilege. To set up this privilege, perform the following steps:
| 1. |
Select Start > Programs > Administration Tools > User
Manager.
|
| 2. |
Select User > New User.
|
| 3. |
Enter a username of ntoem
and a password of ntoem.
Select Password Never Expires, deselect all the other options,
and click the Groups button.

|
| 4. |
Select the Administrators and ORA_DBA groups and
click Add. Then select the Users group and click Remove.
Click OK twice.

|
| 5. |
Select Policies > User Rights and then click the Show
Advanced User Rights check box.
|
| 6. |
Select Logon as a batch job from the drop down box and click
Add.

|
| 7. |
Click Show Users.
|
| 8. |
Scroll down, select ntoem, and click Add.
|
| 9. |
The ntoem user has
been added. Click OK twice.

|
| 10. |
Select User > Exit.
|
| 11. |
Reboot your system. Note: When
your system is loaded, make sure you select your machine name as
the domain.
|
Skip to Next Topic
Setting Up Windows 2000 Access Privileges
The Job system requires a local Windows 2000 user with the Log On As
Batch Job privilege. To set up this privilege, perform the following steps:
| 1. |
Select Start > Settings > Control Panel.
|
| 2. |
Double clik Users and Passwords.
|
| 3. |
Click Add.

|
| 4. |
Type NTOEM for the User name. Click Next.

|
| 5. |
Enter a password. Example: NTOEM. Click Next.

|
| 6. |
Select Other, then Administrator from the drop down menu.
Click Finish.

|
| 7. |
Click the Advanced tab.

|
| 8. |
Click the Advanced button.

|
| 9. |
Double click Users in the right hand pane.

|
| 10. |
Right click NTOEM and select Properties.
|
| 11. |
Click the Members Of tab.
|
| 12. |
Click Add.

|
| 13. |
Select ORA_DBA. Click Add.

|
| 14. |
Click OK. Click Apply. Click Close.

|
| 15. |
Close Local Users and Groups.

|
| 16. |
Click OK.

|
| 17. |
From Control Panel, double click Administrative Tools.

|
| 18. |
Double click Local Security Policy.

|
| 19. |
Double click Local Policies in the right hand pane.

|
| 20. |
Double click User Rights Assignments from the right hand
pane.

|
| 21. |
Right click on Logon As Batch Job and select Security...

|
| 22. |
Click Add.

|
| 23. |
Select NTOEM. Click Add. Click OK. Click
OK.

|
| 24. |
Close Local Security Settings.

|
| 25. |
Close Administrative Tools.

|
Unlocking the Sample Schema Users
When the Oracle9i
database is installed, the Sample Schema database is created and the users
are locked for security reasons. In order to log in as a sample schema
user, you need to unlock the user. To do so, perform the following steps:
| 1. |
Unzip postinstall.zip
into your working directory.
|
| 2. |
Open the SQL*Plus session you just created and execute the
following commands:
connect / as sysdba
@unlock_users
SET TERMOUT OFF SET NEWPAGE 0 SET PAGESIZE 0 SET LINESIZE 132 SET ECHO OFF SET FEEDBACK OFF SET HEADING OFF
SPOOL unlockusers.sql
SELECT 'ALTER USER '|| username ||' identified by '|| username ||'
ACCOUNT UNLOCK;'
FROM dba_users
WHERE account_status LIKE '%LOCKED%';
SPOOL OFF
@unlockusers.sql
SET PAGESIZE 14
SET NEWPAGE 1
SET HEADING ON
SET FEEDBACK ON
SET ECHO ON
SET TERMOUT ON
|
Setting the Temporary Tablespace to Extend Automatically
For some of the later courses in this series, you will need to use a
lot of space in your temporary tablespace. The default temporary tablespace
size is 40 MB, thus you should set the tablespace to extend automatically
when it needs more space. To do this, perform the following steps:
| 1. |
From your SQL*Plus session, execute the following statements:
@alter_temp
SET TERMOUT OFF SET NEWPAGE 0 SET PAGESIZE 0 SET LINESIZE 132 SET ECHO OFF SET FEEDBACK OFF SET HEADING OFF
SPOOL altertemp.sql
SELECT 'ALTER DATABASE TEMPFILE '''|| a.name ||'''
AUTOEXTEND ON NEXT 5M MAXSIZE 200M;'
FROM v$tempfile a, v$tablespace b
WHERE b.name = 'TEMP'
AND a.ts# = b.ts#;
SPOOL OFF
@altertemp.sql
SET PAGESIZE 14
SET NEWPAGE 1
SET HEADING ON
SET FEEDBACK ON
SET ECHO ON
SET TERMOUT ON
|
Module Summary
In this module, you should have learned how to:
 |
Create
a shortcut to your working directory |
 |
Unlock
the sample schema users |
 |
Configure
the Oracle Management Server |
 |
Log in to the Oracle Enterprise Manager Console |
 |
Set up the NT Access Privileges |
 |
Set the temporary tablespace to extend automatically |
Copyright © 2002 Oracle Corporation. All Rights Reserved.
Close Window
|