a lab tutorial about how you can get started and automate db12c multitenant lifecycle using...

Oracle DB12c Multitenant

Database Lifecycle

Management with Oracle

Enterprise Manager

of 53

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 for the new Database 12c Pluggable Databases.

Scenario: Company “Plug Inc” decides to adopt Database 12c’s Pluggable Databases.

Sally (the DBA Manager) asks Clark (the DBA lead) to start the migration of the Databases to DB12’s Pluggable Databases in the next 3 months. Sally also wants Clark to start providing DB12c PDB for any new Database request unless it’s for Production. The following conversation is set in the 2 months from the launch of Oracle Database 12c.

Can you also add - How many of these PDBs are running on Exadata versus non-

Exadata?

Sure. (Inventory Reports and Configuration Search, 10 mins)

Clark, hope we are not creating anything other than PDB unless it’s a production

request. Can you send me a report?

Definitely. In fact, will send 2 reports to contrast things better for management

reporting - #1 How many of our DBs are PDB vs Regular? #2 DB versions in Non

production post the mandate to show its all PDBs.

JULY 2013

Oracle Releases DB12c

Great job with PDB testing, the results were impressive. Good news is that now we

have new licenses for DB12. Can you start moving old databases to PDBs using a

phased approach?

Thanks. Got a head start using a test license and deployed a few PDBs. Will

‘MIGRATE’ the HR Database from test environment to a PDB.

It takes just a few clicks using EM. (Migrate to PDBs, 20 mins)

Aug 5th 2013

Sep 17th 2013 02:00 PM

Sep 17th 2013 02:08 PM

Did you see the request from the Finance apps guys on a test PDB? Should I tell

them it’s going to take time?

On it, just takes few mins and a couple of clicks with EM. (PDB Clone, 5 mins)

Can you check if the ERP’s DB12 confirms to the compliance mandates? Can you

correct any issues seen in the next few weeks before the half yearly meeting?

Will run it against the Gold Standard to check for violations. Need to review the

impact and give you a more accurate timeline on remediation. (Compliance Mgmt., Topology Viewer, Patching 15 mins)

Sep 20th 2013

Sep 23rd 2013

of 53


Getting Started

The following exercises are based on Enterprise Manager 12c Release 3 (12.1.0.3) with latest Database and My Oracle Support Plug-ins (12.1.0.5). This lab is constructed on an Enterprise Manager 12c setup which manages:

1. A Standalone Database 11gR2 (11.2.0.3) (Used in Scenario #1 for Migration) 2. A DB12c (12.1.0.1) Container Database (called ‘test.oracle.com’) with 5 Pluggable

Databases. 3. 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.

Sep 23rd 2013 ERP DB needs a patch to be compliant to the new Gold Standard. I also received a

mail from the SA (Security Admin) to apply the latest PSU patch.

I created a test patch plan with both the patches, ran an analysis. There aren’t any issues

in applying them. With EM12c’s new ‘Out of Place’ automation, prepared a new clone

OH and patched it. I just need 10mins in the weekend, will click a button, EM will then

switch the Databases and run SQL to complete patch deployment. All of these with no

touch to the target or EM for updating info.

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 53


Scenario #1. Migrate non DB12 to a Pluggable Database

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) (Basic deployment from scratch) Automate Migration of the non CDBs to a PDB (Focus in this lab) Business Case/ Problem Statement

You have been asked to migrate a 11.2.0.3 database to a Pluggable database (PDB) inside an existing Container database (CDB). Use Enterprise Manager 12c’s automated PDB migration feature to perform the migration quickly.

JULY 2013

Oracle Releases DB12c

Great job with PDB testing, the results were impressive. Good news is that now we

have new licenses for DB12. Can you start moving old databases to PDBs in phase wise

manner?

Thanks. Got some head start, used a test license and deployed few PDBs. Will

‘MIGRATE’ the HR Database from test environment to a PDB.

It just takes a few clicks using EM. (Migrate to PDBs, 20 mins)

Aug 5th 2013

of 53


1. Migrate 11.2.0.3 DB into a Pluggable (PDB) within an existing Container Database (CDB)

1.1 Login using username: oracle and password: oracle12

1.2 Navigate to menu options Targets->Databases

of 53


1.3 From the list, choose 12.1.0.1.0 Container Database – ‘test .oracle.com’ and Click on the database name

to navigate to its home page.

Tip: Use Search to quickly identify the ‘test’ database.

1.4 From the database home page, navigate to ‘Provisioning -> Provision Pluggable Databases’.

of 53


1.5 Select the ‘Migrate Existing Databases’ option from the PDB Operation list and click ‘Launch’

You can Provision Pluggable Databases inside a Container Databases,..

1.6 From the options of data migration, choose ‘Use Oracle Data Pump Full Transportable…’ option.

Migration path for a non Container Database (CDB): a) Plug as a PDB Method: PDB based migration is supported for non-CDBs of version 12.1 or higher. This option creates an XML description of the database that is used to create the PDB. The datafiles will also be copied over as part of the migration. b) Data Pump Method: Data Pump based migration is supported for non-CDBs of version 11.2.0.3 or higher. This option will use Oracle Data Pump to export the data from non-CDB which will be imported into the PDB using Oracle Data Pump import. The datafiles will also be copied over as part of the migration.

of 53


1.7 Credentials are already set as Preferred, click Next

1.8 Click “Add” and select the database “hr3.oracle.com” of the version 11.2.0.3.

of 53


1.9 Change the Database Credentials to ‘SYSDBA Database Credentials’ and Database Host Credentials to

‘HOST-ORACLE’ named credential.

of 53


1.10 Complete the interview with the following information:,

Export Directory - /tmp

PDB Properties - PDB Administrator : ‘oracle’ , Password ‘oracle12’

Import Directory - /tmp

of 53


1.11 Specify data file location by clicking Browse next to ‘Datafile Location’ and select ‘cdata’ directory row

then click OK.

of 53


1.12 Click ‘Next’ , the action runs the validations

1.13 Click ‘Close’ after successful Validations

of 53


1.14 From the schedule page, retain the default schedule ‘Immediately’ , click ‘Next’

1.15 Verify the details on the Review page, click ‘Submit’

1.16 Upon submission the details of the job can be viewed directly via ‘View Job’ button

of 53


1.17 The process steps and details can be tracked from the Procedure Activity page.

The ‘hr3’ 11.2.0.3 Database will be migrated as a Pluggable Database into the Container

Database – test. The process of migration takes about 30 minutes. We will return to

see the results of the migration process in lab 6. For now, continue on in the lab.

Skip to the next exercise.

of 53


Scenario #2. Using Inventory & Configuration Search

Business Case/ Problem Statement

You have been asked to report on the current and historic distribution of PDBs to regular databases as well as how many PDBs are running on an Exadata. Use the Inventory and Usage details page as well as Configuration Search to answer these requests quickly.

2.1 Navigate to menu options Enterprise->Configuration->Inventory and Usage Details

Can you also add - How many of these PDBs are running on Exadata versus non-

Exadata?

Sure. (Inventory Reports and Configuration Search, 10 mins)

Clark, hope we are not creating anything other than PDB unless it’s a production

request. Can you send me a report?

Definitely. In fact, will send 2 reports to contrast things better for management - #1

How many of our DBs are PDB vs Regular? #2 DB versions in Non production post the

mandate to show its all PDBs.

Sep 17th 2013 02:00 PM

Sep 17th 2013 02:08 PM

of 53


2.2 Choose “Databases” from list next to Show.

By default we see the distribution of databases by database version.

Clark’s response to “How many PDBs versus Regular Databases we have?”

For sending the report in a mail, do print screen and paste in the mail.

2.3 Select the rows for ‘Database versions – 10.2.0.4’, ‘ Database Instance 11.2.0.3’ and ‘Pluggable Database

12.1.0.1’ and Click ‘View Details’.

of 53


2.4 Switch the Chart view to ‘Trend’ to see the historical trend of the growth of different Database version

Here we can see the answer to the first question posed by Sally which was to ensure no new databases

have been created that were not PDBs. We can see there are now 25 PDBs in the environment. Now

let’s move on see how many are installed on Exadata Database Machines.

of 53


Configuration Search

Creating a configuration search to identify how many out of ‘25’ PDBs are on Exadata Database Machine.

2.5 Navigate to menu options Enterprise->Configuration-> Search.

2.6 Click ‘Create’ to create a new Configuration search.

EM12c provides pre-defined Configuration search templates, users can create custom search using the collected

configuration properties of the targets. The search can be saved for repeated or future usage.

of 53


2.7 Select the Target Type to ‘Pluggable Database’

2.8 To figure out if the PDBs are on Exadata or not, add a Relationship

of 53


2.9 Choose the Destination Target type to ‘Host’

2.10 Choose the Relationship Type as ‘Hosted by’ and Click ‘OK’

of 53


2.11 To indicate we want to restrict our selection to Exadata, we will use a target property. Start by clicking

‘Properties’

2.12 Choose ‘Is DB Machine Member’

of 53


2.13 Enter ‘1’ ( which means true ) next to ‘Is DB Machine Member’ then click ‘Search’ to identify the PDBs

that run on the Host which are a member of Exadata DB Machine

2.14 Out of the 25 PDBs , 11 PDBs are running on Exadata Database Machine.

Clark can send the report by clicking ‘Print’

2.15 The Search can be saved for future executions to generate report. Click ‘Save As’ and provide a name ,

Click ‘Ok’

of 53


Scenario #3. Rapid Clone of Pluggable Database

Value Proposition: On-demand Cloning of Pluggable Database (PDB)

Reduced time and effort by automated Cloning of PDB’s.

Fast creation of test benches for Test and Development environments making application lifecycle management lot easier

Extensible framework allows customers to incorporate their own scripts along with the out of box feature (Pre and post scripts)

Business / Technical Challenge: One of the biggest IT challenges is to quickly create clones of production databases for Test and Dev instance.

Oracle’s Solution:

Oracle Enterprise Manager provides comprehensive automated workflows using which a DBA’s can easily clone PDB’s , this enables automation and effectively lowers the Total Cost of Ownership (TCO).


You have been asked to create a clone of the existing Finance PDB. Use Enterprise Manager’s automated cloning feature to accomplish the task quickly and easily.

Did you see the request from the Finance apps guys on a test PDB? Should I tell

them it’s going to take time?

On it, just takes few mins and a couple of clicks with EM. (PDB Clone, 5 mins)

Sep 20th 2013

of 53


3. Clone of Pluggable Databases

3.1 Go to Databases Home page; From the menu: ‘Targets > Databases’

3.2 From the list, choose the 12.1.0.1 Container Database – ‘test .oracle.com’ and click on the database

name to navigate to its home page.

Tip: Use Search to quickly identify the ‘test’ database.

of 53


3.3 Navigate to : ‘Oracle Database > Provisioning > Provision Pluggable Databases’

3.4 From the options select “Create Pluggable Databases” and click ‘Launch’

of 53


3.5 From the options of Create, select ‘Clone PDB’ and click search next to Source PDB.

3.6 Search and select ‘FINANCE’ PDB

of 53


3.7 Click ‘Next’.

3.8 Specify the name for the new PDB ‘FINANCE1’

3.9 Ensure the Preferred Credentials are set as SYSDBA

of 53


3.10 Upon successful verification, click Next

3.11 Specify the Temporary Working Directory – ‘/tmp’ and click Next.

3.12 With the default schedule – Immediate , click Next

of 53


3.13 Review the details and Click Submit

3.14 To review in-depth step by step execution, Click ‘View Execution Details’

3.15 Update the View Data time to 30 sec Refresh, select any step as it executes to view Details.

of 53


3.16 Select Create Pluggable Database Job step to view the details.

Newly cloned PDB – ‘FINANCE1’ is created in just over 2 mins.

3.17 From the targets menu , select Databases and select the ‘test.us.oracle.com’ database

of 53


3.18 Select the ‘test.us.oracle.com’ database to navigate to its home page.

3.19 Newly cloned PDB – ‘ FINANCE1’ is listed under the CDB – ‘test.oracle.com’

of 53


Scenario #4. 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 graphically display targets and their relationships to one another view perform Impact and Root cause analysis before taking action. Remediation requiring the application of patches can be performed automatically using Patch Plans for single or mass patch deployments.


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.

Can you check if the ERP’s DB12 confirms to the compliance mandates? Can you

correct any issues seen in the next few weeks before the half yearly meeting?

Will run it against the Gold Standard to check for violations. Need to review the

impact and give you a more accurate timeline on remediation. (Compliance Mgmt., Topology Viewer, Patch Automation 15 mins)

Sep 23rd 2013

of 53


4. Use the Compliance Standards to check for deviations from corporate standard.

4.1 Go to Targets->Databases

4.2 Select ‘erpdb.us.oracle.com’ database to go to its homepage.

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. Continue after clearing the message.

of 53


4.3 Navigate to ‘Oracle Database ->Compliance -> Standard Associations’.

4.4 Click on ‘Edit Association Settings’ to associate a new compliance standard to this database.

4.5 Click ‘Add’ to choose from list of compliance standards.

of 53


4.6 Select ‘Corporate DB Compliance Standard’ and click OK.

4.7 Click OK to begin compliance evaluation against the selected standard.

4.8 Click Yes to confirm the association.

of 53


4.9 Click OK.

4.10 Navigate to ‘Oracle Database -> Compliance->Results’ to view the results of this target’s compliance

standings.

We can see there is 1 critical violation to the Corporate DB compliance standards. Let’s take a look to see what it is.

of 53


4.11 Select ‘Corporate DB Compliance Standard’ and click ‘Show Details’.

4.12 Select the ‘Mandatory Required Patch – 16705020’ rule to view details of the violation.

of 53


4.13 Select the ‘Violation Events’ tab to get to the details of the violation.

4.14 Select the event from the table to see more details.

Here we can see we are missing a mandatory patch as determined by corporate security. 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 53


Use Topology Viewer to understand CDB/PDB Relationships 4.15 Navigate to ‘Oracle Database -> Configuration -> Topology’

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.

PDBs that will be impacted by patching

Container Database

of 53


Scenario #5. Patch Automation

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 is 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.

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.

Sep 23rd 2013 ERP DB needs a patch to be compliant to the new Gold Standard. I also received a

mail from the SA (Security Admin) to apply the latest PSU patch.

I created a test patch plan with both patches, ran an analysis there aren’t any issues in

applying them. With EM12c’s new ‘Out of Place’ automation, prepared a new clone OH

and patched it. I just need 10mins in the weekend, will click a button, EM will then

switch the Databases and run SQL to complete patch deployment.

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 53


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.


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 with its PDB in Out of Place patching, reducing the downtime and helps handle any issues during maintenance with ability to switch back to the old Oracle Home.

5. 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.

5.1 Navigate to ‘Enterprise -> Provisioning and Patching -> Patches & Updates’

of 53


5.2 Open up Patch recommendations, Click “All Recommendations”.

Search for target “test.oracle.com” from the list. Switch the type to “Target Name”.

EM generates automatic patch recommendation list against Oracle recommended patches (like CPUs, PSUs ,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. 5.3 Select the PSU patch recommended for 12.1.0.1 Database, click “Add to Plan” and select “Add to New”

of 53


5.4 Provide a name to the plan, recommended format “<YourShortName>_ Patch_CDB_12101 and click

‘Create Plan’.

5.5 Click ‘View Plan’ to open the plan and navigate to Patches page in the Plan wizard.

of 53


5.6 Click “Add Patch…” to add the patch required based on the corporate compliance standard – patch

“16705020”.

5.7 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 53


5.8 Plan now contains both the patches. Navigate to the next step in the Patch plan - Deployment

Options.

5.9 Patch Plan supports both ‘In-Place’ and ‘Out –of-place’ modes of patching. In this lab, we will follow

the new methodology – Out of Place mode.

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’ .

of 53


5.10 Specify both Home Name – “shortname_psu’ and Home Location. For OH location copy the existing

location and change the final directory to ‘db12c_shortname_psu’. Click Validate and after validation, click

‘Create’.

of 53


5.11 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.

5.12 Scroll down the review page to see the Impact targets list. This lists the complete topology of the

Container Database and its Pluggable Databases included in this plan.

5.13 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.

of 53


Tip: Wait for few seconds, the link for Show detailed results will show up in the Analysis message bar.

5.14 From the procedure execution, click on a step to see the complete execution logs.

of 53


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.

5.15 The Analysis takes about ’10mins..’ in the mean time, check the pre-cooked Patch Plan where Analysis

for the same target and patches are completed.

Switch the older tab , click on ‘Patches and Updates’ to view the list of Patch plans.

of 53


5.16 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 53


5.17 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.

5.18 This step takes close to 20+mins, we would skip to a plan which is already prepared and proceed to

deploy from there. Click on ‘Patches and Updates’ and go to the list of Patch plans page.

of 53


5.19 Choose the patch plan ‘CDB12.1_OCTPSU_PREPARED ‘ and click open or click ‘View’

5.20 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 53


5.21 Click ‘Deploy’, this would trigger a procedure to switch the Databases (the CDB and the corresponding

PDBs) from old OH to the new OH.

5.22 Click on ‘Show Details’ in the message bar and track the steps of the Patch Plan’s deployment phase.

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 is 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.

END OF LAB

a lab tutorial about how you can get started and automate db12c multitenant lifecycle using...

Technology