Is there any reason I couldn't have 2 distinct CA APM 10.7 SP3 environments talk to the same DB?
We have a temporary low volume CA APM 10.7 SP3 environment. I want to build another CA APM 10.7 SP3 environment that we will cut the agents over to. Together both environments will have low traffic and before the traffic on the go forward environment becomes high, we'll have decommissioned the temporary 10.7 environment. Are there any problems with doing this?
Release : 10.7.0
This goes for Oracle as well as Postgres. Since your original 10.7 environment has a DB already set up, adding a second environment to that same DB (must use same user and password) could produce some undesirable effects in that both environments will create tables for the same day (every day) thus giving you duplicate tables. This will hamper DB performance and APM performance as well. It is not advisable to do this.
The two modules that use the Oracle (or Postgres) DB are Team Center and CEM. Even if you do not use either, tables will be created as it is the design of APM.
So the best practice would be to have your second 10.7 environment create a new DB within the same Oracle instance thus producing fewer headaches