Tasks that are performed via jobs in the database will be double accounted in the system time model that has been introduced with Oracle 10g.
So if you execute significant workload via DBMS_JOB or DBMS_SCHEDULER any system time model related statistic like DB Time, DB CPU etc. that gets recorded for that workload gets double accounted.
This bug is not particularly relevant since your top workloads will still be the same top workloads, because all other statistics (like Elapsed Time, CPU, Buffer Gets etc.) are not affected by the bug.
At the 5th of august, the database machine (half rack) has arrived at VX Company. The machine arrives wrapped (in plastic) on a pallet. Because the whole rack is already assembled, which means all the parts are already in the rack, the machine is quite heavy (600 kilograms I’ve been told). After some pushing, pulling [...]
After many happy months spent sauntering contentedly through the database, I recently came across a curious little bug in SQLDeveloper 1.5.4 where the Triggers on a View are not displayed in the appropriate Tab. Not to worry, it’s about time I upgraded to 2.1.1 anyway. Or so I thought. I should have known – it’s [...]
After enjoying the excellent hospitality of our host here in Pisa (6 courses) we were ready for our second day at YAPCEU 2010 here in sunny Pisa.
Larry’s new catch phrase “My Language is a four letter word” was the ‘Buzz word’ for today. We settled down to some very interesting talks, the highlight [...]
Larry Wall gave another of his unique keynote addresses at the first day of YAPCEU 2010 here in sunny Pisa (yes the place with the tower)
This year was a little diversion from his usual pattern as Larry was assisted by his better half and his demon seed. Larry told us as a language designer [...]
Recently while checking the segment’s size for a particular schema, i noticed a materialized view log (MLOG$_TABLE_NAME) occupying almost 10Gb of space. What is materialized view log? From the Oracle document :- When DML changes are made to master table data, Oracle Database stores rows describing those changes in the materialized view log and then
Welcome to Log Buffer, a weekly review of the database industry. This week’s issue Log Buffer #198 is generously published by Sam DeFilippis, who manages Oracle Notes blogs, with latest postings on Oracle GoldenGate.
As always, if you’d like to host your own issue of Log Buffer, simply reach out to the Log Buffer coordinator.
Please enjoy [...]
Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.I just found out that columns ENQUEUE_ENABLED and DEQUEUE_ENABLED in views DBA_QUEUES, ALL_QUEUES and USER_QUEUES, return a couple of (unnecessary?) leading and trailing blank characters.select name, queue_type, translate(dequeue_enabled, ' ', '.') dequeuefrom dba_queues;NAME
If Logical Mistakes happen, we can address them with the Flashback techniques, introduced in Oracle Database 10g already, even if in an Data Guard Environment. In case of “Flashback Table To Timestamp” or “Flashback Table To Before Drop”, there is nothing special to take into account regarding the Standby Database. It will simply replicate these [...]
August 6, 2010 An ERP mailing list email asked if there was a way to determine which Oracle clients had not been upgraded to the Oracle 126.96.36.199 client - I also recently encountered a request to determine similar information about the Oracle client versions of potential sessions, so I thought it might be fun to develop a [...]