X

An Oracle blog about Oracle Enterprise Manager and Oracle Management Cloud

  • July 7, 2020

Turbocharge Your Database Provisioning: Use Enterprise Manager Lifecycle Management to Increase Efficiency, Consolidation and Standardization

Martin Pena
Senior Director Product Management

Provisioning is arguably the first step in the lifecycle of database management.  And in many regards, it is perhaps the most important step.  Provisioning databases in a consistent and standardized way, sets the stage for creating standardized database deployments; standardization is essential for getting the most bang for the buck when implementing database automation at scale.  Consistent deployments of databases, will make tasks such as backup, recovery, patching, and upgrades easier to manage and automate at scale.

Oracle Enterprise Manager provides a complete set of out-of-box tools that enables rapid provisioning of databases, in a consistent, standardized manner. The Database Lifecycle Management Pack (DBLM) helps database administrators eliminate manual and time consuming tasks; the following features form the building blocks of DBLM provisioning automation:

  • Database Provisioning Console displays information about provisioning setup, profiles, deployment procedures, and information about getting started with provisioning
  • Deployment Procedures –are sets of predefined steps that automate the provisioning process
  • Provisioning Profiles are used to ensure standardization in deployment and to minimize errors
  • Database Templates are used for cloning or creating additional databases. 

These provisioning automation tools can be used across the entire database fleet to provision the full range of database configurations, including:

  • Multitenant Databases
  • Single Instance and RAC Databases
  • Data Guard and Far Sync configurations
  • Databases on Virtualized Exadata
  • Databases for Self Service Users

In addition to providing basic database provisioning, the tools can also be focused on more advanced and strategic functionality:

Customized Deployment Procedures:  Out of box deployment procedures provide immediate value for provisioning a wide range of database deployments.  In addition, administrators can customize these deployment procedures to provide greater flexibility to precisely model the new databases to conform with internal practices.

Lock down access for controlled and error-free deployments:  DBLM allows administrators to define and setup a clear separation of the Designer and Operator roles for provisioning.  Senior DBAs, as designers, can build standardized templates based on internal best practices.  Specific parameters can be locked down or remain editable.  Junior DBAs can use these pre-defined templates to execute the provisioning.  This model helps enforce standard deployments of new databases.

Migration of non-CDBs to PDBs:  As customers move toward the multitenant architecture to take advantage of consolidation opportunities, DBLM can be used to perform error free and efficient migrations to multitenant  architecture.  The product offers choices between various migration technologies; customer can choose the best fit for their environment, including Clone PDB and Data Pump.

Learn More:

Webinar: Automate your Database Provisioning to Increase Efficiency and Standardization

Date: July 9th, 2020 10 am PST

Learn how DBAs are automating provisioning to rapidly create standardized database deployments across on-premise and Oracle Cloud Infrastructure (OCI) data centers. Additionally, DBAs are deploying a self-service portal to enable organizations like DevOps to create databases on-demand while achieving maximum resource utilization and standardization.

Register for this interactive session including live demonstrations and dedicated time to get your questions answered by Oracle experts.

This webinar is from the Deep Dive Enterprise Manager Webcast Series.

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.