6 Troubleshooting

For troubleshooting issues related to Oracle Exadata Database Machine, see Troubleshooting the Exadata Plug-in in Oracle Exadata Database Machine Getting Started Guide.

List of members of the cloud target does not show Database Instance

From cloud target home page, use the left navigation icon to view the navigation panel. Expand the list of available targets in the navigation panel, locate your database instance, and check if it belongs to a cluster database.

If the database belongs to a cluster database, then this is an expected behavior. It is not associated to the cloud target explicitly as a system member.

List of members of the cloud target does not show Cluster DB

All the hosts that are part of the cluster must be mentioned in the discovery properties file. To resolve the issue, add the missing host in the refresh procedure properties file and refresh the cloud target. See Refresh the Cloud Target After Discovery.

List of members of the cloud target does not show Storage Servers

Discovery is usually skipped in one of the following scenarios:

• Credentials are not supplied in the discovery properties file. See Discover the Cloud Target Using emcli.
• IP's of the storage servers are typically listed in the file /etc/oracle/cell/network-config/cellip.ora which is located in one of the hosts mentioned in the discovery properties file. Discovery will be skipped if the file is not present on any of the hosts.
• Credentials are incorrect. See Create Credential Set.
• exacli is not installed on any of the hosts.

To resolve the issue, try one of the following:

• Ensure that proper named credentials are created and provided in the property file.
• Ensure that exacli is installed on each of the hosts listed in the property file that was used for discovering the cloud target.