“Connection to the Database Server Failed” Error
If you received an error message resembling the following after getting all element details, verify that the database instance is running:
The connection to the database server failed. Check that the Oracle instance 'OIQ3 on host '192.168.1.162:1521 is running correctly and has the management software for Oracle installed correctly.
Assume you received the error message listed above. You would want to verify the following:
•Oracle instance OIQ3 on host 192.168.1.162 port 1521 is running.
•The management software for Oracle is installed on the server running the Oracle instance. One of the installation's tasks is to create an APPIQ_USER user account with enough privileges for the software to view statistics from the database.
Once you have verified these items, run Discovery Data Collection again. If you continue to see the error message, contact customer support.
An Element is Not Listed on the Discovery Data Collection Page
If HP SE cannot identify an element passed to it by the HP SIM Connector, the element is not listed when you run Discovery Data Collection. HP SE may have failed to identify the device due to an incorrect credential.
Check the
You can test the element credentials in HP SE to verify that they are correct.
1.Select Tools > Storage Essentials > Home.
2.Click Discovery and then click Setup.
3.Click Add Address.
4.Enter the IP address or DNS name and the credentials you want to test. Click OK.
5.Click Test.
6.When you are finished, select the IP address or DNS name you added and click the Delete icon.
7.Repeat the steps to discover the element. See ”Discovering Elements” on page 27 for instructions.
DCOM Unable to Communicate with Computer
Sometimes the following error message appears in the event log of the management server when the software is monitoring a Brocade switch:
DCOM was unable to communicate with the computer 192.168.10.21 using any of the configured protocols
where 192.168.10.21 is the IP address of the Brocade switch. Ignore this error message.
706 Troubleshooting