Skip Headers
Oracle® Enterprise Manager Exadata Management Getting Started Guide
Release 12.1 (12.1.0.1, 12.1.0.2, and 12.1.0.3)
Part Number E27442-04
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

3 Post-Discovery Configuration and Verification

Once the Oracle Exadata Database Machine has been discovered through Enterprise Manager Cloud Control 12c, you must complete post-discovery configuration on the following targets:

Remember:

You must remove the SNMP notification on the cell, InfiniBand switch, ILOM, Cisco switch, PDU, and KVM manually if you remove these targets from Enterprise Manager.

Starting with Exadata plug-in Release 12.1.0.3, when the Exadata Database Machine target is deleted through Enterprise Manager Cloud Control, there is an option to remove the SNMP notification from the cells and InfiniBand switches.

3.1 Set Up Compute Node Agent to Receive SNMP Notification

You must configure SNMP forwarding on each of the compute nodes being used as monitoring agents for other targets.

For the Enterprise Manager Agent to receive traps, an SNMP trap forwarder must be set up on the host where the Enterprise Manager Agent is running so that the forwarder utility can receive traps using port 162 and forward the same to the agent receivelet's listening port.

Note:

The Enterprise Manager Agent receivelet listening port is specified as the value of the EMD_URL property in the <AGENT_INST>/sysman/config/emd.properties file, where <AGENT_INST> is the location of the Agent's agent_inst directory.

Follow the steps below on the compute nodes being used to monitor other targets. Ideally, you should perform the steps on all compute nodes in preparation for a scenario when monitoring is moved to a compute node that was not previously being used to monitor other targets.

The following commands must be run as root user:

  1. Get the port value from EMD_URL property in the <AGENT_INST>/sysman/config/emd.properties file. This is the port at which receivelet will listen over UDP for traps (for this example, the port value is 3872).

  2. Confirm that the receivelet is listening on this port over UDP. An entry should be seen in the below command's output:

    netstat -an | grep 3872 | grep udp

  3. Run the following command to stop the forwarder utility:

    service snmptrapd stop

    Typically, the service command will be located in the /sbin directory.

  4. Add the following entry to the /etc/snmp/snmptrapd.conf configuration file:

    authcommunity log,execute,net <community string>
forward default udp:localhost:3872

  5. Run the following command:

    chkconfig snmptrapd on

  6. Run the following command to start the forwarder utility:

    service snmptrapd start

3.2 Configure Storage Cell SNMP for Enterprise Manager Monitoring

Exadata Storage Cell SNMP configuration is performed using the cellcli command and can be run in batch using dcli from a compute node.

Notes:

  • For Enterprise Manager Cloud Control 12c Bundle Pack 1 (BP1):

    The SNMP trap setup for Exadata Storage Cells is done automatically after finishing the guided discovery process.

  • For Exadata plug-in Release 12.1.0.2 and later:

    During the discovery process, you can optionally provide the necessary root credentials to set up SNMP trap for Exadata Storage Cells. If you have done so, then you can skip the remaining steps of this section and proceed with Configure and Verify SNMP for InfiniBand Switch Targets.

Using the ALTER CELL Command

While using the ALTER CELL command, all existing subscribers should be specified along with the new subscriber being added. Similarly, you can also modify the notificationPolicy or notificationMethod attributes.

While using the ALTER CELL command, the host= and community= attribute values should be quoted, and type= is NOT quoted.

If you are using the DCLI utility to set up SNMP alerting, then any command containing punctuation, which will be interpreted by the local shell, must be enclosed with double quotation marks. If the command includes the following characters, then outer quotation marks and escape characters are required:


$ (dollar sign)
' (quotation mark)
< (less than)
> (greater than)
( ) (parentheses)

The backslash (\) is the escape character that allows the characters to be passed to the CellCLI utility without being interpreted by the remote shell.

3.2.1 Check Current SNMP Configuration

Check the current SNMP configuration using the following cellcli commands:

  1. To list the current subscribers for SNMP:

    cellcli -e list cell attributes snmpSubscriber

    When correctly configured, this command should list the Master and non-Master agents for the cell target, for example:

    # cellcli -e list cell attributes snmpSubscriber
((host=[hostname.mycompany.com],port=3872,community=public),
(host=[hostname2.mycompany.com],port=3872,community=public))

  2. To list the currently configured notification methods:

    cellcli -e list cell attributes notificationMethod

    Possible values are snmp, mail and snmp,mail. When correctly configured, this command should return either snmp or snmp,mail, for example:

    # cellcli -e list cell attributes notificationMethod
snmp,mail

  3. To list the currently configured notification policy for SNMP:

    cellcli -e list cell attributes notificationPolicy

    Possible values are any or all of Critical, Warning, and Clear. When correctly configured, this command should return Critical, Warning, Clear, for example:

    # cellcli -e list cell attributes notificationPolicy
Critical,Warning,Clear

3.2.2 Configure SNMP Values Using cellcli

To set the values of snmpSubscriber, notificationMethod and notificationPolicy:

  1. Set the snmpSubscriber value:

    cellcli -e "alter cell snmpSubscriber=((host='[host name]',port=[port}),(host='[host name]',port=[port]))"

    Where [host name] and [port] values are Agents monitoring your cell targets.

    Note:

    Take special care not to overwrite existing settings for snmpSubsriber. If there are existing subscribers, then append the agent subscriptions. For example, if the cellcli -e list cell attributes snmpSubscriber command returned: 
    # cellcli -e list cell attributes snmpSubscriber
 ((host=ilm-asr1.example.com,port=162,community=public,type=asr))

    Then you must append the Agent subscriptions:

    #cellcli -e "alter cell snmpSubscriber=((host=ilm-asr1.example.com,port=162,
community=public,type=asr),(host='[host name]',port=[port]),(host='[host name]',port=[port]))"

  2. Set the notificationMethod value:

    cellcli -e "alter cell notificationMethod='snmp,mail'"

  3. Set the notificationPolicy value:

    cellcli -e "alter cell notificationPolicy='Critical,Warning,Clear'"

3.2.3 Configure SNMP Values Using dcli (optional)

The SNMP configuration commands can be run using dcli to perform the configuration in batch on all storage cells:

  1. Set the snmpSubscriber value:

    dcli -g cell_group -l root "cellcli -e \"alter cell snmpSubscriber=((host='[host name]',port=[port]),(host='[host name]',port=[port]))\""

    Where [host name] and [port] values are Agents monitoring your cell targets.

  2. Set the notificationMethod value:

    dcli -g cell_group -l root "cellcli -e \"alter cell notificationMethod='snmp,mail'\""

  3. Set the notificationPolicy value:

    dcli -g cell_group -l root "cellcli -e \"alter cell notificationPolicy='Critical,Warning,Clear'\""

3.2.4 Verify SSH Connectivity

Open a new terminal and verify whether the SSH connectivity was successfully established:

ssh -l cellmonitor <cell_ipaddress> cellcli -e 'list cell detail'

  • If you are not prompted for any password, then you can assume that the connectivity is established.

  • If you are asked to confirm whether you want to continue connecting, specify Yes.

3.2.5 Remove a Subscription

To remove the subscription, use the ALTER CELL command again by excluding the host name that you want to remove from the snmpsubscriber list.

Notes:

The SNMP receivelet listens on a single address and port for all monitored targets. The port is the UDP port with the same number as the TCP port used in the EMD_URL.

By default, the SNMP receivelet listens on all addresses; if the property SnmpRecvletListenNIC is set in the emd.properties file, the receivelet will attempt to resolve the value as either a name or IP address, and listen on only that address.

This parameter is independent of AgentListenOnAllNICs and EMD_URL because in some installations, the Agent may need to communicate with the OMS and with managed targets on different networks.

3.3 Configure and Verify SNMP for InfiniBand Switch Targets

The SNMP configuration for Enterprise Manager monitoring of InfiniBand Switches is done automatically as part of the Enterprise Manager guided discovery process. It is good practice, however, to verify that SNMP configuration has been successful.

Notes:

  • For Enterprise Manager Cloud Control 12c Bundle Pack 1 (BP1):

    The SNMP trap setup for Exadata Storage Cells is done automatically after finishing the guided discovery process.

  • For Exadata plug-in Release 12.1.0.2 and later:

    During the discovery process, you can optionally provide the necessary root credentials to set up SNMP trap for Exadata Storage Cells. If you have done so, then you can skip the remaining steps of this section and proceed with Configure the Compute Node ILOM SNMP for Enterprise Manager Monitoring.

To configure (if necessary) and verify the SNMP configuration for an InfiniBand Switch:

  1. Log in to the InfiniBand Switch ILOM web interface using the URL https://<ib_switch_hostname> as root.

    Note:

    Try using Internet Explorer if the console does not display all fields/values in your browser of choice.

  2. Click Configuration, then System Management Access, and finally SNMP.

  3. Ensure the following values are set:

    State=Enabled
Port=161
Protocols=v1,v2c,v3

    If you need to make changes, make sure you click Save.

  4. Click Alert Management.

  5. If not already listed, for each Agent that monitors the InfiniBand Switch target, select an empty alert (one that has the Destination Summary 0.0.0.0, snmp v1, community 'public') and click Edit. Provide the following values:

    Level = Minor
Type = SNMP Trap
Address = [agent compute node hostname]
Destination Port = [agent port]
SNMP Version = v1
Community Name = public

    Click Save.

  6. Verify the InfiniBand Switch SNMP configuration for Enterprise Manager monitoring:

    snmpget -v 1 -c <community_string> <hostname_of_IB_switch> 1.3.6.1.4.1.42.2.70.101.1.1.9.1.1.5

    For example:

    $ snmpget -v 1 -c public my_IB_switch.my_company.com 1.3.6.1.4.1.42.2.70.101.1.1.9.1.1.5
SNMPv2-SMI::enterprises.42.2.70.101.1.1.9.1.1.5 = INTEGER: 1

    Note:

    If the Timeout message is displayed as a output for the above command, then it means that the InfiniBand Switch is not yet configured for SNMP.

    Note:

    To remove the subscription: 
    echo "set /SP/alertmgmt/rules/12 destination='0.0.0.0' destination_port=0" | spsh

3.3.1 Set Up SNMP for InfiniBand Switch Targets Using Enterprise Manager

You can set up SNMP for InfiniBand Switch targets using the Enterprise Manager Cloud Control console:

  1. Navigate to the IB Network target (not the individual switches) and select Administration.

  2. Select the IB Switch target type, then one of the IB Switch targets.

  3. Select the Setup SNMP Subscription command, then select the management agent URL that monitors the InfiniBand switch target from the Agent URL list. Click Next.

  4. Provide credentials for the InfiniBand switch. Click Next.

  5. Review the details you provided. If there are no further changes, then click Submit.

Perform steps 1-5 for both the Monitoring Agent and Backup Monitoring Agent of the InfiniBand switch target.

3.4 Configure the Compute Node ILOM SNMP for Enterprise Manager Monitoring

The compute node ILOM targets are responsible for displaying a number of disk failure alerts for their respective compute node that are received as SNMP traps. For Enterprise Manager to receive those traps, the /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl script must be run to configure SNMP subscriptions for the agents that have been configured to monitor the compute node ILOM targets. This step is applicable to Exadata Plug-in Release 12.1.0.2 and later.

The exadata_mon_hw_asr.pl script is run as the root user with the -set_snmp_subscribers parameter to add SNMP subscribers. For example:

# /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers "(host=hostname1.mycompany.com,port=3872,community=public,type=asr,fromip=11.222.33.444),(host=hostname2.mycompany.com,port=3872,community=public,type=asr,fromip=12.345.67.890)"
Try to add ASR destination Host - hostname1.mycompany.com IP - 11.222.33.44 Port - 3872 Community - public From IP - 22.333.44.555
Try to add ASR destination Host - hostname2.com IP - 11.111.11.111 Port - 3872 Community - public From IP - 22.333.44.555

The script needs to be run on each compute node:

For example, if you have an X2-2 machine with compute node targets edbm01db01 through edbm01db08 and associated compute node ILOM targets edbm01db01-c through edbm01db08-c, then you would need to run the script once on each compute node - therefore, the script would be run eight times in total.

This is a good example of where Manual selection of Management Agents for targets is useful. If the first two compute nodes are always the Monitoring Agent and Backup Monitoring Agent, then it is easy to work out the values needed for -set_snmp_subscribers parameters, the host and port values would be the same for all compute nodes.

Important Note:

The exadata_mon_hw_asr.pl script, overwrites any existing SNMP subscriptions. While setting the SNMP subscribers, make sure that current subscribers are included in the new list of subscribers.

It is possible to use the exadata_mon_hw_asr.pl script to get the current set of subscribers using the -get_snmp_subscribers parameter.

For example:

# /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type=asr

Suppose the current list is:

(host=hostname1.mycompany.com,port=162,community=public,type=asr,fromip=11.222.33.444),
(host=hostname2.mycompany.com,port=162,community=public,type=asr,fromip=11.222.33.444)

Then new subscriptions can be added using the following command:

/opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -set_snmp_subscribers "(host=asrhostname1.mycompany.com,port=162,community=public,type=asr,fromip=11.222.33.444),
(host=asrhostname2.mycompany.com,port=162,community=public,type=asr,fromip=11.222.33.444),
(host=hostname1.mycompany.com,port=3872,community=public,type=asr,fromip=11.222.33.444),
(host=hostname2.mycompany.com,port=3872,community=public,type=asr,fromip=11.222.33.444)"

After adding the new subscribers, run the command exadata_mon_hw_asr.pl script with the -get_snmp_subscribers parameter to get the list of SNMP subscribers and verify the new SNMP subscriptions were added successfully. For example:

# /opt/oracle.cellos/compmon/exadata_mon_hw_asr.pl -get_snmp_subscribers -type=asr
(host=host1.mycompany.com,port=162,community=public,type=asr,fromip=10.10.10.226),
(host=host2.mycompany.com,port=162,community=public,type=asr,fromip=10.10.10.226),
(host=host3.mycompany.com,port=3872,community=public,type=asr,fromip=10.10.10.226)
,(host=host4.mycompany.com,port=3872,community=public,type=asr,fromip=10.10.10.226)

3.5 Verify Configuration for Oracle ILOM Server

To verify that Alerts can be successfully raised and cleared for the Oracle ILOM Server targets, perform the following steps:

  1. Log in to the Enterprise Manager Cloud Control console as an administrator.

  2. Click Targets and select Exadata. Select one of the Oracle ILOM Server targets using the Target Navigation pane.

    The ILOM target page will be displayed, showing the current status of that target as well as any incidents that have been raised for it.

  3. Raise an alert manually from the ILOM Server being validated. Run following command as root on the first database server in the cluster:

    ipmitool -I lan -H sclczdb01-c -U oemuser -P oempasswd -L OPERATOR event PS0/VINOK fail assert

    The output will be similar to:

    Finding sensor PS0/VINOK... ok
0 | Pre-Init Time-stamp | Power Supply #0x65 | State Asserted

    After running the above command, wait a few minutes then refresh the ILOM target page. An incident should appear in the Incidents section.

  4. Clear the alert raised in step 3. Run the following command as root on the first database server in the cluster:

    ipmitool -I lan -H sclczdb01-c -U oemuser -P oempasswd -L OPERATOR event PS0/VINOK nofail deassert

    The output will be similar to:

    Finding sensor PS0/VINOK... ok
0 | Pre-Init Time-stamp | Power Supply #0x65 | State Deasserted

    After running the above command, wait a few minutes then refresh the ILOM target page. The incident that was raised in step 3 should show as cleared in the Incidents section.

    Note:

    Do not forget to clear the alert raised in step 3, as it was raised for testing only and did not reflect a true fault condition!

  5. Repeat for the remaining configured ILOM service processors in your Oracle Database Machine.

3.6 Set Up SNMP for Cisco Ethernet Switch Targets

The Cisco Ethernet Switch must be configured to allow the Agents that monitor it to be able to both poll the switch and to receive SNMP alerts from the switch. To allow this, perform the following steps (swapping the example switch name dm01sw-ip with the name of the Cisco Ethernet Switch target being configured):

  1. Login to the Cisco switch and enter Configure mode:

    # telnet dm01sw-ip 
User Access Verification Password: 
dm01sw-ip> enable
Password:
dm01sw-ip# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
dm01sw-ip(config)#

  2. Enable access to allow the Agents monitoring Cisco Switch target to poll the switch.

    In the command, [EMagentIPaddr] is the IP address of the server where the Enterprise Manager Agent is running. The SNMP community specified must match the value provided when configuring the Cisco Switch target:

    dm01sw-ip(config)# access-list 1 permit [EMagentIPaddr]
dm01sw-ip(config)# snmp-server community <community_string> ro 1

  3. Set the monitoring Agent as the location where SNMP traps are delivered. The SNMP community specified must match the value provided during Enterprise Manager Cisco Switch Management Plug-In setup:

    dm01sw-ip(config)# snmp-server host <EMagentIPaddr> version 1 <community string> udp-port [EMagentRecvltListenPort]

    Where [EMagentRecvltListenPort] is the EMD_URL port of the emagent or SnmpRecvletListenNIC property value if it is enabled.

  4. Configure the Cisco Switch to send only environmental monitor SNMP traps:

    dm01sw-ip(config)# snmp-server enable traps envmon

  5. Verify settings and save the configuration:

    dm01sw-ip(config)# end
dm01sw-ip# show running-config
dm01sw-ip# copy running-config startup-config

3.6.1 Verify the Cisco Ethernet Switch SNMP Configuration

Run the snmpwalk command line utility or equivalent tool to verify the Cisco Switch configuration.

Run the following command to fetch and display the data from the Cisco switch:

snmpget –v 1 –c <community_string> <hostname_of_cisco_switch> 1.3.6.1.4.1.9.2.1.56.0

Note:

If a timeout message is displayed as an output for the above command, then it means that the Cisco Switch is not yet configured correctly.

3.7 Set Up SNMP for Power Distribution Unit (PDU) Targets

To enable Enterprise Manager to collect metric data and raise events for the PDU target, you must configure the PDU to accept SNMP queries from the Agents that monitor the PDU target. Also, appropriate threshold values for different phase values needs to be set on the PDU.

This section assumes that this is a first time configuration of the PDU. SNMP must be enabled and the trap section completed. Granting SNMP access to a different monitoring Agent IP address is an example where only the "Trap Host Setup" section needs to be changed.

  1. Log in to the PDU network interface through a browser at http://<pdu-name>, for example: http://edbm01-pdu1.example.com

  2. Click Net Configuration, then log in again.

  3. Scroll down until you reach the SNMP section of the frame.

    Note:

    The network interface for the PDU is a frame within a window. In order to scroll down on this page, you must see the scroll bar for the PDU frame as well as the outside scroll bar for the browser in which you accessed the PDU.

  4. If your PDU is not SNMP-enabled, select the SNMP Enable check box, then click Submit.

  5. Scroll to the NMS region of the frame.

  6. Enter the following in Row 1 under NMS:

    • IP: Enter the IP address of the first monitoring Agent

    • Community: Enter "public"

  7. Click Submit.

For details on configuring the PDU thresholds settings, see PDU Threshold Settings for Oracle Exadata Database Machine (See Doc ID 1299851.1) in My Oracle Support.

3.7.1 Verify the PDU SNMP Configuration

Use the snmpwalk command line utility or equivalent tool to verify the PDU configuration.

Run the following command to fetch and display the data from PDU:

snmpget –v 1 –c <community_string> <hostname_of_pdu> 1.3.6.1.4.1.2769.1.2.3.1.1.1.0

Note:

If a timeout message is displayed as an output for the above command, then it means that the PDU is not yet configured correctly.

3.8 Set Up SNMP for KVM Targets

The KVM needs to be configured to send SMNP traps to the Agents that monitor it.

Configure the KVM to send traps to monitoring agent host and receivelet listening port, the port value of EMD_URL property from the $ORACLE_HOME/sysman/config/emd.properties file (for example, 3872):

  1. Log in to the KVM management console through a browser at https://<kvm-name>, for example: https://edbm01sw-kvm.example.com

  2. Click SNMP under Target Devices in the left-hand navigation bar.

  3. Select the Enable SNMP check box and enter the appropriate community name in the Read, Write, and Trap fields (for example, enter "public").

  4. Click Save.

  5. Click Destinations under SNMP in the left-hand navigation bar.

  6. Enter the IP address of the Agent monitoring the KVM target.

  7. Click Save.

3.8.1 Verify the KVM SNMP Configuration (Base SNMP Configuration)

Run the snmptrapd command line utility or equivalent tool to verify the KVM configuration.

Follow the steps below on the monitoring Agent host:

  1. Log in as root.

  2. Run the following command:

    service snmptrapd stop

  3. Rename the /etc/snmp/snmptrapd.conf file to be /etc/snmp/snmptrapd.conf_bk to create a backup.

  4. Run the following command:

    snmptrapd -p 162

  5. Reboot the KVM (to generate SNMP traps).

  6. The terminal where the snmptrapd command was run should display the received trap which is generated by the KVM due to the reboot.

If step 6 is confirmed, the KVM has been configured correctly. Rename the backup file and restart the snmptrapd service:

  1. Use Ctrl+C to stop the snmptrapd command that was started in step 4 above.

  2. Rename the /etc/snmp/snmptrapd.conf_bk backup file to be /etc/snmp/snmptrapd.conf

  3. Run the following command:

    service snmptrapd start

3.8.2 Verify the KVM SNMP Configuration (SNMP Forwarding to Agent)

Follow the steps below to validate that the monitoring Agent can receive the SNMP traps generated by the KVM and convert the received traps to Enterprise Manager events.

  1. Log in to the KVM.

  2. Click Overview on the left side of the screen under Unit View, Appliance.

  3. Click Reboot.

  4. Click OK to confirm KVM reboot in the window that asks if you want to continue.

  5. In the Enterprise Manager Cloud Control console, go to the KVM target page. An Incident should be displayed for the KVM reboot event in the Incidents and Problems section of the page.

3.9 Oracle Exadata Database Machine Dashboard Creation

You can create a Database Machine dashboard to monitor the performance and usage metrics of the Database Machine system, its sub-components, as well as all the database system components residing on the Database Machine.

Dashboard Creation for Exadata Database Machine Plug-in Release 12.1.0.3 and Later

For Exadata Database Machine plug-in Release 12.1.0.3 and later, create the Database Machine Dashboard:

  1. Log in to Enterprise Manager.

  2. From the Enterprise Manager home page, click the Enterprise menu. Select the Reports submenu, then Jobs, and finally Activity.

  3. Select Database Machine Services Dashboard from the drop-down menu next to the Create Job option.

  4. Click Go.

  5. Enter a name of the job (for example, CREATE_DBM_JOB_1).

  6. Click Add and select the DBMachine target. After adding, make sure the target is selected by clicking on the check box next to it.

  7. Click the Parameters tab.

    Three options are provided through the drop-down:

    • Select Create if it is a new report.

    • Select Update for updating an existing report with new components.

    • Select Cleanup to remove services created by the Create job executed earlier.

  8. Finally, click Submit to perform the operation.

    A message CREATE_DBM_JOB_1 submitted successfully should display.

    You can monitor the job by clicking on the link corresponding to the job.

Dashboard Creation for Exadata Database Machine Plug-in Release 12.1.0.2 and Earlier

For Exadata Database Machine plug-in Release 12.1.0.2 and earlier, create the Database Machine Dashboard:

  1. Go to the following directory:

    /opt/oracle.SupportTools/emkit/exadata/dashboard/

  2. Run the following script:

    perl DashboardOperations.pl

Running this script will generate one Dashboard report per Database Machine system.

Note:

For details of script usage, please see the Dashboard Report Script README.

Creation of the dashboard assumes the use of the OMS emkit and can only be run from the OMS server that the kit was deployed on.

How to Make the Report "Public"

The generated report is accessible only by the Enterprise Manager user who creates it. To make the report public:

  1. Select the dashboard report from the list of reports shown after following the steps mentioned above.

  2. Click Edit.

  3. Select the Run report using target privileges of the report owner option under Privileges section in General tab.

  4. Click the Access tab.

  5. Select the Allow viewing without logging in to Enterprise Manager option.

  6. Click OK.

Find All Database Machine Reports

To find all Database Machine reports:

  1. Log in to Enterprise Manager.

  2. From the Enterprise Manager home page, click the Enterprise menu. Select Reports, then Information Publisher Reports.

  3. Search for the report name. Dashboard report names, one for each Database Machine, are displayed in the following format:

    [DBMachine Name]_DASHBOARD_REPORT

  4. Click on the report to view the dashboard report.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Feedback page
Contact Us