Avoiding the Perfect Storm My First Post as a Pythian DBA, hopefully many more to come! (And if you are in the mind of finding a positive career change, the link there at the top is a good read, too! :))
-
-
This is an Apex query and it no longer exists in the environment it once resided in- When I first came across it, the first red flag was the optimizer cost of 109 billion, (yeah, I had to count the numbers a couple times in disbelief…) I was reminded of it when Chet from OracleNerd tweeted about a poorly written Apex query and I had to share. All names and identities have been changed to protect the innocent, (and more likely, the guilty…) Enjoy! UgliestQuery!
-
This Statspack bug is an older one, but I ran into it this week again. The work around is very simple to correct the problem, but its surprising how disconcerting it can be for anyone seeing “unique constraint violated”. Seen in the alert log: Tue Dec 14 09:00:43 2010 Errors in file <dir>/xxxx_j000_xxxx.trc: ORA-12012: error on auto execute of job xxx ORA-00001: unique constraint (PERFSTAT.STATS$MUTEX_SLEEP_PK) violated ORA-06512: at “PERFSTAT.STATSPACK”, line 5264 ORA-06512: at “PERFSTAT.STATSPACK”, line 104 ORA-06512: at line 1 ***************************************************** Pulled from the trace file listed above from the alert log: <dir>/xxxx_j000_xxxx.trc Oracle Database 10g Enterprise Edition Release 10.2.0.1.0…