We did a "real" upgrade to 12c this weekend, where "real" means a production system, as opposed to my laptop, a play VM etc etc :-)
It all went relatively smoothly except for one interesting thing, that I can’t 100% say was caused by the upgrade, but it would appear to be the case.
After the upgrade, our scheduler external jobs started failing. A quick look in the alert log revealed:
Sun Jun 29 09:26:11 2014 ORA-12012: error on auto execute of job "FIRE_SCHED_DAILY" ORA-27496: credential "LOCAL_OS_ACCT" is disabled
So its possible (not proven) that upgrading to 12c might disable credentials. In this particular case, the database went from standalone to a pluggable database.
The remedy was the simply drop and recreate the credential
This is just a temporary note to remind London-based Oracle technical folks that the first free evening event arranged by e-DBA will take place this coming Thursday (3rd July), 6:30 – 9:00 pm.
The event is free and includes breaks for beer and food, but you do have to sign up in advance – places are limited. July
The theme for the evening is “Upgrades”: covering general principles (Jonathan Lewis), 12c specifics (Jason Arneil), and tools (Dominic Giles and James Anthony)
Even if you’re not interested in upgrades, you might want to attend if you haven’t heard about Swingbench and SLOB (Silly Little Oracle Benchmark).
This is just a temporary note to remind London-based Oracle technical folks that the first free evening event arranged by e-DBA will take place this coming Thursday (3rd July), 6:30 – 9:00 pm.
The event is free and includes breaks for beer and food, but you do have to sign up in advance – places are limited. July
The theme for the evening is “Upgrades”: covering general principles (Jonathan Lewis), 12c specifics (Jason Arneil), and tools (Dominic Giles and James Anthony)
Even if you’re not interested in upgrades, you might want to attend if you haven’t heard about Swingbench and SLOB (Silly Little Oracle Benchmark).
The big data phenomenon threatens to break the existing data supply chain (DSC) of many information providers, particularly those whose chains are neither flexible nor scalable and include too many error-prone, manual touch points. - Cognizant
Those of you that have been around Enterprise Manager 12c for some time will recall the joy (for want of a better word!) we used to have configuring BI Publisher to work with Enterprise Manager. For those of you that haven’t looked at it yet, BI Publisher is the replacement for the now deprecated Information […]
When I was about 14 or 15 years old I had this idea that I could create a company selling stuff and make a fair amount of money at it, very easily. What prompted these thoughts were advertisements that attempted to persuade you to buy things that were not at all special or unusual or even good, but the ads claimed that they were in fact fantastic and desirable and having them would significantly improve your life. Often the ads were for really quite rubbish things. It was blatantly obvious that, whilst no factual lies were uttered, the promise of the sun always shining, the big smile on your face, the family joy (with mandatory cute dog) and the inner glow that comes from the product were ludicrous. The product was not going to do that, the whole underlying premise of these adverts were ludicrous lies.
In particular, I was struck by breakfast cereal advertisements.
I made a short post over at ToadWorld about bringing my nephew to my office in Dallas this week for a Young Programmer's camp. He had a great time as far as I could gauge the excitement of a 16 year old boy (errrrrr....young man)! He rocked it out creating several different game knock-offs and got a feel for what it would be like to be a software developer. Fun stuff!
Take a look at the follow-up to my DBMS_APPLICATION_INFO post over at ToadWorld. I discuss how to use DBMS_MONITOR to trace the specific sections of code you registered with DBMS_APPLICATION_INFO.
#555555;">I sometimes want to import AWR repositories from cloned databases to compare performance differences between the databases which should have the same performance characteristics. Unfortunately the clones have the same DBID this importing their AWR repositories into a central AWR repository would be probelematic as I wouldn’t have a way to tell which database the data came from as the DBID is the same. So here is a procedure to change the DBID. THe procedure requires importing the data into the awr_stage user, changing the DBID, then moving the data into the AWR repository:
(see #2970a6;" href="http://gavinsoorma.com/2009/07/exporting-and-importing-awr-snapshot-data/">http://gavinsoorma.com/2009/07/exporting-and-importing-awr-snapshot-data/ for info on normal exporting and importing of AWR repositories)
#!/bin/bash
# ps doesn't show real time CPU usage but average - skewed for long running processed
#TOP5=`ps xo pid --sort pcpu | tail -5 | xargs echo | sed -e 's/\s/,/g'`
TOP5=`top -b -d 1 -n 1 | head -12 | tail -5 | awk '{print $1;}' | xargs echo | sed -e 's/\s/,/g'`
sqlplus / as sysdba <<-EOF
set linesize 200 pagesize 999
select spid, s.username, s.program, sql_id, event from v\$session s, v\$process p where s.paddr = p.addr and spid in ($TOP5);
exit
EOF
regards,
Recent comments
3 years 6 weeks ago
3 years 18 weeks ago
3 years 22 weeks ago
3 years 23 weeks ago
3 years 28 weeks ago
3 years 49 weeks ago
4 years 17 weeks ago
4 years 47 weeks ago
5 years 31 weeks ago
5 years 31 weeks ago