Wednesday, December 19, 2007
After correcting my dbhome not found problem, I now encounter a “VER10LIST=10 is not an identifier” error when executing the dbstart script. Found Metalink Note 466241.1 explaining the necessary modification to the $ORACLE_HOME/bin/dbstart script.
At or near line 87, you need to modify the code from this:
export VER10LIST =`$ORACLE_HOME_LISTNER/bin/…`
The script is executing using the Bourne shell and the syntax for setting an environment variable is:
After fixing the above problem, the next error encountered is “`COUNT=$’ unexpected” at or near line 259. This error is also resolved with a modification listed in Metalink Note 466241.1.
COUNT=`expr $COUNT + 1`
Thursday, September 13, 2007
I subscribe to the Hotsos Monthly Newsletter, available to those who register for a free account at Hotsos.
In the most recent newsletter there is a case study article about using histograms to resolve a performance problem. I haven’t had much opportunity to use histograms so I discovered you can specify the column name and set the bucket size in the method_opt parameter in DBMS_STATS package.
Below is the example from the article itself.
ownname => ‘M’,
tabname => ‘WFA’,
method_opt =>’FOR COLUMNS PROCESSNAME SIZE 12, ESCROLE SIZE 5, ASSIGNSTATUS SIZE 7′);
Due to my limited experience with this topic, it is unclear to me why those specific number of buckets were picked for each column. Was it arbitrary or was there an educated reason. Based on the author’s data distribution analysis, I thought it correlated to the number of distinct values, but that does not appear to be the case with the ESCROLE and ASSIGNSTATUS columns. I’ll add that to the next layer of the histogram onion to be peeled.
Anyway, I found the case study worth reading and thought I would share. Might come in handy someday soon.
Oracle9i Database Performance Tuning Guide and Reference Release 2 (9.2) – Using Histograms
Wolfgang Breitling Hotsos Symposium Papers/Presentations regarding histograms