Database Lifecycle Management and Cloud Management - Hands on Lab (OOW2014)

EM12c Database Lifecycle Management –
Database Fleet
Standardization & Transition to Database as a Service

of 66
ORACLE ENTERPRISE MANAGER Cloud Control 12c
Database Lifecycle Management
Oracle Database 12c Lifecycle Management with Oracle Enterprise Manager
The objective of this lab is to showcase the Oracle Enterprise Manager Cloud Control 12c’s lifecycle management capabilities and show how database organization can begin their cloud journey with Self service (Database as a Service).
Part 1
Scenario: Company ‘Plug Inc’ had a big unplanned outage last weekend. Key members of the organization met and analyzed the problems. One of the key focus areas in the presentation to the CTO/CIO is the action plan of implementing stricter standardization and better automation across the IT within the next 6 months.
Based on the requirements and inputs from the key members, the DB Infra head draws a list of key attributes to achieve. Sally (DBA manager) and Clark (lead DBA) discuss the features and implementation. You will be playing the role of Clark, using Enterprise Manager 12c you will manage the lifecycle of Database to achieve the goal of standardization.

of 66
GOAL: More Strict Standardization & better Automation
In this part, you will try out the following exercises: Exercise No Feature Time Exercise Relation to the scenario
1
Configuration Management
5 mins
Identifying databases assets in the fleet - Perform an inventory check and identify the databases count. Figure out the no. of DB12c – PDBs in the fleet.
Sally wants to provide a report to Ravi on the DB asset list. You are also identifying the PDBs in the list, since there is a security patch recommended by Kate for DB12c databases too.
2
Compliance Management
10 mins
Rolling out new corporate standards. Use the compliance rule to identify the databases missing the missing security patch.
Resolving Compliance Officer (Kate) requirements. Also ensuring all Databases is at the secure patch levels.
3
Patch Automation
10 mins
Deploy the recommended security patch to a DB12c CDB with PDBs.
Automated patching of the DBs. It also fits into Ravi’s mandate of having standard systems and usage of more automation.
4
Provisioning
15 mins
Use the patched DB12c’s image to create the Standard DB12c profile. Also, associate compliance standards as a part of the Provisioning process to create Standard and certified level of software.
This tie back to the main theme of Standardization and more automation. Taking patched software and baking compliance rule along with it.

of 66
Getting Started
The following exercises are based on Enterprise Manager 12c Release 4 (12.1.0.4). This lab contains an Enterprise Manager 12c setup which manages:
1. A DB12c (12.1.0.1) Container Database (called ‘test.oracle.com’) with 5 Pluggable Databases.
2. Some additional Databases of 11.2.0.3 and 12.1.0.1 releases for Configuration Mgmt. exercises.
You could directly try the use cases in your local EM environment. If you want to participate in Oracle’s workshop, contact your local Oracle sales or account team.
Scenario #1. Using Inventory
Business Case/ Problem Statement
You have been asked to report on the current Database distribution across your environment. You are also identifying the list of PDBs in your enterprise as they might potentially need the mandated patch from compliance. Use the Inventory and Usage details page to answer these requests quickly.
1 Inventory and Usage Details
1.1 Navigate to menu options Enterprise->Configuration->Inventory and Usage Details

of 66
1.2 To view the Databases in the fleet, choose “Databases” from the show list.
1.3 It displays the Database distribution by version.
A quick look up to know the Database distribution in the fleet.
Clark’s response to “What DBs do we have currently in our Database fleet?” For sending the report in a mail, he can print screen and paste in an email.
The table in the lower half of the page gives you a complete detailed list. It can be exported directly to be sent as a part of the report.

of 66
1.4 The compliance team recommended checking the Container DBs. From the table, select the Container Database.
A weekend outage impacted the ERP sites. Let’s select the ERPDB for quick Compliance evaluation.

of 66
Scenario #2. Compliance Mgmt, Topology Viewer
Solution Overview
Enterprise Manager automates the validation of database adherence to Oracle as well as internal requirements. Should remediation be needed for detected violations, users can identify the impacted list of targets using a target’s Topology. Understand the target’s relationships and associations during the root cause analysis before taking action. Remediation requiring the application of patches can be performed automatically using Patch Plans. Patches can be rolled out to one or multiple targets in a single deployment window.
Apply the corporate database compliance standard to the ERP database and check for any violations of corporate policy. Use topology viewer to determine impacted PDBs to correct CDB violations. Use patch automation to remediate the drift from standard.

of 66
2 Use the Compliance Standards to check for deviations from corporate standard.
2.1 ERPDB Database Home page
You will receive an informational IO Error message that the Network Adaptor could not establish the connection. This is expected as the target is not available in the Hands on lab environment. Ignore the message and continue.
2.2 Navigate to ERPDB’s Menu: ‘Oracle Database ->Compliance -> Standard Associations’.

of 66
2.3 Click on ‘Edit Association Settings’ to associate a new compliance standard to this database.
2.4 Click ‘Add’ to choose from list of compliance standards.
2.5 Select ‘Corporate DB Compliance Standard’ and click “OK”.

of 66
2.6 Click OK to begin compliance evaluation against the selected standard.
2.7 Click ‘Yes’ to confirm the association.
2.8 Click OK.
2.9 Navigate to ‘Oracle Database -> Compliance->Results’ to view the results of this target’s compliance standings.

of 66
You can see there is 1 critical violation to the Corporate DB compliance standards. Let’s look at the details.
2.10 Select ‘Corporate DB Compliance Standard’.
2.11 Select the ‘Mandatory Required Patch – 16705020’ rule to view details of the violation.

of 66
2.12 Select the ‘Violation Events’ tab to get to the details of the violation.
2.13 Select the event from the table to see more details.
Here we can see we are missing a mandatory patch as determined by corporate compliance. The Recommendation tells us to apply the patch. Before we can apply the patch, we need to understand what the impact on PDBs contained in the CDB will be. We will use the topology view to understand the relationship between this CDB and its PDBs.

of 66
2 Use Topology Viewer to understand CDB/PDB Relationships
2.14 Navigate directly to the topology view of the Database to view its relationships.
2.15 Notice that we can see all of the pluggable databases that are related to this container as well as the listener, oracle home and host.
This gives a quick view of the PDBs that are impacted while modifying the container Database.
PDBs that will be impacted by patching Container Database

of 66
Scenario #3. Patch Automation
You have been asked to patch the CDB along with its PDBs with one-off patches and PSU to mitigate the compliance standard deviation and stick to security guidelines. You have very low margin of error. Use Enterprise Manager 12c’s Patch automation feature to patch the CDB and associated PDB’s via Out of Place patching, which reduces the downtime and helps handle any issues during maintenance while retaining the ability to switch back to the old Oracle Home.
Patching is one of the important phases of the product lifecycle that enables you to keep your software product updated with bug fixes. Oracle releases several types of patches periodically to help you maintain your product. However, patching has always been the most challenging phase of the lifecycle because it can be time consuming, complex, risky, and involves downtime. The new Pluggable database feature in Oracle Database 12c simplifies patching in some ways but amplifies the need to maintain a current PDB inventory to ensure the complete impact of applying the patch is understood.
Solution Overview
Cloud Control addresses the patching challenges with its much-improved patch management solution that delivers maximum ease with minimum downtime.
to Ran the compliance standard evaluation, identified some of the DB12c targets needs a patch to be compliant to the new corporate compliance standard. We are moving completely out of doing things with scripts and using EM for patching. I created a test patch plan with both patches, ran an analysis there aren’t any issues in applying them. To minimize Downtime and Risk, I used EM12c’s new ‘Out of Place’ mode of patching. Created a new clone of the OH and patched it. I need just 10mins in the weekend, with a click of a button will switch the Databases to the patched home along with complete SQL run.
Can you approve and fwd my request. Apps team can spare 10mins this weekend, can’t they 
(Patch Automation. Analyze and Prepare in weekday (25mins).
Deployment during weekend maintenance - 5 mins)

of 66
The new patch management solution also offers the following benefits:
 Integrated patching workflow with My Oracle Support, therefore, you can see Oracle’s recommendations, search patches, and roll out patches all using the same user interface.
 Comprehensive pre-requisite checks to identify issues before the maintenance windows.
 As a part of analysis, conflicts for patches are checked against your environment. In case of conflicts, automatic merge patch requests are placed directly with Oracle and conflicts are replaced with resolution patches.
 Supports patching flexible patching options such as rolling and parallel both In Place and Out of Place modes to handle maintenance needs.
 Patch automation is available for both in offline (disconnected) and online (connected) mode of the EM environments.
3 Use Patch Plans to deploy PSU and other one-off patches to the container and its pluggable Databases.
Before rolling out the patches to the ERPDB, Clark applies it to the Test Container Database with Pluggable Databases.
3.1 Navigate to ‘Enterprise -> Provisioning and Patching -> Patches & Updates’

of 66
3.2 To view detailed Patch recommendations, click “All Recommendations”.
3.3 Search for target “test.oracle.com” from the list. Switch the filter to “Target Name”, enter “test.oracle.com” in the search field and click the search icon.
EM generates automatic patch recommendation list against Oracle recommended patches (like CPUs, PSUs, and Bundle patches.) for all the Databases it manages. This feature can be made available also in OFFLINE or Disconnected EM, where your OMS cannot communicate with outside network or My Oracle Support.
3.4 Select the PSU patch recommended for 12.1.0.1 Database, click “Add to Plan” and select “Add to New”

of 66
3.5 Provide a name to the plan, recommended format “<YourInitials>_ Patch_CDB_12101 and click ‘Create Plan’.
3.6 This shows the impacted targets which share the same OH. In this lab env. the Oracle Home is used by multiple targets, mimics a consolidated and messy development env. As an admin for test, you are allowed only to handle ‘test.oracle.com’ DB. EM12c’s patch plan allows you the flexibility to administer selective databases only. Select “Add Original Only”
3.7 Click ‘View Plan’ to open the plan and navigate to Patches page in the Plan wizard.

of 66
3.8 Select Patches in navigator and click “Add Patch…” to add the patch required based on the corporate compliance standard – patch “16705020”.
Search for patch “16705020”
3.9 Add the patch to the plan. Click ‘Add to This Plan’, search for the CDB – test.oracle.com and add it to the plan.

of 66
3.10 Select “Add Original Only”
3.11 Plan now contains both the patches. Navigate to the next step in the Patch plan - Deployment Options.

of 66
Patch Plan supports both “In-Place” and “Out –of-place” modes of patching. In this lab, we will follow the new methodology introduced in EM12c– “Out of Place mode”.
3.12 For Out-of-Place mode, need to specify the new location of the Oracle Home where the source home would be cloned. Click ‘Create New Location’.
3.13 Specify both Home Name – “<yourshortname>_psu’ and Home Location. For OH location copies the existing location and change the final directory to ‘db12c_shortname_psu’. Click Validate and after validation, click ‘Create’.

of 66
3.14 All the other inputs for deployment options are auto filled, the status on the left panel shows all questions responded. Click ‘Review’ and from the review page, submit the plan for the 1st phase – Analysis, to run validation and pre- requisite checks prior to patching.

of 66
3.15 Click ‘Analyze’ to kick off the Analysis. During this phase, plan executes multiple checks; the details can be tracked from the underlying procedure execution. Click ‘Show Detailed’ results.
Tip: Wait for few seconds, the link for Show detailed results will show up in the Analysis message bar. If the message bar is collapsed, open it to view the link.

of 66
3.16 Procedure execution lists all the steps. Click on any step to view the details along with the complete logs.

of 66
During Analysis phase, the patch plan runs Patch applicability checks, OUI and Opatch pre-requisite checks, space and inventory checks, target sanity checks, runs specify tools like ‘cluvfy’ for cluster verification, SQL plus sanity check and other custom checks learnt from other Enterprise customers.
The Analysis takes about ’10mins’.In the mean time, check the pre-cooked Patch Plan where Analysis for the same target and patches is complete.
3.17 Switch the older tab/EM window on your Browser. Click on ‘Patches and Updates’ to view the list of Patch plans. (Or navigate to Patches and Updates page if the procedure activity didn’t open up in the new window.)

of 66
3.18 Click open the plan ‘ CDB12.1_OCTPSU_ANALYZED’. Analysis on the patch plan has run already successfully and the plan is ready for deployment for the next step. Click on ‘Review’

of 66
The next phase of the plan is called ‘Prepare’. During this phase the source OH is cloned and patched.
Note: This operation doesn’t need downtime. Typically DBAs can do this before the maintenance window and keep everything prepared for the deployment.
Prepare step runs for 20+mins. To save time in the lab, we will take a Patch Plan which is already prepared.
3.19 Click on ‘Patches and Updates’ and go to the list of Patch plans page.

of 66
3.20 Choose the patch plan ‘CDB12.1_OCTPSU_PREPARED ‘and click open or click ‘View’
3.21 This patch plan has already been Prepared, that is the source OH is cloned and patched. It’s ready for the deployment of the Database. Click ‘Review’.

of 66
3.22 Click ‘Deploy’, this would trigger a procedure to switch the Databases (the CDB and the corresponding PDBs) from old OH to the new OH.
3.23 Click Submit to deploy immediately.
3.24 Submit fires of a procedure in the back end. Click ‘Show Detailed Results’, to track the execution of the procedure invoked by the Patch Plans. (In couple of seconds the link to the procedure would show up, if it doesn’t click the refresh icon on top right to get the link to show.)

of 66
During Deployment, the Database(s) are switched from Old Oracle Home to the new Oracle Home. If there are any SQLs in the patch (say CAT PSU.SQL in PSU patches) will be applied to the DB. The target inventory information and the EM target information are updated with the new OH info making it seamless to monitor within EM.
It takes about 3-5mins to complete the process. Once completed the Container Database (test) and its Pluggable Databases will be running from the newly patch Oracle Home.
If the deployment is still in progress, let it run and start the next exercise.

of 66
Scenario #4 Provisioning a CDB with a PDB within.
You been asked to ensure standards and increase automation in the DB operations. One of the key tasks in DB operations is provisioning of new Databases. Use Enterprise Manager 12c’s automated provisioning procedure to deploy CDB with PDB within it.
Solution Overview
Oracle Multitenant simplifies the consolidation process by plugging multiple databases into a multitenant container database without changing applications. It also provides comprehensive automated workflows using which DBA’s can easily migrate their database to a CDB.
Use Oracle Enterprise Manager Cloud Control to manage enterprise configurations by:
 Provisioning Container Databases (CDB) with one or many Pluggable Databases (PDB)
Note: In this exercise, you will leverage the Profile of the pre-patched software and also plug-in the new compliance standard mandated within the process to ensure Standardization. To further this and ensure the standards are followed across the datacenter for any new deployments by the DBA team, you would save the procedure with the input values locked and share it with the other DBAs. This lowers risk of errors and propagation of standards.
EM12c’s Provisioning supports automation of the Database software deployments. With the ability to use the pre-patched software’s image for Provisioning, enables quicker delivery of the deployment and up to the current standard, eliminating the need to do any maintenance after deploying the software.
Provision CDB + PDBs
From Media
Or Gold images
Pluggable Databases (PDB)
Container Database (CDB)

of 66
4 Provisioning Container Databases (CDB) with Pluggable Databases and Creating a Standard procedure for successive deployments.
4.1 Navigate to menu options Enterprise -> Provisioning and Patching > Database Provisioning

of 66
4.2 Select the “Provisioning Oracle Database” procedure from the list of deployment procedure and click ‘Launch’
4.3 You are going to Provision “12.1.0.1.0” Database on ‘Linux x86-64’. This is a Standalone Database Install, so choose “Do not Provision” for GI . For Database select “Deploy software and create a Database” option.

of 66
4.4 Click to lock the inputs, this would grey out the fields and persist it.
4.5 To select destination hosts, click ‘Add’ and choose ‘em12.oracle.com’ as the destination host.

of 66
Click Next.
4.6 There are 4 more steps in the procedure of Provisioning of Database Oracle Homes along with creation of Databases. Let’s start with “Setup Hosts” click on the link.
4.7 1st step in the task is to pick OS credentials for ‘Oracle’ account and ‘root’ account. Select ‘HOST-ORACLE’ and ‘HOST_ROOT’ for Normal and Privileged users respectively.

of 66
4.8 Click to lock the inputs, this would grey out the fields and persist it. Click ‘Next’.
4.9 2nd step in this task is to specify OS groups. Default groups are recommended. Directly accept the values and Click to lock the inputs.
4.10 Task No:1 - Host setup is complete. Click on the next task ‘Deploy Software’.

of 66
4.11 ‘Gold Image’ of the DB 12.1.0.1 software can be created in EM either directly from the Zip files (install media) from OTN or from a reference install. In this case the Gold Image is pre-created for the lab. Select the software “OracleDB_12101_Profile_Dabase gold image” from the list.
4.12 Click the Lock Icon to lock down the software for future deployments.

of 66
4.13 Next specify the Oracle Base and Oracle Home locations. Leave the Base to the default recommended value. Click the lock icon for the Oracle Base.
4.14 Suffix your shortname to the default value for Database Oracle Home. (%ORACLE_BASE%.../db_YourInitials)
4.15 Specify “/tmp” for the Root Dispatcher location. Lock all the fields including -Installer Parameter and Click Next.
4.16 Tasks 1 and 2 are complete with all values set and locked. Next task in the process is configuring the Database under Create Databases step. Click ‘Create databases’

of 66
4.17 First step in the task is to pick a Template. Choose the DataWarehouse template from Oracle Home.
4.18 Lock the template choice by clicking the lock icon, then click “Next”

of 66
4.19 Next step is to provide Database identification details like Name, SID. Specify Global Database Name: ‘newtest.oracle.com’, SID; newtest In this exercise we would create just “ 1” PDB in the CDB, specify the PDB Name as “newbiz”
4.20 Since this would be dynamic based on the every deployment request, DO NOT click Lock for the Identification parameters. Click ‘Lock’ for PDBs that would be created.

of 66
4.21 Choose the option for same passwords for all accounts. Specify password ‘Oracle12”.
4.22 Click Lock to lock the credentials field, , then click “Next”
4.23 Next step in the task is to define Storage options. Review the default values. Click the Lock icon for every field and then Click ‘Next’

of 66
4.24 Next step in the task is to define Initialization Parameters. Review the default values. Click the Lock icon for every field and then Click ‘Next’
4.25 Specify the name of the listener as “LISTENER_NEWTEST” under port “1530”. Lock all the fields including the Listener.

of 66
4.26 Click ‘Next’ to get to Review page and Click ‘Next’
Last task in the process is to associate the deployment with a Compliance Standard. This ensures the Database being provisioned is setup with Compliance from the beginning.
4.27 Associate with the Corporate DB Compliance Standard – custom created for the company. Click ‘Lock’ icon to lock the field and then click ‘Next’
4.28 Completing tasks checks the arrows across it and locks indicate fields with values protected. Click ‘Next’ to proceed to deployment.

of 66
4.29 Go with the default schedule – Immediate, click ‘Next’ to go to the Review page.
4.30 Before submitting the procedure for deployment, you can preserve all the values entered during the interview as a configured deployment procedure. Click ‘Save’ to store the procedure. Specify name “MyShortname_CompanyCDBProcedure” and a description.
Tip: No spaces in the name field. This is being rectified in the upcoming patch bundle cycle.

of 66
4.31 Click ‘Save’ and then Click ‘Ok’ in the confirmation screen.
4.32 Click ‘Submit’ to fire the procedure to deploy the Container Database with a Pluggable Database within it.
Upon submit, the procedure is triggered to begin deployment. The steps can be tracked, and you can view the logs from the steps directly. The procedure deploys a 12.1.0.1 Container Database (‘newtest’) with a Pluggable Database (‘newbiz’).
The process of deployment takes about 30 minutes. Flip through the steps below to the next exercise.
You can come back to view the procedure status and view the provisioned Database.

of 66
4.33 Navigate to ‘Enterprise -> Provisioning and Patching -> Procedure Activity’
4.34 Find and select the Provisioning Oracle Database job which may either be in running or Succeeded Status.
4.35 Navigate to ‘Targets > Databases’

of 66
4.36 From the list, choose the 12.1.0.1 Container Database - “newtest .oracle.com’ and click on the database name and navigate to its home page.
Tip: Use Search to quickly identify the ‘newtest’ database.
4.37 Select the newly migrated ‘test.oracle.com_HR3’ PDB to navigate to its home page.
The CDB “new_test” and the PDB “New Biz” is provisioned inside it.
At times there can be a delay in PDB being shown in the list, as the post creation configuration should be still be running.

of 66
Part 2
Scenario: Post the CIO circle meeting, Tim sets the new vision for IT – Move to cloud, which would delivers faster services, cheaper and with lower risk. He appoints his confidant and vetted expert Dave as the Cloud Architect. Dave along with Thomas will guide the company’s journey towards cloud.
Based on the guidelines set by Dave, Sally (DBA manager) works with Clark (lead DBA) to pilot their Database operations towards Self Service within the confines of their private cloud. You will be playing the role of Clark, using Enterprise Manager 12c you will kick start the pilot for private cloud setup and self service Database provisioning.

of 66
GOAL: Self Service IT - Databases in Private Cloud.
In this part, you will complete the following exercises: Exercise No Feature Time What are you doing? Relation to the scenario
1
Create CDB Pool
10 mins
As an administrator you are setting up the cloud for end users. Since it’s PDB to be made as self service option- you are creating a CDB Pool and associating a PDB’s service catalog to be used during provisioning requests.
Aligning to the company’s new direction of moving to an on- premise Private cloud. Clark sets up cloud infrastructure for self service provisioning starting with the new DB12c.
2
Request PDB via Self Service (PDBaaS)
10 mins
Requesting a PDB as a Self Service User.
Ravi can now login and try out Self Service provisioning in the internal PDB cloud.

of 66
Scenario #5. Pluggable Database as a Service (PDBaaS)
Introducing Self Service Provisioning with EM12c’s Database as a Service (DBaaS). This allows Clark and his team to scale up to the demands of the new responsibility. Self service allows metering, charge back or show back allowing his team to accurately plot the usage by the business and this information can be used to predict the demand.
EM12c Database as a Service’s one of the product offering is Pluggable Database as a Service. On demand provisioning of Pluggable Databases in a Container Database (CDB) pool. End users are provided with different services for example differentiated based on size (S, M, and L) to pick from on the self service console.

of 66
5 Creation of a Container Database (CDB) pool for Self Service
5.1 Create Pool
5.1.1 Navigate to Setup->Cloud->Database
5.1.2 From the Database Pools page, select Create… ->For Pluggable Database
5.1.3 Specify a name to the Pool and provide a description.

of 66
5.1.4 Set the values for Container Databases as follows: PaaS Infrastructure = ‘PDB Zone’, Target Type=’Database Instance’, Platform=’Linux x86-64’ and Version = ’12.1.0.1’
5.1.5 Click Add in order to select the CDBs to include.
5.1.6 Select ‘test.oracle.com’ database and click Select.

of 66
5.1.7 Specify the Credentials. Select for Host = ‘HOST-ORACLE (ORACLE)’ and for Database = ‘DB-SYS-Global (ORACLE)’
5.1.8 Review your inputs and then click Next.
5.1.9 Accept the default Placement Constraints by clicking Submit.

of 66
5.2 Setup “Quotas” to regularize the usage
5.2.1 Select the Quotas item to edit the Self Service user database quotas.
5.2.2 Select ‘DBAAS_CLOUD_USERS’ row and click Edit…
5.2.3 Set the quotas for ‘Number of Pluggable database Service Request’=5 and ‘Number of Schema Service Requests = 1. Then click OK.

of 66
5.3 Associate a Service Template with the Pool
5.3.1 Select ‘Profiles and Service Templates’ from the menu.
5.3.2 Select Create…->For Pluggable Database from the Service Template area.
5.3.3 Enter ‘Development_Env_Small’ as the Name. Select ‘Create Pluggable Database from Profile’ and click the Search icon.

of 66
5.3.4 Select ‘ONDEMAND_PDB’ and then click ‘Select’
5.3.5 Click Add button to choose a Zone and Pool to deploy this type of Service Template request.

of 66
5.3.6 Select PDB_Zone then click Select.
5.3.7 Select the PDB_Zone row and click Assign Pool.
5.3.8 Choose the PDBaaS_Pool then click Select.

of 66
5.3.9 Ensure your setting match the screen below then click Next.
5.3.10 Click Create… from the Workloads area.
5.3.11 Enter ‘Small_Dev_Workload’ for the Name and set the resource values as follows: CPU=1, Memory=2, Sessions=25 and Storage=5. Then click Create.

of 66
5.3.12 Click Next.
5.3.13 Accept the default Initialization Parameters by click Next.
5.3.14 Click Next.

of 66
5.3.15 Click Add in the Roles area.
5.3.16 Choose ‘DBAAS_CLOUD_USERS’ role then click Select.
5.3.17 Ensure your settings match the screen below and click Next.

of 66
5.3.18 Check your settings with below screen and then click Create.
You have now successfully setup the Database Cloud Self Service Portal.

of 66
6 Deploying of Pluggable Databases from Self Service Console (PDBaaS)
6.1 Logout of Enterprise Manager as the Oracle user.
Deploying of Pluggable Databases from Self Service Console (PDBaaS)
6.2 Login as self service user JOHN_SMITH Password = ‘oracle12’

of 66
6.3 Select Databases from the Manage menu.
6.4 Select Request->Pluggable Database from the Database Service Instances menu.
6.5 Choose the ‘Development_Env_Small’ Service Template and click Select.

of 66
6.6 Enter PDB Name = ‘jsdev1’ and Database Service Name = ‘jsdev1svc, Select ‘Small_Dev_Workload’ for Workload Size.
6.7 Enter ‘oracle’ for Administrator Name with password = ‘oracle12’.
6.8 Ensure your settings match the screen below and click Submit.
The request status can be seen in the Request area. It will take about 5 minutes to complete the request.

of 66
If you have time, you can wait for the request to complete.
6.9 Select ‘Real Time: 30 Seconds Refresh’ from the View Data option to automatically refresh the page and request status.
6.10 Once the Request succeeds, you should be able to see your new Service Instance in the Database Service Instances area. Select test.oracle.com_JSDEV1 to go to the targets home page.

of 66
6.11 Here you can see important information about the newly created PDB like Connect string and available space. You will also notice you can Shutdown or Startup the PDB yourself.

of 66
END OF LAB

Database Lifecycle Management and Cloud Management - Hands on Lab (OOW2014)

More Related Content

What's hot (20)

Similar to Database Lifecycle Management and Cloud Management - Hands on Lab (OOW2014) (20)

Recently uploaded (20)

Database Lifecycle Management and Cloud Management - Hands on Lab (OOW2014)