Enterprise Manager 12c introduced a lot of functionality around cloning Oracle databases and refreshing the data once it was cloned. You can see some of the earlier material I have posted on this area in the following posts:
This is the second of the two posts I wanted to copy from Dave Wolf’s web site. As I mentioned in the first of these two posts, Dave is a colleague of mine who used to own the DBLM area as far as the Enterprise Manager product management team is concerned. However, he has moved to another area in Oracle and I have inherited his responsibilities for change management, compliance management and configuration management, so I want to make sure this material remains available. This post was originally written in April, 2015, and relates to the STIG compliance standards for Oracle Database 11gR2. I’ll be updating this material with another blog in the next month or so with information on the latest STIG compliance standards, so stayed tuned for that! But here’s Dave’s earlier post:
A tweet from Connor McDonald earlier on today reminded me of a problem I managed to pre-empt a couple of years ago.
Partitioning is wonderful if done properly but it’s easy to get a little carried away and really foul things up. So company “X” decided they were going to use range/hash composite partitioning and, to minimise contention and (possibly) reduce the indexing overheads, they decided that they would create daily partitions with 1,024 subpartitions.
This, in testing, worked very well, and the idea of daily/1024 didn’t seem too extreme given the huge volume of data they were expecting to handle. There was, however, something they forgot to test; and I can demonstrate this on 12c with an interval/hash partitioned table:
I don’t reblog very often–if ever. However, this blog post from EMC’s Itzik Reich is a jewel. If you are like everyone else in IT and are starting to take an interest in Docker I recommend viewing Itzik’s post!
Containers are huge, that’s not a secret to anyone in the IT industry, customers are testing the waters and looking for many ways to utilize containers technologies, it is also not a secret that the leading vendor in this technology is docker.
I thought this was kind of a cool feature- the ability to send a message to appear to specific or all users in the Cloud Control Console. I have to admit that I used to like a similar feature in Microsoft/MSSQL to send network broadcast messages to desktops that offered one more way to get information to users that they might be less inclined to miss.
There is sliced bread in SQL. You'll find it in the from of window
functions. They are so very important and useful that it's irresponsible
not be understand them and use them.
Read the full post at www.gennick.com/database.
A comparison to sliced bread is a rhetorical device evoking the wonder of some new invention or feature in comparison to what went before. Sliced bread revolutionized the making of lunches and toast for breakfast. It meant so much to harried families that a World War II attempt to ban the slicing of bread to save on resources was opposed by New York City Mayor LaGuardia and lasted a mere 49 days from January 18, 1943 until being rescinded on March 8 that same year.
There is sliced bread in SQL.
Okay, had some good fun yesterday with my free trail for Oracle Cloud service for Database…
This is the first of two posts in the area of compliance management that has been previously published by a colleague of mine, Dave Wolf. Dave has moved to another part of Oracle now, and I’ve inherited some of his reponsibilities as product manager, including change management, compliance management and configuration management, so I wanted to copy his material to my blog so it’s not lost. Thanks Dave, for putting this material together originally!
I was lucky to be granted some Oracle Cloud subscriptions. Today I needed an 126.96.36.199…