Monday, February 17, 2014

oracle database12c EM Express and CDB




Oracle Database 12c: EM Express and CDB

Enterprise Manager Database Express, also referred to as
EM Express, provides support for CDB.  Users can configure EM Express both at the root and the PDB containers, with each container using a different HTTPS/HTTP port.

At the root container, data is displayed for the entire CDB, and all actions taken impact all containers.  Data pertaining to a PDB, such as a user or a SQL statement, is qualified with the container name.  The actions a user can perform at the root container include: viewing and setting initialization parameters; administering common users and privileges; and managing memory configuration, undo information and redo logs.

When a user is connected to a PDB, data is displayed only for the container in question, and actions only impact that container.  This means that data pertaining to the CDB will not be visible at the PDB, and not all pages will be available.  The actions a user can perform when connected to a PDB include viewing and setting initialization parameters for the PDB, and managing tablespaces and profiles.

The functionality available on a CDB and a PDB is not identical, and also differs from the functionality available on a non-CDB system.


Active Report Examples

http://www.oracleimg.com/ocom/groups/public/@otn/documents/digitalasset/111282.gif
http://www.oracleimg.com/ocom/groups/public/@otn/documents/digitalasset/111282.gif
Frequently Asked Questions
Answers
How do I configure EM Express on a CDB?
You can configure EM Express at the root container or at the PDB.  Simply login to the container and set the HTTPS/HTTP port.  Each container will need to use a different port.
SQL> connect sys/<password>@<container> as sysdba
Connected

SQL> exec dbms_xdb_config.sethttpsport(5501);

PL/SQL procedure completed
If you're using a listener TCP port other than 1521, you will also need to set the dispatchers and local_listener  initialization parameters, just like you would in a non-CDB system.  Please see the documentation for further information.

Why is the Storage menu missing the Tablespaces entry in a CDB?
Tablespaces are local to a PDB, so the Tablespaces entry is not available at the root container.  To view and manage tablespaces or datafiles on a PDB, go to the EM Express configured on that PDB.

Can I manage and create Common Users with EM Express?
Yes, Common Users can be created and managed from the root container.
At the PDB container, you can only create and manage local users.

Why are tabs missing from the Performance Hub?
At the PDB container, only the Activity and Monitored SQL tabs are visible because these are the only tabs that display PDB-specific data. 
At the root container, all tabs are available in the Performance Hub.

Can I see the activity breakdown by PDB?
Yes, at the root container, you can see the Average Active Sessions breakdown by container using the Home Page and the Performance Hub (Summary tab or Activity tab).
This data is taken from ASH, not metrics, so you might see a discrepancy when comparing average active sessions per container against a different breakdown.

Why do I see PDB$SEED when viewing Activity breakdown by PDB?
Although PDB$SEED is just a seed database, when queries are issued against CDB_* views, the server internally switches to all containers, including PDB$SEED, to retrieve data.  If there are frequent queries against CDB_* views, this could result in activity captured against PDB$SEED.


Can I plug and unplug PDBs with EM Express?
No, EM Express does not provide full CDB management capabilities in DB 12.1.0.1.0.


How can I tell if I'm connected to the root container or to a PDB?
You can get this information from the Status region in the home page.  If you are at the root container, the type will show "CDB (# of PDBs)", and if you are at the PDB, the region will include the Container Name to which you're connected.
In addition, the blue panel at the top of the page will have an icon on the top left that indicates if the database is a CDB.  The database name will be displayed after the icon:

If you're connected to a PDB, the container name will be displayed after the database name:

Can Point-In-Time recovery be conducted at Pluggable Database (PDB) level?
Yes, it will be possible.
Can database services be created inside a Pluggable Database (PDB)?
Of course you can have many services within a PDB. Each will denote the PDB within which it is defined as the initial current container. Use the normal methods to create, maintain, and drop additional services in a PDB. A PDB’s default service must not be dropped. Of course, service names should be unique across all the databases that are registered with a particular listener.
Can I have local TEMPORARY tablespace at Pluggable Database (PDB) level?
In spite, during the PDB creation only SYSTEM and SYSAUX tablespaces created, you can create local temporary tablespace later for every PDB. UNDO tablespace can NOT be local and stays on the CDB level.
Is conventional database mode will be still available in 12c database and later versions?
Yes, on Oracle 12c you will have two options of creating a usual old-fashioned Oracle database (non-CDB) or creating a Container Database (CDB) that will hold all your Pluggable Databases (PDB) that you will create or plug later. However, based on my information non-CDB mode will be available only in 12c release 1 for compatibility reasons and will be discontinued in 12cR2.
Will Oracle 12c database have only one container?
Yes and No! In fact, Oracle considers a CDB as well as all PDBs as containers. Every container has own name. For example a single Container Database (CDB) has a container name CDB$Root. Every Pluggable database has a container name similar to the PDB name. On CDB level by default your current container is CDB$Root but you can switch between PDBs’ containers also. On CDB level you can change current container with following SQL:
alter session set container = my_cdb
or verify current container with below SQL:
selectSys_Context('Userenv', 'Con_Name') "current container" from dual;
Is cloning a PDB from one in a different CDB supported?
I have not seen it in 12c Beta 2, but Oracle intends to support it in the final version. You’ll identify the source CDB by creating a database link to it from the CDB in which you will create the clone.
Is online PDB cloning supported?
Not in 12c Beta2, but Oracle intents to remove this restriction in the final versionby using the same approach that allows online RMAN backup: by re-constructing any blocks that change during the time it takes to copy the source PDB’s datafiles.
Why switching PDB Open_Mode/Restricted modes requires 2 SQL commands?
Not sure why, but in final 12c release it will be possible to go from any one Open_Mode/Restricted combination to another with a single use of the alter pluggable database statement.
Will it be possible to allocate/restrict resources (CPU/Memory) of PDB’s (Pluggable)?
Yes, it will be possible using new functionality of Oracle 12c Resource Manager.
Using 12c Resource manager you will be able control CPU, Exadata I/O, sessions and parallel servers. A new 12c CDB Resource Manager Plan will use so-called “Shares” (resource allocations) to specify how CPU is distributed between PDBs. A CDB Resource Manager Plan also can use “utilization limits” to limit the CPU usage for a PDB. With a default directive, you do not need to modify the resource plan for each PDB plug and unplug. However I’m not aware of a possibility to restrict memory of PDBs, since they will share one single SGA.
Oracle 12c Pluggable Database - Resource Manager
While waiting for Oracle 12c database release I’ll post some more things on Pluggable Database feature

Top Questions and Answers for Pluging into Oracle Database as a Service

By David Swanger on Oct 22, 2013

On Monday, October 21st we hosted an online forum that shared a comprehensive path to help your organization design, deploy, and deliver a Database as a Service cloud.
If you missed the online forum, you can watch it on demand by registering here.
We received numerous questions.  Below are highlights of the most informative:
DBaaS requires a lengthy and careful design efforts. What is the minimum requirements of setting up a scaled-down environment and test it out?
You should have an OEM 12c environment for DBaaS administration and then a target database deployment platform that has the key characteristics of what your production environment will look like. This could be a single server or it could be a small pool of hosts if your production DBaaS will be larger and you want to test a more robust / real world configuration with Zones and Pools or DR capabilities for example.
How does this benefit companies having their own data center?
This allows companies to transform their internal IT to a service delivery model for the database. The benefits to the company are significant cost savings, improved business agility and reduced risk. The benefits to the consumers (internal) of services if much fast provisioning, and response to change in business requirements.
From a deployment perspective, is DBaaS's job solely DBA's job?
The best deployment model enables the DBA (or end-user) to control the entire process. All resources required to deploy the service are pre-provisioned, and there are no external dependencies (on network, storage, sysadmins teams). The service is created either via a self-service portal or by the DBA.
The purpose of self service seems to be that the end user does not rely on the DBA. I just need to give him a template. He decides how much AMM he needs. Why shall I set it one by one. That doesn't seem to be the purpose of self service.
Most customers we have worked with define a standardized service catalog, with a few (2 to 5) different classes of service. For each of these classes, there is a pre-defined deployment template, and the user has the ability to select from some pre-defined service sizes. The administrator only has to create this catalog once. Each user then simply selects from the options offered in the catalog. 
Looking at DBaaS service definition, it seems to be no different from a service definition provided by a well defined DBA team. Why do you attribute it to DBaaS?
There are a couple of perspectives. First, some organizations might already be operating with a high level of standardization and a higher level of maturity from an ITIL or Service Management perspective. Their journey to DBaaS could be shorter and their Service Definition will evolve less but they still might need to add capabilities such as Self Service and Metering/Chargeback. Other organizations are still operating in highly siloed environments with little automation and their formal Service Definition (if they have one) will be a lot less mature today. Therefore their future state DBaaS will look a lot different from their current state, as will their Service Definition.
How database as a service impact or help with "Click to Compute" or deploying "Database in cloud infrastructure"
DBaaS enables Click to Compute. Oracle DBaaS can be implemented using three architecture models: Oracle Multitenant 12c, native consolidation using Oracle Database and consolidation using virtualization in infrastructure cloud. As Deploy session showed, you get higher consolidating density and efficiency using Multitenant and higher isolation using infrastructure cloud. Depending upon your business needs, DBaaS can be implemented using any of these models.
How exactly is the DBaaS different from the traditional db? Storage/OS/DB all together to 'transparently' provide service to applications? Will there be across-databases access by application/user.
Some key differences are: 1) The services run on a shared platform. 2) The services can be rapidly provisioned (< 15 minutes). 3) The services are dynamic and can be relocated, grown, shrunk as needed to meet business needs without disruption and rapidly. 4) The user is able to provision the services directly from a standardized service catalog..
With 24x7x365 databases its difficult to find off peak hrs to do basic admin tasks such as gathering stats, running backups, batch jobs. How does pluggable database handle this and different needs/patching downtime of apps databases might be serving?
You can gather stats in Oracle Multitenant the same way you had been in regular databases. Regarding patching/upgrading, Oracle Multitenant makes patch/upgrade very efficient in that you can pre-provision a new version/patched multitenant db in a different ORACLE_HOME and then unplug a PDB from its CDB and plug it into the newer/patched CDB in seconds. 

Oracle Database 12c Manageability—Answers to Your Common Questions

Sep 20, 2013





Since the launch of Oracle Database 12c, we at Oracle have received several questions about the new management capabilities built into Oracle Enterprise Manager 12c. Here are the answers to some of your more common questions. Enjoy!
Question: How does data masking differ from data redaction?
Data Redaction, which is part of Oracle Database 12c Advanced Security's product portfolio, provides selective, on-the-fly redaction of sensitive data in query results prior to display by applications so that unauthorized users cannot view the sensitive data. It enables consistent redaction of database columns across application modules accessing the same data. Data Redaction minimizes changes to applications because it does not alter actual data in internal database buffers, caches, or storage, and it preserves the original data type and formatting when transformed data is returned to the application. Whereas Data Masking, which is part of Oracle Data Masking Pack, allows DBAs and testers to "mask" sensitive and valuable information and replace it with realistic values for QA and testing purposes. This allows production data to be safely used for development, testing, and outsourced/off-shore partners or other non-production purposes. Read the Data Redaction whitepaper and read the Oracle Data Masking whitepaper.
Question: What is EM Express?
Oracle Enterprise Manager Database Express, or simply EM Express is embedded inside the database and is auto-configured at the time of installation. With only a 20 MB disk footprint, there is no resource usage when EM Express is not invoked or used. Oracle Enterprise Manager Database Express can manage both single instance and Oracle Real Application Clusters (Oracle RAC) databases. The tool also has built-in support for container databases (CDBs). Along with in-depth support for performance management features, Oracle Enterprise Manager Database Express can be used for configuration management, storage management and security management.
Question: Does each pluggable database (PDB) have its own EM Express? How do you make sure EM Express is not installed with every 12c database?
Yes. You can setup EM Express for each pluggable database. EM Express is installed by default. If you do not want to use it then do not set the XDB http/https port. Read the introduction to EM Express.
Question: How do you use EM Express to monitor pluggable databases?
EM Express can be invoked at the root container or inside a PDB. So either a container database administrator (CDBA) or a pluggable database administrator (PDBA) can use EM Express to monitor and manage a pluggable database. Read the introduction to EM Express.
Question: Do you use EM Express and EM cloud control at same time? What's the difference?
You can use both EM Express and EM Cloud Control on the same database. EM Express is built inside the database while EM Cloud Control uses an agent to monitor the database. Read the documentation.
Question: In order to use EM Express functionality in Oracle Database 12c, do you need to have the database packs installed?
Although the basic administration features (configuration, security, storage management) are included in EM Express, the performance management features such as, Performance Hub and SQL Tuning Advisor are licensed separately by Oracle Diagnostics Pack and Oracle Tuning Pack.
Question: Is EM Express available for Oracle Database Standard Edition?
Yes. EM Express is available for Oracle Database 12c Standard Edition. Read more.
Question: Can you do metering and chargeback in EM Express?
No. You cannot do metering and chargeback in EM Express. Metering and chargeback functionally is built into Oracle Cloud Management Pack for Oracle Database and can be used with delivering database as a service (DBaaS). Read the Delivering Database as a Service whitepaper for more details.
Question: Will EM Express be able to manage Data Guard?
No. There are no Data Guard management capabilities in EM Express.
Question: Can we create reports using metric extensions in EM Express?
No. You cannot create reports using metric extensions in EM Express.
Question: Can we use our existing Oracle Enterprise Manager 11g to monitor and manage Oracle Database 12c?
No. You cannot use Oracle Enterprise Manager 11g to manage Oracle Database 12c. In order to take advantage of all the new capabilities you will need to upgrade to Oracle Enterprise Manager 12c (Release 3) and use database plug-in 12.1.0.4.
Question: Which previous database versions are compatible with Oracle Enterprise Manager 12c?
Please check the support matrix in My Oracle Support as the information is updated regularly.
Question: Which versions of Oracle Database can be used with the Consolidated Database Replay feature?
You can use the Consolidated Database Replay on Oracle Database 11.2.0.2.0 and above. Please see My Oracle Support Note 1453789.1.
Question: We are using both Oracle Database 10g and 11g, we are trying to consolidate onto Oracle Database 12c, what is your recommendation?
We recommend using Oracle Real Application Testing to thoroughly test your consolidation. Learn more about using SQL Performance Analyzer to do unit testing of your SQLs' for response time and consider using Consolidated Database Replay to test your consolidation on Oracle Database 12c for throughput and scalability. You can capture workload on Oracle Database 10g and 11g and use Consolidated Database Replay on Oracle Database 12c. For more information on upgrading, be sure to visit the Oracle Database 12c upgrade page on the Oracle Technology Network.
Question: Do we still need the management server and agent running on every box if we upgrade to Oracle Database 12c?
Yes. The architecture used by Oracle Enterprise Manager 12c remains the same and is independent of your upgrade to Oracle Database 12c.
Question: When using Oracle Enterprise Manager 12c (not EM Express), is a separate agent still needed to monitor and collect stats on the instances and hosts?
Yes.
Question: Are there Oracle Enterprise Manager 12c agents available for Oracle Solaris?
Yes. Read more.
Question: Is Enhanced Real-time ADDM only for Oracle Database 12c or can you use it for previous versions?
Enhanced Real-Time ADDM is only available with Oracle Database 12c. Read the data sheet.
Question: Is ADDM integrated into the database or is it a database option?
For ADDM you need to license Oracle Diagnostics Pack.
Question: Several of our applications deal with spikes of activity as a norm, for example, we would get a file every 15 minutes and then process it. So spikes in our systems are normal. How does the new Enhanced Real-time ADDM work to spot the performance spikes?
Enhanced Real-Time ADDM uses a built-in algorithm to detect performance spikes. The current state of the database is evaluated against 9 different criteria (CPU, Memory, I/O, etc.) to determine whether there is a performance problem with your database.
Question: What's the difference between DBAs, PDBAs, and CDBAs?
The database administrator in the multitenant world has two new roles. The Container Database Administrator (CDBA) is responsible for the entire database which holds or contains pluggable databases. The Pluggable Database Administrator (PDBA) is responsible for individual pluggable databases servicing a specific application. For more information read the Oracle Multitenant whitepaper.
Question: To monitor batch jobs, where multiple sessions could be created, how is the batch job identified for monitoring?
Real-Time Database Operations monitoring doesn't’ support multi session yet. However if your batch job uses a single session you can set this job for monitoring via bracketing (i.e. begin operation and end operation).
Question: For the new multitenant architecture, how are resources (i.e. CPU, I/O, memory) handled among pluggable databases? Will there be memory set aside or capped for each PDB? How do you isolate PDBs for one another?
You can allocate CPU resources across pluggable databases via resource management plans. Memory management across PDBs is not yet supported. Read the documentation.
Question: For pluggable databases (PDBs), do you apply database patches to specific PDBs or do you apply the patches to the entire container database?
Database patches should be applied to the entire container database. Read the Oracle Multitenant whitepaper and watch the Pluggable Lifecycle Management demo for more information.

12c Database : New Background Processes

Here is the filtered tables after comparison of 11g with 12c Background Processes.
Name
Expanded Name
Short Description
Long Description
External Properties
AQPC
AQ Process Coordinator
Per instance AQ global coordinator
AQPC is responsible for performing administrative tasks for AQ Master Class Processes including commands like starting, stopping, and other administrative tasks. This process is automatically started on instance startup.
Database instances Advanced Queueing
ARSn
ASM Recovery Slave Process
Recovers ASM transactional operations
The ASM RBAL background process coordinates and spawns one or more of these slave processes to recover aborted ASM transactional operations. These processes run only in the Oracle ASM instance.
Oracle ASM instances
Possible processes are ARS0-ARS9.




BWnn
Database Writer Process
Writes modified blocks from the database buffer cache to the data files
See the Long Description for the DBWn process in this table for more information about the BWnn process.
Database instances
FENC
Fence Monitor Process
Processes fence requests for RDBMS instances which are using Oracle ASM instances
CSS monitors RDBMS instances which are connected to the Oracle ASM instance and constantly doing I/Os. When the RDBMS instance terminates due to a failure, all the outstanding I/O’s from the RDBMS instance should be drained and any new I/O’s rejected. FENC receives and processes the fence request from CSSD.
Oracle ASM instances
GCRn
Global Conflict Resolution Slave Process
Performs synchronous tasks on behalf of LMHB
GCRn processes are transient slaves that are started and stopped as required by LMHB to perform synchronous or resource intensive tasks.
Database instances, Oracle ASM instances, Oracle RAC
IPC0
IPC Service Background Process
Common background server for basic messaging and RDMA primitives based on IPC (Inter-process communication) methods.
IPC0 handles very high rates of incoming connect requests, as well as, completing reconfigurations to support basic messaging and RDMA primitives over several transports such as UDP, RDS, InfiniBand and RC.
Oracle RAC
LDDn
Global Enqueue Service Daemon Helper Slave
Helps the LMDn processes with various tasks
LDDn processes are slave processes spawned on demand by LMDn processes. They are spawned to help the dedicated LMDn processes with various tasks when certain workloads start creating performance bottlenecks. These slave processes are transient as they are started on demand and they can be shutdown when no longer needed. There can be up to 36 of these slave processes (LDD0-LDDz).
Database instances, Oracle ASM instances, Oracle RAC
LGnn
Log Writer Worker
Writes redo log
On multiprocessor systems, LGWR creates worker processes to improve the performance of writing to the redo log. LGWR workers are not used when there is a SYNC standby destination. Possible processes include LG00-LG99.
Database instances
LREG
Listener Registration Process
Registers the instance with the listeners
LREG notifies the listeners about instances, services, handlers, and endpoint.
Database instances, Oracle ASM instances, Oracle RAC
OFSD
Oracle File Server Background Process
Serves file system requests submitted to an Oracle instance
This background process listens for new file system requests, both management (like mount, unmount, and export) and I/O requests, and executes them using Oracle threads.
Database instances, Oracle RAC
QMnn
AQ Master Class Process
Per instance per AQ Master Class Process
Each of this type of process represents a single class of work item such as AQ notification, queue monitors, and cross process.
Database instances Advanced Queueing
RM
RAT Masking Slave Process
Extracts and masks bind values from workloads like SQL tuning sets and DB Replay capture files
This background process is used with Data Masking and Real Application Testing.
Database instances
RMON
Rolling Migration Monitor Process
Manages the rolling migration procedure for an Oracle ASM cluster
The RMON process is spawned on demand to run the protocol for transitioning an ASM cluster in and out of rolling migration mode.
Oracle ASM instance, Oracle RAC
RPOP
Instant Recovery Repopulation Daemon
Responsible for re-creating and/or repopulating data files from snapshot files and backup files
The RPOP process is responsible for re-creating and repopulating data files from snapshots files. It works with the instant recovery feature to ensure immediate data file access. The local instance has immediate access to the remote snapshot file’s data, while repopulation of the recovered primary data files happens concurrently. Any changes in the data are managed between the instance’s DBW processes and RPOP to ensure the latest copy of the data is returned to the user.
Database instances
SAnn
SGA Allocator
Allocates SGA
A small fraction of SGA is allocated during instance startup. The SAnn process allocates the rest of SGA in small chunks. The process exits upon completion of SGA allocation.
Database instances
The possible processes are SA00 – SAzz.




SCCn
ASM Disk Scrubbing Slave Check Process
Performs Oracle ASM disk scrubbing check operation
SCCn acts as a slave process for SCRB and performs the checking operations. The possible processes are SCC0-SCC9.
Oracle ASM instances
SCRB
ASM Disk Scrubbing Master Process
Coordinates Oracle ASM disk scrubbing operations
SCRB runs in an Oracle ASM instance and coordinates Oracle ASM disk scrubbing operations.
Oracle ASM instances
SCRn
ASM Disk Scrubbing Slave Repair Process
Performs Oracle ASM disk scrubbing repair operation
SCRn acts as a slave process for SCRB and performs the repairing operations. The possible processes are SCR0-SCR9.
Oracle ASM instances
SCVn
ASM Disk Scrubbing Slave Verify Process
Performs Oracle ASM disk scrubbing verify operation
SCVn acts as a slave process for SCRB and performs the verifying operations. The possible processes are SCV0-SCV9.
Oracle ASM instances
TTnn
Redo Transport Slave Process
Ships redo from current online and standby redo logs to remote standby destinations configured for ASYNC transport
TTnn can run as multiple processes, where nn is 00 to ZZ.
Database instances, Data Guard




VUBG
Volume drive Umbilicus Background
Relays messages between Oracle ASM instance and Oracle ASM Proxy instance that is used by ADVM (for ACFS)
Oracle ASM instances, Oracle ASM Proxy instances

No comments:

Post a Comment