Connectivity Agent Fails Frequently If Competing with Oracle Database Classic Cloud Service for Resources

If the connectivity agent is installed on the same virtual host as Oracle Database Classic Cloud Service, the agent competes with the database for resources. If the host is undersized or physical resources are insufficient, the connectivity agent can fail due to a lack of physical memory. This scenario may require the connectivity agent to be restarted frequently.

The following approaches are recommended:
  • Install the connectivity agent on its own compute node (recommended).
  • Provide enough resources on the VM where the connectivity agent and database are running.