Troubleshoot Setup and Discovery

Troubleshoot Siebel Discovery

You can troubleshoot discovery of the Siebel entity through these steps:

1. Check the Discovery status window to see if the discovery process has generated Fatal or Critical errors.
   1. From the left pane in Oracle Management Cloud, select Administration.
   2. Click Discovery and select Discovery Job Status. All the discovered entities are listed along with the status of discovery in the Discovery status window.
   3. For the entity you want to check, click the status. The Discovery status window displays the status of discovery, summary of the discovery process, details of all the validations that were run during the discovery process along with results for each validation, and also a list of tasks on how to manually check the status of discovery.
   4. If the discovery process has thrown some Fatal / Critical errors, resolve and retry discovering the entity.
2. If the logs available in the console do not provide enough information, then check the agent logs and in the file gcagent_sdk.trc file, look for this message - Siebel Discovery finished. If this message doesn't appear, then the discovery might have failed. If you see the message, then monitor gcagent.log messages which promotes the entities to agent.

Warning Message: Discovery fails or Protocol is not set

After discovering the Siebel entity, you might see a warning for a Database entity with the message that the Protocol is not set, and the default protocol is selected as TCP. You can ignore this warning.