I am currently doing a lot of work around the Lifecycle Management Pack in 12c. The pack has changed guise over the previous couple of releases however now it seems to encompass a lot of very very handy tooling.
Clearing problems using emcli is a quick way to remove scores of incidents in 12c, I used this recently to housekeep a 12c implementation which had hundreds of old incidents in it.
Just a quick blog entry, as this caught one of our guys out this morning. When you have a 12c Mutli-tenant environment, common profiles must start with C## in their naming…
Before I start on this weeks 15 minutes I just want to outline my view point on scripting be it, shell, perl or any other language. Personally I’m not really into it and if I count the amount of times that I arrive on a client site to then decipher a 4 page shell script which backs up a database (using RMAN!) I would probably break down in tears. I am not sure how people justify the time for such shell scripting indulgencies, however the real pain is once that person has left the organisation the maintenance of those scripts falls down to everyone else; and no one really knows how it hangs together or how to trouble shoot it. Of course I could read the handy trouble shooting guide that came with it or the associated documentation or just put it into ‘debug’ mode…..I think you get the point. If you want to save someone 15 minutes in the future then find an alternative to the ‘we could just right a quick script’ option.
Following on from the blog post a couple of weeks ago I came across an interesting way to supress alerts coming out of particular database targets. This was the result of an Oracle SR and although the resolution detailed provides the required result it didn’t really resolve the original question, but I will come onto that.