Hi,

YES!! It is always recommended to have the OMS & Repository DB on different servers to avoid performance issues.

Regards,
Venkat

Venkata Thiruveedhi-Oracle wrote:

 

Hi,

 

YES!! It is always recommended to have the OMS & Repository DB on different servers to avoid performance issues.

 

Regards,
Venkat

I too would like to see a link to documentation on this subject. Why would haveing them on different servers (thus increasing network latency in communications) avoid performance issues?

Hi Richard,

There is no specific document which explains this.

In general the expectation is to have the OMS & Repository configured on different servers.

Even if you see the Pre-reqs for the Hardware Requirements the OMS & Repository required hardware details were provided separately.

https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/embsc/oracle-enterprise-manager-deployment-prerequisites.html#GUID-C72126D0-C99F-4348-8CCB-7C49FC2E4ED2

In this page you have a note section:

Note:

If you plan to have the OMS and the Management Repository on the same host, then meet the requirements described in Table 1-1 and Table 1-3, and make sure the CPU, RAM, and hard disk space requirements are a combination of the values mentioned in both tables.

This means the general scenario is to have them on different servers.

But in case if you want to have them on the same server, you should make sure the Resources Required for OMS + Resources Required for Repository DB should be present on that single server.

Best Regards,
Venkat

Venkata Thiruveedhi-Oracle wrote:

 

Hi Richard,

 

There is no specific document which explains this.

 

In general the expectation is to have the OMS & Repository configured on different servers.

Even if you see the Pre-reqs for the Hardware Requirements the OMS & Repository required hardware details were provided separately.

 

https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.3.1/embsc/oracle-enterprise-manager-deployment-prerequisites.html#GUID-C72126D0-C99F-4348-8CCB-7C49FC2E4ED2

 

 

In this page you have a note section:

Note:

 

If you plan to have the OMS and the Management Repository on the same host, then meet the requirements described in Table 1-1 and Table 1-3, and make sure the CPU, RAM, and hard disk space requirements are a combination of the values mentioned in both tables.

 

This means the general scenario is to have them on different servers.

But in case if you want to have them on the same server, you should make sure the Resources Required for OMS + Resources Required for Repository DB should be present on that single server.

 

Best Regards,
Venkat

"This means the general scenario is to have them on different servers."

I think that's reading too much between the lines.  I see the statement to which you are referring as simply an acknowledgement that the OMS and the repository may be on the same server. Simply a statement of how to calculate your requirements if you choose that configuration.  I do not read that as being an implied commentary on which configuration is 'expected' or 'recommended'.

Hi,

There is no documented proof which says it has to be on same server or on different server.

We have cases where there are few bugs which were been filed and Engineering team confirmed them to be performance issues due to the hugh operations on Repository.

If you are able to maintain enough resources and your system is capable of managing the situation,  then yes!! you can have them on the same server.

But if any one is planning to have them on different server and if they want to know if it is supported, then answer is  YES!!

In this case it is a question if they can have!! YES they can have.

Regards,
Venkat

I (obviously?) agree that the short answer to the OP's question is 'yes, you can have the OMS and the repository on different servers.  I was just making the expanded and deeper discussion that there does not appear to be any "recommendation" or "assumption" as to such.  All I see in the documentation is a position-neutral position, with statements as to "if you do it one way, be sure to ..."

That's true, mostly because some customers have OEM monitoring 10 databases on 10 hosts.  Obviously, having a standalone DB server and MW server for this is overkill and not absolutely required.   When you start to grow and go up the MAA levels documented for OEM to a true enterprise tool, then it is highly recommended, yet still not required.  Just like the minimum disk space for agent is 1gb, but it's recommended to have 5-10gb isolated mount point.    There are various best practice white papers available, but standard docs will always doc min requirements.