Oracle Enterprise Manager Configuration Guide
Release 2.1
A75685-01

Library
Product
Contents
Index

Prev Next

6
Setting Up the Console

The Oracle Enterprise Manager Console is a graphical interface for administrators. From the Console, you can perform the following tasks:

This chapter discusses the topics listed below:

Starting the Enterprise Manager Console

The Console gives you a central point of control for the Oracle environment through an intuitive graphical user interface (GUI) that provides powerful and robust system management.

After you have created a repository and started your Management Server and Intelligent Agent, you are ready to start the Enterprise Manager Console.

To start the Enterprise Manager Console, perform the following steps.

  1. Start the Enterprise Manager Console.

    • On Windows platforms:

      From the Start menu -> Oracle-<Oracle_Home_Name> -> Enterprise Manager, select Console.

    • On UNIX:

      At the command line, enter 

      oemapp console

      The command string is case-sensitive and must be entered with lowercase characters.

      Note:

      You can also start Enterprise Manager from a web browser. Refer to "Running Oracle Enterprise Manager from a Web Browser" on page 6-6 for information on installing the Enterprise Manager web site and setting up your web browser to run Enterprise Manager. 

    The Oracle Enterprise Manager Login screen appears, prompting you for your administrator name and password.

  2. 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 the super administrator. After other administrator accounts have been created using the super administrator account, you can login as a different administrator.

  3. Select the name of the node where the Management Server is running from the pull-down list. The Management Server on the node you select must be one which is configured with the repository you want to access.

Note:

You must have the Management Server installed and configured before performing this step. 

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

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

Note:

In order to run Enterprise Manager from a web browser, you must remove any proxies that are configured for use by your web browser. You can do this by either:

  • Choosing to connect directly to the network using the web browser's proxy setting, or

  • Choosing to manually configure the proxy, but specify not to use the proxy for the webserver that runs the Enterprise Manager web site.

If you should experience problems with the proxies, refer to "Troubleshooting the Web Browser" on page C-16. 

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

    http://<webserver hostname>:<port number>/
    oem_webstage/EMWebSite.html    .

    For example: 

    http://jfox-sun:3339/oem_webstage/EMWebSite.html

Note:

The Oracle Application Server Listener port number is 3339. 

  1. 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.

Note:

Once you are prompted to install the plug-in and you exit or cancel, you will no longer be prompted to install it the next time you launch the browser-based Enterprise Manager. In this situation, to install the plug-in, enter the URL:
http://<webserver hostname>:<port number>/oem_webstage/java-plugin/
install_win32.html. 

  1. 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.

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

Note:

Launching the browser-based Oracle Enterprise Manager for the first time may take several minutes, and if you are running a dial up connection, download times will typically be longer and vary based on the line speed. 

  1. 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 the super administrator. After other administrator accounts have been created using the super administrator account, you can login as a different administrator.

Note:

If you are not able to connect to the Management Server specified, you must return to the EmWebSite.html page to enter a different Management Server machine name. You cannot simply enter a new Management Server machine name at the Oracle Enterprise Manager Login screen. 

  1. Bookmark the URL.

General Setup

This section includes information about setting up the Console for jobs, email and paging notification, and remote SYSDBA management:

Setting Up the Job System

This section contains the following topics:

Creating a Windows NT User Account for Running Jobs

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

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

Note:

If you do not set up the "logon as batch job" privilege, you will receive the "Failed to authenticate user" message when you run jobs on the node. 

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

Creating a New Windows NT User Account

To create a new Windows NT user account on the Windows NT 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 Start Menu. See the Windows NT 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" is not used for the user name.

  3. Under the Policies menu of the User Manager NT 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 NT 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 NT 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 NT Domain User as Your Intelligent Agent User

Note:

The NT Domain User works only if the machine is a primary domain controller (PDC); otherwise, jobs will fail with VNI-2015 "authentication error." In all non-PDC environments the account must be local to the machine. 

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

  1. Under the Policies menu of the User Manager NT 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.

Note:

If you have both a local and a domain user with the same name, the local user takes precedence. 

Note:

If you have a domain user set up, you must set the domain password to be the same as the local password in order for scheduled jobs to run when they are submitted using the domain user account.  

Setting Up Preferred Credentials for Managed Services

In order for the Intelligent Agent to execute jobs or monitor for 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 many events that it runs. If you have not set the preferred credentials correctly, jobs and events may fail.

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

Setting Up Email Notification

Setting Up the SMTP Gateway

Oracle Enterprise Manager supports sending email notifications using SMTP. To allow administrators to use email for notification, you 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, 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 you do not specify the above information, when an 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.

Complete this property sheet page to set up paging and email notification methods for the administrator. You can also send a test page or email with the Test options on this page.

Paging Information

Item  Description 

Carrier: 

After a node containing paging services has been discovered, select the name of the paging carrier service from the pull-down list.  

Pin: 

Enter the paging personal identification number (PIN) for your page. A PIN is only required for alphanumeric pagers, and not for numeric pagers. This entry is required for the GSM, TAP, and FLEXTD protocols for alphanumeric pagers. For GSM, the PIN is the actual phone number of the administrator. For numeric pagers, enter the pager number. 

Test: 

To test the validity of the paging information, select the paging service from the pull-down menu, enter the PIN number (if needed), and click the Test button. A message appears informing you of the status of the page.If the test fails, check the paging services configuration file (paging.cfg). Refer to "Configuring and Starting the Paging Service" on page 6-20 for explicit instructions on paging setup and configuration. You can also view the paging trace log file in the ORACLE_HOME\sysman\log directory if tracing is enabled for paging on the machine which has the Intelligent Agent Paging Extensions. 

Email Parameters

Item  Description 

Receiver's Mail: 

Enter the email address of the administrator to whom email notification will be sent.  

Test: 

Click the Test button to check the validity of the mail information. A message displays to inform you of the status of the test email. If the test fails, check the email configuration. If tracing has been enabled for the Management Server, you can also view the mail trace log file in the ORACLE_HOME\sysman\log directory. 

Subject Prefix: 

Enter an optional prefix that is added to the email notifications. This allows you to further differentiate notifications from the Enterprise Manager Console that are sent to administrators. 

Event Notification Filter

The Event Notification Filter allows you to filter email/pages sent to administrators according to the event's level of severity. Filtering is set at the user level through Administrator Preferences dialog. You can select any combination of the following levels of event severity. Selecting all levels of severity provides no filtering.

Job Notification Filter

The Job Notification Filter allows you to filter email/pages sent to administrators according to job status. As with the Event Notification Filter, filtering is set at the user level through the Administrator Preferences dialog. Selecting all job statuses provides no filtering.

Configuring and Starting the Paging Service

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

Note:

Paging Service Agent Extensions are only supported on Windows NT. 

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).

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.

Note:

You must have a modem installed on the Windows NT machine that you are running the paging service. 

  1. 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 baud may result in the loss of data with the paging service carrier. The baud rate of 9600 baud for your modem is only a recommendation. You must find the baud rate setting which is optimal for your system. 

    1. Install the Paging Service Agent Extensions. Refer to the installation guide provided with the database release for information.

    2. The installation of the Paging Service Agent Extensions provides a template configuration file, paging.cfg.template, located in the ORACLE_HOME\sysman\config directory. Review this template, which contains detailed instructions and examples on how to define the configuration properties specific to your carrier and service provider for configuring your paging service.

    3. Copy the paging.cfg.template file to the paging.cfg file, which is also located in the ORACLE_HOME\sysman\config directory. This is the Oracle Home of the database where the Intelligent Agent is installed. Oracle recommends copying this file (not renaming it) in order to retain paging configuration information. If you do not copy this file, all comments concerning paging configuration will be removed. In addition, when updates to Enterprise Manager software are made, any configuration will be lost and not retrievable.

    4. Based on the instructions in the paging.cfg.template file, modify the paging.cfg file according to your paging needs and save it. Refer to the Table 6-1, "Paging Configuration Properties" for summary information about the paging configuration properties. The paging.cfg.template file contains 14 properties, but not all of these properties require a value and certain properties are only applicable to certain types of pagers (numeric or alphanumeric).

    5. Restart the Intelligent Agent.

      1. Go to Start > Settings > Control Panel > Services.

      2. Select the Oracle<ORACLE_HOME_NAME>Agent service, click Stop and then click Start.

    Note:

    Whenever paging configuration changes are made (additions or deletions), the Intelligent Agent must be restarted. 

    On the machine from which you run the Management Server, follow these instructions:

    1. Ensure the Oracle Management Server is running. If it is not running, you must start it.

      1. Go to Start > Settings > Control Panel > Services.

      2. Select the Oracle<ORACLE_HOME_NAME>ManagementServer service and click Start.

    Note:

    Configuring the paging service is independent of the management server. Only when you want to start the paging service do you require that the management server be up and running. 

    Property  Can be set for Numeric Pagers  Can be set for Alphanumeric Pagers   Required  Comments 

    CARRIER_NAMES 

    Yes 

    Yes 

    Yes 

    Value cannot contain spaces 

    PAGER_TYPE 

    Yes 

    Yes 

    Yes 

    Value can be either NUMERIC or ALPHANUMERIC 

    COUNTRY 

    Yes 

    Yes 

    Yes 

    If dialing a DBA in the same country as the paging carrier, set value equal to that country's country code.

    For example, if dialing a DBA in the United States and the paging carrier is in the United States, set value =1.

    If dialing a DBA in India and the paging carrier is in India, set value =91.

    If dialing a DBA in a different country as the paging carrier, you need to obtain not only the DBA's country code but also the code for dialing out of the paging carrier's country.

     

    COUNTRY (cont.) 

     

     

     

    For example, if dialing a DBA in the United States (country code 1) and the paging carrier is in Brazil (use 00 to dial out), you would set value =001.

    If dialing a DBA in Spain (country code 34) and the paging carrier is in Germany (use 00 to dial out), you would set value =0034.

    Value cannot contain any extra punctuation or spaces. 

    AREA_CODE 

    Yes 

    Yes 

    Yes 

    Set value to the DBA's area code.

    Value cannot contain any extra punctuation, such as parentheses
    ( '( )' ). 

    PHONE_NUMBER 

    Yes 

    Yes 

    Yes 

    Set value to the number that needs to be dialed to send a page.

    This number can be either the number of the paging carrier or the direct number to the pager itself (the latter case would not have a PIN).

    Value cannot contain any extra punctuation, such as dashes ( '-' ), periods ( '.' ) or spaces. 

    TIMEOUT 

    Yes 

    Yes 

    No 

    Total time taken for a page to complete. Numeric paging will timeout after the specified number of seconds in the timeout property if the page has not been completely sent.

    Timeout must always be greater than the time it takes to send a page.

    Do not set the timeout to a very high value as numeric pagers will wait for "timeout" number of seconds before they terminate.

    If value is left blank, the paging service will use the modem's default setting.

    Oracle recommends setting the value = 60. 

    CONNECTION_DELAY 

    Yes 

    No 

    No 

    Set value to the number of pauses that will be established on the phone line before the page message is sent.

    The duration of a pause is modem-specific and typically used when the service carrier is not fast enough to receive a message.  

    SUFFIX 

    Yes 

    No 

    Yes 

    Set value if your paging carrier has a voice prompted message.

    Use commas as pauses to indicate the time to wait before choosing an option.

    For example, if you want to establish four pauses and press 1 before sending the message, you set value =,,,,1

    If the voice prompted message requires pressing pound after option selection to start sending the message, then you set value =,,,1# 

    PROTOCOL 

    No 

    Yes 

    Yes 

    Value can be either TAP, FLEXTD, or GSM 

    OEM.MANAGEMENT_SERVER 

    Yes 

    Yes 

    No 

    Set value only if using a remote Management Server.

    Enter the name of the machine where your Management Server is running. This is the Management Server you log in to.

    OEM.MANAGEMENT_SERVER=
    <oms-hostname> 

    OEM.MANAGEMENT_SERVER (cont.) 

     

     

     

    Notes on Multiple Management Servers:You cannot configure multiple management servers in the paging.cfg file. When paging starts up, it will only read the second one if you have entered two management servers. Multiple management servers use the same paging service regardless of what is in the paging.cfg file because that information is stored in the repository. If the management server listed in the paging.cfg were to fail in a dual-management-server environment, paging will continue without needing to be restarted because it bound to the listed management server at start up.  

    OEM.MANAGEMENT_SERVER (cont.) 

     

     

     

    		 If the management server listed in the paging.cfg were to fail in a dual-management-server environment and if at some point the other management server also fails (or the paging service fails), the paging service will not start until you have listed the second management server in the paging.cfg file, assuming that the first management server also was not restarted at some point before the failure. 

    OEM.MANAGEMENT_SERVER.BOOTPORT 

    Yes 

    Yes 

    No 

    Set value only if not using default value of 7771.

    Value needs to be an integer.  

    TRACING.ENABLED 

    Yes 

    Yes 

    No 

    Set value for debugging purposes; paging service will then track what paging is occurring by writing trace statements for all telephone line handling and any successes or failures.

    Value can be either TRUE or FALSE.

    If value =TRUE then you must specify a value for the property TRACEFILENAME and a value for the property TRACING.LEVEL.

    If value =FALSE then you need not specify values for TRACEFILENAME and TRACING.LEVEL. 

    TRACING.LEVEL 

    Yes 

    Yes 

    No 

    Set value to specify the detail of trace information to collect if tracing is enabled.

    Value can be either 5 (user level which collects critical messages and error messages), 3 (admin level which collects critical, error, and warning messages) or 2 (level which collects maximum trace information). 

    TRACEFILENAME 

    Yes 

    Yes 

    No 

    Set value for where to write tracing output if tracing is enabled.

    Oracle recommends setting the value =PAGING_LOG.TRC.

    By default, this file is located in the Intelligent Agent's ORACLE_HOME\
    SYSMAN\LOG\ directory. 

    Note:

    You cannot leave the COUNTRY and AREA_CODE property entries blank even if the paging service and the DBA are in the same country or if the paging service and the DBA are in the same area code. If you leave the entries blank, paging notification will not function.  


    Example 1

    For example, if you have and/or want the following:

    • numeric paging

    • paging service should register with a remote Oracle Management Server on a non-default boot port of 7774

    • DBA located in Australia (country code 61)

    • paging service located in New Zealand (use 00 to dial out of country)

    • DBA's pager number - with area code - is (800) 555-1234

    • paging service should establish four pauses before sending the page message

    • paging service takes 60 seconds to send a page to the paging carrier

    • paging carrier has voice prompted message and the paging service should choose option 1 after four pauses

    • tracing not enabled

    Your PAGING.CFG file would look like the following: 

    
CARRIER_NAMES=CARRIER_NUMERIC_PAGER 
OEM.MANAGEMENT_SERVER=nsulliva.us.oracle.com 
OEM.MANAGEMENT_SERVER.BOOTPORT=7774 
CARRIER_NUMERIC_PAGER.COUNTRY=0061 
CARRIER_NUMERIC_PAGER.AREA_CODE=800 
CARRIER_NUMERIC_PAGER.PHONE_NUMBER=5551234 
CARRIER_NUMERIC_PAGER.CONNECTION_DELAY=4 
CARRIER_NUMERIC_PAGER.TIMEOUT=60 
CARRIER_NUMERIC_PAGER.PAGER_TYPE=NUMERIC 
CARRIER_NUMERIC_PAGER.SUFFIX=,,,,1 
CARRIER_NUMERIC_PAGER.TRACING.ENABLED=FALSE


    Example 2

    For example, if you have and/or want the following:

    • alphanumeric pager with GSM protocol

    • DBA located in Norway (country code 47)

    • paging service located in Sweden (use 009 to dial out of country)

    • DBA's pager number - with area code - is (800) 666-1234

    • paging service takes 75 seconds to send a page to the paging carrier

    • tracing enabled to the maximum level and to write to PAGINGLOG.TRC file

    Your PAGING.CFG file would look like the following: 

    
CARRIER_NAMES=CARRIER_ALPHANUMERIC_PAGER 
CARRIER_ALPHANUMERIC_PAGER.COUNTRY=00947 
CARRIER_ALPHANUMERIC_PAGER.AREA_CODE=800 
CARRIER_ALPHANUMERIC_PAGER.PHONE_NUMBER=6661234 
CARRIER_ALPHANUMERIC_PAGER.TIMEOUT=75 
CARRIER_ALPHANUMERIC_PAGER.PAGER_TYPE=ALPHANUMERIC 
CARRIER_ALPHANUMERIC_PAGER.PROTOCOL=GSM 
OEM.TRACING.ENABLED=TRUE 
OEM.TRACING.LEVEL=2 
TRACEFILENAME=PAGINGLOG.TRC

    Example 3

    If you have the following in your modem settings:

    • Outside line: 5 for local

    • Outside line: 9 for long distance

    • Area Code: 650

    • Location: USA

    Your PAGING.CFG file should have the following: 

    COUNTRY=1
AREA_CODE=650
PHONE_NUMBER=6380899

    The number dialed will be 5 6380899.

    If in the modem settings your area code was 210, the number dialed would be 9 1 650 6380899.

    The "1" dialed for long distance is automatically computed based on the area code and country settings specified in control panel -> modem -> dialing properties.

    Note:

    Example 3 is not a complete example. It only shows how to set the COUNTRY, AREA_CODE, and PHONE_NUMBER. 


    Example 4

    For example, if you have and/or want the following:

    • numeric pager

    • DBA located in the US (country code 1)

    • paging service located in the US

    • DBA's pager number - with area code - is (650) 645-8989

    • paging service should establish 4 pauses before sending the page message

    • paging service has voice prompted message and the paging service should choose option 1 after 4 pauses, then choose option 3 after 5 pauses. 

      CARRIER_NAMES=SERVICE1 
PAGER_TYPE=NUMERIC
SERVICE1.SUFFIX=,,,,1#,,,3#
SERVICE1.CONNECTION_DELAY=4
SERVICE1.COUNTRY=1
SERVICE1.AREA_CODE=650
SERVICE1.PHONE_NUMBER=6458989

    The above example causes the following number to be dialed: 

    16506458989 , , , , 1# , , , 3# , , , , 123456
<--number--><-------suffix----><|><--message-->
                                connection Delay

    Note:

    Example 4 is not a complete example and does not include all required properties. You must add all necessary properties. 

    Starting the Paging Service

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

    1. 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

    On the machine from which you run the Enterprise Manager Console, follow these instructions:

    1. Log on to the Console.

    2. Discover the Node on which you configured the paging service or refresh discovery for that Node. The Paging Service should then appear underneath the discovered or refreshed Node as well as under a new Paging Service folder.

      See the Oracle Enterprise Manager Administrator's Guide for instructions on how to perform discovery.

    3. Set paging notification preferences. Each administrator who wants paging notification must follow these steps.

      1. Within the Console go to System > Preferences > Notification.

      2. Select a paging service Carrier from the drop down list. What is listed here depends on what was set in the PAGING.CFG file on the Intelligent Agent machine.

      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 Test.

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

    4. Set administrator notification schedule. Each administrator who wants paging notification must follow these steps.

      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.

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

    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 NT Services Control Panel.

    You can also stop paging service by typing 

    oemctrl stop paging

    Paging Status Codes for Numeric Pages

    Numeric pages need to be interpreted as follows:

    For job notifications, you will receive a 6 digit number. The first 3 digits indicate the job-id. The last 3 digits indicate job status.

    For event notifications you will receive the event ID with the status code.

    The job and event IDs are internal numbers not shown on the Console.

    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

    If JJJ= job id then, 

    JJJ100 => job started for job# JJJ 
JJJ200 => job completed for job# JJJ
JJJ300 => job failed for job# JJJ

    For example, if 001100 is displayed on your numeric pager, then you know that job id 001 just started. If 001300 appears, then you know job id 001 just failed.

    If EE= event ID then, 

    EE500 => event cleared for event # EE

    For example, if 7500 is displayed, you know that event number 7 had a status change and the status is now cleared.

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

    Note:

    DHCP is not supported for Oracle Enterprise Manager on nodes running the Management Server or the Intelligent Agent. It is supported only on 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 NT, Windows 95, Windows 98) to the application (Console).

    In order that the operating system 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. Select Control Panel -> Network

    2. Select Protocols

    3. Select TCP-IP Protocol-> Properties

    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.

    1. Select "Obtain an IP address from a DHCP Server."

    2. Apply your changes.

    3. Configure the listener.ora file with the new dynamic IP address obtained by the machine. You must add the following entry: 

      (ADDRESS=
    (PROTOCOL= TCP)
     (HOST= dynamic host name)
     (Port= 1521)
)

Note:

The listener.ora file must be configured when the repository is on the dialup line. 

  1. 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 (NT)

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

    $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.

Server Side (UNIX)

  1. Login as ORACLE and set your environment variables. 

    setenv ORACLE_HOME your_oracle_home
setenv ORACLE_SID your_oracle_sid

Note:

This example assumes that you have set up your database as ORACLE. 

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

    cd $ORACLE_HOME/dbs
  2. Run the ORAPWD executable to create a new password file.$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.
  1. Edit the init.ora file. Add or change the following parameter remote_login_passwordfile=exclusive in the init.ora file.

  2. 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
  3. Grant SYSDBA and/or SYSOPER roles to users who will be performing remote DBA operations

Prev Next
Oracle
Copyright © 2000 Oracle Corporation.
All Rights Reserved.

Library
Product
Contents
Index