Being in the remote administration business is a strange beast and offers lots of challenges, but when you are working for multiple clients sometimes connecting to the servers can be challenging enough. Here’s a little idea that I had this morning that may save someone some grief, so I thought I would jot it down for all to see.
I’m giving a NoSQL overview presentation at MOTS in two days. The conference organizers didn’t ask me for a white paper, so I thought I could get away without writing one. But it turns out that I don’t really feel that I can speak confidently about a topic if I didn’t write the paper. I wonder if other presenters have this addiction too. So I’m posting the paper here for your enjoyment. Feedback is very welcome.
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
Holy mackerel, use.perl.org is shutting down! Pudge is changing jobs and, as his now-previous $workplace was hosting the site, he is temporarily shutting down the site. Breath easy, though, the blog entries are not all going to disappear in a puff of smoke — the site will be put in ‘static’ mode for the time being, and there is the possibility it will reappear somewhere else.
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:
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.
Do you regularly scuba dive in a motley sea of other peeps’ codebase, trying to bring on surgical changes without doing too much collateral b0rking on the code formatting? If so, Steffen Mueller has a nifty trick to share with you. Using Text::FindIndent, he shows how to configure Vim such that it can magically adapts to any indentation policy.
Michigan OakTable Symposium (MOTS) is a unique event taking place just before Oracle OpenWorld — 16-17 September. Why unique? This is the first conference (is it not?) where all presenters are members of OakTable Network, a group that gathers number of like-minded IT professionals with scientific approach to Oracle database technology and to the life in general.