6
Setting Up the Console

If you want to use another webserver other than the Oracle HTTP Server, the supported webservers are listed below:

• Apache 1.3.9 and higher on Unix

• Internet Information Server (IIS) 4.0 on Windows NT or Windows 2000

For information on configuring the above webservers, refer to Appendix F, "Configuring the Webserver and Directory Mapping".

Step 3 Run the Browser-Based Oracle Enterprise Manager

After performing the above steps, you are ready to run the browser-based Oracle Enterprise Manager.

1. Launch your web browser and enter the following URL regardless of which webserver you have installed.

   http://<webserver hostname>:<port number>/

   For example:

   http://jfox-sun.us.oracle.com:3339/
   

The index (EMWebSite.html) page will appear. The index page allows you to launch various products, documentation, and web sites.

• On this index page, enter the machine name for the Management Server to which you want to connect and click the application icon or name of the application you want to launch.

Figure 6-2 The EMWebSite.html Page
Text description of the illustration website.gif

3. If you are entering the URL for the first time, you must install the Oracle JInitiator plug-in Release 1.1.7.30.
   • On Netscape, you are automatically prompted to install the plug-in.

• On Microsoft Internet Explorer, you can click the "Download Plug-in" link on the index page to install the plug-in.

• Follow the instructions on the plug-in page to install the plug-in. Installing the plug-in may take several minutes depending on your machine and network environment.

• After installing the java plug-in, launch your web browser and enter the following URL:

  http://<webserver hostname>:<port number>/

  The index (EMWebSite.html) page will appear. The index page allows you to launch various products, documentation, and web sites.

• On this index page, enter the machine name for the Management Server to which you want to connect and click the application icon or name of the application you want to launch.

• Then a dialog will appear, which explains the following:
  • You will not be able to close the Oracle Enterprise Console 2.2 screen without stopping the Console, DBA Studio, or SQL*Plus Worksheet since the application has been launched from this browser window.

  • You can exit the EMWebSite without exiting the Console, DBA Studio, or SQL*Plus Worksheet.

  Once the java plug-in is installed, the Oracle Enterprise Manager Login dialog will appear.

8. If you are logging in to Oracle Enterprise Manager for the first time, type in the default credentials (administrator name and password).

   Administrator = sysman

   Password = oem_temp

   These credentials are for the default Super Administrator account. The first time you start Enterprise Manager, you must login as this Super Administrator. After other administrator accounts have been created using the Super Administrator account, you can login as a different administrator.

You can return to the index (EMWebSite.html) page to launch documentation, release notes, Quick Tours, and other web sites, and you can exit the index page without closing the Console.

• Bookmark the URL.

Setting Up the Event System

Beginning with Oracle 8.0.6 databases and higher, the OEM_MONITOR role is created by the Oracle database creation scripts. This role permits access to database functionality within Enterprise Manager running events against a database (tablespace full, buffer cache hit ratio) or browsing through the objects in a database via the Console Navigator tree. These types of functionality require database credentials on which to perform these operations. Rather than granting the powerful DBA role to the database credentials, many administrators prefer to provide only the necessary privileges required to do these operations. Granting the OEM_MONITOR role to the database credentials, ensures that the user has the minimum sufficient privileges required for these operations.

For database users on 7.3.x databases, you need to define the OEM_MONITOR role manually.

Here are the steps you need to perform:

1. Create a role called OEM_MONITOR

   drop role OEM_MONITOR;
   create role OEM_MONTOR:
   
   

2. Grant the "connect" role to OEM_MONITOR

   grant connect to OEM_MONITOR;
   
   

3. Grant the system privileges "analyze any" and "create table" to OEM_MONITOR

   grant analyze any to OEM_MONITOR;
   grant create table to OEM_MONITOR;
   
   

4. Create the SELECT_CATALOG_ROLE role as defined in sc_role.sql.

5. Grant the SELECT_CATALOG_ROLE to the OEM_MONITOR role

   grant select_catalog_role to OEM_MONITOR;
   

You are now ready to grant the OEM_MONITOR role to the database user that will be used as "database preferred credentials" in Enterprise Manager. In addition to granting the OEM_MONITOR role to a user, you must also ensure that the QUOTA for the user account is set to UNLIMITED.

The "Continued Row" event test needs to analyze results into a table so it needs both the "analyze any" and "create table" privileges.

Setting Up the Job System

This section includes information about setting up the Console for jobs.

Creating a Windows NT or Windows 2000 User Account for Running Jobs

In order for the Intelligent Agent to execute jobs on a managed node

• a Windows NT or Windows 2000 user account must exist that has the advanced user right, "logon as batch job." The privilege can be assigned to an existing local or domain user, or a new Windows NT or Windows 2000 user.

• the preferred credentials for the node must be set for that user in the Oracle Enterprise Manager Console. Refer to "Setting Up Preferred Credentials for Managed Services" on page 6-20.

• the user must have read/write permissions to ORACLE_HOME\NETWORK directory as well as read, write, update, and delete permissions to the TEMP directory or the ORACLE_HOME directory.

Creating a Windows NT or Windows 2000 user account is required to permit many of the components to allow the Intelligent Agent node to submit jobs to the server node.

You must create a Windows NT or Windows 2000 user account for every managed node. Follow one of the three procedures listed below.

Creating a New Windows NT or Windows 2000 User Account

To create a new Windows NT or Windows 2000 user account on the Windows NT or Windows 2000 machine where the Intelligent Agent is installed and grant the "log in as batch jobs" privilege to this user, perform the procedure below.

1. Select the User Manager from the Administrative Tools via the Windows NT or Windows 2000 Start Menu. Refer to the Windows NT or Windows 2000 documentation for information on the tools.

2. Select New User from the User menu and check for the following:
   • The "User Must Change Password at the Next Logon" option box is not checked

   • "SYSTEM" or "system" cannot be used for the user name.

3. Under the Policies menu of the User Manager Windows NT or Windows 2000 utility, select the User Rights option.

4. Check the "Show Advanced User Rights" box.

5. Select "Logon as a batch job" from the list of privileges.

6. Give the selected user this privilege.

Assigning Privileges to an Existing Windows NT or Windows 2000 User Account

Alternately, to assign privileges to an existing local user account, perform the following steps.

1. Choose the user on the User Manager panel and check for the following:
   • The "User Must Change Password at the Next Logon" option box is not checked

   • "SYSTEM" or "system" is not used for the user name.

2. Under the Policies menu of the User Manager Windows NT or Windows 2000 utility, select the User Rights option.

3. Check the "Show Advanced User Rights" box.

4. Select "Logon as a batch job" from the list of privileges.

5. Add the advanced user right to this user.

6. Click the Add button.
   1. Fill in the "List Names From" field: (choose your domain)

   2. Click Show Users button.

   3. In the listbox, choose the domain user.

   4. Click Add.

   5. Click OK.

7. In the User Rights Policy window, click OK.

Configuring a Windows NT or Windows 2000 Domain User as Your Intelligent Agent User

Alternately, to configure a domain user as your Intelligent Agent user, perform the following steps.

1. Under the Policies menu of the User Manager Windows NT or Windows 2000 utility, select the User Rights option.

2. Check the "Show Advanced User Rights" box.

3. Select "Logon as a batch job" from the list of privileges.

4. Click the Add button.
   1. Fill in the "List Names From" field: (choose your domain)

   2. Click Show Users button.

   3. In the listbox, choose the domain user.

   4. Click Add.

   5. Click OK.

5. In the User Rights Policy window, click OK.

Setting Up Preferred Credentials for Managed Services

In order for the Intelligent Agent to execute jobs or monitor events on a managed node, each administrator must specify valid credentials for the services running on that node. Preferred credentials are set from within the Console for each managed service.

To set preferred credentials in the Console, follow the steps outlined below:

1. Select System > Preferences > Preferred Credentials to view the services available for management using the Intelligent Agent.

2. For each managed service that requires authentication, enter the appropriate credentials for the service, such as username, password and role.

3. If some services of a particular type require the same credentials, use the <DEFAULT> credentials selection for that service type to have those credentials used by all services of that type.

   For example, if Administrator_1 has a username and password of admin1/pass1 on all the databases that he manages, he only needs to enter admin1/pass1 as his credentials in the <DEFAULT> database entry. All databases administration tasks will use these <DEFAULT> credentials.

   Furthermore, if he has just one database which requires different credentials from admin1/pass1, he can enter different credentials for that database by selecting that specific database.

The Intelligent Agent authenticates the user name and password for all jobs and all events. If you have not set the preferred credentials correctly, jobs and events may fail.

For Windows NT or Windows 2000 users, you must set the preferred credentials for the node (where the Windows NT or Windows 2000 Intelligent Agent resides) to be the same as the user that is set up to "Logon as a batch job."

Configuring and Starting the Paging Service

If you want to be notified via paging in Oracle Enterprise Manager, you must explicitly install the Oracle Enterprise Manager Paging Server. This paging service is not installed as part of the base Oracle Enterprise Manager installation; it is installed through a Custom installation type. Refer to the installation guide provided with the database release for more details.

Only one paging service installation is required if you wish to utilize paging for notification purposes within Oracle Enterprise Manager.

The paging service supports either numeric or alphanumeric pagers and utilizes the following paging service protocols (for alphanumeric pagers only).

• TAP (Telocator Alphanumeric Protocol)

• GSM (Global System for Mobile Communications)

• FLEXTD

To use alphanumeric paging, you need a phone number to call for the modem at the paging service provider and the pin number for your pager. Contact your paging service provider for the phone number to call. It is the number for the modem for sending pages.

Your paging provider may also have a feature for sending email to your pager. If you have that feature, you can configure an administrator's preferences for notification to use email, and specify your pager as the email receiver. This method will also work with many providers for sending notification to a cell phone.

Configuration of the paging service is not automatic. Follow the steps below to configure paging.

Setting Up Paging

On the machine from which you want to run the paging service, follow these instructions:

1. Install a modem.

2. Specify modem settings.
   1. Go to Start > Settings > Control Panel > Modems.

   2. Specify how your calls are dialed by clicking Dialing Properties from the Modems Properties page and then setting the following parameters:
      • From what area code you are dialing

      • From what country you are dialing

      • How you access an outside line. If you are not required to dial a number to access an outside line, leave this field blank.

   3. Set the Maximum Speed parameter by clicking Properties from the Modems Properties page. Oracle recommends setting this parameter to 9600K Baud; however, you should find the baud rate setting optimal for your system.

   Note: A baud rate higher than 9600 may result in the loss of data with the paging service carrier. The baud rate of 9600 for your modem is only a recommendation. You must find the baud rate setting which is optimal for your system.

   3. Install the Oracle Enterprise Manager Paging Server. Refer to the installation guide provided with the database release for information.

   4. Start the Paging Service.
      1. Go to Start > Settings > Control Panel > Services.

      2. Select the Oracle<ORACLE_HOME_NAME>PagingService and click Start.

      You can also start the paging service by typing the following at a command prompt

      oemctrl start paging
      

   Adding a Paging Server

   Note: Only Super Administrators can add a paging server; this functionality is not available to regular administrators.

   1. From the Enterprise Manager Console, select Preferences from the System menu. The Edit Administrator preferences property sheet appears. Click the Notification tab to access the Notification page.

   2. From the Notification page, highlight Paging Servers from the tree list.

   Figure 6-3 Administrator Notification Preferences: Paging Server
   Text description of the illustration pageserv.gif

   3. Right-click Paging Servers to obtain the pop-up menu and choose the Add item or click the Add Server icon on the detail view to the right.

   4. When the Add Paging Server dialog appears, enter the name of the machine on which the paging server runs.

   Figure 6-4 Add Paging Server Dialog

   
   
   Text description of the illustration addpages.gif
5. Press the OK button.

   If the Console is unable to find the paging server with the given hostname, an error appears, saying "VD-4362: Could not add paging server, as paging server <hostname> could not be reached."

   If the paging server is found, a new paging server object is added under the "Paging Server" object in the tree list. The new paging server will have no paging carrier. You must add at least one paging carrier in order for paging to function.

   Adding Paging Carrier

   Note: Only Super Administrators can add a new paging carrier; the functionality is not available to regular administrators.

   1. From the Notification page, highlight Paging Carriers from the tree list.

   2. Right-click Paging Carriers to obtain the pop-up menu and choose the Add Carrier item or click the Add Carrier icon on the detail view to the right.

   3. When the Add New Paging Carrier dialog appears, fill in the fields.

   Figure 6-5 Add Paging Carrier Dialog

   
   
   Text description of the illustration addcarri.gif

   Once defined, you can view the paging carriers by expanding the appropriate paging server and carrier objects in the tree list.

   • Name

     Paging carrier name. Field accepts alphanumeric characters and underscores.

   • Type

     Type of paging carrier. Enterprise Manager supports alphanumeric or numeric.

   • Protocol

     TAP, FLEXTD, or GSM. Protocol selection is only available if the carrier type is Alphanumeric.

   • Connection Properties
     • Country Code: The country code used to dial the pager if the call is international.

     • Area Code: Area code used the by country in which the pager is located.

     • Number: Local dialing number of the pager.

     • Suffix: Permits identification of voice messages from a paging carrier and allows the person being paged to choose from several options when using a touch tone phone. For example, commas can be used as pauses. The Suffix field accepts the following characters: integers, commas, pound sign, and the star (asterisk).

   Note: This option is only available if the paging carrier type is set to Numeric.

   • Dialing Properties
     • Timeout (in seconds): Maximum dialing time allowed for a successful page.

     • Delay (in seconds): Time delay before dialing.

   • Press the OK button.

   Specifying Paging Notification Preferences

   While the Super Administrator configured the paging server and its carrier(s), all administrators who want page notifications must specify their own notification preferences by following the steps below:

   1. Log on to the Console.
      1. Go to System > Preferences > Notification. Then highlight Paging on the tree list to view Paging Preferences on the detail view to the right.

      2. Select a paging service carrier from the drop down list.

      3. Enter the Pin number for your alphanumeric pager. If you have a numeric pager, leave this field blank.

      4. Test the paging notification by clicking the Test button.

   2. Set your notification schedule. If you neglect to do so, you will not receive page notifications.
      1. Within the Console go to System > Preferences > Schedule

      2. Choose when you want to be notified by paging. If you do not select any days/hours to be notified by paging, you will never receive a page.

      Refer to the Oracle Enterprise Manager Administrator's Guide for instructions on how to set up the notification schedule.

   Other Paging Server Operations

   Removing a Paging Server

   Note: Only Super Administrators can remove a paging server; the functionality is not available to regular administrators.

   1. From the Notification page, highlight the paging server object you want to remove from the tree list.

   2. Right-click the paging server object to obtain the pop-up menu and choose the Remove item or click the Remove Server icon on the detail view to the right.

      A warning dialog appears, saying "Remove Paging Server <servername>?"

   3. Click "yes". The Console will check if anyone is currently using any carrier from the paging server. If not, all paging carriers will be removed, and the paging server will be removed as well. Otherwise an error dialog appears, saying "The paging server cannot be removed because at least one carrier is being used.

   Viewing Information on Paging Server

   Note: Only Super Administrators can view information on a paging server; the functionality is not available to regular administrators.

   From the Notification page, left-click the paging server object.

   The detail view to the right will show information about that paging server such as the paging carrier names, the pager types, the protocol, and whether or not they are in use.

   Pinging a Paging Server

   Note: Only Super Administrators can ping a paging server; the functionality is not available to regular administrators.

   To check the status of the paging server, follow the steps below:

   1. From the Notification page, highlight the paging server you want to ping.

   2. Right-click the paging server object to obtain the pop-up menu and choose the Ping item or click the Ping Server icon on the detail view to the right.

   Querying Status of the Paging Service

   To check the paging status, right-mouse click the carrier name to access the Ping Paging Service item in the context-sensitive menu.

   Stopping the Paging Service

   Stop the paging service from the Windows NT or Windows 2000 Services Control Panel.

   You can also stop paging service by typing

   oemctrl stop paging
   

   Removing a Paging Carrier

   Note: Only Super Administrators can remove a paging carrier; the functionality is not available to regular administrators.

   1. From the Notification page, highlight the paging carrier object you want to remove from the tree list.

   2. Right-click the paging carrier object to obtain the pop-up menu and choose the Remove item or click the Remove Carrier icon on the detail view to the right.

      A message appears, saying "Remove Paging carrier <carrier name>?"

   3. Click "yes." The Console checks if anyone is current using the carrier. If not, it will be removed and the notification tree updated.

   Editing a Paging Carrier

   Note: Only Super Administrators can edit a paging carrier; the functionality is not available to regular administrators.

   1. From the Notification page, select the paging carrier object. The paging carrier information appears in the detail view to the right.

   2. Make the changes.

   3. Click the OK button.

      The Console will validate all the carrier information, update the notification tree. All administrators who have selected to use this carrier will automatically inherit the new changes.

      If the validation fails, an error dialog appears stating which entry failed to validate and what type of input is expected. When you click the "OK" button in the error dialog, all the paging carrier's entries are set back to their original values.

   Viewing Information about a Paging Carrier

   From the Notification page, select the paging carrier object. The paging carrier information appears in the detail view to the right.

   Testing a Paging Carrier

   1. Right-click the paging carrier object and choose the "Test" menu item. A dialog appears, asking for the PIN.

   2. Enter the PIN if your pager is an alphanumeric pager and click "OK" to continue. If it is a numeric pager, leave this field blank.

   Setting Up Email and Paging Notification

   Setting Up the SMTP Gateway

   Oracle Enterprise Manager supports sending email notifications using SMTP. To allow administrators to use email for notification, the Super Administrator must specify the SMTP mail gateway that is used for the SMTP email system.

   SMTP is a TCP/IP-based mail protocol and requires that TCP/IP services are set up on the Console machine.

   From the Enterprise Manager Console, the Super Administrator must select Configure SMTP Gateway from the System menu and supply the following information.

   Field	Description
   SMTP Mail Gateway:	Enter the name of the machine on which the SMTP mail gateway resides, such as mailserver.company.com.
   Sender's SMTP Mail Address:	Enter the sender name you want to identify yourself as, such as Enterprise Manager Mail. Note: Some SMTP servers cannot process spaces. If that is the case with your environment, then use quotes, such as "Enterprise Manager Mail". The name specified will then appear as the sender of the email notification.

   If the Super Administrator does not specify the above information, when any administrator tries to configure his email notification, an error message will appear.

   Setting Up Email and Paging Notifications

   Then, each administrator must define preferences for his or her own email or paging notifications. From the Enterprise Manager Console, select Preferences from the System menu. The Edit Administrator preferences property sheet appears. Click the Notification tab to access the Notification page.

   The Notification page allows you to set up paging and email notification methods for the administrator. This page consists of a hierarchical tree list and a detail view area that changes according to the object selected in the navigator. The tree list consists of three to four top-level objects, depending on the type of user that is logged in:

   • Filters (Selected by default)

   • Email

   • Paging

   • Paging Servers (available only to Super Administrators)

   Figure 6-6 Administrator Notification Preferences
   Text description of the illustration notipref.gif

   Filters

   Notification filters allow each administrator to specify when to send an email notification as opposed to a page notification as a result of a job or event status change.

   • Event Notification Filter: The Event Notification Filter allows you to filter email/pages sent to an administrator according to the event's level of severity. Filtering is set at the user level by checking or unchecking the Email/Page options on this property sheet page. You can select any combination of the following levels of event severity. For example, you can set filtering so that an administrator is notified via email if there is a warning and notified via the paging system if there is an alert. Selecting all levels of severity provides no filtering.
     • Alert

     • Warning

     • Clear

     • Node Down

     • Reassign

   Job Notification Filter

   The Job Notification Filter allows you to filter email/pages sent to an administrator according to job status. As with the Event Notification Filter, filtering is set at the user level by checking or unchecking the desired option. Selecting all job statuses provides no filtering.

   • Start

   • Complete

   • Fail

   • Delete (Job removed)

   Email

   This page allows you to specify notification parameters for email.

   Figure 6-7 Administrator Notification Preferences: Email
   Text description of the illustration notemail.gif

   • Receiver's Email: Enter the email address of the administrator to whom the mail is being sent.

   • Subject Prefix: Enter an optional prefix that is appended to the E-mail subject. That allows administrators to quickly identify messages from Enterprise Manager in their mail.

   • Limit message length: Allows you to specify the maximum message body length of an E-mail notification. By default, this length is unlimited.

   • Current Definition: Displays the current settings for format and content of E-mail notifications. To set or change the default parameters, expand the Email object in the tree list. You can select format and content options for the Subject line and Message Body. You can further expand the Message Body object to specify options at the Per Event Test level.

   • Test: Click the Test button to check the validity of E-mail configuration. A message displays to inform you of the status of the test email.

   Email Subject Definition

   This page allows you to select the content and format of the email subject line. By default, Type, Name, and Status are selected. You use the left/right arrows to move items back and forth between the Available and Selected lists.

   Once an item has been selected, you can control the order in which the item appears by selecting it in the list and using the up/down arrows (located to the immediate right of the Selected list) to reposition the item within the list.

   Note: The following information also applies to inserting content into the Email/Paging message body.

   • Available: Lists available content.

   • Selected: Lists currently selected content and the order in which the content should be displayed.

   • Use Abbreviated Format: For Type (Job or Event), Status, and Target Type, you can select the Use Abbreviated Format option. The following abbreviations are used by the system:

   Target Type

   • DB for Database

   • L for Listener

   • N for Node

   Status

   • S for Started

   • CO for Completed

   • F for Failed

   • D for Deleted

   • W for Warning

   • A for Alert

   • C for Cleared

   • NU for Node Unreachable

   • R for Reassign

   Timestamp Format

   This option is available if Timestamp is chosen from the Selected list. You use the pull-down menu to select one of the pre-defined formats.

   Do not include titles

   When selected, classification titles such as Status, Service Name, and Timestamp are omitted from the message.

   Append job output

   When selected job output is appended to the end of the notification. For instances where job output is large, you may want to specify a limit to the message length. If the job output pushes the notification length past the specified limit, then the job output will be truncated, not the message itself.

   Paging

   This page allows you to specify notification parameters for paging.

   Figure 6-8 Administrator Notification Preferences: Paging
   Text description of the illustration notpage.gif

   • Carrier: After a paging server is specified by a Super Administrator and the name of the paging carrier service and the corresponding paging carriers have been configured, select the name of the paging carrier service from the pull-down list.

   • PIN: Enter the PIN for your paging carrier. This entry is only required for alphanumeric pagers.

   • Limit message length: Allows you to specify the maximum message length of paging notifications. By default, this length is set to 256 characters.

   • Current Definition: Displays the current settings for format and content of paging notifications. To set or change these parameters, expand the Paging object in the tree list. You can select format and content options for the Message Body. You can further expand the Message Body object to specify options at the Per Event Test level.

   • Test: Click the Test button to check the validity of the paging configuration. For alphanumeric pagers, enter the PIN number. For numeric pagers, the message "700" is sent.

     Click on the Send button to send a test page to the specified pager. A message informs you of the status of the test page.

     If the test fails, check the log file. If tracing is enabled for paging, you can also view the paging trace log file in the ORACLE_HOME\sysman\log directory on the machine which has the paging server.

   Paging Status Codes for Numeric Pages

   Numeric pages need to be interpreted as follows:

   For job notifications, you will receive a 3 digit number which indicates the job status.

   For event notifications you will receive the status code.

   The event status and job status codes are listed as follows:

   100 = Job Started

   200 = Job Completed

   300 = Job Failed

   400 = Job Deleted

   500 = Event Cleared

   600 = Event Warning

   700 = Event Alert

   800 = Event Node Down

   900 = Event Unknown

   1000 = Event Assignee Changed

   Email/Paging Message Body Definition

   This page allows you to select the content and format for the body of the email or page message. By default, Name, and Status are selected. You use the left/right arrows to move items back and forth between the Available and Selected lists.

   Figure 6-9 Administrator Notification Preferences: Email/Paging Body
   Text description of the illustration empgbody.gif

   Expanding the Message Body object in the navigator and selecting per Test allows you to use a subset of the following option settings on a per test basis. Refer to "Email Subject Definition" on page 6-35 for more information on manipulating message content.

   • Available: Lists available content.

   • Selected: Lists currently selected content.

   • Use Abbreviated Format: For Type (Job or Event), Status, and Target Type, you can select the Use Abbreviated Format option. The following abbreviations are used by the system:

   Target Type

   • DB for Database

   • L for Listener

   • N for Node

   Status

   • S for Started

   • CO for Completed

   • F for Failed

   • D for Deleted

   • W for Warning

   • A for Alert

   • C for Cleared

   • NU for Node Unreachable

   • R for Reassign

   Timestamp Format

   This option is available if Timestamp is chosen from the Selected list. You use the pull-down menu to select one of the pre-defined formats.

   Do not include titles

   When selected, classification titles such as Status, Service Name, and Timestamp are omitted from the message.

   Paging Server

   The paging server object is available only to Super Administrators.

   This page lists all available paging servers currently recognized by Enterprise Manager. The multi-column list consists of two columns: the name of the paging server and whether the paging server is currently being used.

   Figure 6-10 Administrator Notification Preferences: Paging Server
   Text description of the illustration pageserv.gif

   Refer to the "Configuring and Starting the Paging Service" on page 6-22 for more information about the following topics:

   • Adding a Paging Server

   • Adding Paging Carrier

   • Removing a Paging Server

   • Viewing Information on Paging Server

   • Removing a Paging Carrier

   • Editing a Paging Carrier

   Except for the Add Paging Server icon, the icons are grayed out unless a specific paging server is selected from the list.

   Configuring the Console If Using a Dialup Line to Connect to the Management Server

   Note: Dynamic IP addresses attributed by DHCP are not supported on nodes running the Management Server or an Intelligent Agent. DHCP is supported only on Enterprise Manager clients.

   When the Console connects over a dialup line, the Console machine obtains a dynamic IP address. This dynamic IP address needs to be sent by the operating system (Windows 2000, Windows NT, Windows 95, Windows 98) to the application (Console).

   In order for the operating system to return the correct IP address, the network communication protocol (TCP-IP) needs to be configured to obtain the IP address using the Dynamic Host configuration protocol. This setting is specified as follows:

   1. Go to Start menu-> Settings

   2. Select Control Panel -> Network

   3. Select Protocols

   4. Double-click TCP-IP Protocol.

   IMPORTANT:

   You must make note of your previous settings in order to return to those settings when you connect the same machine to the network via ethernet. Copy the Settings specified in IP Address, Subnet Mask and Default Gateway to a file.

   5. On the IP Address page, select "Obtain an IP address from a DHCP Server."

   6. Click the OK button.

   7. Connect to the network via your dial-up line. You will now be successfully able to launch the Console.

   Note: If you are not running from a web browser, you may need to restart your system after making the changes.

   Configuring a Remote Database for Backup or SYSDBA Administration

   Before using one of the backup management wizards or starting up or shutting down a database through Oracle Enterprise Manager, you need to set up your database for remote SYSDBA management.

   The following procedure outlines the operations you may need to perform on both the server and client if they have not been performed already through the Database Configuration Assistant.

   Additional Information:

   Refer to the operating system-specific documentation for your Oracle database for the exact name of the password file creation utility for your system.

   Server Side (Windows NT or Windows 2000)

   1. From the command prompt, run the ORAPWD executable to create a new password file.

      Note: The name of the ORAPWD executable depends on the database version. Oracle 7.3.X: ORAPWD73 Oracle 8.0.X: ORAPWD80 Oracle 8.1.X: ORAPWD

      For example,

      $ORACLE_HOME\bin\orapwd file=<fname> password=<password> entries=<users>
      

      where

      fname is the name of password file (mandatory),

      password is the password for SYS (mandatory),

      entries is the maximum number of distinct DBAs and OPERs (optional),

      There are no spaces around the equal-to (=) character.

      The <fname> will be created in the Oracle_Home/Database directory.

   2. Edit the init.ora file located in the Oracle_Home/Admin/<SID>/pfile directory. Add or change the following parameter remote_login_passwordfile=exclusive in the init.ora file.

   3. Shut down your database and then restart it from Control Panel > Services.

   4. Grant SYSDBA and/or SYSOPER roles to users who will be performing remote DBA operations.

      Note: The grant is necessary even if the user already has this privilege set. The GRANT command will flush the username and the password to the password file if one is defined. After each reset/recreate of the password file, grants for all users with SYSOPER and SYSDBA have to be reset to ensure that the password file has all the necessary usernames stored.

   5. Check which users are defined in the password file by using the V$PWFILE_USERS view. The view will show which users are currently present in the password file.

   Server Side (UNIX)

   1. Login as the owner of the software (for example, Oracle) and set your environment variables. The following is a CSH example.

      setenv ORACLE_HOME  the_database_home
      setenv ORACLE_SID   the_database_sid
      
      

   2. Change to the dbs directory in your Oracle home.

      cd $ORACLE_HOME/dbs
      
      

   3. Edit the init.ora file. Add or change the following parameter remote_login_passwordfile=exclusive in the init.ora file.

   4. Shut down your database and then restart it.
      1. Start SQL*Plus Worksheet.

      2. Log in as a user with the SYSDBA role.

      3. Type

         shutdown immediate 
         startup
         
         

      Shutting down the database is necessary for the database to pick up the changes in the init.ora file.

   5. Run the ORAPWD executable to create a new password file.

      Note: The name of the ORAPWD executable depends on the database version. Oracle 7.3.X: ORAPWD73 Oracle 8.0.X: ORAPWD80 Oracle 8.1.X: ORAPWD

      For example,

      $ORACLE_HOME/bin/orapwd file=<fname> password=<password> entries=<users>
      

      where fname is the name of password file (mandatory),

      password is the password for SYS (mandatory),

      entries is the maximum number of distinct DBAs and OPERs (optional).

      There are no spaces around the equal-to (=) character.

      The <fname> will be created in the $Oracle_Home/dbs directory.

   6. Grant SYSDBA and/or SYSOPER roles to users who will be performing remote DBA operations

      Note: The grant is necessary even if the user already has this privilege set. The GRANT command will flush the username and the password to the password file if one is defined. After each reset/recreate of the password file, grants for all users with SYSOPER and SYSDBA have to be reset to ensure that the password file has all the necessary usernames stored.

   7. Check which users are defined in the password file by using the V$PWFILE_USERS view. The view will show which users are currently present in the password file.

   Setting the Format of Dates

   To set up how the order of the date elements are to be displayed in the Oracle Enterprise Manager Console and DBA Studio, you must set the following environment variables:

   • NLS_DATE_FORMAT for the month, date, and year

     mm-dd-yyyy
     
     

   • NLS_TIMESTAMP_FORMAT for the date and time

     mm-dd-yyyy hh:mi pm
     

   Note: You can only set up the order in which the elements are to be displayed; you cannot set up what is to be displayed.

   Windows Platforms

   To set the environment variable:

   set NLS_DATE_FORMAT = mm-dd-yyyy
   set NLS_TIMESTAMP_FORMAT = mm-dd-yyyy hh:mi pm
   
   

   UNIX

   To set the environment variable:

   setenv NLS_DATE_FORMAT mm-dd-yyyy
   setenv NLS_TIMESTAMP_FORMAT mm-dd-yyyy hh:mi pm