In case you haven’t noticed it – and chances are you haven’t noticed because I just created it! – I’ve added a new page called “Tips and Techniques” to the website. It’s where I keep a random collection of odd items I’ve come across that might be of interest yet don’t deserve a full blog post. It’s sort of like a FAQ list, but not necessarily with the “F”.
You can reach it either via (more...)
This is an interesting point that came up recently, where someone had a DBaaS environment running on an Exadata system for a couple of months, with no issues. It has recently started to return errors on the Database Cloud Self Service portal in the “Placement Algorithm” region:
Constraint : Number Of Databases
Current Resource Usage: 18
Total Resource Available: 10
Maximum Limit Defined: 10
Requested Value: 1
Total Resource that can be used: 10
In the past few posts, I’ve covered setting up PDBaaS, using the Self Service portal with PDBaaS, setting up Schema as a Service, and using the Self Service Portal with Schema as a Service, all of these using Enterprise Manager Cloud Control 12c release 184.108.40.206. Now I want to move on to an area where […]
In a previous blog post, I covered setting up Schema as a Service for schema level consolidation. In this post I’m going to cover how to use the Self Service Portal with Schema as a Service in EM 220.127.116.11. Just as it was in my posting on using the Self Service Portal with DBaaS, our […]
Schema as a Service provides database consolidation by allowing administrators to host multiple application schemas within a single database. This offers Database as a Service to possibly hundreds of application users without creating database sprawl. Users can perform day-to-day actions like provisioning, monitoring, and backup, all from a single Self Service console. Schema as a […]
Regularly I create VM's for courses as a 'Virtual Course Environment'. Earlier I did an install of Oracle Enterprise Manager 12c. But now there was a request for an integrated BI Publisher install.
Having an OEM12c install, the integration with BI Publisher with OEM12c is pretty straightforward. The install guide (more...)
Now that Oracle Enterprise Manager Cloud Control 12c Release 3 (aka EM12cR3!) has been out for a few weeks, I decided to brave it and upgrade our Production stack today. In this post, I’ll be upgrading an EM12cR2 (18.104.22.168) installation which consists of two OMSes, running (more...)
Enterprise Manager Oracle Management Server (OMS) installations generate huge amounts of log and trace files under the covers these days, and although the logs are rotated out-of-the-box, they’re not automatically deleted. Over time (as I was reminded again today ), these logs can amount to a large portion of your (more...)
Original Post can be viewed at Upgrade Enterprise Manager Cloud Control 22.214.171.124 to 126.96.36.199
Oracle released 188.8.131.52 Enterprise Manager few days back and have released it for most of platforms. You can directly upgrade Enterprise Manager Cloud Control 12c Release 1 (184.108.40.206) [with or without Bundle Patch 1] to 220.127.116.11 There are no pre patches required for this. But this upgrade requires considerable downtime. Oracle has termed this upgrade [...]
In order to meet the minimum security requirements, the SYSTEM user use must be restricted, only the actual DBA must have access to it. Other users requiring access to Enterprise Manager to monitor and "view" must be granted especific minimum privileges.
The SELECT_CATALOG_ROLE and the CONNECT
roles are good enough to see most of the E.M. contents, but when trying to access the Tablespaces page from Enterprise Manager
error shows up.
When tracing I discovered the query used to fill up the Tablespaces Page:SELECT /*+first_rows */ d.tablespace_name, NVL(a.bytes / 1024 / 1024, 0), DECODE(d. (more...)
I was recently refreshing a test database with production data (using datapump if anyone cares) and had forgotten to check the tablespace sizes between prod and test. During the load, I obviously ran out of space. A quick check in prod showed I needed 4GB of space. The test tablespace was set to grow to 2GB max. To add space, I performed a simple command to add the space.
ALTER DATABASE DATAFILE '/u01/oracle/data01/blah.dbf' RESIZE 8GB;
I resumed the datapump and went on my merry way. A few minutes later I received an email from Grid Control that the tablespace (more...)