This is just a quick post to note that I’ve corrected my blog on Storage Indexes here, after a follow up blog from Kerry Osborne indicating an error on my part.
As of 10.2, Oracle supplies two scripts that enable you to extract and load AWR data into another database (even one already running AWR snapshots). You can even take the AWR data from a 10.2 database on Solaris and load it into an 11.2 database on Windows XP (other variations may work…but these are the two versions I have handy). I also took 11.2 database on Linux and loaded it to the Windows database
One of the tasks that I was involved in was 700GB database emergency cloning for an important functional issue troubleshooting. It was 10.2.0.5 (10GR2) 64 Bit database on Linux. To make a long story short I gave the DUPLICATE command a try. I used the comand in this post to start the process. After 4h of the restore process I was horrified (you know how it is to work under time and management pressure) at seeing the following errors
I’m very excited to welcome yet another fellow Oakie to Pythian — Daniel Fink has recently joined us in Denver. In the last couple weeks, we have enjoyed having Dan at our Headquarters in Ottawa.
Welcome to Log Buffer, the weekly roundup of database industry news. We’re only a week or so away from Oracle OpenWorld. Everyone is buzzing with activity, promoting their speaking sessions and making last minute plans. For all of you bloggers who will be attending, don’t miss the annual Bloggers Meetup, announced recently by Alex Gorbachev. “Count yourself in” if you’ll be joining the gang so that accurate attendee numbers can be provided to Jillian’s to ensure everyone is well fed and watered ;)
Welcome to the third installment of a series describing the Oracle Exadata platform. In part 1 we talked about hardware components, and in part 2 went on to discuss software. We now move on to how these components are packaged and licensed.
I’ve just come across an old known issue again today. Was working in the greatest and latest 12.1.2 Oracle e-Business Suite environment. Surprisingly, I face the old issue when WF_LOCAL_ROLES and WF_LOCAL_USER_ROLES objects (among other objects) are set to NOLOGGING mode. The easiest solution is to switch the whole database to FORCE_LOGGING mode:
As part of my preparation for the Exadata OCP Exam, I was reading through the “Oracle® Exadata Storage Server Software User’s Guide”. I found the two famous events in the Exadata world, “db file scattered read” and “db file sequential read” that cause so much confusion, have been renamed to “cell multiblock physical read” and “cell single block physical read” accordingly. Hopefully Oracle will port those events’ names to the RDBMS world as well in version 12c.
As I work on putting together slides, I’d like to remind you all of my Oracle OpenWorld 2010 presentation, a customer case study migrating a complex data warehouse environment to Exadata. I’ll be presenting along with Michael Aldrich of LinkShare and Aiman al-Khammash of Oracle, and focusing on our own experience with Exadata, lessons learned, and advice for others choosing to implement Exadata.
There was a discussion on the OTN General database forum, in which the OP asked creating a table with just one row and restricting that table to just one row. Here is my attempt at it.