After imported METADATA from 10.2 to 11.2... I found "INVALID" status on objects, then used "utlrp.sql" script:
< lost connection >
In alert log file:
Tue Mar 01 14:19:49 2011
SERVER COMPONENT id=UTLRP_BGN: timestamp=2011-03-01 14:19:49
A frequent query request is that, when you've used MAX or MIN to find the highest, latest or otherwise most favoured row(s), you want the values of the other columns in that row.
Often a suggested answer is the use of a sub-query. But this overlooks one of those less well known features in Oracle SQL, the KEEP clause.
Consider the test case:
create table test_max
March 1, 2011 (Updated March 2, 2011) (Back to the Previous Post in the Series) (Forward to the Next Post in the Series) In the previous blog article in this series, we examined the output generated by one of my programs. Most of that output was centered on the analysis of the time model statistics in Oracle Database [...]
current_listener Syntax : set current_listener
LSNRCTL> set current_listener LISTENER LSNRCTL> show current_listener
displaymode Syntax : set displaymode
LSNRCTL> show displaymode Service display mode is NORMAL LSNRCTL> set displaymode VERBOSE
inbound_connect_timeout Syntax : set inbound_connect_timeout
LSNRCTL> set inound_connect_timeout 0
log_directory Syntax : set log_directory
LSNRCTL> set log_directory
Yes, I love AWR and ASH reports when performing database detective work. They are an essential tool in my performance tuning arsenal, along with the logs, trace files/profiling, Oracle Enterprise Manager and a suite of personally collect queries from over the years. As complex as databases are these days, the more data that I have at hand to backup what I am tuning or reporting on, the more comfortable I am, (OK, so I’m not one for “theories”… )
In a previous post, I have mentioned that I have tried to mine AWR data to confirm an I/O issue occurred around 2:18 PM of Feb 18; however I encountered some issue and instead found out 'sar' was helpful. Today, I worked out the query against AWR tables. The query is as follows:
rem -- Adapted from the scripts written by Karl Arao: http://karlarao.wordpress.com
In my last post When does METHOD_OPT SIZE REPEAT not obey we saw how SIZE REPEAT sometimes appears to know best and creates a FREQUENCY histogram with a different number of buckets than previously specified.
The mechanics of this became clearer while pondering another question that I often ask myself.
How does METHOD_OPT SIZE REPEAT remember the value last specified in order to repeat it?
The Binary Log As said binary log transform multi thread concurrent data/structure modification in to a serialize steps of activity. To handle this, a lock for the binary log—the LOCK_log mutex—is acquired just before the event is written to the binary log and released just after the event has been written. Because all session threads [...]