provision oracle database using em 12c -...
TRANSCRIPT
Provision Oracle Database using EM 12c Date: 14 December 2011 Author: Rob Zoeteweij http://oemgc.wordpress.com In this paper I describe the provisioning of an Oracle Database, assuming that the target host does not contain the Oracle Software. From the Enterprise Menu we select “Provisioning and Patching” “Database Provisioning” Prerequisites Some things I run into and were not checked by the procedure: Make sure the asmadmin and asmdba groups are present and user oracle is in each of them (yes of course groups dba, oinstall and oper need to be there when using them).
We will select the “Provision oracle Database” Deployment Procedure and press [Launch]
In this example we won’t use a provisioning profile
As the Host we are going to use as the destination does not contain the Grid Infrastructure or the Database software, we check both checkboxes:
• Deploy Grid Infrastructure for Standalone Server • Deploy Database Software
We check both checkboxes:
• Configure Grid Infrastructure • Create a new Database
We enter myserver2 as the destination for the provisioning and press [Next]
Next we need to provide all configuration details for the various tasks that will be processed during the provisioning. Select the Setup Hosts link
We will choose to override the Preferred Credentials by select a Named Credential set (UNIX_ORACLE_ACCOUNT) in this example. Press [Next]
Next you should enter all OS groups to be used. I did exactly what was suggested and used groups oinstal, dba, oper, asmadmin and asmdba. Press [Next] Next select the Deploy Software link
Here we need to select the Source for both the Grid Infrastructure and the Oracle Database. In both case we will use components that we have created in the Software Library before. Next all destination locations need to be entered. Finally we enter a working directory location and press [Next] Next we select the Configure Grid Infrastructure link
Next we need to configure the Grid Infrastructure In this example we create two Disk groups as ASM Storage: DGDB01 /dev/sdb1 Redundancy: EXTERNAL DGFRA01 /dev/sdc1 Redundancy: EXTERNAL We select Disk group DGFRA01 as the Disk group to store the spfile Next we need to enter the password for the ASMSNMP and SYS users We will use tcp/ip port 1521 for the Listener Press [Next] Next select the Create Databases link
In this example we will use the default DBCA “General Purpose or Transaction Processing” template
Press [Next]
We will name the Database orcl1.mycorpdomain.com and it’s SID orcl1 After entering the password for all administrative accounts, press [Next]
We select “ASM” as Storage Type The Database Files should be located in Disk group DGDB01 and we prefer to use “Oracle Managed Files” We want the database to use Fas Recovery Area and use DGFRA01 for Recovery Area Location
We will enable Archiving
For this example we will use Automatic Memory Management We will not explicitly specify the CPU count After selecting the Database Character Set and National Character Set we press [Next]
We will use Listener LISTENER on port 1521 Press [Next]
After reviewing the page we will press [Next] Next we need to select the Compliancy Standards link
We select “Configuration Best Practices for Oracle Database” as Compliancy Standard and press [Next]
Press [Next]
We choose to have the provisioning job immediately Press [Next]
After checking the final Review page we press [Submit]
Then finally after 2 hours and 3 minutes the procedure ends successful. Do believe me this say more about the power of my testing system then about the deployment procedure that is doing anything it should. Did I mention the fact that I spend some minutes trying to figure out why the step that configures the ASM instance failed because the oracle user was not in the asmdba group…?