|[pic] |IT Infrastructure |Document Number |EDCS-xxxxxxx |
| | |Based on Template |No EDCS, Rev 0.x |
| | |Created By |Manickaraja Kumarappan |

IT Infrastructure Standards

Provisioning through Oracle Enterprise Manager

For document reviewers and modification history, see Table of Contents, Document History.

Any change to this document need to be reviewed and approved by Standard team or SME of this Domain. For document modification refer Revision History in next page.

Table of Contents

1. Purpose and Scope 3

2. Pre-Install requirements 3

3. EM Deployment Entities that are available today 4

3.1. List of Deployment Procedures 4 3.2. List of Software Library Components 5 3.3. List of Database Templates 5

4. Steps to Provision Oracle Components 6

4.1. Provisioning a RAC Database. 6 4.2. Provisioning a Standalone Database. 17 4.3. Monitoring a submitted procedure. 28

5. Executing root.sh script post install 32

5.1. For CRS install 32 5.2. For RDBMS Install 33

6. Manual Tasks 33

7. Glossary 34

8. Appendix 34

9. References 34

10. Documentation History 35

a. Revision History 35 b. Contributors 35 c. Reviewers 35

Purpose and Scope

This document provides complete steps for provisioning an Oracle CRS, RDBMS home and create a vanilla database through Oracle Enterprise Manager (OEM) Cloud control 12c.

Pre-Install requirements

a) Enterprise Manager Agent should be installed and configured across all hosts where provisioning is being attempted. b) All the mounts for installing oracle component should be in place as per Cisco standards. c) User should have access with “DBA” rights to OEM 12c. d) SSH should be set across all the DB nodes in case of RAC. e) CRS Oracle Home and RDBMS Oracle Home should be empty. Everything including lost+found should be removed prior to attempt provisioning through EM. f) Make sure central inventory is in place (check /oracle/product/oraInventory and /etc/oraInst.loc). INVENTORY_LOC inside this file should point to /oracle/product/oraInventory. g) You are suppose to have oraredo_mirr mount irrespective of whether the DB provisioned being MVDC or not (only in case of NAS storage). In case the same is missing, then as a work around please create a link and point it to /oracle/oraaredo. Example ln -s /oracle/oraredo /oracle/oraredo_mirr h) If you are attempting to run a provisioning procedure for the very first time, you should create a named credential in OEM. If you have already done that you can simply re-use the same and can skip this step. In order to create a named credential login into OEM Navigate to setup (on the right hand side) -> security -> named credential - > create [pic] Fill in the following stuffs. Credential Name: Meaningful name (could be same as your username) Credential Description: optional Authenticating Target Type: Host Credential Type: Host Credentials Scope: Global UserName: Your CEC user id Password: Your CEC password Confirm Password: Your CEC password Run Privilege: Sudo Run as: Oracle [pic] i) Click Test and Save. j) Choose any host (may be the host on which you are going to attempt provisioning) and make sure test succeeds. k) At any point of time if you want to see the status of submitted procedure, you can do so by navigating to Enterprise - > provisioning and patching - > procedure activity

EM Deployment Entities that are available today

1 List of Deployment Procedures

Below table will summarize when to use what procedure when a deployment is attempted through Enterprise Manager.

|S.No |Requirement |Procedure Name |Items to be checked while submitting procedure |
|1. |Install CRS, Clone Oracle Home and |Cisco Provision Oracle RAC Database |Deploy Grid Infrastructure |
| |Create Database | |Deploy Database Software |
| | | |Configure Grid Infrastructure |
| | | |Create a New Database |
|2. |Install CRS, Clone Oracle Home |Cisco Provision Oracle RAC Database |Deploy Grid Infrastructure |
| | | |Deploy Database Software |
| | | |Configure Grid Infrastructure |
|3. |Install CRS |Cisco Provision Oracle RAC Database |Deploy Grid Infrastructure |
| | | |Configure Grid Infrastructure |
|4. |Clone Oracle Home on a RAC Cluster |Cisco Provision Oracle RAC Database |Deploy Database Software |
| |and create Database | |Create a New Database |
|5. |Clone Oracle Home |Cisco Provision Oracle RAC Database |Deploy Database Software |
|6. |Clone Oracle Home and Create Database|Cisco Provision Oracle Database |Deploy Database Software |
| |for Non-RAC | |Create a New Database |
|7. |Clone Non-RAC oracle Home |Cisco Provision Oracle Database |Deploy database Software |
|8. |Create RAC/NON-RAC database |Cisco Create Oracle Database |N/A |

All these procedures can be accessed by navigating into OEM -> Enterprise -> Provisioning and Patching -> Database Provisioning

[pic]

2 List of Software Library Components

➢ CISCO_11203_CRS_PSU_CURRENT – 11.2.0.3 CRS with current PSU ➢ CISCO_10205_CRS_PSU_CURRENT – 10.2.0.5 CRS with current CPU ➢ CISCO_11203_DB_PSU_CURRENT – 11.2.0.3 RDBMS with current PSU ➢ CISCO_11203_DB_PSU_PREV – 11.2.0.3 RDBMS with current-1 PSU ➢ CISCO_10205_DB_PSU_CURRENT – 10.2.0.5 RDBMS with current PSU ➢ CISCO_10205_DB_PSU_PREV – 10.2.0.5 RDBMS with current -1 PSU

3 List of Database Templates

➢ CISCO_11203_NONERP_NONRAC_NAS_DB_TEMPLATE ➢ CISCO_11203_NONERP_RAC_NAS_DB_TEMPLATE ➢ CISCO_11203_NONERP_RAC_ASM_DB_TEMPLATE

Steps to Provision Oracle Components

1 Provisioning a RAC Database.

• Navigate to OEM - > Enterprise -> Provisioning and Patching - > Database Provisioning. • Choose Cisco Provision Oracle RAC Database and click Launch [pic] • Review the check boxes under “Select tasks to Perform” and select as per the requirement (all 4 needs to be checked in if your intention is to provision CRS, Oracle Home and create Database) • If you are provisioning CRS, then you need to click [pic] under Select destination hosts and add the host which are part of the cluster • While adding hosts, please make sure they are added in ascending order. For example if a 4 node RAC is being provisioned on svr1,svr2,svr3,svr4 then while adding them please make sure first svr1 is selected, followed by svr2, then svr3 and then svr4. If this order it not maintained then we might have problem while creating DB on this cluster (DB instance order might be improper). • If you are provisioning Oracle Home (on a host where CRS already exists), then you to click [pic] and add the cluster name where you want to provision Oracle Home. Cluster should be discovered in OEM prior to this and if not it is not possible to provision Oracle Home. • If you don’t know the cluster name, then query by host name and look for a target of type “cluster”. There will be only one target of type “cluster” for a set of cluster nodes. • The configuration details will be asked based on check boxes that were checked earlier. o Setup Hosts (Required under all scenarios) ▪ Click Setup Hosts hyperlink ▪ Choose a Named credential for both Normal & Privileged user (refer pre-requisite section if you don’t have one) ▪ [pic] ▪ Click Next ▪ Enter “dba” as OS Group Name for all the components (OINSTALL, OSDBA, OSOPER, OSASM, ASMDBA, ASMOPER). You may see all or few based on components ▪ [pic]Click Next ▪ Make sure you have a green check mark next to Setup Hosts hyperlink. ▪ [pic] o Deploy Software (Required under all scenarios) ▪ Click Deploy Software hyperlink ▪ You will be required to select two components (if you are deploying both CRS and RDBMS Oracle home) or just one (based upon which one you selected) ▪ Click the magnifying glass ([pic]) Icon next to each component and select one which fits your requirement. You may refer above section in this document to know about various components that are in use. ▪ [pic] ▪ Enter the Oracle Base for Grid Infrastructure (Usually /oracle/admin/GRID) – Applicable only if CRS is being installed ▪ Enter Grid Infrastructure home (Usually /oracle/product/grid_home) – Applicable only if CRS is being installed ▪ Don’t check “Shared Grid Infrastructure home” ▪ Enter Oracle Base for Database (usually /oracle/product/). Cisco standard is to have /oracle/admin/ as Oracle Base. However due to existing issue with EM, we need to provide an Oracle Base which is a subset of Oracle Home. However we are changing this as per Cisco standard at later stage and hence we don’t have to worry. – Applicable only if RDBMS code tree is installed. ▪ Enter Database Oracle Home – Usually /oracle/product// -- Applicable only if CRS is being installed. ▪ Don’t check “Shared Database Oracle Home ▪ [pic] ▪ Enter working directory as “/oracle/export/tmp” ▪ Leave Install parameters as blank ▪ [pic] ▪ Click Next ▪ Make sure you have a green check mark next to Deploy Software o Configure Grid Infrastructure (Required only if you provisioning CRS) ▪ Click Configure Grid Infrastructure hyperlink ▪ Select the storage type for both GI and Database as appropriate (Either ASM or File system in case of NAS). By default ASM is selected ▪ [pic] ▪ Enter Cluster Name (Standard is to provide Cluster name based on Scan Name). For example if SCAN name is SCAN-D2C001 then enter Cluster name as CRS-D2C001 ▪ Enter Scan Name: Query /etc/hosts and enter the scan name accordingly ▪ Enter Scan Port: 1541 is our standard for Scan Port. ▪ [pic] ▪ Under GNS settings, enter the virtual host name (if it is not pre-filled) for all the RAC nodes. If it is pre-filled just verify the entries and make sure they are correct. ▪ [pic] ▪ Under GI Network, Verify the IP of eth1, eth0 and make sure eth0 points to Public interface and eth1 points to Private Interface. Minimum one public and one private interface are required. You can issue netstat –anr command on host to fetch the public and private IP’s. ▪ [pic] ▪ Under File System Storage Leave the Redundancy as External for both OCR and Voting disk ▪ Enter the full path where you want to store OCR & Voting disk. ▪ Example: • OCR_LOCATIONS= /oracle/GRID_D2C001/fs01/OCR1,/oracle/GRID_D2C001/fs02/OCR_MIRROR2 • VOTING_DISKS= /oracle/GRID_D2C001/fs01/VOTE1, /oracle/GRID_D2C001/fs02/VOTE_MIRROR2, /oracle/GRID_D2C001/fs03/VOTE_MIRROR3 ▪ [pic] ▪ Click Next ▪ Make sure their exist a Green check mark next to “Configure Grid Infrastructure” o Create Databases (Required only if you are creating a DB) ▪ Click “Create databases” hyperlink ▪ Choose “Select Template From Software Library” Radio button ▪ Click the Magnifying glass next to Template (where it says No template selected) ▪ Select the template as appropriate (you may refer the table above on this document for list of templates that are in use) ▪ Enter “Temporary Storage Location on Managed Host(s) as /oracle/export/tmp ▪ [pic] ▪ Click Next ▪ Leave the Configuration type as “Administrator Managed” and make sure all nodes are displayed on the screen ▪ [pic] ▪ Under Identification enter Global Database Name as DBNAME.CISCO.COM: Example: D2C001A.CISCO.COM ▪ SID Prefix as just DB Name: Example: D2C001A ▪ [pic] ▪ Under Database Credentials Choose “Use the same administrative password for all accounts” and provide password as “oracle123”. The password provided here is just temporary since we will be changing the same at later stage. ▪ [pic] ▪ Click Next ▪ Under Storage Type, choose as appropriate where the Database files will be stored. ▪ [pic] ▪ Under Database Files Location, make sure “Use Database File Locations from Template” is selected. ▪ [pic] ▪ Under Recovery Files Location, if you are going to use Fast Recovery area then select “Use Fast Recovery Area” check box ▪ Under Recovery Area Location specify the location where you want your recovery files to be created. Our standard is to provide /oracle/oradata_flashback//fs01. Example: /oracle/oradata_flashback/D2C001A/fs01 ▪ Specify Fast Recovery Area Size (MB) based on the mount point space available. ▪ [pic] ▪ If you want the database being provisioned to be in archivelog mode, then select “Enable Archiving” check box. ▪ [pic] ▪ Click “Specify Archive Log Locations” button to specify the location where archive log needs to be placed. ▪ You can enter as many location as required. ▪ Our Standard is to enter one location and it needs to be entered as /oracle/archive//fs01/.arch. Example /oracle/archive/D2C001A/fs01/D2C001A.arch ▪ [pic] ▪ Click OK ▪ Click Next ▪ Review the memory parameters and change as per requirement ▪ [pic] ▪ Review Database sizing and change as per requirement. ▪ [pic] ▪ Leave the HOST CPU count to 0 ▪ [pic] ▪ Choose Character set as per requirement ▪ [pic] ▪ Leave the Database Connection Mode to “Dedicated Server Mode” ▪ [pic] ▪ Click Next ▪ Under Database Features leave the default components selected AS-IS unless otherwise you have a business requirement to deselect any. ▪ [pic] ▪ Under Custom Scripts, no need to specify any script. Just leave it blank ▪ [pic] ▪ Click Next ▪ Just review all the items here. If you want to make any change click “Back” button to go back and make changes. ▪ If everything is fine then click Next. ▪ Make sure you have a Green Check Mark next to Create databases. o Compliance Standards (Required only if you creating a DB) ▪ Click Compliance Standards hyperlink ▪ Leave the compliance standard set to “None” which is default ▪ [pic] ▪ Click Next ▪ Make sure you have a green check mark next to Compliance Standard hyperlink. ▪ At this point you should have Green check marks against all the items listed in the screen, if you cannot proceed further ▪ [pic] ▪ Click Next ▪ On the field “Enter EMAIL for notification” enter your Cisco email address. This is where notification will be sent on issues if any post deployment process. ▪ On the field “Enter Lister Port” enter the desired port number where you want to configure the Listener for the database being deployed. This port number should be free and should be available across all RAC Nodes. ▪ [pic] ▪ Click Next ▪ Leave everything to default on this screen. ▪ You may save this if you want to re-use the value entered at later point of time. • If you want to submit a saved procedure, all you have to do is, goto Enterprise -> Provisioning and Patching -> Database Provisioning, Under “Provision Oracle RAC Database” you should be able to see the one which you saved. Just select it and move forward with submission ▪ Click Next ▪ Review all the details entered and then click Submit. ▪ It will ask you to reconfirm, just click Yes to reconfirm and procedure will be submitted for execution ▪ [pic]

2 Provisioning a Standalone Database.

• Navigate to OEM - > Enterprise -> Provisioning and Patching - > Database Provisioning. • Choose Cisco Provision Oracle Database and click Launch [pic] • Review the check boxes under “Select tasks to Perform” and select as per the requirement (both “Deploy Database software” and “Create a new database” needs to be selected if intention is to clone a oracle home and create vanilla database) • [pic] • Under “Select destination hosts” click [pic] • Select the host where you want to have the DB created. • [pic] • [pic] • Click Next • The configuration details will be asked based on check boxes that were checked earlier. o Setup Hosts (Required under all scenarios) ▪ Click Setup Hosts hyperlink ▪ Choose a Named credential for both Normal & Privileged user (refer pre-requisite section if you don’t have one) ▪ [pic] ▪ Click Next ▪ Enter “dba” as OS Group Name for all the components (OINSTALL, OSDBA, OSOPER). ▪ [pic]Click Next ▪ Make sure you have a green check mark next to Setup Hosts hyperlink. ▪ [pic] o Deploy Software (Required under all scenarios) ▪ Click Deploy Software hyperlink ▪ You will be required to select a component for RDBMS Oracle home ▪ Click the magnifying glass ([pic]) Icon next to “Oracle Database” component and select one which fits your requirement. You may refer above section in this document to know about various components that are in use. ▪ [pic] ▪ Enter Oracle Base for Database (usually /oracle/product/). Cisco standard is to have /oracle/admin/ as Oracle Base. However due to existing issue with EM, we need to provide an Oracle Base which is a subset of Oracle Home. However we are changing this as per Cisco standard at later stage and hence we don’t have to worry. – Applicable only if RDBMS code tree is installed. ▪ Enter Database Oracle Home – Usually /oracle/product// -- Applicable only if CRS is being installed. ▪ [pic] ▪ Enter working directory as “/oracle/export/tmp” ▪ Leave Install parameters as blank ▪ [pic] ▪ Click Next ▪ Make sure you have a green check mark next to Deploy Software o Create Databases (Required only if you are creating a DB) ▪ Click “Create databases” hyperlink ▪ Choose “Select Template From Software Library” Radio button ▪ Click the Magnifying glass next to Template (where it says No template selected) ▪ Select the template as appropriate (you may refer the table above on this document for list of templates that are in use). Example CISCO_11203_NONERP_NONRAC_NAS_DB_TEMPLATE ▪ Enter “Temporary Storage Location on Managed Host(s) as /oracle/export/tmp ▪ [pic] ▪ Click Next ▪ Under Identification enter Global Database Name as DBNAME.CISCO.COM: Example: DBCIM.CISCO.COM ▪ SID Prefix as just DB Name: Example: DBCIM ▪ [pic] ▪ Under Database Credentials Choose “Use the same administrative password for all accounts” and provide password as “oracle123”. The password provided here is just temporary since we will be changing the same at later stage. ▪ [pic] ▪ Click Next ▪ Under Storage Type, choose as appropriate where the Database files will be stored. ▪ [pic] ▪ Under Database Files Location, make sure “Use Database File Locations from Template” is selected. ▪ [pic] ▪ Under Recovery Files Location, if you are going to use Fast Recovery area then select “Use Fast Recovery Area” check box ▪ Under Recovery Area Location specify the location where you want your recovery files to be created. Our standard is to provide /oracle/oradata_flashback//fs01. Example: /oracle/oradata_flashback/D2C001A/fs01 ▪ Specify Fast Recovery Area Size (MB) based on the mount point space available. ▪ [pic] ▪ If you want the database being provisioned to be in archivelog mode, then select “Enable Archiving” check box. ▪ [pic] ▪ Click “Specify Archive Log Locations” button to specify the location where archive log needs to be placed. ▪ You can enter as many location as required. ▪ Our Standard is to enter one location and it needs to be entered as /oracle/archive//fs01/.arch. Example /oracle/archive/D2C001A/fs01/D2C001A.arch ▪ [pic] ▪ Click OK ▪ Click Next ▪ Review the memory parameters and change as per requirement ▪ [pic] ▪ Review Database sizing and change as per requirement. ▪ [pic] ▪ Leave the HOST CPU count to 0 ▪ [pic] ▪ Choose Character set as per requirement ▪ [pic] ▪ Click Next ▪ Under Listener Configuration enter a “Listener Name”. Usually LISTENER_. Example: LISTENER_DBCIM ▪ Enter a Port where you want listener to be configured. Make sure the port entered is not in use at host level. If not you may get an error message as “Specified Port is already in use by different listener on this host” ▪ [pic] ▪ Under Database Features leave the default components selected AS-IS unless otherwise you have a business requirement to deselect any. ▪ [pic] ▪ Under Custom Scripts, no need to specify any script. Just leave it blank ▪ [pic] ▪ Click Next ▪ Just review all the items here. If you want to make any change click “Back” button to go back and make changes. ▪ If everything is fine then click Next. ▪ Make sure you have a Green Check Mark next to Create databases. o Compliance Standards (Required only if you creating a DB) ▪ Click Compliance Standards hyperlink ▪ Leave the compliance standard set to “None” which is default ▪ [pic] ▪ Click Next ▪ Make sure you have a green check mark next to Compliance Standard hyperlink. ▪ At this point you should have Green check marks against all the items listed in the screen, if you cannot proceed further ▪ [pic] ▪ Click Next ▪ On the ORACLE_BASE field enter the value for ORACLE_BASE as per Cisco Standard which is /oracle/admin/. Example /oracle/admin/DBCIM ▪ [pic] ▪ On the field “Enter EMAIL for notification” enter your Cisco email address. This is where notification will be sent on issues if any post deployment process. ▪ On the field “Enter Lister Port” enter the same listener port which you entered in previous step. ▪ [pic] ▪ Click Next ▪ Leave everything to default on this screen. ▪ You may save this if you want to re-use the value entered at later point of time. • If you want to submit a saved procedure, all you have to do is, goto Enterprise -> Provisioning and Patching -> Database Provisioning, Under “Provision Oracle RAC Database” you should be able to see the one which you saved. Just select it and move forward with submission ▪ Click Next ▪ Review all the details entered and then click Submit. ▪ It will ask you to reconfirm, just click Yes to reconfirm and procedure will be submitted for execution ▪ [pic]

3 Monitoring a submitted procedure.

✓ Navigate to OEM - > Enterprise -> Provisioning and Patching - > Procedure Activity to see all the procedure executions (those which are currently running as well those which got completed in the past) ✓ If a procedure is submitted by Person “A”, then Person “B” won’t be able to see the same. If their exist a required for Person “B” to monitor/take action on the procedure submitted by person “A”, then person “A” has to grant permission on the procedure he submitted. o In order to grant a privilege, choose the procedure execution on which privilege needs to be granted (by navigating into OEM -> Enterprise -> Provisioning and Patching -> Procedure Activity) o Click “Edit Permissions” button o [pic] o Click Add o Search by CEC ID to whom access needs to be provided o Click Select o [pic] o Under “Manage Target Privilege Grants” drop down list choose the privilege as appropriate (“FULL” is recommended) o [pic] o Click OK o Their after granted person will have full privilege on the procedure. ✓ Execute Prerequisites and Fixups (second step in the procedure) will be running for considerable amount of time. This is the step which does end-to-end validation to make sure the host setup if fine and parameter provided during the interview process is valid. ✓ At any given point if someone needs to know what exactly is being done and to see the relevant log files, just click the step name (which is usually hyper link), ✓ [pic] ✓ Then keep click the host name (which is again a hyper link) on which it is running/completed. ✓ Click the status (running/failed/succeeded) which is again a hyper link ✓ [pic] ✓ Expand the execution details arrow and you will see the complete log of the execution. ✓ [pic] ✓ Incase if a step got failed you will easily come know the reason for failure by reviewing corresponding log file. ✓ [pic] ✓ Incase if a step is failed, then you have an option either to Retry or to Ignore. Please note that all steps cannot be ignored. If a step is very critical and a dependent for subsequent steps then that step cannot be ignored. Ignore button will be disabled in this case. ✓ You need to select the host where you want to retry/ignore and then click corresponding button. ✓ [pic] ✓ If the issue is identified (by going through the log file) and cause for failure is fixed then one can click “retry” so that the same failed step will be reattempted and upon success it will proceed further. ✓ It is highly recommend to always use “Retry” and Ignore should never be used unless otherwise it is essential. ✓ Also Retry will only execute the procedure from failure point, this saves time and no need to repeat the steps which already got completed.

Executing root.sh script post install

1 For CRS install

❖ While installing CRS, execution procedure will fail while running root.sh. This is expected since our ID’s doesn’t have sudo access to root for running root.sh ❖ [pic] ❖ Once the step is failed, login into DB node, manually invoke root.sh o sudo /oracle/product/grid_home/root.sh ❖ Review the log file and incase of no errors run rootcrs.pl o sudo /oracle/product/grid_home/crs/install/rootcrs.pl ❖ once rootcrs.pl execution got completed, check the component status on CRS and make sure everything is in “UP” status. ❖ Please make sure root.sh & rootcrs.pl is executed in the order in which RAC instances would be created. For example if it is a 4 node RAC DB on hosts svr1,svr2,svr3 and svr4, then please execute root scripts first on svr1, once it got completed executed it on svr2, then svr3 and at last on svr4. ❖ Follow the same on all the remaining RAC Nodes. ❖ Once it is done, go back to EM, select the failed step and click retry. ❖ [pic] ❖ This time it will succeed and will move forward. ❖ Their after procedure should not fail and should complete all the way till end.

2 For RDBMS Install

Incase of RDBMS oracle home clone, root.sh script has been disabled since it is not mandatory to execute it before subsequent steps completes. However one has to run this script post deployment process to make sure process is complete.

You can login into DB node and run sudo $ORACLE_HOME/root.sh. This needs to be done across all RAC nodes.

Manual Tasks

This section lists all the tasks that are manual as of now.

1. Execution of root.sh script 2. Pinning CRS nodes in case of RAC 3. Any links those are missing which are communicated through e-mail at end of the process. 4. [pic] 5. Reviewing and scheduling the cron jobs for monitoring (Production Focus, log file manager, archive utl etc.) 6. Registering listener in LDAP 7. Making entry in DBTS 8. Scheduling backup and coordinating tasks with DIG team. 9. EMAN entry

Glossary

Appendix

1 Cisco specific customizations

Given below are Cisco specific customizations that are done as part of DB provisioning.

1) Create dedicated listeners with same port across all RAC nodes 2) Make oratab entries as per Cisco standards 3) Deploy standard scripts as per Cisco standards 4) Create CCPADMIN schema 5) Perform SOX/RDAC related setups 6) Pin Standard objects into shared pool 7) Increase AWR retention period as per Cisco standards 8) Install OS Watcher 9) Configure Splunk if applicable 10) Create EMAN Monitor User 11) Register DB in OCM 12) Configure Local and Remote listener parameters as per Cisco Standards 13) Create various softlinks as per Cisco standard 14) Disable standard gather stats job 15) Enable force logging 16) Move .patch_storage to /oracle/dump 17) Create password file 18) Register DB in RMAN catalog 19) Create password file with sys/rman schema passwords 20) Turn off auto extend across all DB files

References

Provisioning & Patching Oracle Database using Enterprise Manager 12c
Oracle Enterprise Manager 12c Documentation

OEM Wiki Page

Documentation History

1 Revision History

|Version |Revised On |Revised |Revised For |Reviewed |Reviewed |
| | |By | |By |On |
| | | | | | |

2 Contributors

|Name |Email Id |Role |
|Manickaraja Kumarappan |mkumarap@cisco.com |EM System admin |
|Pascal Laporte |plaporte@cisco.com |EM System admin |
|Venkata Kiran Gunturi |vgunturi@cisco.com |EM System admin |
|Surekha Jampala |surjampa@cisco.com |EM System admin |

3 Reviewers

|Name |Email Id |Role |
|Pascal Laporte |Plaporte |EM System admin |
| | | |
| | | |
| | | |

End of Document