|
Frequently
Asked Questions
- How do I configure EM Express on a CDB?
- Why is the Storage menu missing the Tablespaces entry
in a CDB?
- Can I manage and create Common Users with EM Express?
- Why are tabs missing in the Performance Hub?
- Can I view the activity breakdown by PDB?
- Why do I see PDB$SEED when viewing activity breakdown
by PDBs?
- Can I plug and unplug PDBs using EM Express?
- How can I tell if I'm connected to the root container or a PDB?
Answers
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
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.
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.
Yes, Common Users can be created and
managed from the root container.
At the PDB container, you can only
create and manage local users.
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.
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.
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.
No, EM Express does not provide full
CDB management capabilities in DB 12.1.0.1.0.
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
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.
No comments:
Post a Comment