Recently we performed a fresh installation of Oracle Enterprise Manager (EM) 126.96.36.199 using Oracle Database Enterprise Edition 188.8.131.52. as the management repository database. We also installed Oracle Grid Infrastructure 184.108.40.206 so that we could take advantage of ASM for the database datafiles.
Oracle provides a great pre-configured database template to help for this particular setup when using EM 220.127.116.11 and DB 18.104.22.168 that can save a little bit of installation time and eliminate having to manually configure various database parameters, tablespaces, etc. The first thing to do is to determine if you fall into the small, medium or large deployment of Enterprise Manager. See the Deployment Size portion of the document to determine which deployment size your environment is best suited for. Details about the preconfigured DB template is available right in the EM 12c documentation.
I’m not going to go through every detailed step of what we did but at a high level the following was performed:
- Install the Grid Infrastructure home (22.214.171.124) so we can use ASM for our database datafiles.
- Install the Database home (126.96.36.199).
- Download the EM template, 188.8.131.52 DB Template for EM 184.108.40.206 on Linux x86-64, from the Oracle Technology Network then start DBCA to configure a new database with it.
Once the template is downloaded you’ll want to extract it to $ORACLE_HOME/assistants/dbca/templates so that it appears in the DBCA templates window.
$ cp /stage/EM12_DB_template/220.127.116.11.0_Database_Template_for_EM12_1_0_5_0_Linux_x64.zip $ORACLE_HOME/assistants/dbca/templates $ unzip 18.104.22.168.0_Database_Template_for_EM12_1_0_5_0_Linux_x64.zip Archive: 22.214.171.124.0_Database_Template_for_EM12_1_0_5_0_Linux_x64.zip inflating: set_repo_param_126.96.36.199.0_Database_SQL_for_EM12_1_0_5_0_Large_deployment.sql inflating: set_repo_param_188.8.131.52.0_Database_SQL_for_EM12_1_0_5_0_Medium_deployment.sql inflating: set_repo_param_184.108.40.206.0_Database_SQL_for_EM12_1_0_5_0_Small_deployment.sql inflating: shpool_220.127.116.11.0_Database_SQL_for_EM12_1_0_5_0.sql inflating: 18.104.22.168.0_Database_Template_for_EM12_1_0_5_0_Large_deployment.dbc inflating: 22.214.171.124.0_Database_Template_for_EM12_1_0_5_0_Medium_deployment.dbc inflating: 126.96.36.199.0_Database_Template_for_EM12_1_0_5_0_Small_deployment.dbc inflating: 188.8.131.52.0_Database_Template_for_EM12_1_0_5_0.dfb inflating: 184.108.40.206.0_Database_Template_for_EM12_1_0_5_0.ctl
Next you’ll want to execute the database configuration assistant (DBCA) and when you get to the database template screen use the EM template (for our example we used the small deployment).
It’s important when you get to the Database Options screen that you include the script that will be executed after the database is created called shpool_220.127.116.11.0_Database_SQL_for_EM12_1_0_5_0.sql
Here we can see that the template has set the memory parameters accordingly and the number of connections based on the EM deployment size you chose earlier.
Once the database creation is completed we can see that it created the required EM tablespaces for us.
select name from v$tablespace; NAME ------------------------------ MGMT_AD4J_TS MGMT_ECM_DEPOT_TS MGMT_TABLESPACE SYSAUX SYSTEM UNDOTBS1 USERS TEMP
All that’s left is to install Enterprise Manager and point to this newly created database. With the EM database template you can see that the configuration of the EM management repository database is made a little easier providing us with the recommended settings based on the deployment size of your EM environment.