Grid Control : Change Management Across Non-Prod and Prod

Question

All,
I had some questions with regards to Grid Control Implementation Architechture on Prod and Non-Prod Env's
The best practice is to configure a production Grid Control (GC) environment to monitor only production targets. This prevents nonproduction targets from adversely impacting a production environment.Another issue could be the compliance policy where in the production systems are to be isolated from Non-Production Environments.
If this is the case then we have to have 2 GC environments , 1 for Prod and 1 for Non-Prod. In such a scenario how well can we do change management (Version control ) across the Non-Prod and Prod Environments ?
To be more specific
How is version control managed for Oracle builds if we have separate GC for Prod and Non-PROD? (Change Management pack / Configuration Management Packs are there but what is the real depth of these? )
Change management for the Oracle Environments from DEV -> Test -> Pre-Production-> Production? We aim to have consist build across the environments can we achieve this if the GC is managed by Different OMS/OMR and if we have 2 separate environments how do we sync the GC environments managing PROD/NON-PROD after a change?

Answer 1

This is feature is not there in 10.2
This situation can be avoid by chagning the 9i port to 1522
or install the GC on diffrent box